BuddhistManX

DRZEWIECKI DESIGN - UUEE MOSCOW SHEREMETYEVO X V2 - FSX P3D MiG29SMT / FLYFREESTD - MIG 29/35 FULCRUM FAMILY FSX/P3D Orbx Global Buildings HD Prepar3D setting Options - Display - Image and Texture Quality - Texture Resolution: Very Low - 256x256 All textures of MOSCOW CITY X - MIP1 fix Global Buildings HD used Lorby SI's AO to change the registration priority to high; Central's automatic registration ignored Global Buildings HD's texture due to its low priority. All other Orbx add-ons are turned off. SKY FLYER HANGAR's DIGITAL RUSSIA CENTRAL FEDERAL DISTRICT P3D causes a significant drop in frame rate. Is it incompatible with v5? The music is the theme from the 80's Japanese Armageddon anime. No deep meaning

No, no. I just introduced a paid preset for ReShade. I wasn't familiar with shaders for DX12, so I tried it. I uploaded a modified ground polygon file and an exclusion file that erases the default objects on the four runways included in the LSGK Saanen Airport for FSX & Prepar3D.

After taking off for the first time in a long time, I noticed that there was no shadow on the runway and fixed it. In v5, the default runway object was also displayed. LSGK_Patch.ZIP

Try replacing the following files in 0S9. It seems that there was a problem with the compilation settings of the GP file. ORBX_0S9_GroundPoly.ZIP

The overall taste of this add-on is not bad, but I get the impression that the lighting of the aircraft is incomplete. The navigation light on the top of the fuselage illuminates the cockpit, brightening the panel even during the day. Also, the current P3D landing light effect (fx_landing.fx) doesn't illuminate the light source, so it looks like the light source isn't lit even at night. When I checked the exterior model with Model Converter X (MCX), the effect fx_AH_white.fx was assigned to the light source of the landing light. However, this effect is omitted. I have resolved these to the extent that users find it customizable. Fx_AH_white.fx included in the attached zip file is a point type light source effect. It was created with MCX and has no dynamic light effect. Place it in the following folder together with fx_AHrecog_red.fx. (If installed in C: \ Users \ username \ Documents \ Prepar3D v4 (v5) Add-ons \) Aeroplaneheaven Hurricane MK1 \ Effects Also, rewrite the [lights] section of aircraft.cfg in the following folder. Aeroplaneheaven Hurricane MK1 \ SimObjects \ Airplanes \ AH_Hawker_Hurricane_Mk1 \ aircraft.cfg [lights] // Types: 1 = beacon, 2 = strobe, 3 = navigation, 4 = cockpit, 5 = landing //light.0 = 4, -3.53, 0, 0.62, fx_vclight light.1 = 3, 1.850000, -18.28, -1.200000, fx_navredh light.2 = 3, 1.850000, 18.28, -1.200000, fx_navgreh light.3 = 3, -6.350000, 0.000000, 2.600000, fx_AH_white light.4 = 3, -5.650000, 0.000000, -2.300000, fx_AHrecog_red fx_navredh and fx_navgreh are slightly larger light sources. This will depend on your taste. Finally, I made some modifications to the model file. Aeroplaneheaven Hurricane MK1 \ SimObjects \ Airplanes \ AH_Hawker_Hurricane_Mk1 \ model.Mk1 Open AH_HurricaneMK1_PBR_exterior.mdl in the above folder with MCX (it may take some time to open). Remove the following two effects with the Attached Object Editor. attachpt_AH_white_43 attachpt_AH_white_42 These effects are not needed as they are set in aircraft.cfg. attachpt_navwhih_40 For this, the light source installed on the ladder is too strong, so change the effect name to fx_navwhi. After making the above changes, export it as an mdl file for v4.4 with MCX. This may also take some time. Let's wait patiently. Don't forget to back up the files you change. Once you've mastered all these steps, you'll be able to fix the lights on older aircraft, such as the FSX generation C172 and Beaver. fx_AH_Hurricane.zip P.S. Lockheed Martin \ Prepar3D v4 (5) SDK x.x.xxxxx \ Modeling \ Special Effects \ Visual FX Tool If you copy this folder to the user folder, you can start the effect tool with [tools] on the menu bar and visually check the effect. I opened the .fx file with a text editor and studied the contents a little, and I also learned the troublesome work. C: \ Users \ username \ Documents \ Prepar3D v4(5) Add-ons

Incidentally, the cause of the RW27 crash is probably EGLC_Airport_buildings_RW in the library PBR_EGLC_Buildings.BGL. There may be some invisible error in the concrete platform mounting condition of the bridge object on the RW27 side. Exporting EGLC_Airport_buildings_RW from the library to .mdl in MCX and removing only the RW27 bridge object platform in the Attachment Editor may be a good first aid measure. Then save it as .bgl for v4.4. Delete EGLC_Airport_buildings_RW on the library side. If you don't like flying with no crash. When I check the Aircraft of my favorite add-on on the MCX, I find that I have a huge crash box and I flinch.

Sorry. Simply removing the script file will make the default airport altitude file bad. This can be resolved by adding the following CVX file to the scenery folder. It seems that accurate ground altitude is difficult for runways with seawalls. Aircraft tires remain a little sunk. to EGLC London City Airport\Orbx\FTX_EU\FTX_AA_EGLC\Scenery download cvx file

EGLC, not EGCL? Impatient I ported the v4 EGLC folder to v5 in an attempt. src_EGLC_BLACK01.lua src_EGLC_BLACK02.lua src_EGLC_CONCRETE01.lua src_EGLC_GREY01.lua src_EGLC_SOIL01.lua If anything other than the above files is removed from the scripts folder, EGLC will not look noticeably strange in v5.

In Central, when the AS EGLL is unticked in the FTX ENG configuration, the FTX ENG EGLL disappears. I don't have AS EGLL though. The new FTX ENG v5 version of EGLL looks like the object data(FTX_ENG_EGLL_objects.bgl) is completely wrong.

I noticed that in v5, if you do not delete the following files, KORK will be displayed in duplicate. This is due to an update of airport data in P3D v5(1M1 to KORK). p3dv5\Global Airport Pack\Orbx\FTX_GLOBAL\FTX_FTXG_AIRPORTS\Scenery\ADE_FTX_FTXG_1M1.BGL