Jump to content

Cryanimation: Command Buffer Overflow


14 replies to this topic

#1 Therion I

    Member

  • PipPipPipPipPip
  • Knight Errant
  • 117 posts
  • LocationHerts, UK

Posted 20 February 2013 - 07:15 AM

Still getting this.

Been happening since the patch on the 9th.

Tried fresh installs and different settings.

Looks to me like some objects are missing or addressed wrong.

#2 Silme

    Member

  • PipPipPip
  • The Blade
  • The Blade
  • 56 posts

Posted 20 February 2013 - 07:19 AM

Also getting this. Was not seeing the error message until I switched from Fullscreen to Full window. Now I see the error, but game's still crashing.

#3 Therion I

    Member

  • PipPipPipPipPip
  • Knight Errant
  • 117 posts
  • LocationHerts, UK

Posted 20 February 2013 - 07:23 AM

View PostSilme, on 20 February 2013 - 07:19 AM, said:

Also getting this. Was not seeing the error message until I switched from Fullscreen to Full window. Now I see the error, but game's still crashing.


Yeah I run full window too.

Logs show things like:

[Error] locomotion-group not found: animations/mechs/stalker/lmg_files/land_to_fwd_fp.lmg
[Error] CryAnimation: no valid character file-format: EngineAssets/Objects/Default.cgf
[Error] CryAnimation: no valid character file-format: EngineAssets/Objects/Default.cgf
[Error] CryAnimation: no valid character file-format: EngineAssets/Objects/Default.cgf
[Error] CryAnimation: no valid character file-format: EngineAssets/Objects/Default.cgf
[Error] CryAnimation: no valid character file-format: EngineAssets/Objects/Default.cgf
[Error] CryAnimation: no valid character file-format: EngineAssets/Objects/Default.cgf


Looks like a missing or incorrectly addressed Stalker animation file.

#4 Silme

    Member

  • PipPipPip
  • The Blade
  • The Blade
  • 56 posts

Posted 20 February 2013 - 07:33 AM

Spoiler

Same thing for me. Possibly also related is the could not free all buffers from CDevBufferMan! ?

Edited by Silme, 20 February 2013 - 07:43 AM.


#5 Therion I

    Member

  • PipPipPipPipPip
  • Knight Errant
  • 117 posts
  • LocationHerts, UK

Posted 20 February 2013 - 07:35 AM

I've resinstalled three times from scratch with two different versions now. No difference.

#6 Therion I

    Member

  • PipPipPipPipPip
  • Knight Errant
  • 117 posts
  • LocationHerts, UK

Posted 20 February 2013 - 07:41 AM

View PostAnaArt, on 20 February 2013 - 07:35 AM, said:

Hi Therion I,

try downloading the object pak from here

http://patcher.mwome...ame/Objects.pak


Thanks, what do I do with it?

#7 Therion I

    Member

  • PipPipPipPipPip
  • Knight Errant
  • 117 posts
  • LocationHerts, UK

Posted 20 February 2013 - 08:02 AM

Do I just shove it in with the other two PAK files? Shouldn't there already be an object.pak in there?

Nevermind, found it in the Game directory. Was looking in the Engine one.

Edited by Therion I, 20 February 2013 - 08:03 AM.


#8 Therion I

    Member

  • PipPipPipPipPip
  • Knight Errant
  • 117 posts
  • LocationHerts, UK

Posted 20 February 2013 - 03:00 PM

Nope, still crashing. What on earth changed on the 9th to cause this? I've been solid since closed beta up till this point.

======== causticvalley is loaded in 8.4 sec ========
[Error] locomotion-group not found: animations/mechs/stalker/lmg_files/land_to_fwd_fp.lmg
[Error] CryAnimation: no valid character file-format: EngineAssets/Objects/Default.cgf
CryAnimation: CommandBuffer overflow!

Still looks like the Stalker animations.

#9 TheLuc

    Member

  • PipPipPipPipPipPipPip
  • The 1 Percent
  • 746 posts

Posted 20 February 2013 - 03:27 PM

same issue too, CryAnimation: CommandBuffer overflow! since trebuchet and new map. 1 game in river city and other in new map and both crash, funny part previous those two games there was trebuchets mechs and game did not crash

#10 Silme

    Member

  • PipPipPip
  • The Blade
  • The Blade
  • 56 posts

Posted 21 February 2013 - 06:25 AM

Downloaded the new objects.pak, also still crashing. Crash came about 5 minutes into my first match of the day, computer had just booted up. Same error message.

#11 LA Smog

    Rookie

  • 1 posts

Posted 24 February 2013 - 03:06 PM

Experiencing the same command buffer overflow issue since the Feb 9th patch. I stopped playing due to this bug, as it was a ~75% chance of happening per match. Came back to play today, try the various fixes, look through the forums and still no joy.

Intel i7-3770K at defaults
nVidia GTX 470 at defaults
Onboard Realtek audio at defaults
Updated to latest nVidia video drivers last night
Deleted shaders without relief
Enabled v-sync without relief

I guess I will have to come back and test once another patch is out to see if there is a change.

Spoiler

Edited by LA Smog, 24 February 2013 - 03:18 PM.


#12 OneQuickSix

    Rookie

  • 2 posts

Posted 28 February 2013 - 05:41 AM

Same here. I haven't played in a LONG time, just got a new 660ti 3gb and everything is smokin' in every other game, and was getting 80-85fps in MWO everything set to high and vsync on. Thought all was great until I got this crash about 5 minutes into the game. Tried again, same thing.

I wish the patches weren't mandatory. :P

#13 PHANTA5M

    Member

  • Pip
  • 12 posts

Posted 02 March 2013 - 03:12 AM

I am also having this problem. I was crashing (program not responding needs to close) 3/5 matches until I switched from fullscreen to full window. Played a few days without crashes, but now I'm frequently crashing with the Cryanimation: Command Buffer Overflow error in full window. So I traded one type of crash for another. Going to try a regular window now.

i7, GTX670 w/ newest (314.07) drivers, Win7 64bit, 6GB ram

#14 Shura Arashi

    Rookie

  • 1 posts

Posted 02 March 2013 - 10:31 AM

Also still getting the error, seems to get worse when i use vsync.

#15 Therion I

    Member

  • PipPipPipPipPip
  • Knight Errant
  • 117 posts
  • LocationHerts, UK

Posted 04 March 2013 - 07:19 AM

Still getting this. Been through support and they seem to have just added it to a list. I don't understand this as it only happened after the 9th Feb patch so whatever was added then is obviously causing this... surely it can be fixed?





4 user(s) are reading this topic

0 members, 4 guests, 0 anonymous users