PlaneShift
Development => Development Team Blog => Topic started by: Xillix Queen of Fools on June 30, 2009, 11:42:44 pm
-
XilliX and Lanarel are happy to announce a new BUG DRIVE!!! O--)
We are hoping our enthusiasts will do everything they can to help us verify some pesky bugs so we can get them fixed for you.
Lanarel has comprised the list below and will append notes and guidance where needed.
So, show us what you are made of, put your noses to the grindstone, make something happen!
Bugs that seem dependend on platform and build (install, debug, optimization):
Bug 2075: Problems running/walking in road maps.
Bug 1643: Difficulty climbing ladders.
These bugs could use testing on different systems. Please mention what OS and build you use.
Bug that needs more data to balance correctly:
Bug 2446: Physical stamina drops too quickly.
Mention your character stats (endurance, strength) and who much your char is carrying in inventory
Bugs that may have gone/are not reproduced in a while:
Bug 1194: Crash editing general map
Bug 1048: Crash parsing wrong xml... should work for a stable client. If you can run a stable server, try to reproduce by for example adding wrong xml parts in the database (for items, npcs, quests, ....).
Bug 2129: Server crash when spawning pets after dismissing them
Bug 912: Pet online duration too short. (is this better now if stats are higher?)
Bug 465: Glyph combination research failure. (add examples of things that go wrong).
Bug 333: fall damage and running does not work correctly
For these bugs, comment if you cannot reproduce (we will close the bug if this happens enough). If you can reproduce, also try to give steps so test team can reproduce.
Besides the above mentioned bugs, there are over 500 more open reports. To help with those:
1. Check the comments to see if it is not yet taken care of (or mostly fixed in trunk)
2. Check if it is not a bug due to the newer version of CS. Currently the trunk version in svn is difficult to use for testing unless you have access to updated maps (which are not public). Feel free to look at the many bugs occuring in the binary release or stable.
3. You can help by making bugs reproducible, by adding steps to reproduce. Mention system or character stats if they may be relevant.
4. Feel free to propose fixes. Upload a patch to a pastebin site and add a link. If you cannot fix it yourself but think you found where things are wrong, add that information.
Some bugs may require a private server to test fully soi n case of questions, suggestions, or you think we missed a useful addition to a report, feel free to contact the test team. You can usually find test team members on IRC in #planeshift-build.
Planeshift loves its code-happy player base, WE NEED YOUR HELP!
[Edit: added Lanarels clarificatiions and tidied thread]
-
465 should be an easy fix (a single sort call in the routine that handles spell researching). I'm pretty darn sure it still exists, btw.
-
Ligh makes a very good point.
Some bugs are very hardware dependent, that's why the team needs community help. Even all the testers combined cannot test all the possible (hardware/software) combinations which would create a bug
-
Very good initiative! \\o//
I hope the extended team can help us to shorten the times to the next release. I suggest to keep this thread clean by deleting old posts regarding closed bugs, and update the first post.
-
Also, a small reminder...
In some cases, when the testing team was not able to reproduce a bug, comments have been added asking the reporters for further informations or if they could still reproduce the bug after some time. And it would really help if people who have reported bugs or added comments on bugs could check those bugs from time to time.
Thanks.
-
We're still not seeing a whole lot of activity, we really need the aid people!
-
Tested a bit around like probably others, too, but I don't want to spam the bugtracker with incomplete results. RL that steps between and such, but it's not forgotten...
This is a nice excercise for players and devs to be on the other side and now having to report progress when they don't really want to (players) and having to wait while apparently nothing happens (devs). ;D
Sen
-
http://www.hydlaaplaza.com/flyspray/index.php?do=details&task_id=3017 (http://www.hydlaaplaza.com/flyspray/index.php?do=details&task_id=3017)
The above is for the portal problems, the devs and testers aren't having as much of a problem as many players seem to be.
We need to know what Operating Systems and Hardware people who have this trouble are running.
You should note also important settings like if it happens more or less if you have all maps loaded and such.
Please, if you want these fixed, respond.
Note the exact procedure you went through to produce the buggy results so that we can try to reproduce and fix it.
-
I was not sure what "portal problems" meant so I looked at that list. I noticed the the "puddle" issue is referred to as a portal issue even though I would not think of it as being at a portal itself. I can certainly take some time this weekend and detail what I am seeing near various portals when I play. Just wanted to mention it because some may not be completely clear what that refers to. Is there any benefit to reviewing these sorts of things thrice... once with just that level loaded, once with keep last on, and once with all maps loaded (if the machine can handle it of course)? Are there any other variations on settings or options that count when reviewing these?
-
Im posting here in hope it is at least a bit useful here. (Not sure what Im supposed to post ;) )
#1836 The black hybdr is actually just very dark for me (gone worse in last versions)
#1891 Im surprised that this one needs to be confirmed, I have this since I started playing and seen it on xp (32), linux (32), windows vista (64) and linux (64) and each time I passed there :P
#1796 is the most interesting; I never had the gap between arena and hydlaa until the last stable build I did whenever the !leaf_replaced bug got fixed by Lanarel (when was that....?)
I could post that in the bugtracker along with the system data below, but Im not sure if it wouldn't be just spam there...
For the rest and to do anything useful Im trying to introduce some basic data one could post about hardware and os.
= Hardware =
CPU: Intel E8400
RAM: 4GB
GPU: nVidia Corporation G94 [GeForce 9600 GT] (rev a1)
= OS =
Linux 32Bit (openSuse 11.1)
Graphics driver version: 180.29
Did I forget something?
Sen
-
#1836 - hybdr is the forest junction? Indeed, it is rather unlit, on all systems I played on (Win32 only, but a variety of hardeware).
But much more strange is the fact that already the short piece of road from the north gate to the forest is dark, and that the Laanx statue alone is dark, since a certain date (like when lighter2 was implemented). It seems like both are always in deep shadow.
-
@Sen
Thanks for taking time to check those bugs. I would prefer adding info to the bugs in the bug tracker, so that even if a bug can not be fixed in the near future, we have the information you obtained. For example in bug like 1836, having more hardware information would be good. Many people do not have problems with that forest road, so it would be interesting to see if everyone with the problem had similar hardware.
For bilbous and all 'lazy people' like him: to find the mentioned bugs in the bug tracker, go to http://www.hydlaaplaza.com/flyspray/ , add the number in the box on the top right, and click 'show task'. Or you go to http://www.hydlaaplaza.com/flyspray/index.php?do=details&task_id=1 and replace the 1 with the bug number :)
-
A good dose of figuring out how hard this is would be good for EVERYONE.
-
@ Lanarel:
As I previously replied in the bugtracker, #1836 might also depend on the map loading sequence. And others mentioned the game daytime. Therefore, passing this area once and replying "everything is fine for me" will not be the most useful result; we will need a series of checks from the same tester each...
-
Added a few replies to what I could test. Hope it helps.
-
Barely any movement on the bug drive, I guess bugs aren't that important?
-
Not many bugs I would know how to test with existing chars and a release version, but only with a developer character on a test server...
And as often as I have compiling issues, as hard it is to run one.
-
I've been through all of them twice since yesterday there are many that could just use someone saying "yep, still an issue" from players.
-
I agree that there could be more people replying to this thread or in the bugtracker - hard to believe all are as slow as myself ;)
Despite the lack of result I can provide I already worked (rough guess) 8 hours for this - unfortunately mostly for getting a compiled client to work and messing around with the database to reproduce #1048. Just telling this to make clear that something does happen; though not visible.
Sen
-
Yes we've seen more activity and are appreciative of those who've helped thus far.
I am only talking to those who could help but won't when I give a poke to the readers to add in their time and support.
Cheers for Ligh and Sen and Nykolai and Verden and all the testers!
http://www.hydlaaplaza.com/flyspray/index.php?do=details&task_id=3026 (http://www.hydlaaplaza.com/flyspray/index.php?do=details&task_id=3026) <-- this one needs two guilds to test who's gonna get it?
http://www.hydlaaplaza.com/flyspray/index.php?do=details&task_id=2998 (http://www.hydlaaplaza.com/flyspray/index.php?do=details&task_id=2998) <--- requires player confirmation
http://www.hydlaaplaza.com/flyspray/index.php?do=details&task_id=2816 (http://www.hydlaaplaza.com/flyspray/index.php?do=details&task_id=2816) <--- requires player confirmation
http://www.hydlaaplaza.com/flyspray/index.php?do=details&task_id=2815 (http://www.hydlaaplaza.com/flyspray/index.php?do=details&task_id=2815) <--- requires player confirmation
http://www.hydlaaplaza.com/flyspray/index.php?do=details&task_id=2702 (http://www.hydlaaplaza.com/flyspray/index.php?do=details&task_id=2702) <--- requires player confirmation
http://www.hydlaaplaza.com/flyspray/index.php?do=details&task_id=2689 (http://www.hydlaaplaza.com/flyspray/index.php?do=details&task_id=2689) <--- requires player confirmation
http://www.hydlaaplaza.com/flyspray/index.php?do=details&task_id=2664 (http://www.hydlaaplaza.com/flyspray/index.php?do=details&task_id=2664) <--- requires player confirmation
http://www.hydlaaplaza.com/flyspray/index.php?do=details&task_id=2572 (http://www.hydlaaplaza.com/flyspray/index.php?do=details&task_id=2572)<--- requires player confirmation
http://www.hydlaaplaza.com/flyspray/index.php?do=details&task_id=2386 (http://www.hydlaaplaza.com/flyspray/index.php?do=details&task_id=2386) <--- requires player confirmation
http://www.hydlaaplaza.com/flyspray/index.php?do=details&task_id=2354 (http://www.hydlaaplaza.com/flyspray/index.php?do=details&task_id=2354) <--- requires player confirmation
http://www.hydlaaplaza.com/flyspray/index.php?do=details&task_id=2316 (http://www.hydlaaplaza.com/flyspray/index.php?do=details&task_id=2316) <--- requires player confirmation
http://www.hydlaaplaza.com/flyspray/index.php?do=details&task_id=2277 (http://www.hydlaaplaza.com/flyspray/index.php?do=details&task_id=2277) <--- requires player confirmation
Thanks for the comments so far, you are helping many bugs fixed and closed in the last two days, please keep the information flowing.
-
keep it up these informations can be really helpful to identify the bugs!
-
It appears that most of these bugs are posted by people who do not take email notifications. Would it be out of line to send them a form letter asking for further details after a period of time? I had a look at your latest list (thank you for linking them). I left a comment on the last one as it appeared to ambiguous enough to offer a different interpretation.
I have guilds on both servers so I could possibly assist on the first one but as my membership on both consists of the 5 of me I can't very well be the turncoat. I do know that Tuxide has wanted to be at war with the Odd Cods on ezpc but as a matter of fact I do have opposing forces in that server where I could become a turncoat either a banker or a zombie could trade sides. Another Jerk and Stupid Geek are willing. Hmmm let me check, I might be able to do it all myself if my guild privileges are right, well they are on the same account. Another Jerk does have invite though...I can't tell if the war is ongoing.
-
Also an interesting and quite annoying bug, IMHO: #1792 - Stats&Skills window does not open when trying to get training (http://www.hydlaaplaza.com/flyspray/index.php?do=details&task_id=1792) - I hope the added comment helps confirming and tracing it.
-
Also an interesting and quite annoying bug, IMHO: #1792 - Stats&Skills window does not open when trying to get training (http://www.hydlaaplaza.com/flyspray/index.php?do=details&task_id=1792) - I hope the added comment helps confirming and tracing it.
I added my 2 tria to this one; it's fairly minor but another bug to squish :)
-
I am not even halfway done going through them ALL.
I really thank you all for participating, get friends, call your armies, help help help!
-
Having items that need confirmation listed here helps. Otherise, I will take time to go through the tracker entries when I get some time. Thanks!
-
Bug Drive! :love: 's you.
-
Gogogo!!!!! Xillix, as the ones you have listed get fixed, should we mention it here as well as on the tracker?
-
We'll see oomi, I've been at the review for days and it's poisoning my mind and killing my will to do other work, I sure would like more player support...
-
Items marked as requiring confirmation or check on trunk need to be reviewed by checking out through the CVS and compiling, correct? Just unsure as to the exact meaning of those entries, thanks. Folks, Xillix is not being dramatic in his above post, the amount of work that needs to be done is impressive.
-
I believe, some bugs (especially about icons) can already be fixed just by an approval by a responsible leading art developer and an assignment in a database ... ;)
-
Items marked as requiring confirmation or check on trunk need to be reviewed by checking out through the CVS and compiling, correct? Just unsure as to the exact meaning of those entries, thanks. Folks, Xillix is not being dramatic in his above post, the amount of work that needs to be done is impressive.
Most bugs requiring confirmation or more info, can be done with the binary install client. Just check the comments in the bugs to see if it ONLY happens on trunk :)
With most of the bugs, the problem is not just confirmation (no need to just say 'me too!'), but to figure out in what cases it happens, and then find a way to reproduce. At the point where we have a recipe "Go here, do that, crash" we can figure out where the problem is and find someone to fix it :).
Also thanks to everyone who already added info, found related bugs, etc. I saw that activity (besides everything Xillix and other staff are doing at the moment) has increased a lot.
-
for example it would be useful if someone figured out how to reproduce this: http://www.hydlaaplaza.com/flyspray/index.php?do=details&task_id=2354
the code doesn't show really the problem (and it's difficult to track as this thing works in various quite separate parts of code) yet I've seen it happening some times (mostly on clients crashing during login, but was unable to reproduce by forcing a client quit (SIGKILL kill -9) or other means to terminate it during loading)
-
Yes best practice is to tell your hardware
confirm bug
produce precise instructions on how to reproduce it (meaning how someone on test team would make it happen)
For the "investigate this on trunk" bugs that's a check to see if the bug persists for you in the experimental version of PS.
-
Kill kill kill!
(http://z.about.com/d/paranormal/1/0/9/T/giant_bugs.jpg)
Before it is too late.
-
http://www.hydlaaplaza.com/flyspray/index.php?do=details&task_id=2446 <---------- Community to the rescue.
Thanks to everyone so far who helped out.
Please folks this needs to broaden out, we need more support from more people, right now only a handful have even lifted a finger to help out.
http://www.hydlaaplaza.com/flyspray/index.php?do=details&task_id=2977 <---------- Community to the rescue.
-
I spent about 40 minutes on the first one, but couldn't get anything to noticeably happen on 3 different characters. But I have great ping times.
The second one I cannot help out on, but it doesn't surprise me, being Windows. Maybe someone set a drink down on the machine and triggered a bluescreen.
Please folks this needs to broaden out, we need more support from more people
Getting a lot of people with different systems to review these and post feedback is key to getting problems worked out. Thanks for posting direct links, Xillix.
-
Verden: thanks for testing, but could you information about your characters to that bug report too?
And could people try with weak characters (i.e., a new xacha with 30 STR :) ). If there really still is a problem with starting characters not being able to walk for more than a minute, it needs to be changed.
-
Lanarel - just what I did (custom created Lemur: STR = 22, END = 17 ~ myastenia): I could walk this char almost twice along the Tutorial parcours.
-
Arguing about rp vs pl is far less effective for the good of Planeshift than helping here. Come on folks, show the love!
-
I created 12 new characters using the Quick setup option, making them all Street Warriors and then ran each for 10 seconds to try and establish a baseline. I will try to check other actions across all of them, as I understand running is not the only problem. But thats it for today, thanks.
-
Verden: sounds like a great test. Check lighs last findings in that bug. Seems that especially weak chars with filled inventory (for his weak one 5 ore or so I guess) get exhausted pretty fast. A few more data about that (so not only empty inventory) would be perfect.
-
My starting assumption was that Quick Setup characters maybe don't have the problem. Of course to really check it, I think you would need 72 characters LOL. If anyone can envision short tests that can be used to compare all of these characters for other actions, that would help. I suppose the next thing to do would be to get timings for all of them with filled inventories. Then test all with empty and filled inventories when fighting a rat to the death. Then check zoning across instances with empty and full inventories. Oh god... kill me now.
I am also admittedly not completely fluent with searching the tracker, my apologies if any of my entries are duplicates.
-
This keeps getting supplanted by low consequence discussions.
We still need more active help.
-
Advertize rewards, Xillix... :sorcerer: -- Ah, no second Xiosiamas. :surrender:
__
Question: On a system with ATI Radeon 9250 and Catalyst 6.x (newer versions don't support 9250 anymore), I have issues colliding with the geometry, e.g. while walking into a ladder, the rendering speed drops to a few seconds per frame.
Is this related to ladder climbing issues at all? Is this related to !leaf issues instead? Is there any other issue related enough? Or is this worth a whole separate issue?
-
Ligh: yes, probably related to the ladder climbing problem.
-
With some help from the community we closed many bugs last week, however, over 400 remain!
We're working to get a better working trunk so more of you can help, but we still need a lot of bugs confirmed.
Please cut the idle chatter and help us out here.
-
Advertize rewards, Xillix... :sorcerer: -- Ah, no second Xiosiamas. :surrender:
__
Question: On a system with ATI Radeon 9250 and Catalyst 6.x (newer versions don't support 9250 anymore), I have issues colliding with the geometry, e.g. while walking into a ladder, the rendering speed drops to a few seconds per frame.
Is this related to ladder climbing issues at all? Is this related to !leaf issues instead? Is there any other issue related enough? Or is this worth a whole separate issue?
Ligh, I am using the same card, but with the Mesa driver since Catalyst 6.x doesn't work with the latest Xorg. I don't think I have this issue, though I do have endless !leaf problems and also ladder climbing issues. How do I find out my FPS in PlaneShift?
Might it be worth compiling a list of which which bugs plague which combination of OS/Card/driver? There are probably trends. Doing it on a per-bug basis we might be missing the overall picture.
Xarthen
-
It might be worth it, sure.
-
Ligh, I am using the same card, but with the Mesa driver since Catalyst 6.x doesn't work with the latest Xorg.
I play under Windows XP Pro SP3.
How do I find out my FPS in PlaneShift?
You may need to start the client with parameter "-plugin=bugplug:iBugPlug". I am not sure if the release client has it enabled.
-
I appear to only get emailed notifications when a bug report is closed. That sound right?
And I just, just found how to click your tracker user name and look at my notifications. Thanks for feedback, sorry for dupes.
Later: Started getting email notifications of changes, thank you.
-
Still need help without player support we're going to lose steam here!
-
About the flyspray notifications: due to a bug in flyspray, instead of making them less optional, they were disabled for a week. It should be corrected now. This could be the reason you only got an email for the closing of the bug :). Also, on you preferences page (click your username, top left), you can select (up to a point) for which you want to get notifications. And chose what columns you want for example.
Keep the info on the bugs coming! Many bugs already got information added, sometimes making us find bugs that were lost a bit. It is one of the reasons we (test team and devs from different departments) were able to close 87 bugs last week! Another good example is the stamina bug, where the info given by Sen, Ligh and Verden was enough for Xordan to see where something went wrong. It should become much less of a pain to walk around with a new weak character carrying 5 ores for 30 seconds and then having to rest :)
-
Speaking of bug notifications, I got one recently for bug 2090 (http://www.hydlaaplaza.com/flyspray/index.php?do=details&task_id=2090) which I apparently commented on at one point but was unable to look at it to refresh my memory due to it being hidden. It isn't a big deal as it was a closure notification but perhaps hidden bugs ought to notify no further than that they are being hidden to people unable to view them. It was kind of useless for the tracker to notify it was closed when I could not look at it. I suppose that might be a limitation of the software though.
-
Thanks for checking those notifications. Glad the information is helping.
-
http://www.hydlaaplaza.com/flyspray/index.php?do=details&task_id=3030 <--- players needed.
-
Most people who play the game don't read forums. You want the full support of the playerbase, have GMs put up posters ingame, OOC be damned.
-
UtM makes a good point. I should add somewhere along the way here, that sometimes my cognition (I wuz really tired) is off when I am thinking about the game and how it should work, sorry for any unnecessary reports on the tracker. But thank you for the feedback everyone.
-
OOC be damned is really not as helpful as people might think, but thanks for the thoughts.
We've closed more bugs than were opened the release and are now making a huge dent in legacy bugs.
Everyone who wants to "have a say" in how things will go moving forward, needs to put the discussions aside and focus on this thread.
-
You could limit the OOC aspect by having gms wander around in bug skins with bug numbers as names. The IC story could be it is a cruel joke by a chaotic god and they only disappear once the bug is closed. GM priests might suggest arcane rituals corresponding with tests of the bug details that might serve to dispel these critters. It is a bit of a stretch but it might catch on or at least amuse a few people. You don't even need anyone to play the bugs just position them near places where the bugs might occur and make them impervious. You could also make them annoying by frequently vocalising nonsense in main chat.
-
:offtopic: I like prolix's suggestion, though would use simply worldshouts to reach players not reading the forums :P
-
I love the suggestion Prolix... I'll try to get on next week to help with the bug drive. I should have some free time then to dedicate to this.
-
back to the bugs, and in order to avoid spamming the bug-tracker:
#3054: Weltall suggested this might be a duplicate of #1307,
indeed it seems that way, intel mac os 10.5.7 running /stable has Hall of Mirror
effects not just out of the sewer behind Kada Els but also exiting laanx dungeon.
The sewer exit still lets you fall in a hole, or a couple of meters into the map below,
when exiting without jumping over the border. Laanx dungeon exit is always a hole.
-
Don't fear spamming the bug tracker. I sure as hell don't
-
Laanx dungeon exit is fixed \\o//
-
@player_of_games: please use the bug tracker. In here, things may get overlooked. In the bug tracker, at least it will be where it belongs if someone finds it :). Also, test team and devs are really active in the bug tracker lately, so chances that things are unseen are small.
In general, don't be afraid to add bugs to the bug tracker, as long as you are not upset if we close them :). Reasons we might close reports for bugs that you are sure happen, are mostly that it is already fixed, but not in game. We will find a nicer way to archive those bugs some time, but for now they will be closed as fixed. Also if we ask for more information when we can not reproduce, please provide it, or we may close the report after some time.
Anyway, thanks again for all the help!
Oh, and I almost forgot the most important thing: Xordan fixed bug 1796 (and its 100 duplicates). O--)\\o// \\o// \\o// O--) This means next release with new maps, the portal problems will be gone (not only the one at laanx dungeon exit)!
p.s. I will be gone for a week, but the rest of the test team with help from the devs will keep a look on the bugs.
-
Bug drive continues!
With the help of many reporters, we have been able to close 67 bugs last week \\o//.
Thanks again and, please, keep the information coming!
-
I spent an hour or two looking at the code trying to find the /away code so I could make a specific suggestion about http://hydlaaplaza.com/flyspray/index.php?do=details&task_id=913 but I didn't get very far. Surely it wouldn't be too hard to code in an exception for the auto-responder if it could only be located somewhere ;)
-
It seems that many, many bugs are meeting their just deserts. Keep squashing em!
/me hands out a few pairs of nice stompin' boots
-
Stomp away.
http://www.youtube.com/watch?v=ULAAuq-kyRA (http://www.youtube.com/watch?v=ULAAuq-kyRA)
-
I'm on irc now looking for direction as to how best to help out. I'll be around for just over 2 hours if there is anything I can do to help. (#planeshift-build)
-
All unconfirmed is a good place anyone can help.
All ready to test are good to test.
This is still going on and still needs your help.
-
We still need some help here:
Bug #1264 (http://www.hydlaaplaza.com/flyspray/index.php?string=shortcut+resize&project=2&search_name=&search_in_comments=1&search_in_details=1&search_for_all=1&field6%5B0%5D=&field4%5B0%5D=&field2%5B0%5D=&field1%5B0%5D=&field7%5B0%5D=&status%5B0%5D=open&percent%5B0%5D=&opened=&dev=&closed=&changedfrom=&changedto=&openedfrom=&openedto=&closedfrom=&closedto=&sort=asc&order=private&do=details&task_id=1264): a glitch with the shortcuts window bar disappearing when one clicks 'Done' in a shortcut.
Does anybody still have this? If yes, please provide information about it on the bug tracker.
If you used to have it but do not anymore, put a comment as well.
Thanks :)
-
I have never experienced that... but I'd blame either the graphic driver or some logic in the button refreshing routine. Might as well be due to a 1-column vertical layout; mine is multi-column horizontal.
-
Hello
After it is clear that... hmmm... the borg are responsible for this problem.. ::| ... I just wanted to say that I was, like LigH, not able to reproduce the problem. I tried to mess around in the configuration files and the gui itself, but everything reacted as expected. Maybe its more graphics card / driver related issue (NVidia in linux here)
Sen
#edit# (There was a post deleted to which I answered...)