My 3090 Settings for my G2 (2.7.11)

[Panzertard]

On 1/4/2021 at 2:21 PM, speed-of-heat said:

I record the frametime with FPSVR with a hotkey starting and stopping at a similar point in the track (there is some variability here, but not enough to cause me concern) and then I take an average of the data produced for each column and call that "the number" . 

Dear Dr.Speed.

Are you using the fpsVR builtin 'hotkey' in the Settings, Advanced, "Frames data logging": CTRL-F11

And then you run the numbers yourself from the CSV created?

Or are you just using the Median/AVG summary from the 'History Viewer' per run?

 

I'm trying to find the best way to get consistent results every time.

I'm not sure if I trust the fpsVR to exclude the frames before the flight starts, before we mange to press 'fly' and start the run.

 

  

On 4/30/2021 at 9:26 AM, ShaunX said:

Noticed that I got a SteamVR Beta update this morning so decided to rerun the last test again. Ran it twice. (MSAA is still x2)

 

 

coincidence ?

@ShaunX, may I ask the same as above, are you running the CSV output and you crunch the AVG yourself with your own spreadsheet?

 

Edited May 7, 2021 by Panzertard

[speed-of-heat]

2 minutes ago, Panzertard said:

Dear Dr.Speed.

Are you using the fpsVR builtin 'hotkey' in the Settings, Advanced, "Frames data logging": CTRL-F11

And then you run the numbers yourself from the CSV created?

Or are you just using the Median/AVG summary from the 'History Viewer' per run?

 

I'm trying to find the best way to get consistent results every time.

I'm not sure if I trust the fpsVR to exclude the frames before the flight starts, before we mange to press 'fly' and start the run.

 

Yep, I use ctrl+shft+F11 to avoid a clash with some modules , I have a standard track, and start and stop and a “similar” point in each mission, and then I remove the “ marks from the CSV, and then take an avg of each column, the half second- 1 second variance makes little practical impact on the outcome.

[Panzertard]

3 minutes ago, speed-of-heat said:

Yep, I use ctrl+shft+F11 to avoid a clash with some modules , I have a standard track, and start and stop and a “similar” point in each mission, and then I remove the “ marks from the CSV, and then take an avg of each column, the half second- 1 second variance makes little practical impact on the outcome.

Much appreciated, thank you.

[Burt]

Seems to be a new setting in steamvr 

Feild of View fault settings at 100

But then again I’ve been in 2d mode and just now hook my G2 up and glad I did.

I love the crisp look of 2d but VR... oh man!

[ShaunX]

10 hours ago, Panzertard said:

Dear Dr.Speed.

Are you using the fpsVR builtin 'hotkey' in the Settings, Advanced, "Frames data logging": CTRL-F11

And then you run the numbers yourself from the CSV created?

Or are you just using the Median/AVG summary from the 'History Viewer' per run?

 

I'm trying to find the best way to get consistent results every time.

I'm not sure if I trust the fpsVR to exclude the frames before the flight starts, before we mange to press 'fly' and start the run.

 

  

@ShaunX, may I ask the same as above, are you running the CSV output and you crunch the AVG yourself with your own spreadsheet?

 

 

 

I use CTRL-F11 to start logging after I click fly, then again immediately after the track ends.

 

I then open the log in Excel, remove the all the " marks with a replace command, then I delete usually the first 2 or 3 rows, which tend to show GPU framerate = 0, then at the bottom, I remove all the rows which occured between the track ending and me pressing CTRL -F11 - It's pretty obvious which ones they are as the pattern changes totally.

 

Then I use the "=Average" function on column D, then copy it to C and B

 

I get extremely consistant results this way.

 

I also leave my G2 hanging on it's stand before I even start WMR and do everything with desktop commands to ensure I get a consistant headset view throughout the tests.

 

My sequence is:

 

Switch on G2 - WMR auto-launches

Launch FPSVR from start menu - SteamVR auto-launches

Launch DCS from start menu

Click ALT-Enter to go Fullscreen DCS

Start the track file and click CTRL-F11

Track file ends - Click CTRL-F11

Edited May 8, 2021 by ShaunX

[0414 Wee Neal]

Hi SOH

great thread thank you.  I have a G2 with 2080 and suffer from regular SteamVR crashes.  I have tried all the normal repairs of windows, DCS, reloading WMR for Steam Vr, Steam VR etc.  Checked to duplicate versions of Steam and so on..... However it still crashes, although less frequently.  If I was to hazard a guess I would say that this happens on the cusp of a heavy load e.g. just about to land on the Supercarrier, Huey landing when ground tracer starts etc.  

 

If you were to hazard a guess do you think this could be an instance of my GPU peaking and causing the crashes and if so what setting would you recommend to reduce the likelihood of that threshold being hit?

 

Its so bad I am seriously looking at the Quest 2!!

 

Thanks

 

Neal  

[speed-of-heat]

23 minutes ago, 0414 Wee Neal said:

Hi SOH

great thread thank you.  I have a G2 with 2080 and suffer from regular SteamVR crashes.  I have tried all the normal repairs of windows, DCS, reloading WMR for Steam Vr, Steam VR etc.  Checked to duplicate versions of Steam and so on..... However it still crashes, although less frequently.  If I was to hazard a guess I would say that this happens on the cusp of a heavy load e.g. just about to land on the Supercarrier, Huey landing when ground tracer starts etc.  

 

If you were to hazard a guess do you think this could be an instance of my GPU peaking and causing the crashes and if so what setting would you recommend to reduce the likelihood of that threshold being hit?

 

Its so bad I am seriously looking at the Quest 2!!

 

Thanks

 

Neal  

i'm completely guessing... i'd say a borderline unstable overclock/low voltage ... on your GPU, but, there really are to many variables to consider (for me) you should make a separate post under Game Crash - ED Forums (eagle.ru), and I would include a track from the crash and your dcs log files as well as your settings, in steam and in dcs and version numbers etc, as well as previous steps you have taken in order.   If its load related you could try dialling back some of your settings, shadows, msaa etc.. , i wish you the best of luck diagnosing it !

[imacken]

Not sure if this is old news as I haven't been using VR so much in the last week or so, but are these new settings useful?

[speed-of-heat]

just testing them now m8, they only came out last night ... FOV does what it says on the tin:

 

			Frametime in ms		Delta From Previous
Ver	Test	Baseline	GPU	CPU	GPU	CPU	Changes
2.7.0.5118	26	Test 21	10.70	7.39	0.18	-0.04	Shadows Reduced Frame Rate Impact MOD
2.7.0.5690	39	Test 26	10.72	7.44	-0.03	0.21	5690 baseline 80% CRM
2.7.0.5690	40	Test 26	10.73	7.24	-0.02	-0.05	Steam Version 1.17.8
2.7.0.5690	41	Test 26	12.11	7.34	-1.41	0.05	Steam Version 1.17.8 100%CRM
2.7.0.5690	42	Test 26	11.92	7.28	-1.22	0.11	Steam Version 1.17.8 100%CRM 90% FOV
2.7.0.5690	43	Test 26	11.78	7.21	-1.08	0.18	Steam Version 1.17.8 100%CRM 80% FOV
2.7.0.5690	44	Test 26	11.19	7.33	-0.49	0.06	Steam Version 1.17.8 90%CRM 90% FOV

 

In summary you can read the number but 80& is too much for FOV for me 90% is liveable with i think maybe... and with 90% on the CRM from a base of 100% you get pretty similar perf to 80% .. mostly it is robbing peter to pay paul ... so far 

[imacken]

The FOV is a complete mystery to me. Weird view point, and I'm struggling to see the point of it, tbh.

I can't even see where the Override World Scale setting is!

Having said all that, ny VR performance is shot to hell.  As I said, what with stuff going on, setting up new devices, etc. I haven't been using VR much in 2.7, but something has changed dramatically for me,  Don't know if it's a DCS update, WMR, SteamVR or what, but something is seriously wrong.  I'm to try the release version to at least eliminate WMR or SteamVR.

[speed-of-heat]

i literally had to kill of my saved game file and just build back up from scratch... but also check the bloody pesky vrsettings file

 

The world setting is a switch you have to operate first right at the bottom of custom settings ... not clear at all....

 

the FOV reduces the size of the goggles for the same resolution ... its for those wo really dont mind a loss of peripheral vision and do want a increase in clarity ... more head swivel less squint

 

Edited May 8, 2021 by speed-of-heat

[imacken]

I'll check the settings file, but I never touch it now that the motion smoothing settings are in the UI.

 

Yep, I mean I see what the FOV setting does, but I certainly see no performance gain when I reduce it to 50%, and as we are always moaning about the (relatively) poor FOV on the G2, then I really can't see the point of it.

[speed-of-heat]

agreed, but its interesting data ... and actually doing the work here means my head doesnt have to explode when i explain adding up again

[speed-of-heat]

updated for FOV

[zildac]

My default.vrsettings was reverted, so had to comment out the below again, post update

 

[speed-of-heat]

to be fair it does say it will get overwritten each time the drive gets updated

[zildac]

3 minutes ago, speed-of-heat said:

to be fair it does say it will get overwritten each time the drive gets updated

Absolutely, I'd completely forgotten tbh

[speed-of-heat]

i do wonder why they continue to explicitly set anything there ... still ours is not to reason why..

[zildac]

22 minutes ago, speed-of-heat said:

i do wonder why they continue to explicitly set anything there ... still ours is not to reason why..

For sure, me too, as @imacken said 99.9% of the required settings are now exposed via the UI so it's a bit strange.

Edited May 8, 2021 by zildac

[speed-of-heat]

World scale work is done. 

[imacken]

3 hours ago, zildac said:

My default.vrsettings was reverted, so had to comment out the below again, post update

 

It also says 

    // Please refrain from editing this file, as it is replaced with every update to the driver. 
    // Instead, modify settings through the UX available as an overlay on the SteamVR dashboard.

 

I have not edited that file for a very long time since the SteamVR settings moved to the UI, and SteamVR has always been able to control motion projection. No need to mess with that file any more.

[zildac]

12 minutes ago, imacken said:

It also says 

    // Please refrain from editing this file, as it is replaced with every update to the driver. 
    // Instead, modify settings through the UX available as an overlay on the SteamVR dashboard.

 

I have not edited that file for a very long time since the SteamVR settings moved to the UI, and SteamVR has always been able to control motion projection. No need to mess with that file any more.

Yup, it does indeed. Which would suggest that any settings made in the dashboard would update this file OR that entry is no longer used, however mine was still "none" after the update even though I made no changes. I guess it means that this entry in the file is deprecated now?

 

Edited May 8, 2021 by zildac

[imacken]

Not sure what you mean.  That graphic is correct. You set your preference for MR in SteamVR 'per-app setting' as shown.  Never have to touch the settings file we are talking about.

I must be missing your point, sorry.

[zildac]

Probably my explanation. The value in the VRSettings file was "none" after the upgrade (I had previously commented it out and always have - perhaps wrongly), however in the UI it was still set to "SteamVR per app settings" which would suggest that the VrSettings entry is no longer used to determine the status of that particular item.

[imacken]

What I'm saying is that makes no difference. It is always set to 'none' by default.  But, as it says in the file, don't edit that since the settings moved to the SteamVR UI.  (I know there is the other line, but I feel that is an artifact of the previous way of doing things.

Mine is always at default in that file, i.e. 'none', but MR is perfectly controlled by the setting in SteamVR UI. See attached.