fly_edds

I'm not a fan of these "good driver - bad driver" discussions, as they're mostly related to (demanding AA + other) settings in Nvidia control center, which will be resetted when a new driver is being installed. So forget about this, it's nearly always wasted time - but it can for sure help to improve peformance

Hi, I think your cloud.fx has been corrupted by a faulty REX4 update. You can fix it by downloading the default P3D3.2 cloud.fx file: http://www.mediafire.com/download/05t68smuyy7s5v6/Cloud.fx Copy it to Prepar3D v3\ShadersHLSL and overwrite. Hopefully this will help you... (as it did for me)

Hi, I have some advice for Kaspersky users. -In settings, go to "Performance" (not sure how it is named in the english version exactly) -Scroll down to the buttom, you can specify prepar3d.exe here. Kaspersky will pause now everytime you start the prepar3d.exe process and resume when the process terminates!

Any idea what that means exactly? I'm still having the hope that Aerosoft lights will be fixed someday... Maybe they have fixed the bug that default lights lost the bloom inside of a specific radius around the aircraft?

Hi, I thought DSR would be much more demanding on the GPU than SGSSAA? Maybe I'm wrong... When I use 8xMSAA + 4xSGSSAA the load on my 970 (4Gb) is almost always at 100%. I would expect a similar load when using DSR. Or is it a bug of P3D? What do you think? I've noticed that even 2xSGSSAA can be a massive performance killer.

Hello Jarkko, your forum activity and invest of your spare time is much appreciated! Nearly all other forum moderators are very inactive in the last weeks/months, have you heard anything from them? Especially Shells and rjord disappeared a long time ago... Thanks!

Last post is only 3 days old and they have to be approved manually. Maybe moderators are busy elsewhere or people are finally satisfied and don't have problems anymore (me included :smile:) Vectored approaches will hopefully be improved as announced by alpha117, we will see how it develops...

Yeah, it's that easy (C:\ProgramData\Lockheed Martin\Prepar3D v2\scenery.cfg)

@suvo Scenery Config Editor is working in P3D, using it every day.

Here's a little comparision I've done in P3D 2.4 (PMDG 737 NGX, AS Heathrow Extended, FTX Global, ASN) LOD 4.5 3.18 LOD 2.5 3.04 Difference ~140 MB VAS High res cockpit 2.97 Low res 2.77 Difference ~200 (!) MB VAS Scen. complexity sparse 3.11 Scen. complexity normal 3.18 Difference ~ 70 MB VAS Road traffic 30 2.71 Road traffic 0 2.66 Difference ~50 MB VAS Summarized: Turn down LOD and TML, use 512/1024 clouds. Building density sparse and (as a compensation) vegetation density max is also helpful. Use low res cockpit textures if possible. (Would be very helpful for the 777, PMDG :rolleyes:) Lowering scenery complexity might also help, especially on huge airports, but lowering it below normal can induce scenery problems.

Hi! In case you didn't know, you can easily "import" your old Sweetfx settings to ReShade/SweetFX 2.0. The values are nearly the same. At least my old SweetFX profile looks absolutely the same in Reshade. You can download my settings here: http://www.file-upload.net/download-10140147/SweetFX_settings.txt.html

So far it's stable on my system. No crashes and massive frame drops when accessing the menu anymore. (menu bar as well as right-click menu) But I'm unable to undock gauge windows (Feelthere Map gauge in my case) without loosing half of the framerate I had some hope that "ReShade" would also fix this...

Just opened my prepar3d.cfg after a very long time and... ooops...what do I see? TEXTURE_BANDWIDTH_MULT=1800 :huh: I will return to a value of around 200 (GTX970) Maybe I've finally found the source of those annoying micro stutters on my rig, so thanks anyway!

Hi Matias, at first I want to say thank you for this very helpful tool! I have a little idea for (possible) future versions: Maybe you can add an option to generate the sample file without the "//"? In the past I let them all active, so I didn't had to activate/deactivate the airports I want before flying. I've never seen any performance loss. But I've written a little batch-file which removes all //, so it's no problem at all Sebi

I've forwarded them the complete correspondance with FSPS (dev of Fiber Accelerator), including the "OK" for a refund. I've tested the free trial - some hours after purchasing, FSPS extended the free trial from 5x5 mins to 5x60mins.