vrdubin6

This is a wonderful update. I just did a little bit of testing. With the setting on low it was pretty much the same as before. Going to medium seemed to help a bit but once you get to high/ultra it is like night and day when panning around. So much smoother.

After reading through this I'm excited to get home and test the update. It's been kind of a shame having a powerful GPU and only having high FPS and smoothness when looking forward. It's been a choppy mess with TrackIR.

I just upgraded to a 3080 Ti as well and I'm pretty happy. 3440x1440 at mostly ultra settings with a few things turned down/off.

No issues here with the WT G3000/5000 mod. Did a couple Longitude flights over the weekend and GP was captured just fine both flights.

Bummer, I'm still getting the same major issue I was dealing with before.

As with anything they can fail but that doesn't mean you will get a leak. I had an H100 that only lasted 3 years but it was due to a clogged pump so no major issues occurred and it was replaced under warranty.

Yes, to an extent. You can import views from other aircraft or download camera presets from the community. I have a handful of outside presets that I apply to all aircraft and then set up cockpit presets for all planes individually. It takes a couple minutes to set up a new plane.

Everyone's system is different so by no means do I think this is a cure for everyone, but hopefully it can help at least someone. Long story short, on my system v5 doesn't like Intel's/Window's power saving features. I have an older system (6600k - 980ti) and I've had the same stable overclock for years. My overclock has never given me issues with any games and I'll run Cinebench/OCCT/etc. from time to time to verify everything is still stable. And then came v5. With v5 I was getting fairly frequent freezes to where I couldn't do anything and would have to restart. Assuming CTD was usually software based but these freezes seemed hardware based. I ran the usual gamut of tests and everything was still stable so I started messing around with C-states and such. I made sure Windows was set to "high performance" power mode and disabled all power saving features in the BIOS (all c-states, C1E and EIST). This completely resolved my issue with v5 freezing. I know some people prefer to disable all of these features on any overclocked system but I've always liked having them on as long as I know I have a stable overclock. Guess I'll be leaving them off for the time being and maybe give it another whirl when the as additional v5 hotfix/updates roll out. I figured it was worth sharing my experience in hopes that it can help someone else. Cheers!

I posted the fix in the below thread. You can install with all the simulator options grayed out but the config tool wont work. For everything to work correctly you need to make a dummy registry entry so the installer thinks you have v4 installed and then point the installer to your v5 add ons folder.

I just posted the topic on the Prepar3d forums. I figured I would try here first and see if others had the issue.

Here is a better video. You can see it shortly after where I've started the video and again a couple times near the end.

Excuse the cell phone video. I just did a test flight and quickly wanted to get a video of this cloud flickering problem. I have tried various settings, fresh Windows install, different drivers, etc. The clouds intermittently flicker like this about every 5-10 seconds and it ruins the flight when cloudy. Any ideas to resolve the issue? These are the addons I'm using but it does it with a vanilla install as well. v5 HF1 with legacy clouds/weather (no Truesky) Orbx LC/Base/CRM/Trees ENVTEX/ENVSHADE ASP3D Video

I think I had the same issue but after shutting it down once it was then cold and dark each time going forward.... don't quote me on that but I'm pretty sure that's what I remember. I didn't have any issues with the config taking affect other that cold and dark.

Weird, the only time I've seen this is airports with new ICAO codes, but that doesn't seem to be the case with KHAF? v5 updated their database and a lot of airports updated to their new ICAO code so if you're running ORBX scenery it will have the old code and v5 will have the new code. Basically loading 2 airports in the exact same spot. You might have better luck posting it on the ORBX forums. They have a pretty lengthy list of bugs they are working on.

I don't suggest editing your registry if you aren't comfortable with it, but this is fairly straightforward. Click the Windows key Type "regedit" - this will open the registry editor Go to the path in my screenshot and create a new key called "Prepar3D v4" Within that Prepar3D v4 key create a new string value just like the one I've highlighted. Named "SetupPath" with the value data being the location of your v5 installation. The installer will now think you have v4 installed and it will be an available option. The installer will want to install to your v4 add ons folder so just change that to your v5 add ons folder and complete the install.

Curious as well. I just checked the website and the Prepar3d download is still for v4.

You can’t open it but you made changes? You have to install ENVDIR to use it. It is the main program that is the interface to use ENVTEX/ENVSHADE/ENVSOUND. Make sure you use the update option in ENVDIR because older versions of ENVSHADE aren’t compatible with v5. After updated make sure it finds your v5 installation and that the little green “shaders” switch should be ticked on just like in GSalden’s screenshot. Then make sure you install (green down arrow on the bottom left) which takes a minute or so to install into P3D and then you’re done.

You can map a hotkey to reload shaders in P3D. Not quite on the fly but you can then tweak ENVSHADE and then reload the shaders to test.

Flysimware Lear has become my favorite plane. Not really slower than a tubeliner but don't let that stop you.

This works but without the registry entry I don't think you are able to use the configuration utility.

Yes, if you are comfortable editing the registry. I just made a dummy v4 registry entry that points to the my v5 installation location. The installer recognizes v4 being installed and worked without a hitch.

I knew it was something easy! Thanks so much for the quick feedback as always. This was the first time I had reinstalled from scratch instead of copying over full panel folders.

I had been using v5 without issue but today I decided to do a clean install of HF1 and I cannot for the life of me get the d-to/home buttons working like I always have. Standard install of the fix. I have the f1vc.xml in the rxpGTN folder within the panel folder and the line added "gaugexx=rxpGTN!f1vc.xml,0,0,1,1" to the panel.cfg that I've always used in the past. I'm sure I'm missing something simple but it isn't working with my Duke, Legacy or A2A 182. I'm stumped.

ENVSHADE doesn't have luminance adaption. It's the main reason I run it. It drove me nuts with stock v5 for the week I didn't have ENVSHADE.