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

I would try pushing the D key to reset the Direction Indicator... It looks like it might have been incorrect.

I found something strange... If I start P3D with the Duke and go to the GPS500 test page, it does not show the correct HSI needles. If I then switch to another plane with a GNS530 and go to the test page, it shows correctly. If I then switch back to the Duke and go to the test page, it works correctly there also.

Lets hope that RXP can comment, this looks like a bug. 😉

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

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