As far as i know, this is a well known behavior of rF2 and at least all tabbed programs themselves... When you switch (alt+tab) back to rF2, the FPS should increase again.
Before alt tab, solid 60 fps. After alt tab frames all over the place, decreasing as much as 50 percent. The sim doesn't become stable after this, until I exit the sim and start over again.
I believe the track at full details is near the vram limit of a 2GB gfx card. When you alt-tab to firefox, Windows has to free up some GPU memory for the browser (around 200MB, depends on the website) and you loose this memory for textures in VRAM. If you go back to rFactor, the game engine has to read the missing textures from (slow) system gpu memory (you may notice the difference between physical GPU memory and by directx reported memory in the video settings). When this happens I see stutter and a decrease in fps. Check the green VRAM bar on the top left of the screen (if you press 2x Ctrl + f). If it's more than half way down you run partially on system GPU memory and should reduce texture details.
Nice explanation, thank you. I will check out the VRAM bar next time I load up Nords. Oh btw, forgot to mention: The FPS decrease and stuttering I get when alt-tabbing back from another program is worst on the GP part of the track. As soon as I leave the modern layout and go unto the old, it gets better. I'm guessing because the recently added GP track isn't fully optimized yet?
Thanks mianiak, it's good it know we are allowed to do that if we have the time. Cheers. @Tosch, looking good . DJC
I noticed relatively heavy flickering on the rear of the Apex Modding Mercedes SLS GT3, which I didnt have on other tracks. Several other drivers reported the same issue. I tried diffrent opponent detail levels, but no change. Any ideas?
http://en.wikipedia.org/wiki/Z-fighting Car modders should avoid these "coplanar polygons", but I see them all the time and not only in modded content.
Here is a mirror for the 1.99 beta: https://mega.co.nz/#!e4ImwT5C!W4Z4qljnMiXRl_rbFztDi_hBvY-okQMfnrBRUEbsn3o
Wow, it's been a few months since I tried this track but this version is amazing. Well done to all involved.
Found some sick hdr settings. -Brightness of the sky is ok -Whitepoint settings work for sky and track at the same time -Good saturation and contrast -No overexposure in cockpit view -Sun occlusion works for the first time since 2012 like it should (almost no shadows when the sun is hidden by clouds). My question to ISI. Who had the questionable idea to run the automated profile with light intensity 40 times stronger than needed? Edit: @DJC Did you notice the reduced reflection on the "space boxes"?
Yes, this looks terrific. Is it just for Nords or would it work as a general setting? And can you share it? Preferably with ISI so they can use it, but failing that, the rest of us can spend hours installing it in every individual track.
Wow, I can't wait to see it in motion, sounds real good. Are there really no major drawback to the profile? Night time racing look ok?
@Tosch You really should send every single value, screenshot etc to the devs. To Luc and Pierre. It could be for the mutual benefit and OUR benefit in the process!
Jesus! Tosch...everytime I think it can't get better, You guys pull a rabbit out of the hat. This update process reminds me of years as a young Porsche/Audi technician. Every year, I kept thinking the 911 was going to be discontinued....every year it got better. I fully expected the development to stop years ago and it's still going...even now some 28 years after I stopped fixing the cars on a full-time basis.