ToniH

You need to make some registry information modifications to make Config Tool work. Add new key folder to HKEY_LOCAL_MACHINE\SOFTWARE\Lockheed Martin called "Prepar3d v4" and then add 2 new string values into folder. The first string value needs to be renamed License and modify string value, if you have "Academic" version you need to put "Academic" into string value( License - Academic) The second one string value need to be renamed SetupPath and modify string value to ex. "D:\Prepar3d v4", that will cheat Config tool to think that you have Prepar3d v4 installed and it works fine.

Is there any news when this next version of P3D v4 comes out?

Realism shader pack settings are these: Terrain and Shadows: - Terrain brightness: High - Shadow intensity: Medium Autogen: - Enable autogen brightness setting: enabled Clouds: - Enable Cloud shade with alternative popcorn fix: Enabled HDR: - Step 2 enabled P3d v3.2 settings in HDR - Brightness setting is: 1.10 - Bloom: 1.00 - Saturation 1.20 I also have Reshade installed and im using default DX11 settings.

I made some adjustments for my P3D, it's now perfect for me. Not too dark cockpit anymore.

Flying from TAPA to TFFF. Everything looks nice in my P3D now. Thank you for making this addon

Yes we talked in your forums for this coming PC upgrade. I ordered yesterday new computer parts into my PC, on next week the big project starts Thank you for your help very much

Well, it was totally small thing that caused the problem, the Prepar3d.cfg in Appdata/Roaming/Lockheed Martin/Prepar3d v3 folder, i removed that, P3D made new and all works fine Thank you for helping me

Im going to make total PC Hardware upgrade on next month, so i will leave my Diamond now into the hangar and fly when the pc upgrade is done. I will then reinstall all to fresh and clear HDD, so im very hopeful that all these problems are gone then

But i have installed latest P3D version of Diamond using the wrapper That is the funny thing, the problem is only in gauge registration, eaglesoft gauges works fine, the only one what does not work is KAP 140. After the plane install, the KAP installer starts, it copies all files and after i close the KAP installer, there comes activation screen and quickly goes away, There might be registry complications between my earlier FSX Diamond KAP 140 install. I uninstalled FSX and FSX diamond after the P3D install. I have reinstalled plane many times now, still no luck. I have now two exe files in my P3D folder, the original Prepar3d.exe, and Prepar3d.exe renaimed FSX.exe. When i want to fly Diamond, i use fsx.exe.

Hi I have problem using KAP 140 , couple days ago the gauge worked fine, but yesterday the gauge started saying that Gauge is not Registered. I have reinstalled plane many times yesterday, i found that when i renamed Prepar3d.exe to FSX.exe, gauge works fine, but when i rename gauge back to Prepar3d.exe, gauge not work? Where should i start to find fix for this problem?

I think the issue is not brakes, cos if i pull Throttle tu Full. Nothing happens, RPM does not rise etc, only warning sound i hear.

Thanks your great Tutorial Caio, i will test NGX using yours procedures. I hope i finally can start flight using -700 series B737.

I tested this tutorial, nothing still happens.http://www.youtube.com/watch?v=eX95TdEHH3c

Ok, thanks i will try this tutorial video. I think i messed up whit the APU systems before engine start.

All ground thinks are removed, chokes too. :( Nothing happens. Maby i need reinstall all models again. I hope this will remove the issue.