I've just taken delivery of my reverb G2 and so did a windows update and graphics driver update.

I now keep having an issue with p3D. When things are working as they should I'm seeing between 60 and 100 fps with my settings , however the sim has now started running at about 12 FPS and also having CTDs due to running out of VRAM.

On pressing shift Z I noticed P3D reporting I was using 4.5 GB out of an available 6.0 GB vram, this is strange as i have a 1080TI with 11GB. When I checked the graphics settings the graphics card drop down menu was showing 4 graphics cards available, these were listed as 1080TI 0.0 , 1080TI 0.1,  1080TI 0.2 and 1080TI 0.3, to be clear I only have the one graphics card on my machine.

The 1080TI 0.0 had the correct resolution of 4K selected and the other ghost cards were showing 1080P resolution set.

I've tried installing the previous graphics driver which initially fixed it then the fault returned so went back to the latest driver which again fixed it then the fault returns.

The ghost graphics cards aren't always there, last night I had just the one card showing and performance was good, this morning I'm back to showing multiple cards and 12 FPS.

Does anyone have any idea how to fix this or what's causing it? Any help would be much appreciated , thanks.

 

Edited December 12, 20205 yr by jon b

Try deleting your prepar3d.cfg and let the app rebuild it.

Thanks for the reply, I did try deleting the .cfg but the problem remained.

Ive done a fresh client install and that, so far ,seems to have worked, back up to 80 FPS and only one GPU showing in the menu.

I really don’t know what was causing the issue.

Well, at least you are back up and normal ops!

Happy Holidays!

The descriptor '0.x' indicates that Windows is recognising multiple outputs on the same GPU, rather than multiple GPUs. If you did have another GPU in that machine it would show up as '1.x'. For example, I have five displays on one machine across two GPUs - 2 on one and 3 on the other - so I see 0.0 to 0.1 and 1.0 to 1.2. You should only see a display in the Prepar3d display list if there's actually a monitor connected to that output, though.

It's almost certainly the G2 install - Windows may have re-enumerated the displays after you plugged in the device but before the G2 drivers were installed (assuming you did it in that order) so it may have seen the HMD as the wrong class of device initially, and this may have bled through to P3D. I've seen odd things like this from time to time and it usually needs a reboot and sometimes a P3D .cfg delete (or removing the offending entries from the config file manually) to fix. I think this is why most VR headsets come with a note to install the drivers before you connect the hardware. 

 

Ah, thank you for that detailed explanation. I suspected the addition of the G2 may have been behind it as all was fine when I was running the odyssey plus a couple of days ago.

The only difference was the odyssey was using an HDMI port and the G2 is plugged into the display port ? I don't know if ,  but since I've done a fresh client install everything is good again. V5.1 in VR with the G2 is smooth and looks incredible.

Thanks again for the reply.