![]() I think I will settle with 60% as the picture did not get worse, at least I could not notice it and the gpu occupation dropped significantly to 70/200 setting. ![]() So then I decreased the res scale to 65% and my GPU usage droped down to 70% while the picture in the Rift was not noticable worse! Little bit of yaw dropping moment. I started with 70% res scale and 200% pixel density and I could hold 90fps for about 20secs than my gpu needed to slow down because it got to 80deg as the usage was at 98%. I can see in the Afterburner that I had some drops in fps, but I can't tell where they were on track. Other than that, it was possible to get 90fps, need to enable the fps widget again to check while driving how the fps are behaving in braking zones etc. Had the same problem as you at Nürburgring, as soon as you apporach the stadium section the fps drops to 45fps, no chance. Before that I was running 100% res scale and 140% pixel density as I had no problem with 45fps ASW. Shows GPU working within capabilities, and CPU is spiking a lot.Ĭlick to expand.Did try your settings yesterday, especially the res & vr pixel density thingy and I must say they worked pretty great! I had a lot of settings in the same range, but res scale, vr pixel density and Post processing were different. First 55% log showing hotstint work, top log is CPU thread/usage, bottom is GPU load. Log below of HWInfo over a short period, 30-40mins.Also plan to take a look at firmware in case bios updates bring improved stability. pointed me in a few options to take a look at in terms of ensuring GPU isn't overheating or overboosting above supported vcores. After 45-60mins gaming began getting graphical artifacts on HMD and on main windows display. ![]() Rest of track 45-90fps, usually dropped in the braking zones > not helpful when trying to hit a pinpoint turn in!.FPS 90 at start, and most of way down pit straight, dropping to 40-45fps at the T1 complex > has mentioned this is a common issue on the Nurb release and some potential odd graphics within the game.Ran TT Hotstints last night as a test for setup (Nurburbring, 22:00 settings as per TT event for S3). Json changes : spectator screen disabled fpsvisible enabled ![]() Logging : HWInfo (cpu & gpu usage), CAM (Nzxt cooling for cpu temp) TIP: With ACC you can now save preset custom graphics settings, so I will be creating one with higher res scale, and one with lower to flick over to quickly on big grid style races.Īny questions let me know, and i'll report back how the settings work on an "older" CPU architecture!īit of an update after testing yesterday for anything on similar old potatoes like me.Res scale can then be increased if your HW can handle it, runs it at 60%, I'm hopeful to get it at 50% with an older CPU. Resolution scale and pixel density - set pixel density to 200%, res scale to 50%, therefore leaving 100% per screen on HMD (headset).This can be done in ".\Config\vrSettings.json "spectatorScreenMode": 0".My preference will be to disable this entirely as I'm not streaming or anyone needs to watch me race, plus will conserve additional rendering/load.Resolution: unless streaming, or wanting people to watch your race, lower this to minimum 1024x768 - this is only the mirror window left on your desktop when the HMD is on.Settings to stop 45FPS+ASW situations where possible (obviously dependent on your individual hardware limitations).Initial settings implemented as below, limited running but benchmark FPS to be completed tonight. Looks for balance of Max CPU/Thread Usage and GPU core loading, ratio roughly CPU:GPU HW : i5-4690k 4.6Ghz (OC), RTX 2070 (stock), Rift CV1 Courtesy of for both of HW : i9-9900k (hyper threading off in bios - not required), GTX 1080Ti, Rift CV1ĩ0fps 99% time, lowers res scale for bigger races to stablise FPS with bigger grids.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |