sab12

Thanks to those who replied to this topic. I tried to proceed with your guidance and suggestions and hit an unexpected snag. When I used the media creation tool to download Windows 11 onto a USB drive and then tried to do the upgrade to Windows 11, I was not given the choice for saving my files and/or apps. This is a known problem but with many possible and, to me at least, obscure reasons/fixes and no guarantees that any of them will actually work. It did give me a message that it was going to wipe out everything and a box to verify that I understood that for which I am grateful. At the moment I am trying to decide whether to try to fix this snag or just bite the bullet and clean install. Have any of you encountered and overcome this problem? Thanks, Stephen

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

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

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 Dan and Michael, Based on your helpful responses, it appears that my expectation that every descent would begin right on path was not realistic and that "normal" would include descents already in need of some intervention. Thanks for convincing me that I haven't been doing something wrong and encouraging me to and helping me develop my piloting skills Stephen Bickford