• I was wondering if anyone can help with my game ruining issue?
    8 replies, posted
Hello everyone, i have recently built a new pc and the specs are as follows GTX 1060 6GB Ryzen 5 2600x @ 3.8 8GB G.Skill RIPJAWS DDR4 @ 3000mhz (dual chanel) and i also thought i would mention that rust is installed on an SSD RUST IS LITERALLY UNPLAYABLE i get anywhere between 5 and 10 fps on LOWEST SETTINGS and i am aware that my pc is not top of the line, but its not that bad My brother has an i5-4440, gtx1050 and 8GB DDR3 in single Chanel and he gets smooth 60 fps on medium settings. I have exhausted all of the options in my knowledge i would appreciate any help Thanks
What are your virtual memory settings set to? And are you running memory-hungry programs like a web browser at the same time?
I am unaware as to what virtual memory settings are, but i am closing all unnecessary background processes before playing rust
https://files.facepunch.com/forum/upload/459721/72bb9d2d-9cd1-47b1-aa54-43c7e3c60baa/Capture.PNG are these virtual memory settings?
That's the right window, although what you screenshotted is not the settings as much as the status. The rest of that window is the actual settings. If it's already set to 'custom settings', I'd suggest setting the minimum and maximum to 16384 and pressing 'set' then clicking OK and restarting the computer to make the change apply. Now, this will not do a lot, but it should help Windows be more efficient with memory when it needs virtual memory. You might also want to make sure the power performance settings are set to 'high performance' so the computer isn't doing anything silly like underclocking the GPU to conserve power.
If the problem is low fps I doubt that this is mainly a ram/vram issue. If the sum of those was too low to store the current processes Windows would simply start terminating them, and crashed are not the problem here. Performance wise, having to resort to using VRAM is likely to produce some stuttering when loading new chunks of the world or performing actions for the first time, unless you have the VRAM on a very fast SSD with low latency. On 2Gb VRAM on an OGZ Agility, 8Gb on a HDD and 8Gb DDR2 this causes some stuttering for me at times, with a Samsung Evo over PCIe and 8Gb DDR4 there are no issues at all. What screen resolution are you playing on? If you play on WQHD or higher try lowering your resolution to 800x600 or something. If this works, the problem might be the computational power of your graphics card. Since you built you PC I hope you made sure to install it in the right slot and configuration. Most mainbords use PCIe x16 sockets but only connect a few of the lanes or branch some of them off for other purposes like M2 SSDs. Depending on your configuration this might limit the bandwidth to your graphics card, but I doubt that this would cause any issues unless it's in an x4 configuration or lower. But this is just a guess, don't take it as a fact.
thanks for the reply, im not sure if im reading this right, but what to you by VRAM on an SSD. my graphics card is installed in the correct PCIe , and i should be able to play my native resolution (1920x1080) as i have a 6GB 1060.
Alright, I don't think that I understand your problem, given the information that I have. I'll just give you a general answer. The thing is that there may be (very likely) two different problems at play here. If you don't care skip to the end. I'm not a game but an application developer and a CS student, but I'll try my best to make the reliability of the each of the following information clear. You graphics card takes the scene (the rust world and objects) and performs transformations (like moving your player or objects of the world), lighting and rendering, i.e. calculation of the pixel values for your screen. Most of this is done repeatedly for every rendering pass and you framerate indicates how many times this is done per second. If your gpu is too slow this number will be low and obviously make it difficult to play. The game engine does all the logic and communication with the server and tells the graphics card what to do. This should also happen multiple times per second. Depending on how it handles things it might be possible that the game engine is occupied with a task for longer than it should be and is not able to send updates to the graphics card. In this case the GC might even continue rendering with it's usual (high) framerate, but since the scene does not change it renders the same frame multiple times, resulting in a low effective framerate. If this is not the case the framerate might also drop, but not because of your card itself. This might happen if your CPU is too slow, your network has high latency of packet loss and, most importantly for Rust, if your physical RAM is too low. This is how VRAM works (skip it if you know already): In your PC the program code as well as the data is stored in your RAM. If it gets too full it takes longer to find free blocks which reduces performance and if it is completely full there is not enough space for all of the processes anymore. To make sure that your PC doesn't crash your operating system will thus end a process to make sure to have some space available. Since RAM was scarce in the past, a system has been invented to prevent this from happening: As soon as your RAM is almost full some blocks of it will be moved to your hard drive to free some space. The space that you allocate for this task on your hard drive is called virtual RAM. As long as programs whose blocks are removed don't run into it there is no problem. If one does however, the process will be paused by the os and the block will be requested from your hard drive and put back into the RAM. This event is called page fault, as these blocks are called pages. Finding this block can take in the order of 5 milliseconds for HDDs and 0,1 milliseconds for SSDs. This usually works quite well, because after some time frequently needed blocks will highly likely be in the RAM most of the time while the VRAM is filled with blocks that are rarely or not needed. So what happens in Rust? Rust uses a technique called LOD (level of detail) where objects that are far away are replaced by less detailed versions to lower the workload for your graphics card. Usually this should not be noticeable. It seems to me that all these models are transferred to the RAM as soon as one connects to a server to make sure that they are ready when needed. This however results in a ton of memory consumption - about 6Gb right now. Together with the memory needs of your OS this will force your system to use the VRAM if you have 8Gb or less physical RAM. So what can happen now? Let's say you run around towards a monument. This was not needed before and will very likely be in your VRAM on your hard drive (where it was before loading it in the first place). A page fault will be generated and the thread will be stopped until the model is back in the RAM. After this it still has to be transferred to the graphics card before it will be rendered. If this happens this will cause invisible or low quality objects and, depending on the number of those, even stuttering. So in general, doing things that are different than the ones you did before will cause your game to stutter if you have insufficient RAM. Rust also uses a technique called occlusion culling where only objects are rendered that lie in the direction that you look at. I don't know how exactly this is implemented in this case, but this also doesn't seem to work too well and causes at least visual problems. TL;DR: What can you do? Low FPS -> Buy either a better or a second version of your graphics card, if it supports Crossfire or SLI Stuttering -> Buy more RAM. If this is not an option make sure that your VRAM is on a fast or even on multiple SSDs. If this is not possible either try Windows Ready Boost. Rubber banding -> Make sure that your internet connection is stable and that the server that you play on is running with a sufficient framerate. I play with a really slow CPU (Intel Core 2 Quad) and this doesn't seem to cause any problems, so I'd assume that those issues are usually not caused by slow processors.
Thank you very much for your reply, I will take into consideration all of the information you have given me.
Sorry, you need to Log In to post a reply to this thread.