Lol, very classy.
Iāll test it again, and report. When it happened, I was doing the Cannon ball Run ( Not registered, as I had the Mod), so could not check it out .. just reload the whole plan again, and kept going.
Question - Can the GNS530 drive the Glideslope indicator on the DG in the Carenado Seminole?
I notice the NAV flag on the DG is red whether the GNS is in GPS mode or VLOC mode. The Course indicator is working however, IOW, centered when sitting on the runway and to the right when on left downwind.
(BTW, I just crashed about 5 minutes into a flight with the Seminole. My flight plan was KASH-KASH, and I had loaded the ILS14 Approach before takeoff, but not activated it. I was downwind on 14 passing LODTI when MSFS stopped, and sat there with no sound for about 2 minutes (I had had a similar issue in the Piaggo 149D when I was sitting on the tarmac, and after about 3 to 5 minutes, MSFS came back to life, so I was hoping for the same here), and then CTDād. There is nothing to say that it was caused by the mod, just reporting my experience. I was not doing anything with the GNS530 at the time, just flying along and descending because I overshot my altitude (hand flying, no AP)).
Unfortunatly this cannot help. A CTD is a kernel crash, not a jauge crash.
At our level we donāt have the kernel sources. Only a debugging of the kernel sources or a very verbose kernel log could help. We donāt have any of them.
No relationship between HSI and GPS. They both communicate with the same kernel but they are independant jauges.
The kernel is the engine. All jauges, including GPS communicate with it by receiving events (pilot actions) and exchanging some variables (ex plane position, flight plan waypoints, etcā¦).
For the CTD, I donāt know. The GPS is a central instrument on board but it cannot be the source of all the issues of this buggy software.
Thatās why itās important to try to reproduce an issue and to do many tests trying to isolate the problem with the minimum stuff. As soon as Iām sure the origin is the GPS, I can start debuggin at the GPS level and probably fix the bug (not always).
So is there any way to get the Glide Slope Indicator of the HSI to activate or follow Nav1 (or Nav2)? Carenado doesnāt give any documentation on whatās connected to what, and Iām new to GPS and HSIās. The other Nav indicator is being driven. Iām not sure if itās being driven by Nav1 or Nav2. I should have checked that.
Yeah, I was just reporting a CTD. I just got through two circuits with the Seminole⦠one where I iced up on the way down about 8 miles out and managed to still land on the runway with zero vision
, then melted the plane and did another circuit all the way through, was pulling into the parking space and bam, this time a pretty much immediate CTD. My guess is the problem is the Seminole with the latest update. This time I was observing the plane from the outside when it CTDād. Just reporting, I havenāt a clue whatās causing the CTD. Super fun plane to fly though, Iām starting to get the hang of it.
BUG Report: Limitation of 4 maps in cockpit for GPS systems.
Affects GNS530 and GNS430 ..
If we can get Asobo to fix this, then the GNS530 MOD, can proceed to support more maps !!!
The more Zen Desk Bug submission for this, the better ā¦
Demo Mod to show this created by @ScorpionFilm422
Even if the direct-to is a VOR, all data in the FP stops displaying.
maybe this is correct, because you are no longer ON the FP, so that on-route data is really meaningless.
The WPs are still there.
If you then select a WP, and activate the LEG, the all data for that leg and after comes .back.
All data prior to the current leg is lost.
I believe this was done to get around the āturn backā bug ?
or since the version where you hold the FP in memory and can write it back, to support adding a WP. (Asoboās bug that recently stopped adding WPs)
It really does not matter is past leg data does not display, ā just I am sure it use to ??
Maybe I need to refresh my memory, as to what the Garmin Simulator does ā¦
Sim & RW are getting mixed up in my head !!!
What do you mean by āall data stops displayingā
If you mean distances and DTK, itās normal.
When you are in direct To mode you are out of the flight plan and distances are not displayed.
The real GPS works like this.
If you are flying your flight plan, all the flew WP distances are not here anymore. Normal too.
This is the dynamic distance implementation I made as it is (nearly) in the real GPS.
@ScorpionFilm422 Just to let you know. I did few flights on 1.0.21 and everything works ok so whatever causes my CTDs is in the v.1.0.22
You would think with all these issues with the g530 and 430 ms would fix it already. Why they would release the sim before having the most common gps unit in aviation working properly I have no Idea. I would pay ms if they would just fix LPv so we could do proper gps approaches.
Is there any way of getting automatic notifications of new releases for this mod? An installer Ć la FBW would be nice, but I understand it involves a lot of work.

@ScorpionFilm422 Just to let you know. I did few flights on 1.0.21 and everything works ok so whatever causes my CTDs is in the v.1.0.22
Confirm this.. CTD in V22, not in V21.
I was on AP, KIAD - KBOS with some VOR WPs, .. left it running for an hour ā when I came back, it was CTD.
Left on NAV map 2 .. was not touching the sim, when it did its CTD.
Ran all 24 hours of the CannonBall Run, with V21, and was rock stable.
Running the same FP as I was running when it CTD in V22, now with V21.
Neither flight was Real Weather, so both flight should be quite similar. (No AI traffic either )
anyone got the link for 21?
I didnāt reproduce the issue.
The only difference I can see here between 1.0.21 and 1.0.22 is airspace messaging but I really donāt see what can make a CTD here.
Will set an option to disable this messaging in 1.0.23.
Interesting. As a matter of fact, I was skirting the edge of Class C in both my crashes. And I have yet to see any messages associated with the Class C airspace. Iāll look for them. Iāve been flying out of KASH, which is underneath the Class C of KMHT. And my crashes only happened with the Seminole. My third flight of the day with the Seminole did not result in a crash, (although I did keep a wider berth of the area on this third flight), and I did not get a crash with the Mooney, which I used for a couple of flights, and in that I followed pretty much the same path as the other flights, perhaps penetrated deeper into the class C airspace in fact.
Maybe Asobo broke their messaging around Class airspace?
Do you have to be in contact with Center for messaging about airspace to work maybe? (I wasnāt)
For the CTD guys. There is a topic addressing 3rd party apps crashing the sim when retrieving live traffic. Are you using Little Nav Map or other 3rd party apps when this happens? Are you running live traffic? Hereās the thread:
Another link discussing this issue. Not sure who/if any are looking into the issue.
NEW RELEASE 1.0.23
Available at: https://pms50.com/fs2020/gns530/pms50-gns530.zip
Changelog
v1.0.23
- Approach frequency automatically set to standby only if the current active frequency is different
- Official embedded and not modified 1.12.13.0 MSFS files
- Saving some GPS states between sessions: Northup/TrackUp, Data display in Map page and Channel spacing.
- Bugfix: auto reactivation of approach after a directTO was not always working after update 1.12.13.0
I take it back, just flew it again, and this time I saw messaging. Difference was this time I took off on 32 and turned right towards KCON (wow itās windy today), whereas yesterday, I was taking off on R14 and turning right crosswind and staying west of the airport as I turned northwest. So maybe I wasnāt close enough to trigger messages. (Iāve found you have to be within a mile or two it seems for airspace requests to trigger, although, I havenāt actually measured it).