CTD when using GPS
-
@RetiredMan93231 Thanks for the info!
That does it! I'm also removing the mod and will see if I get stable flying back. I so want(ed) it not to be causedd by the mod, because it's so much better than the stock 530, but I seem to have tried everything else with no success.
If my problem is the mod, I'm mystified as to why. I've used it for many many months, with no apparent issues. Then two things happened: I started flying the JF Piper v1.3 instead of 1.2, and Asobo released their hotfix. After that, I've had crash-fest galore... So why it would be the mod, I don't know - but now I'll try it and report back.
-
@theissondergaard Could it be that Asobo's hotfix iintroduced a conflict with the GNS530 mod. Might that explain why the mod was working OK for you before? Just a thought ...
-
Pretty sure the mod has nothing to do with it. It simply reads and writes data from/to the sim in a common way, I don't see anything particularly special in what it's doing especially compared to mods like the FBW A32NX.
But I'm curious about your feedback.
It could as well be that we all have different reasons of CTD which would result in no common findings. Hard to tell.Anyone flying another aircraft than the JF PA28R and having CTDs as well?
-
@copper said in CTD when using GPS:
Anyone flying another aircraft than the JF PA28R and having CTDs as well?
I was not having CTD's prior to installing the GNS530 Mod... and it not occur with other aircraft. But, I do have CTD's on rare occasions when I try to configure a second new flight without first completely quitting to the desktop and restarting MSFS.
-
"Unfortunately", so far so good without the mod. Completed 3 flights from parking to parking without any ctd. I put everything back to my normal configuration, meaning AI traffic on, live weather, ground aircrafts in airports, a full community folder etc. Only thing changed is that I'm not running the 530 mod.
Still too early to conclude for me, though. I did also have 3 flights a few days ago, with the mod, only to then have it crash on me multiple times. I'll need to log at least 2 more days without crashes - and then I'll want to put the mod back and have crashes, before I'm willing to blame it :)
Also, I had happily forgotten how much the stock 530 is lacking.... :crying_face:
-
@RetiredMan93231 I know this is quite a lot to ask :) But given how immediate and consistent your problems were with the mod, I was wondering if you'd be willing to put it back in, and then take some flights with another aircraft using the 530, like the 172 classic, or the Mooney from Carenado, provided you have one of those. Would be very interesting to see if it's a problem across aircrafts (which I'd assume it is).
Also, very sorry for recommending the mod to you in the first place :anxious_face_with_sweat: I swear, it used to work very very well, and it's so much better than the stock 530 :D
-
@theissondergaard , Thanks for the recommending this mod originally, it has much more functionality than the default 530, and when they get the CTD problem fixed I plan to add it back in...
Have you had any more CTD's since removing it...? Also, I have not reported this bug to the Author... have you?
-
"Have you had any more CTD's since removing it...?"
I have not, but also only had 3 flights today without it. It's too early for me to say for sure, I'll need a few more crash-free days :)I have told the author of the mod about this thread and that some of us suspect a problem with the mod. I've posted his response in this thread already, but here it is again.
-.-.-.-.-.
Difficult to answer here. I got CTDs myself with or without the GNS530 MOD. A CTD is always a kernel crash and not a MOD issue written in javascript. We hope Asobo to make the kernel not crashing in any way as far it is possible. Now , the kernel may crash following some orders sent by a MOD (that places the kernel in crash condition).
Sometimes you may have also a temporary freeze especially when selecting a waypoint. This comes back after seconds. Again here, this is at kernel level. I can't do anything.
If the CTD occurs while you don't do anything with the GNS530 buttons, this will be difficult to analyse and it may be caused by many internal events, even with something not related to the MOD. Try to disable traffic here since it may cause hazardous conditions.
Any CTD sequence that can be reproduced will help. Don't hesitate to send them to me (but well checked and not a 3hours flight!). Be sure also to read the bug reporting section of the documentation.
Nothing changed here since 1.0.29. The only difference between 1.0.29 and last version 1.0.31 concerns some minor things and the OBS implementation. Nothing that can cause a CTD here.
-.-.-.-.-.IF I do get more crash-free days, I intend to reach out to the author again with "stronger evidence" :) His problem is of course that it's very very hard for him to reproduce, since it's not obviously triggered by some specific action.
-
For me it's difficult to reproduce, because (luckily) I got CTDs not very often. I guess, it's a combination of the G530 with the altitude hold. I'm not sure, but in my opinion, I only get CTDs when I use the autopilot including the altitude hold, I do not remember any CTDs without the altitude hold, so when I'm flying at VATSIM, I always avoid to use the altitude hold.
I use the G530 Mod in the 1.0.32 Version
Best regards,
Sandy -
A happy update from my side, to anyone following this thread :)
The good news is that I'm now completely crash-free for 4 days running, and that I have a solid idea of what my issue was.
The "bad" news is that it turned out to have absolutely nothing to do with the Piper, the GNS530 mod, AI traffic, Community folder or any of the many other suspects I've had during this annoying period.
It turned out that my culprit was double-configured peripherals. I use flight controls from Virtual Fly, and they have their own calibration software that they recommend using for mapping the peripherals. They also strongly advise to NOT at the same time configure the peripherals within the sim. An advise that I had followed, but for some reason forgot about again sometime recently in the past.... (The problem is that the sim will get simultaneous and confusing signals from the peripherals, causing conflicts)
I'm honestly not quite sure when or especially why it happened, but around the time I started getting CTDs, I must have somehow gotten the yoke, rudder and tpm configured in both places.
I only noticed the problem because sometimes (perhaps 3 out of 20?), when the sim crashed to desktop, the Virtual Fly software would also pop up and tell me it quit with an error. Most crashes would be without any kind of accompanying message, but a few times I saw this. First I ignored it (great!), but third time it happened I started digging in to a possible connection.
In my case, the fix to ALL my problems was simple: Remove the in-sim configuration of my peripherals, to remove the conflict, and now I'm crash-free. I run with all my "old" mods installed, my normal settings with lots of live traffic etc.
It's very possible as @copper stated that people in this thread have widely different reasons for the crashes they experience, and we just happen to find each other because we're in this forum :)
-
@theissondergaard Congrats on figuring out what's causing your CTDs.
What Virtual Fly calibration software are you using? I have the Yoko+, TQ6+ and Ruddo+ and I've seen their VFTest&Calibrate-S for P3D and their VFTest&Calibrate-X for Xplane but nothing for MSFS 2020. When I e-mailed them only last week they informed me that they are still working on VFTest&Calibrate for MSFS 2020 and they expect to release it in about 4 weeks time (i.e. about 3 weeks from now). So I'm curious to know what you are using?
-
@Sender46 You can download the beta version from here:
https://www.virtual-fly.com/es/msfs2020-faqWorks fine for me (just DON'T double configure the devices :D ) Right now, I only use it for the pedals (for softer toe-brakes) and the TQ6+ (for feathering). The yoke and vernio work quite fine just with MSFS configuration for me.
-
@theissondergaard Excellent, thank you for that :) Strange that VF support didn't tell me about that when they answered my e-mail. Wanting softer toe brakes is exactly why I e-mailed them.
