One quick thing it's good to be able to fully use all the Fanatec Mclaren GT3 rim buttons and rotary's..
Ähm, found the solution. I tried to manually map the rotaries in the first days and "destroyed" the factory settings. Now it works. Did not expect them to work since your hint. Thanks for it.
With the above tips for VR, it immediately imrpoives significantly. Kunos shoot themseklves in their feet if not providing better documentaiton and epxlanation ofr options and functions that are not really self-explanatory or could not be known if you do not get them told. https://www.assettocorsa.net/forum/...ate-0-2-discussion.51980/page-14#post-1001882 The same could be said about Raceroom. Some of the options, especially the many FFB otions, are anything but self-explanatory. Documents in a folder named "docs" inside the installation folder have the big advantage that you can print them out. The work to create them and udate them is the same like typing it all for websites and then scattering them around. A doc in an installation folder is something where the player can know and immediately go if he has questions. Beats online scattering by several miles. BTW, in 0.1.x , I had repeatedly BSODs. In 0.2 I have had none so far - even with a full car field of 20 in thunderstorm and at night.
Thanks for this! Will try these out later (only had the first 4 lines). Can you share where we can read about some of these parameters, on what they do? Also, your in-game graphics settings? Are you able to run 90fps w/ AI, or settle with ASW on? Thanks again!
I run 45 fps and did not realize any stutter ore disadvantage. Grafic settings mainly on epic or high. Just shadows and Foliga on low. Remember to set Temp. Antialiasing on Epic to get the new Engine file work proper.
Just to be fair - the options provided by @Eisprinzessin are options that are set directly in the Unreal Engine. In this case you are overwriting settings from the game. So nothing bad or anything but not really planed to do it that way. I'd expect that Kunos will do some work on the engine and the VR-Settings. So with every upcoming fix, you should check the ini-file if the settings are still there and if yes, give it a try without to check if Kunos have made some changes internally. If I get it right, Kunos will release a Hotfix today with some really needed fixes for VR like Keyboard-Controll and hopefully 6DOF instead of the current more or less 3DOF
Thanks. My initial understanding was that AA should be set to at least High.... so it should be at Epic?
No, high or Epic, you are right. But Temporal! A todays Hotfix would be much apreciated. Especially if it contains the possibility to load car setups...
^ Temporal in 2D, FXAA in VR. Temporal in VR is not only more washed-out, but produces ghosting (echo sihouettes behind moving objects). FXAA in 0.2 is not ideal for VR, but for the time being we have to live with it - its all WIP. I play with just that two-liner added to the ini file, not the full list of many more entries. Will be overwritten at next release anyway.
Hm, tried and got to the result, that temp AA looks much better in VR (Oculus) than FXAA. Much better means much better. The mercedes grandstands and other objects far away look much more sharp.
No ghosting with Temporal? Thats weired. I thought that everybody using Temporal has it. Thats what was said. I have it for sure.
In VR. I have tried now the full list of ini-commands instead of just the one command listed by Gamer Muscle. Result: stuttering frame rates, blocky looks, a really rocky ride with medium ingame graphics settings and both Temporal AA and FXAA. Immediately deleted again.