|
6824 | Medium | | 23.11.2015 | Rigwyn Setson | | VBO OFF causes character creation screen to crash rando ... | | 04.06.2020 | No |
Task Description
The character creation screen will sometimes crash when the facial attribute buttons are clicked if VBO is turned off. ( ie vbo box is not checked ). By default on a fresh install of the 64 bit Linux binary, vbo is off.
Testing machine:
Hardware: Gateway DX4870 -w core i5 processor and included ivybridge hd intel graphics ( 2000 or 2500 I think ) OS: Debian 8 64 bit Ram - 8g
Installed as follows: Installed system-wide as root to /opt with permissions for user:user and chmod 755
To reproduce the problem: delete the ~/.PlaneShift , ~/.crystalspace , and /opt/PlaneShift folders install as root going with all defaults - choose system-wide - choose user:user ( in my case, user was my username ) - choose mode 755
Run /opt/PlaneShift/pslaunch Allow it to update the installation VBO will be disabled by default. Start the program and go into character creation. Choose a ylian or dermorian, pick a name and start clicking the facial attribute arrows repeatedly. It may crash after a single click or after hundreds of clicks. It’s very hit or miss.
Turning VBO ON seems to fix the problem.
( edit: changed version to 0.6.3 - this is for the version available on the download page ( german download mirror ))
|
|
6789 | Medium | | 25.02.2015 | Rigwyn Setson | Davide Vescovini | Cannot loot after will with Tire spell | | 01.04.2016 | No |
Task Description
After killing a mob with the Tire darkway spell, you are not allowed to loot the creature. Tried this on onyx daggers, thunder clacker and wrath rats and vesper arangmas so far.
It looks like this happens when the tire spell drains the mob. If you drain the mob with tire, then finish it with a spell like animate shadow, then you get to loot it. If you weaken it with a spell then then finish it off with tire, you cannot loot it.
If this is expected behaviour, then it might be good to add a line to the output explaining why. ie. "You sucked too much. The X and its posessions have turned to dust."
|
|
6208 | Medium | | 01.11.2013 | Rigwyn Setson | | Museum teleports to instance 403 | | 04.06.2020 | No |
Task Description
When entering the museum, the client is teleported to instance 403
The first time I tried this, I got into the museum and out without a problem. The second time, I tried locking the door first. it was on the second attempt that I went to 403
Not sure if attempting to lock the door did it or if had something to do with the portion of the door clicked on ? ( left side, right side, or crossed swords )
Sarko was able to observe this as I did it. Also, whenever he tried to teleport to me, he would fall though the map.
I did this with character Rhilee. Kull was able to do it too ( with his Kull character )
Time of say was just before 6AM US/Eastern time.
Client I am using is 0.5.9.10 on Ubuntu 13.10 I believe Kull is using windows
Position while standing outside the museum in instance 403 was guildsimple 0.00 -1.40 -5.50, instance: 403
|
|
2695 | Medium | | 20.01.2009 | Rigwyn Setson | | client dies | | 20.01.2009 | No |
Task Description
I have noticed that the client died several times this morning. It could be os specific - i did get the latest kubuntu updates last night - not sure if this is related or not.
the crash has been happening in the arena - i havent played long enough this morning to determine if its specific to the arena or not. When the crash occurs, the application just closes silently. I tried changing resolution from 1024x768 to 800x600 and also tried reducing color depth from 32 to 16 - this didnt help.
The crash happened once when right clicking on a tefusang, and once while running in the arena hall( i was not near a load point or anything )
Reran and captured the following message from the console:
Tue Jan 20 03:18:47 2009, Server report HP but object is not alive DistributeLeafObjects failed: !leaf_replaced
This node contains the following objects:
0: 'effect_label_17' (37.5767,3.68264,-2.63993)-(39.7223,4.49162,-0.431339)
1: 'effect_label_4' (6.41886,11.0433,25.3271)-(9.24347,12.5619,28.2276)
2: 'effect_anchor_basic_107' (-1,-1,-1)-(1,1,1)
3: 'effect_anchor_basic_570' (-1,-1,-1)-(1,1,1)
4: 'effect_label_200' (-2.35332,3.68264,71.5901)-(-0.207658,4.49162,73.7987)
5: 'effect_anchor_basic_571' (-1,-1,-1)-(1,1,1)
6: 'effect_decal_201' (-1.60539,-0.51528,72.0146)-(-0.594613,0.495494,73.0254)
7: 'effect_label_53' (nan,3.85719,11.1512)-(nan,4.15533,12.0955)
8: 'ynnwnm' (nan,1.30452,9.98957)-(nan,3.51141,12.3001)
9: 'weapons#doubleaxe01a' (nan,2.1429,11.3593)-(nan,2.67139,12.0827)
10: 'weapons#doubleaxe01a' (nan,2.34182,11.8921)-(nan,3.07607,12.2479)
11: 'helms#helm02_ynnwnm' (nan,2.9832,11.4521)-(nan,3.38924,11.9379)
Regarding my platform, i'm running a toshiba qosmio g35-av600 -w 1gb ram, 32bit core-duo processor, 2.6.24 kernel (ubuntu), nvidia geforce go 7300 ( driver ver. 169.12 )
will try to collect more useful info.
|