Author Topic: bug  (Read 3600 times)

ceres

  • Wayfarer
  • *
  • Posts: 6
    • View Profile
bug
« on: October 25, 2005, 08:09:24 pm »
I\'m not sure I\'m supposed to post this here, but a post of Moogle seems to redirect us here.

The game just crashed with this error :

psclient.bin: coreanimation.cpp:240: void CalCoreAnimation::getPose(float, std::vector >&) const:  l\'assertion ? time >= 0.0f && \"time must be > 0\" ? a ?chou?.

I have used xordan latest installer to install the client version I\'m currently using.

Karosh_Steinkatz

  • Hydlaa Citizen
  • *
  • Posts: 486
    • View Profile
(No subject)
« Reply #1 on: October 25, 2005, 08:18:35 pm »
Did you run the updater before you launched the client? Without some more info I\'d say at least one model was not uptodate and caused Cal3D to freak out. I don\'t think Xordan would release a client with such a bug in the source ;)
Try to give some more lines of output (running the client with -verbose gives more info).


Back to Planeshift again \\o/

Xanthan

  • Prospects
  • Hydlaa Citizen
  • *
  • Posts: 224
    • View Profile
(No subject)
« Reply #2 on: October 26, 2005, 12:23:10 am »
I\'ve been getting this as well, and have made sure to update before
running again when it occurs.  Here\'s the output from psclient -verbose on a typical occurance.  Usually I get bounced out immediately on entering the game:


planeshift.application.client:
  PSLoader: step 5: success

BuildAppearance
:
  Failed to set trait   mesh=\"0\" mat=\"0\" tex=\"0\" shader=\"0.6,0.6,0.6\"/> for mesh.
  Failed to set trait   mesh=\"0\" mat=\"0\" tex=\"0\" shader=\"0.7,0,0\"/> for mesh.
psclient.bin: coreanimation.cpp:240: void CalCoreAnimation::getPose(float, std::vector >&) const: Assertion `time >= 0.0f && \"time must be > 0\"\' failed.
Aborted


-------------------------------------------------------------
I note that no character models appear to have hair textures since the version upgrade.

Xanthan

  • Prospects
  • Hydlaa Citizen
  • *
  • Posts: 224
    • View Profile
(No subject)
« Reply #3 on: October 26, 2005, 01:58:54 am »
On further experimentation, I\'ve noticed that this bug always occurs when entering one particular place:  The corridor in the arena that runs out radially from the centre, and has the Dlayo Gladiator on the stairs at the inside end.

deusieeee

  • Wayfarer
  • *
  • Posts: 3
    • View Profile
(No subject)
« Reply #4 on: October 26, 2005, 04:30:47 am »
im experiencing the same problem, it is also happening to me in the arena.  I have noticed it happens on stairs, not sure if any particular stairs, i think it has happened on a number of them.  I\'ll pay more attention to what stairs i am on from now on.

edit: also not sure if it is a klyros issue either, but thats the race i am.
« Last Edit: October 26, 2005, 04:32:26 am by deusieeee »

ceres

  • Wayfarer
  • *
  • Posts: 6
    • View Profile
(No subject)
« Reply #5 on: October 26, 2005, 08:45:32 am »
I am playing an ylian and it happened to me in the sewers. I had updated before.

With the same configuration(having used xordan installer, 3.012-r2), something that seems to me more serious also it doesn\'t crash the game : strong monsters don\'t seem to notice me. I played for about half an hour and I was just attacked by rats and 1 or 2 times by gobbles. Worse, I have never been attacked by monster I have been attacking. My character not being that strong before the update(I found fighting 3 gobbles in a row difficult) such a change in the difficulty of the game is weird.

Also, although I\'m not sure if it is linked to it or not, I saw no other player in the sewers, and very few in the plaza, which is weird since 34 players are online.

One more bug : My status isn\'t updated, I always appear at 100%HP even though I\'m injured. The output of the client gives a lot of

\"Skipping out of date StatDR packet for \'Self\', version not 255\"
where N is incremented each time.

I guess it must be related?

Anyway, what is the appropriate place to report bugs?
« Last Edit: October 26, 2005, 07:15:08 pm by ceres »

Godfrey

  • Hydlaa Resident
  • *
  • Posts: 69
    • View Profile
(No subject)
« Reply #6 on: October 26, 2005, 07:37:46 pm »
Quote
Originally posted by ceres
strong monsters don\'t seem to notice me. I played for about half an hour and I was just attacked by rats and 1 or 2 times by gobbles. Worse, I have never been attacked by monster I have been attacking.


I saw that once last night; when the rats bit me, I didn\'t take damage, and bigger things never struck at me.  I was going to report it, but when I exited and came back into the game, suddenly they were attacking and doing damage, so I thought it was just a one-time glitch.

Apparently not.

leoni

  • Wayfarer
  • *
  • Posts: 1
    • View Profile
(No subject)
« Reply #7 on: October 26, 2005, 11:48:35 pm »
For me it\'s the same bug.
It also happens in the arena on the stairs. The game crashes everytime I get into the game. For a secend i can see my character than the game crashes with the same error
psclient.bin: coreanimation.cpp:240: void CalCoreAnimation::getPose(float, std::vector >& const: Assertion `time >= 0.0f && \"time must be > 0\"\' failed.

My character is a diaboli. I think it had nothing to do with the races.

Can someone tell me how I can get back in the game with my character without creating a newone? Please let me know when you have an answer.

Carpe Noctem

  • Wayfarer
  • *
  • Posts: 4
    • View Profile
(No subject)
« Reply #8 on: October 27, 2005, 02:11:00 am »
Same error here, and my race is that of a Stonebreaker. The error is as follows (which everyone has seen so far, but just posting to verify that it is more than a singular incident):
SetDRData
:
  Ignoring DR pkt version 185 for entity Tefusang with version 191.

Skipping out of date StatDR packet for \'Self\', version 3 not 255.
Skipping out of date StatDR packet for \'Self\', version 4 not 255.
Skipping out of date StatDR packet for \'Self\', version 5 not 255.
Skipping out of date StatDR packet for \'Self\', version 6 not 255.
Skipping out of date StatDR packet for \'Self\', version 7 not 255.
Skipping out of date StatDR packet for \'Self\', version 8 not 255.
Skipping out of date StatDR packet for \'Self\', version 9 not 255.
Skipping out of date StatDR packet for \'Self\', version 10 not 255.
Skipping out of date StatDR packet for \'Self\', version 11 not 255.
Skipping out of date StatDR packet for \'Self\', version 12 not 255.
Skipping out of date StatDR packet for \'Self\', version 13 not 255.
Skipping out of date StatDR packet for \'Self\', version 14 not 255.
Skipping out of date StatDR packet for \'Self\', version 15 not 255.
Skipping out of date StatDR packet for \'Self\', version 16 not 255.
Skipping out of date StatDR packet for \'Self\', version 17 not 255.
Skipping out of date StatDR packet for \'Self\', version 18 not 255.
Skipping out of date StatDR packet for \'Self\', version 19 not 255.
Skipping out of date StatDR packet for \'Self\', version 20 not 255.
Skipping out of date StatDR packet for \'Self\', version 21 not 255.
Skipping out of date StatDR packet for \'Self\', version 22 not 255.
Skipping out of date StatDR packet for \'Self\', version 23 not 255.
Skipping out of date StatDR packet for \'Self\', version 25 not 255.
Skipping out of date StatDR packet for \'Self\', version 26 not 255.
Skipping out of date StatDR packet for \'Self\', version 27 not 255.
Skipping out of date StatDR packet for \'Self\', version 28 not 255.
Skipping out of date StatDR packet for \'Self\', version 29 not 255.
Skipping out of date StatDR packet for \'Self\', version 30 not 255.
Skipping out of date StatDR packet for \'Self\', version 31 not 255.
Skipping out of date StatDR packet for \'Self\', version 32 not 255.
Skipping out of date StatDR packet for \'Self\', version 33 not 255.
Skipping out of date StatDR packet for \'Self\', version 34 not 255.
Skipping out of date StatDR packet for \'Self\', version 35 not 255.
Skipping out of date StatDR packet for \'Self\', version 36 not 255.
Skipping out of date StatDR packet for \'Self\', version 37 not 255.
Skipping out of date StatDR packet for \'Self\', version 38 not 255.
psclient.bin: coreanimation.cpp:240: void CalCoreAnimation::getPose(float, std::vector >&) const: Assertion `time >=0.0f && \"time must be > 0\"\' failed.
Aborted

That is the message I am getting with the -verbose output.  I have noticed that something similar is happening in the windows client, but can\'t be sure if it is the same error. Seems to stem from this section of code: SetDRData

Could we please have one of the devs check into this to either verify or disagree with this assumption.

Araye

  • Hydlaa Citizen
  • *
  • Posts: 277
    • View Profile
    • The Enlightened
Same error here
« Reply #9 on: October 27, 2005, 11:20:59 pm »
This happens to me when I\'m in the arena going up or down stairs...
« Last Edit: November 26, 2005, 02:56:55 pm by Araye »

Xordan

  • Crystal Space Developer
  • Forum Addict
  • *
  • Posts: 3845
  • For God and the Empire
    • View Profile
(No subject)
« Reply #10 on: October 28, 2005, 01:17:34 am »
It\'s being worked on. Hopefully it\'ll be fixed soon.

Seytra

  • Forum Addict
  • *
  • Posts: 2052
  • No system can compensate lack of common sense.
    • View Profile
(No subject)
« Reply #11 on: October 28, 2005, 01:27:08 am »
I was told that the bug about the time
Code: [Select]

psclient.bin: coreanimation.cpp:240: void
CalCoreAnimation::getPose(float, std::vectorstd::allocator >& const: Assertion `time >=0.0f &&
\"time must be > 0\"\' failed.

is an issue of cal3d. There also is a proposed fix that however isn\'t in the cal3d version the installer is using. However, it will likely be adapted in an upcoming installer release.

If you compile from source, you can apply that fix yourself:
in cal3d, after download, open cal3d/src/coreanimation.cpp
and replace line 240
Code: [Select]

assert(time >= 0.0f && \"time must be > 0\");

with
Code: [Select]

if(time < 0.0f) time = 0.0f;

and recompile everything.

Edit: 1) disabled smileys and 2) Xordan beat me to it.
« Last Edit: October 28, 2005, 01:30:02 am by Seytra »

stfrn

  • Hydlaa Citizen
  • *
  • Posts: 324
  • the beaver ex-dev :B
    • View Profile
(No subject)
« Reply #12 on: October 28, 2005, 03:22:51 am »
And furthermore, thanks for posting the following:

Quote
Skipping out of date StatDR packet for \'Self\', version 3 not 255.


That showed me what was wrong with the stat counters quite quickly. Next client build should not have that problem. If you are compiling, you can update clientvitals.cpp and try it for yourself.
player -> gm -> dev -> bum

ceres

  • Wayfarer
  • *
  • Posts: 6
    • View Profile
(No subject)
« Reply #13 on: October 28, 2005, 11:02:31 pm »
now, the packet being ignored are the packet for monsters status :
  Ignoring DR pkt version 19 for entity Gobble with version 131.
  Ignoring DR pkt version 20 for entity Gobble with version 131.
  Ignoring DR pkt version 21 for entity Gobble with version 131.
  Ignoring DR pkt version 124 for entity Gobble with version 131.
  Ignoring DR pkt version 125 for entity Gobble with version 131.
  Ignoring DR pkt version 126 for entity Gobble with version 131.
  Ignoring DR pkt version 127 for entity Gobble with version 131.
  Ignoring DR pkt version 128 for entity Gobble with version 131.
  Ignoring DR pkt version 129 for entity Gobble with version 131.
  Ignoring DR pkt version 122 for entity Gobble with version 131.
...
  (not only for Gobbles)

They don\'t appear on my screen anyway.

Another question : Will installer with critical bugs fix be released between the \"main\" release? I tried to compile planeshift to get rid of the \"ignore status packet\" bug, but I haven\'t got that much diskspace ...

Xordan

  • Crystal Space Developer
  • Forum Addict
  • *
  • Posts: 3845
  • For God and the Empire
    • View Profile
(No subject)
« Reply #14 on: October 29, 2005, 01:12:06 am »
Yes, I\'ll probably make a minor update fairly soon once all the critical bugs are fixed.