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.

I don\'t know what all is happening, but I do know that the random windows, and such are still going on. About a week ago, everything was working as usual, then it all started getting laggy, with random windows, and rogues that weren\'t there all of a sudden on top of you, that were hitting you but you were \'too far away to attack\'. I know that thanks to the server problems, that my wife lost out on a dagger and sword that she was selling to another player, but when they clicked \'Accept Trade\' the tria came to her, but the weapons that she was selling to the other player just vanished. She gave the player his tria back, but now is out of the weapons. I understand and accept the version of the game and all, but there has got to be a way to fix it.
Just my thoughts.