Hi guys, Nipzon's problems have forced me into triple screens. In spite of having only a mid range r9 280 graphics card knowing full well the fps issues people have on rfactor2 with triple screens and multiview. Something I have found, profound, total rubbish for everyone else I have no idea. But fell across it by chance. I use AMD.......for Nvidia I have no idea if its applicable. When I set up AMD eyefinity I initially set it up as 1 5760 X 1080 screen stretched across the 3 monitors. Ran rfactor2 and set the display so it used multiview and away I went. Well Mag park was my choice and on the same settings otherwise used for single monitor use 23 frames per sec....Off with multiview and happily at my preset 60fps max. That is perfectly fine by me actually as it displays just as my single monitor set up but I could now see my mirrors...
Not the point though as I need fps in multiview. Followed Spinellis (ISI forum graphics guru) advice and turned down shadows, reflections etc and aa and stuff, I'll do a screen shot at some point. Anyhow, that did SFA to improve the framerate.

Ok, I am not going to bore you with my experiments, skip to the chase Al.

I reset up my eyefinity after failing to improve FPS and set it up for 3 seperate screens as I usually use 2 anyway. All were set up at 1920 X1080. Got bored and kicked off rfactor2 without a second thought and realized I hadn't changed the screen setup didn't worry and loaded fine, mag park again and I was triple screened in MULTIVIEW. Bugger says I and hit race and my FPS was 55+ and even with heavy shadows never went below 46FPS with 10 AI on track racing.

So boys and girls, if you are having trouble do as I did, set up 3 seperate screens of your preferred resolution, change the display settings in rfactor2 to combine the total resolutions, select windowed AND multiview and hopefully you will have a good frame rate , you will have to reduce shadows and reflections to low, and nothing else set above high. aa to no more than 8

Feedback welcome good or bad. I'm still testing,

Allan

Found this post in RD about graphics setting in rf2 and nvidia control panel,

www.racedepartment.com/threads/rf2-graph...-check-first.106607/

If you have graphic bugs. Check these things first:

If you ever had changed something in the nvidia control panel in the past. Your graphic bugs might be still present.

- Set your nvidia control panel for rFactor 2 to default !!! It messes with the Config.ini and cache !!!
- Clean up your "UserData/log/CBash" and "UserData/log/shader" folder
- Remove the player.json and config.ini (cut/past to desktop to keep a back-up)
- launche rF2 it will create a new clean config.ini and player.json.
- set your graphic settings again: only use settings available in rF2.


Quote from Tuttle (ISI Dev)

Starting from a clean installation, with a clean player/config file, the best way to proceed with graphics settings is to JUST use ingame settings, pushing on high AA levels and anisotropic filtering x8 or x16 (and of course good track/car quality settings)...and that without overriding anything via inspector and/or CCP.

(Also HDR must be ON if you want a proper modern lighting.)

This way you can load the game and check how it looks. If you see trees are looking properly (no alpha jaggies) and texture are sharp enough to see details into it (aniso texture filtering), you can decide to be happy (and stop tweaking)...or start experimenting extra settings, outside the game.

But this is the time where you can mess with profiles and configs, so you have to check every single step, and every single click you are doing with CCPs and inspectors, to see how things are working. May happen a CCP/Inspector change is going to mess the config.ini and cache... and you can't just roll back from those settings, without cleaning up that file (aka generating a brand new one). Same for the Players.JSON and Transparency AA, or xpaa, using False to make wrong trees looking better and then making correct trees looking wrong.

Still, the easy way to make the game looking at best, is to go easy peasy, with standard ingame settings. This is where you are working inside our choices, instead playing with a very big mix of variables we can't control.

That's great, thank you Nipzon. Nvidia user help is appreciated.

Hi again, quick update to my first post. With my system, low spec AMD graphics card trying to run multiview. Due to this I may see something others with higher spec graphics cards may not see and once again may not be applicable to these users or not be applicable to nvidia graphics card users. My usual fps is between 45 and 60 fps ( it is capped at 60 ) so could possibly go higher but I doubt it. At times when having first loaded rfactor2, either single or multiplayer, when I start to race and check fps at times it is as low as 15 fps and nothing I do in game changes that.

The solution is a a nuisance, but to date works perfectly for me. All I have done is leave the track out to the launchers "first" window ( NOT closing rfactor2 down completely and restarting ) and then simply restart either single or multiplayer and I'm back to 45+ fps. I find the sim quite playable at this although many would cringe that I do....Not tested with other than AI on track though.

The reason I even mention this is those that are having issues with stuttering or input lag when usually able to run far more fps than 60 but capping at 60 OR not monitoring frame rate, may see a similar frame rate drop that I do on game start but not be aware of it. If that is the case and the frame rate is lower than the "norm" for you when running rfactor2, when extra detail, heavier shadows or more vehicles on track occur AND the normal fps drop applicable to that, may see some of the symptoms this post is trying to solve come to the fore to some extent.

It may or may not help anyone but like anything I suggest it will do no harm to try if you experience some issues while using rfactor2.