Skipped rendering frame because gfx device is in invalid state (device lost) [SERIOUS ISSUE] - Rust

The console repeats this message over and over. I can barely play the game because it's running at 10 FPS and I know the cause of this drop in FPS is directly related to the messaged being constantly relayed in the console. I've scowered Google for a solution to this issue, but I haven't found a fix. Is anyone else having this issue? Does anyone know of a fix? I heard it may have something to do with sound card drivers? I really have no clue. Any help would be greatly appreciated. Will provide more information if needed.

Post your specs, please.

I get the same thing in my console, but i'm running 110% fine.

same message when alt-tabing out of the game, no perfomance issues though

Config.cfg [QUOTE]grass.on False grass.forceredraw False grass.displacement False grass.disp_trail_seconds 0 grass.shadowcast False grass.shadowreceive False gfx.ssaa False gfx.bloom False gfx.grain False gfx.ssao False gfx.shafts False gfx.tonemap False input.mousespeed 5 input.flipy False input.bind Left A None input.bind Right D None input.bind Up W None input.bind Down S None input.bind Jump Space None input.bind Duck LeftControl None input.bind Sprint LeftShift None input.bind Fire Mouse0 None input.bind AltFire Mouse1 None input.bind Reload R None input.bind Use E None input.bind Inventory Tab None input.bind Flashlight F None input.bind Laser G None input.bind Voice V None input.bind Chat Return T render.level 0.006478675 render.vsync False render.af 0 render.aa 0 env.clouds False sound.music 0.2940379 sound.volume 0.3147654 footsteps.quality 0 cursor.lock True cursor.recenter False cursor.uncenter False censor.nudity False terrain.idleinterval 0 [/QUOTE]

I had this message appear multiple times before. It was whenever I would alt-tab the message would scroll. When I was in-game with console open, I would never see it, but I would quickly alt-tab, and it would appear.

Processor Intel(R) Core(TM) i7-4700MQ CPU @ 2.40GHz, 2394 Mhz, 4 Core(s), 8 Logical Processor(s) System Type x64-based PC Running Windows 8 [editline]3rd February 2014[/editline] [QUOTE=elixwhitetail;43772070]Post your specs, please.[/QUOTE] Posted specs

Video card and RAM, please. That's just your CPU and your posts show your OS.

I heard that alt-tabbing was related to this message, however, this message spams my console even while I play the game. [editline]3rd February 2014[/editline] [QUOTE=elixwhitetail;43772150]Video card and RAM, please. That's just your CPU and your posts show your OS.[/QUOTE] 8.0GB PC3-12800 DDR3 SDRAM 1600 MHz 2GB NVIDIA GeForce GT745M Discrete Graphics [editline]3rd February 2014[/editline] Intel HD Graphics 4600

I had to Laugh when I read Intel HD Graphics, must not be a techy, that doesnt even come into play with a Discrete card.. Anyhow Your System speccs well exceed this game I would lean towards updating Drivers Nvidia, Realtek, and chipset driver from intel... Dont just update them remove old ones before installing new ones dont reply on the installer to do that correctly for the nVidia and realtek... I would urge others running Windows 8 to post if they had any wierd problems, I build PC's for a living and have seen windows 8.1 update screw up many computers programs and requiring reinstalls... [B][I]If you recently updated to Windows 8.1 you should know that 8.1 is not a standard update every hardware manufacturer had to create drivers specific to windows 8.1[/I][/B]

Use the Nvidia panel to make sure Rust is using your discrete card and not the Intel HD. Rust and Intel integrated graphics get along about as well as water beds and hedgehog cannons.

[QUOTE=Jeddak;43772330]I had to Laugh when I read Intel HD Graphics, must not be a techy, that doesnt even come into play with a Discrete card.. Anyhow Your System speccs well exceed this game I would lean towards updating Drivers Nvidia, Realtek, and chipset driver from intel... Dont just update them remove old ones before installing new ones dont reply on the installer to do that correctly for the nVidia and realtek...[/QUOTE] This laptop is relatively new and I'm almost positive everything is up to date, but I'll still check. [editline]3rd February 2014[/editline] [QUOTE=elixwhitetail;43772364]Use the Nvidia panel to make sure Rust is using your discrete card and not the Intel HD. Rust and Intel integrated graphics get along about as well as water beds and hedgehog cannons.[/QUOTE] Do you mind elaborating on how to do this?

New computers Never have the latest drivers, the disks that come with them are almost always 6+ months old... Read Previous post regarding windows 8.1

[QUOTE=Jeddak;43772423]New computers Never have the latest drivers, the disks that come with them are almost always 6+ months old... Read Previous post regarding windows 8.1[/QUOTE] I'm running Windows 8.

[QUOTE=Jeddak;43772330]I had to Laugh when I read Intel HD Graphics, must not be a techy, that doesnt even come into play with a Discrete card..[/QUOTE] That's a bit ignorant, the integrated definitely matters, not so much the model but the fact that it may default to integrated. Like elix said. Not relative to your problem but it bothers me slightly, turn vsync on. [editline]4th February 2014[/editline] And no vsync doesn't cause frame drops, that is a myth. Think of it as a little man in your GPU that holds the next image to be displayed, his name is back buffer. If this little man is patient and has vsync turned on he waits until your monitor is refreshed before handing the next image over to his good friend frame buffer, frame buffer then draws the image to the screen. Now, if back buffer is not patient and has vsync turned off he will force all of the images on frame buffer as fast as he possibly can, frame buffer can't possibly keep up with this so he gets angry at back buffer and starts tearing up images to spite him. Because of this their once beautiful friendship turns into a hatred for one another. So next time you go to turn off vsync, think to yourself, do I want to destroy a beautiful friendship? Edit: oh it's a server.

Simple fix for this is to add -batchmode to the server's shortcut. ie: Right-Click server.exe and make a shortcut. Right-click the shortcut and select properties. In the Target box add -batchmode like this: ../rust_server.exe -batchmode If your path includes "quotes", put -batchmode outside the last quote after one space. "..\rust_server.exe" -batchmode

[QUOTE=Celsus;43772668]Simple fix for this is to add -batchmode to the server's shortcut. ie: Right-Click server shortcut, select properties. In the Target box add -batchmode like this: ...rust_server.exe -batchmode If your path includes "quotes", put -batchmode outside the last quote after one space.[/QUOTE] How exactly do I do this?

...

[QUOTE=Celsus;43772707]I edited the message above to add the second example. The entire first comment I made is a step by step guide to doing this.[/QUOTE] Where is server shortcut?

...

[QUOTE=Celsus;43772734]I see. Right-click server.exe and make a shortcut. Then right-click the shortcut to get at the target spot I mentioned in message 1.[/QUOTE] I'm sorry for my inability to comprehend, but where exactly is "server.exe"? What are you referring to?

[QUOTE=Celsus;43772668]Simple fix for this is to add -batchmode to the server's shortcut. ie: Right-Click server.exe and make a shortcut. Right-click the shortcut and select properties. In the Target box add -batchmode like this: ../rust_server.exe -batchmode If your path includes "quotes", put -batchmode outside the last quote after one space. "..\rust_server.exe" -batchmode[/QUOTE] This thread is not for getting better performance running a local copy of the leaked server. Read before post.