Board index FlightGear Support Flying

Issues with NAV1 on PA34 - FlightGear 2018.3.2

Controlling your aircraft, using the autopilot etc.

Issues with NAV1 on PA34 - FlightGear 2018.3.2

Postby hmt1 » Thu May 28, 2020 10:47 pm

Hi

Might anybody know why the NAV1 compass reading on the PA34 shows is showing 70 degrees less than the physical heading? As you can see from the posted image, I am at KHVN and lined up on runway 32 (320 degrees) while my NAV1 shows a heading of 030 degrees.

You can also see that I am lined up on the 305 radial on 109.8 at NAV1. For some reason, NAV1 has the red HDG tag sticking out, which I think means the reading has error in it and cannot be relied on.

I have no other issues on the plane - at least not that I can see.

Is this an issue for me only or generally known or a new thing? A search within Flying, however, did not show any threads with both "PA34" and "NAV1".

Operating Specs:
Dual Xeon; 12 GB
Windows 7 Enterprise
FG 2018.3.2
KHVN

Any help would be appreciated.

Thanks.

HMT1


Image
FG Call Sign : HMT1
Base Airport: London Gatwick EGKK.
Planes: Cessna 172P & 182RG, Piper PA-28 Cherokee II & PA-34 Seneca II.
hmt1
 
Posts: 65
Joined: Sat Feb 20, 2010 8:24 pm
Location: East Anglia, England
Callsign: HMT1
Version: 2018.3.2
OS: Windows 7 Enterprise

Re: Issues with NAV1 on PA34 - FlightGear 2018.3.2

Postby WoodSTokk » Fri May 29, 2020 12:24 am

On my 2018.3.2 it is working.
But on 2020.2.0 it's not working because of a nasal error.
WoodSTokk
 
Posts: 543
Joined: Tue Oct 17, 2017 2:30 pm
Location: Milky Way/Sol/Earth/Europe
Callsign: OE-WST
IRC name: WoodSTokk
Version: 2020.3.0
OS: Debian Buster

Re: Issues with NAV1 on PA34 - FlightGear 2018.3.2

Postby hmt1 » Fri May 29, 2020 2:02 pm

Hi WoodSTokk,

Thanks for that insight.

Your experience suggests a likely local issue for me rather than a general one, especially since none raised it except me. I'll reinstall and see how it fairs.

HMT1
FG Call Sign : HMT1
Base Airport: London Gatwick EGKK.
Planes: Cessna 172P & 182RG, Piper PA-28 Cherokee II & PA-34 Seneca II.
hmt1
 
Posts: 65
Joined: Sat Feb 20, 2010 8:24 pm
Location: East Anglia, England
Callsign: HMT1
Version: 2018.3.2
OS: Windows 7 Enterprise

Re: Issues with NAV1 on PA34 - FlightGear 2018.3.2

Postby WoodSTokk » Sat May 30, 2020 12:50 pm

I think its more a race condition between C++ core and Nasal scripts.
There is a message in the console because of non existend properties, but if i look into the property browser, the properties are there.
So i think the script will access the property at a time where the core has not fully populate the property tree.
The result of the race condition differs from computer to computer because of performance.
On some computer it works (FG 2018.3.2 here) and on another not (FG 2018.3.2 on yours and FG 2020.2.0 here).
WoodSTokk
 
Posts: 543
Joined: Tue Oct 17, 2017 2:30 pm
Location: Milky Way/Sol/Earth/Europe
Callsign: OE-WST
IRC name: WoodSTokk
Version: 2020.3.0
OS: Debian Buster

Re: Issues with NAV1 on PA34 - FlightGear 2018.3.2

Postby hmt1 » Sat May 30, 2020 10:15 pm

Hi WoodSTokk,

That is a plausible insight indeed. It could explain why at different times my NAV1 headings seem SLIGHTLY differently offset from the actual magnetic headings the plane is aligned on.

Little can be done, seems to me, is the gist of it. I have a similar issue with 2018.3.5 - so this is likely a machine specific issue as you note. Interesting but puzzling.

Thanks all the same.

HMT1
Last edited by Johan G on Fri Jul 03, 2020 7:21 am, edited 1 time in total.
Reason: Please, do not quote the entire preceding post. It is right above your post.
FG Call Sign : HMT1
Base Airport: London Gatwick EGKK.
Planes: Cessna 172P & 182RG, Piper PA-28 Cherokee II & PA-34 Seneca II.
hmt1
 
Posts: 65
Joined: Sat Feb 20, 2010 8:24 pm
Location: East Anglia, England
Callsign: HMT1
Version: 2018.3.2
OS: Windows 7 Enterprise

Re: Issues with NAV1 on PA34 - FlightGear 2018.3.2

Postby hmt1 » Wed Jun 03, 2020 12:06 am

UPDATE.

I received a PM on the issue I had originally raised.

My original post referred to a misalignment of NAV1 with the actual geographical heading on PA34 - Flight Gear 2018.3.2. This issue has now been replicated by someone else. It conjecture is that this issue might stem from a possible issue with the PA34 code, following an upgrade. The person maintaining the aircraft has been contacted and hopefully it has joined their to-do list. :)

Seeing as this is not a major problem, I suspect we will see an update some where down river.

HMT1
FG Call Sign : HMT1
Base Airport: London Gatwick EGKK.
Planes: Cessna 172P & 182RG, Piper PA-28 Cherokee II & PA-34 Seneca II.
hmt1
 
Posts: 65
Joined: Sat Feb 20, 2010 8:24 pm
Location: East Anglia, England
Callsign: HMT1
Version: 2018.3.2
OS: Windows 7 Enterprise


Return to Flying

Who is online

Users browsing this forum: No registered users and 3 guests