sab12

Deleting the config files in AppDate\Local\ and reinstalling FLASHLIGHT did the trick. Thanks, Stephen

I was running Flashlight successfully (P3d v5.4) until I recently deleted Navigraph's Simlink. After the deletion, the remnants popped up a message about having to start Simlink manually and also Flashlight would not start at all. I got rid of that message by cleaning up some left over Simlink files but, after uninstalling Flashlight and reinstalling it, the Flashlight window opens for a second or two then closes completely. This happens both in P3d and if I just try to start Flashlight from the Start menu. I have the proper settings in P3d per the user manual. Cure or suggestions would be appreciated. Stephen

Even if the engines are running when you start the Dauphin, if you go to the Control Automation Panel (shift + 1) and click the Ready To Fly box, the GPS, attitude indicator, etc. turn on and the Dauphin is completely ready to fly. Steve

Hi Al, So this issue has to wait for if/when a hotfix is issued for P3Dv5.4 by Lockheed Martin? I assume that this also means that there may be new issues with other aircraft that worked before v5.4? Stephen

The C:/P3D/P3Dv5 drive

Hi Al, Your initial suggestion did not help. Will look at your most recent suggestions. Thanks, Stephen

Al. I appear to have the problem you describe with the Payload Manager. I can adjust fuel but not passengers or cargo. Stephen

Hi Al, Thanks for your response. I must admit with some embarrassment that I have been unable to replicate the conditions I posted about. My best surmise is that I unthinkingly loaded the 35A on top of another plane that was already running and that messed a few things up. The 35A is running beautifully in P3Dv5.4. Didn't want to leave any question of possible issues..... Thanks, Stephen

I was using P3Dv5.3 HF2 when I bought and installed the Flysimware Learjet 35A. I have what I believe to be the latest version of the 35a (4.3c) and I am using it with the latest version of the Reality XP 750. There may have been problems with these things that I may have missed but when I upgraded to v5.4 I noted the following: (1) On startup, the mach trim warning light is on and I do not know how to turn it off. (2) The DME guages no longer seem to work for either Nav 1 or Nav 2 Is anyone else experiencing these things? Do you know of fixes? Thanks, Stephen

I just updated to the latest version of RXP GNS 530W/430W V2 and whatever the issue was that caused the problem described in this post has apparently been fixed. Steve

Thanks to ggerolamo and Rogen. With their guidance and suggestions, weather radar in FSW Learjet 35A works beautifully. Steve

Sorry. Found it. Steve

What do you search for in the AVSIM Library to find Roland's Radar? I tried RolASNRadar abd got nothing. Thanks, Steve

Do the mods described above to use the RolASNRadar with FSW Learjet 35A work with AS P3D? Thanks, Steve

Hi Bert, I tried this with my Twin Otter + GPS 530 and Duke B60 + GPS 500 and had the same experience as you did. On reload, the Duke worked correctly after the Twin Otter was loaded. In addition to the HSI needles working correctly, the GPS 500 worked properly while I completed the flight. Agree that RXP definitely needs to look at this. As I mentioned in my original post, the Duke B60 + GPS 500 was working properly when I reinstalled it after a clean reinstall of Windows 10 in Summer of 2022.and I believe there was at least one and perhaps two updates of the GPS 530 between my reinstall of the Duke and the next time I tried to fly it in 2023. Thanks for your help. Steve

Has something changed in recent updates to the GNS 530/430 V2 500 variant? Last summer, I did a complete rebuild of my Windows 10 operating system. I reinstalled both P3D V4.5 HF2 and P3D V5.3 HF3. I installed my RealAir Duke B60 V2 in both with the latest RealityXP GNS 500 variant per the instructions and modifications provided by Bert PIeke. It was working in both versions of P3D. However, I did not fly the Duke again until last week. In the interim, I did multiple updates to keep Windows 10 up to the latest version. After updating to the latest RXP GNS 530/430 V2 last week, I tried flying the Duke in P3D V5. I used a flightplan in the GNS that has an initial DTK of 251 degrees. With the flightplan loaded and activated and the instrument panel NAV/GPS on GPS, the course indicator on the HSI was pointed to 251 as expected but the popup on the course indicator said that it was set to 340. After taking off and using the heading bug set to 251 and the autopilot set to HDG to get near the desired GPS course, when I switched the autopilot to NAV, it flew the 340 course. The same thing happens in the P3D V4.5 installed Duke. Any idea of what changed? This is the .ini I am using: [GPS_500_1] ; is the master device if true. MasterDevice = true ; connects to: 'PFC_STACK','PFC_430','PFC_530' or any '#PID' (#D002 for PFC_430) ; no value connects to first found, 'OFF' disables connection. HardwareDevice = ; hardware selector number or -1 to disable. HardwareIdx = -1 ;connects GPS to HSI if true LinkHSI = true ;connects GPS to Autopilot if true Link0to = true ;Uses Simulator GPS commands if true UseSimGpsCmds = true [GPS_500_1.DEFAULT] ; show screen only gauge if true. nobezel = false ; screen only border size (pixels). border.size = 0 ; screen only border color (#RGB or #RGBA). border.rgba = #000000 ; display mouse tooltips if true. tooltips = false ; enable mouse clickspots if true, disable if false. usemouse = true ; enable alternate click-spots (left CCW, right CW, middle Push) if true. usealtmouse = false ; auto-resize dimension (width,height) refsize = ; left mouse button on the screen toggles popup window by ident (ex: GPS_PANEL or 225). popleft = ; right mouse button on the screen toggles popup window by ident (ex: GPS_PANEL or 225). popright = ; adjust brightness (0 to 100) brightness.bezel = 100 ; offset brightness (-100 to +100) brightness.screen = 0 [GPS_500_1.VC] ; show screen only gauge if true. nobezel = true ; screen only border size (pixels). border.size = 0 ; screen only border color (#RGB or #RGBA). border.rgba = #000000 ; display mouse tooltips if true. tooltips = false ; enable mouse clickspots if true, disable if false. usemouse = true ; enable alternate click-spots (left CCW, right CW, middle Push) if true. usealtmouse = false ; auto-resize dimension (width,height) refsize = ; left mouse button on the screen toggles popup window by ident (ex: GPS_PANEL or 225). popleft = ; right mouse button on the screen toggles popup window by ident (ex: GPS_PANEL or 225). popright = ; adjust brightness (0 to 100) brightness.bezel = 100 ; offset brightness (-100 to +100) brightness.screen = 0 Thanks, Stephen

This is posted in the X-Plane forum which is not the right place for a P3D issue. Sorry - Please ignore. Stephen

Has something changed in recent updates to the GNS 530/430 V2 500 variant? Last summer, I did a complete rebuild of my Windows 10 operating system. I reinstalled both P3D V4.5 HF2 and P3D V5.3 HF3. I installed my RealAir Duke B60 V2 in both with the latest RealityXP GNS 500 variant per the instructions and modifications provided by Bert PIeke. It was working in both versions of P3D. However, I did not fly the Duke again until last week. In the interim, I did multiple updates to keep Windows 10 up to the latest version. After updating to the latest RXP GNS 530/430 V2 last week, I tried flying the Duke in P3D V5. I used a flightplan in the GNS that has an initial DTK of 251 degrees. With the flightplan loaded and activated and the instrument panel NAV/GPS on GPS, the course indicator on the HSI was pointed to 251 as expected but the popup on the course indicator said that it was set to 340. After taking off and using the heading bug set to 251 and the autopilot set to HDG to get near the desired GPS course, when I switched the autopilot to NAV, it flew the 340 course. The same thing happens in the P3D V4.5 installed Duke. Any idea of what changed? This is the .ini I am using: [GPS_500_1] ; is the master device if true. MasterDevice = true ; connects to: 'PFC_STACK','PFC_430','PFC_530' or any '#PID' (#D002 for PFC_430) ; no value connects to first found, 'OFF' disables connection. HardwareDevice = ; hardware selector number or -1 to disable. HardwareIdx = -1 ;connects GPS to HSI if true LinkHSI = true ;connects GPS to Autopilot if true Link0to = true ;Uses Simulator GPS commands if true UseSimGpsCmds = true [GPS_500_1.DEFAULT] ; show screen only gauge if true. nobezel = false ; screen only border size (pixels). border.size = 0 ; screen only border color (#RGB or #RGBA). border.rgba = #000000 ; display mouse tooltips if true. tooltips = false ; enable mouse clickspots if true, disable if false. usemouse = true ; enable alternate click-spots (left CCW, right CW, middle Push) if true. usealtmouse = false ; auto-resize dimension (width,height) refsize = ; left mouse button on the screen toggles popup window by ident (ex: GPS_PANEL or 225). popleft = ; right mouse button on the screen toggles popup window by ident (ex: GPS_PANEL or 225). popright = ; adjust brightness (0 to 100) brightness.bezel = 100 ; offset brightness (-100 to +100) brightness.screen = 0 [GPS_500_1.VC] ; show screen only gauge if true. nobezel = true ; screen only border size (pixels). border.size = 0 ; screen only border color (#RGB or #RGBA). border.rgba = #000000 ; display mouse tooltips if true. tooltips = false ; enable mouse clickspots if true, disable if false. usemouse = true ; enable alternate click-spots (left CCW, right CW, middle Push) if true. usealtmouse = false ; auto-resize dimension (width,height) refsize = ; left mouse button on the screen toggles popup window by ident (ex: GPS_PANEL or 225). popleft = ; right mouse button on the screen toggles popup window by ident (ex: GPS_PANEL or 225). popright = ; adjust brightness (0 to 100) brightness.bezel = 100 ; offset brightness (-100 to +100) brightness.screen = 0 Thanks, Stephen

Have had several 32 bit Eaglesoft planes in the past and have been hoping that you would finally get into the 64 bit arena with a quality corporate jet. I say welcome back and hope that your beta testing will be quick and smooth so that those of us who aren't so concerned about updating our navigation data frequently will finally have an Eaglesoft jet to fly again in 64 bit LM P3D. Steve

Hi vadriver, G-RFRY, and jimcarrel, Thanks for your responses. I am where I am in flight simming today after a start in the first MSFS a long time ago. I jumped to Steam after Microsoft bailed out. I stayed with Steam until Lockheed Martin jumped in and made the leap to 64 bit a while back. As you can tell from my post, I have collected a number of what I consider to be the best quality add-ons along the way.. Rather than starting with the basic P3D graphics and weather facilities, I have put in PILOTS, Orbx, HiFiSimulations, and other add-ons without giving LM's offerings a real try. Rather than using LM's standard aircraft, I have put in several RealAir (still working in 5.3 HF2) planes, PMDG. FSLabs, Majestic Dash-8, Vertx and Reality XP, In some cases, I have had to wait for the developers to catch up with LM's changes. I have been fortunate to mostly escape the scourge of CTD's and gotten reasonably stutter-free performance with reduced slider settings and increasing CPU and GPU upgrades. I generally haven't done much with trying to fine tune things. As noted in my post, for me v5.3 HF2 is a really noticeable improvement. I basically want to fly not tinker but I also don't want to be doing anything aggressively dumb in the way I'm set up or using P3D. I'm also in no hurry to jump to the latest MSFS or X-11. As jimcarrel noted, I am happy but still wanting to make improvements to my Legacy simming world where they are available. Steve

Hi Ray, Thanks for your response. My monitor has a refresh rate of 60. Wondering if I should use the Nvidia Control Panel and set Vertical Sync to Adaptive (half refresh rate) to get to 30. If I did this, I would assume that I don't have to turn on Vertical Sync in P3D graphics but I still need to set frame rate to unlimited? Steve

I have successfully installed P3Dv5.3 HF2 and have all my addons working. The improvement in smoothness and lack of stuttering (I'm not an FPS chaser) with PMDG and FSLabs aircraft, AIG aircraft, and the highest slider settings I have ever been able to use is breath-taking. My CPU is an Intel Core I9 9900 and my GPU is an Nvidia RTX 3060 with 12GB Vram. With the exception of the Vertx Diamond DA-62, Vram usage is no more than half of what I have. Minimum FPS with a 40 fps cap is 15 even in airports like FlyTampa Boston. I have PILOTS 2020 Ultimate Mesh, ActiveSky P3D, ORBX Global Base, Global Buildings, Global Terra Flora, Global Trees, Global Vector, Open LC North America, PNW, Drzewiecki Design Seattle X, and many other ORBX, FlightBeam, FlyTampa, and LatinVFR add-ons. (1) Is there a guide for tuning this latest version of P3D with Nvidia GPU for additional margins in lack of stuttering? I still get occasional microstutters but not any more long pauses. (2) It appears from my forums reading that the ORBX TrueEarth US Washington provides significant improvement in visual rendering. If I install, do I have to deactivate some of the other ORBX add-ons or does the TrueEarth overlay what it doesn't use? Thanks, Steve

Hi Roesti, Thanks for your reply. Will try doing it this way.

I finished re-installing my P3D V5.2 HF1 after a clean re-installation of Windows 10 not long before V5.3 was released. I installed everything I could in the User Documents Prepar3D v5 Add-ons folder and all my Orbx things into their Library. My AIG traffic files are also outside of the P3D root folder. This left me installing my PMDG 777 and 737, Aerosoft Twin Otter, Majestic Dash8Q400, F1 Cessna Mustang, PILOTS FS Global Ultimate 2020, etc. in the P3D simulator root folder. Since I have had good luck with V5.2 HF1, I decided to wait a bit on V5.3 It looks like the positive reaction and experience with V5.3 HF2 is that I will want to install it. Should I wait a bit longer perhaps? The instructions for the P3D V5.3 installation are to uninstall V5.2 HF1 completely and do a complete install of V5.3 HF2. I am assuming that the things outside of the V5 root folder will be left alone. Is there a way to do this without losing the things installed into the P3D V5 root folder or are they collateral damage to progress? Are the instructions I have seen in this forum about deleting the shaders folder and the P3d.cfg folder before running the new installation still recommended? Thanks, Stephen

BTW - Another observation. In V5.2 HF1, if I start the default aircraft and then start the Scout Tundra, the HSI is visible on the panel of the Tundra. Stephen