glider1

Triple check that your max texture resolution is set to 1024 even if you have more than 8GB VRAM. Device hung has many causes. Check that you haven't unknowingly increased the load on your GPU more than you did with the G1. If the settings are identical the device hung problem should be the same on either headset.

I've noticed recently been getting no device hung errors (fingers crossed) once I reduced texture resolution to 1024 which still produces acceptable visual quality in VR on my 2080TI.

OVR Toolkit does the job for me but there is a bit of a learning curve. I find the native WMR desktop too unstable.

I had P2A "freeze" recently. Everything responded slowly including the interface, recognition etc. It was because I had P2A running on the same cores as the sim that were already running at 100% usage. There was no CPU headroom left. The freeze disappeared Once I reduced the CPU core usage on the cores that P2A were on.

Normally the DEVICE HUNG is hard to track down but this time had a clear and concrete example of it. Loaded a scenario with the Milviz 350i. Walked around on outside view with Chaseplane. Noticed that the texture for a spinning prop on the right engine was already loaded but the prop was stationary engines off. Got into pilot view noticed that the texture was not loaded. Started the right engine like normal. Instant DEVICE HUNG.

I get this error randomly in latest P3Dv5. It pops up this message when enabling Virtual Reality. When you click ok the sim works normally until during the flight I will get a CTD in terrain.dll. It is reported on the LM forums but can't see any reply from the devs. Can anyone explain what it is, does anyone else get this and can hint at a solution? Thanks

Hi there I'm trying to work out whether I hit a mountain during my SID departure using LNM GPX trail export. Here is the pic in GE: I can work it out by mousing over the GPX trail but for some reason the GPX track straddles the terrain rather than showing the actual flight path elevation. It would be nice to visually see the flight path over the mountains. Has anyone a solution? Thanks

Have a read of this forum it has a few tips towards the end. Your VR performance should at least be the same. There are a lot of different possibilities like wrong settings/old drivers etc that could degrade performance so there might not be a quick answer.

Can someone explain why sometimes there are huge differences between 2048 and 1024 textures and sometimes not? Here is an example A2A Bonanza at 2048: A2A Bonanza at 1024: Yet other aircraft show 1024 textures pretty well. Thanks

I run a .bat file AFTER the apps are running which switches their AF while they are running. Crude but works. set AF=240 PowerShell "$Process = Get-Process -Name Pilot2ATC_2018; $Process.ProcessorAffinity=%AF%" (Note that the command is all one line no carriage return.) So that batch file will change the AF of the already running Pilot2ATC AF is a decimal value which converts into an affinity mask by the operating system (W10) 240 = 11110000 so P2A will run on the last four cores of the 9700k. Then I start the sim and let it have all the cores since if it overlaps with P2A on the backend cores it doesn't matter because the last four cores the sim uses for scenery loading which shouldn't cause stutters (P3D specific). Cheers EDIT: the need for affinity masking is becoming less urgent these days as the operating system job scheduler is starting to do a better job of preventing apps competing for the same cores

It works well in VR in P3D on a 9700K/32GB/2080TI but I segregate P2A from the sim with an affinity mask so that it is not running on the same primary cores as the sim. That and a good mic is the way to start to get reliable performance. Same to you have a good holiday.

Yeah I if you got one of these DXGI errors flying under light load at high altitude after a long time then heat buildup is a good idea to chase. All the best tracking it down. The 3090 sucks a lot of power too.

If you find out what the cause was it will be especially useful because you are different to most not using a virtual cockpit.

Thanks Chapstick for that guide right so it isn't touching VRAM just adjusting textures. I carefully observed VRAM usage using task manager during an entire VR flight in the Milviz Kingair on a 2080TI W10 HP reverb headset. It went like this: Boot to windows 0.1GB/11GB Load Chrome 0.2GB/11GB Load Little navmap 0.3/11GB Load ASP3D weather 0.3/11GB Load Pilot2ATC 0.3/11GB Turn on WMR VR 2.9/11GB Load P3D 5.1hf all the way to sitting in cockpit 8.5GB/11GB P3D shift-z reports 5.9/10GB which is interesting... Stays on that VRAM entire flight (out and back) Shutdown sim and all apps except browser 0.8/11GB Thanks again and will try to leave 0.5-1.0GB headroom. EDIT: don't know why P3D sometimes reports only 8.5GB total instead of 10GB total.

Thanks and your cautious approach is good have a good holiday. But 8GB out of 8GB is valid with dynamic VRAM turned on and the sim loaded isn't it? If it is bad practice then my original question is still open - how much headroom is enough?

Thanks for that. I think I expressed myself poorly though. Say you are sitting at the scenario window with no shift-z. So you move sliders and load up the flight. You get to the sim and shift-z says that you are using 8 out of 10GB. Then because of whatever reason say because of Little Nav Map now it suddenly reads 8 out of 8 GB. You have dynamic VRAM enabled. Do you abort the flight for likelihood of "Device Hung" or keep going?

Have a good Xmas Rob. Thing is you never know how much VRAM headroom is enough. Do you leave 1GB? 2GB? Then I've heard it around the traps that the actual amount of VRAM indicated is not representative of what is actually available because of fragmentation. Then on top of that the available VRAM will suddenly drop for reasons that don't make sense. For example I'll start the flight on my 2080TI with 10GB VRAM available even if I've used 5GB then for no reason I can work out without any background scenery loading shift-z shows 8GB available and nothing has changed in the sim and I've still used 5GB.

@YoYo Thanks for those detailed settings and the work uploading them they will become my reference point. I found that locking the fps internally on 46FPS meant my 2080TI didn't have to work as hard as on unlimited. I also found that at some airports MSAA is necessary even with 150% SS in SteamVR but it hits VRAM hard. I guess this is not a problem for you with a 3090 and 24GB VRAM so why not you include some MSAA for yourself? Also I notice that you have reprojection on. At one point in the past we concluded it had to be off but I guess with the new drivers it is ok. I turned it on too and smoothness seems fine. My only problem remaining now is that the cockpit is too dark for some planes with EA mode on but thankfully in the Milviz Kingair 350i you can turn on some instrument panel lights even in the day.

Had the same issues for a long time update was fine but not pre-render. - Did a clean install of 460.89 latest Nvidia drivers may have used DDU cleaner but could also have used NVidia custom install can't remember. - Changed Nvidia program options for P3D to "prefer maximum performance" everything else default. - Updated SteamVR and WMR for SteamVR in Steam - Went into SteamVR settings->video and Manage Video Settings For Prepar3D and Custom Resolution multiplier 150% Motion smoothing: disabled Use legacy reprojection mode: off - Went into P3D VR menu and turned on pre-render Then pre-render started working on 2080TI/Reverb G1 combination. Performance seems a bit better but haven't done tests. The 460.89 drivers also worked well on my laptop improving performance in SkyrimVR for some reason. Good drivers. Hope you get it working but update is still good. I'm remembering this off the top of my head, if there is anything else will report back.

For some strange reason in my Windows Store -> Installed the most important app "Mixed Reality Portal" doesn't show up. I actually have to go to Home->Search "Portal" then it finds all the apps with portal and then it shows up as installed.

Thanks got it going the light bar display looks awesome in VR too great job on it. It wasn't your problem it was on my end. For some reason now that I'm testing in P3Dv5 I have to designate the lightbar like this: gauge00=CDX_Lightbar_P3D_V5!CDXLightBar,0,865,1024,159 instead of gauge00=CDX_Lightbar!CDXLightBar,0,865,1024,159 So I changed it in both locations in panel.cfg and re-enabled the 2D panel with: Window05=LightBar Display But the 2D panel isn't needed you are correct. The click spot on the Satloc works too so that the lightbar comes up nice and close to the cockpit in case I need to read it more clearly. Thanks a lot and am spending time with your mod, the Piper Pawnee, and CropdusterX over Christmas.

There are two WMR's to update. The one Threegreen said on the post above and also "Windows Mixed Reality for Stream VR" which should update in Steam.

Got it working by installing latest versions of WMR and SteamVR see post above.

Thanks got it working by installing latest versions of WMR and SteamVR using Steam download. Seems smoother too with pre-rendered option enabled. Here are the settings in my SteamVR panel in 3D: Manage Video Settings For: Prepar3D Custom Resoultion multiplier 100% Motion smoothing: disabled Use legacy reprojection mode: off

Got installed ok into P3D as per instructions and modified the aircraft.cfg. Everything seems to work except for the lightbar display out at the front of the nose behind the cowling the screen is dead it won't turn on when I turn on the Satloc. The Satloc control embedded in the VC turns on when the avionics are turned on and the LED for the satloc timer can be set and the blue buttons illuminate. Radio is on. I notice that there is no lightbar 2D panel in the instrument panel list any more. If you have the time do you have any ideas? Thanks.