Sign in to follow this  
pkofman

530 crashing on second waypoint entry

Recommended Posts

My sim is continually crashing (fsx - se and p3dv3 ) when i try to create a flight plan. It always happens when i input the 2nd waypoint.. I always get a unhandled exception error....

I cannot create a flight plan from scratch... I can create a plan with as a  simple "direct to " plan but thats it . If i enter the second way point.the sim will stop responding , lock up and then crash within 30 seconds. I have the same issue with the minstar 530 in either fsx- se or p3dv3.

please help...

Peter

Share this post


Link to post
Help AVSIM continue to serve you!
Please donate today!

Disable FSUIPC and see if it works.

Share this post


Link to post

Disable FSUIPC and see if it works.

thats very interesting because i always thought i would need fsuipc to run 3rd party apps like this... 

thank you ill give it a shot

Peter

Share this post


Link to post

I decided to work through this issue  and did a clean install of fsx steam

I followed the following sequence;

 

firstly computer spect

w10 x64

steam drive F

p3dv3 drive G

 

removed and reinstalled fsx-steam

 

installed simconnect from within steam

 

installed mindstar 530

 

( i did not update the realnav data base )

 

At this point the sim fsx-steam did everything it was supposed to do and i was able to load a flight plan  with more than 2 waypoints into  the a2a 182. I did not have any sim crashes and the gps did its job and flew the plan.

 

then i continued and installed fsuipc 4.9  

 

**** this caused a problem and a conflict occurred in that  every time i ran the mindstar gps 530 and tried to enter more than 2 waypoints the sim crashed ****** I would get an exception error.

 

the problem occurs in my p3d v3 and i can duplicate it exactly as per the fsx-steam install per above...

 

i verified that fsuipc and the mindstar gps were in conflict because after the sim crashed i went into the modules folder and changed the file extension of the fsuipc .dll and fsuipc .ini ( in other words basically turning off fsuipc )  and things were again working perfectly the a2a aircraft and the mindstar 172

 

What I'm interested in finding out is if there is a work around so that i can have the mindstar product work with fsuipc 4.9. 

Please advise. 

 

Peter

Share this post


Link to post

As it is not our software crashing, there is little we can do.

 

I would recommend discussing this issue with Pete Dowson and/or Lockheed-Martin to obtain a resolution.

Share this post


Link to post

Ok thank you ed but i would suggest that it is a conflict between your software and other sim software. Rather than speaking to fsuipc and p3d ( all they are going to say is " it must be mindstars" software). is there a constructive way to resolve this or given your expertise is there an obvious solution that allows the mindstar 530 to work while the fsuipc is enabled. As you know Fsuipc is required for many other add ins so im wondering if there is a solution beyond disabling tFSUIPC software everytime i want to use the mindstar gps products

Please provide your thoughts 

Thank you

Regards   Peter

Share this post


Link to post

It is quite literally out of our hands.  There is nothing in our software that's actually crashing.  If our software works without issue with FSUIPC not loaded, then that indicates that FSUIPC is doing something that the sim doesn't like when you build a flight plan in our GNS units.

 

We are in full compliance with the sim's SDK and don't use any hacks/hooks/whatever.  We do that intentionally, so that we know that our code isn't invasive.

Share this post


Link to post

It is quite literally out of our hands.  There is nothing in our software that's actually crashing.  If our software works without issue with FSUIPC not loaded, then that indicates that FSUIPC is doing something that the sim doesn't like when you build a flight plan in our GNS units.

 

We are in full compliance with the sim's SDK and don't use any hacks/hooks/whatever.  We do that intentionally, so that we know that our code isn't invasive.

Ok thanks ED.  I just want to point out that this was happening in both fsx-se and p3dv3.. so it is not isolated to LM

I do not have enough knowledge of fsuipc 4.9 to determine a workaround other than to go into the module folder and rename the fsuipc .dll  file to something so that it does not load.  Maybe someone here can assist because i cannot be the only one who has purchased your software that has experienced this issue

Please advise and maybe you have discussed this with others who has figured this out

Peter

Share this post


Link to post

First, there's a thread right under yours... same issue.  Same result.

Second, if there were a solution, I would have already told you.

 

The only person who can figure this out doesn't work for Mindstar Aviation.

Share this post


Link to post

I have been informed that Lockheed-Martin may have provided a correction regarding this. Further information when I have it.

Share this post


Link to post

I have been informed that Lockheed-Martin may have provided a correction regarding this. Further information when I have it.

thank you ed ,,, that would be very constructive and helpful.. maybe i can also apply it to fsx-se.

lets see how it goes.. let me know what you might have something   Pete

Share this post


Link to post

I do not believe you can apply Lockheed-Martin code changes to FSX.

Share this post


Link to post

Using P3D v3.4 I've just installed the latest GNS 1.08.0021 (04Dec) and unfortunately there is still a CTD on entering a flight plan.
Hopefully LM have a fix soon to resolve this. Gary

Share this post


Link to post

Until Lockheed-Martin provides a fix, I can offer you the following thanks to Pete Dowson working with us:

 

Download this version of FSUIPC: http://fsuipc.simflight.com/beta/FSUIPC4958d.zip

There are two new FSUIPC.INI entries supported:

ProvideAIdata=Yes
ProvideAIairports=No
This should prevent the crashing until such time as there is a proper fix.

Share this post


Link to post

Thanks Ed - just tried it and sorry to say its not made a difference, I still have a CTD on FPL page when pressing ENT to load first waypoint. Hopefully LM can come up with something sooner rather than later - fingers crossed!

Share this post


Link to post

Are you running third party navaid update scenery?

Share this post


Link to post

I'm running your own mindstar NavData but also the Navigraph data too. The crash occurs with the Carenado C177, the C90 and their C340 - should I try other aicraft where I'm running the Mindstar GNS series but without a Carenado add on? Please let me know if I can do some testing on other types. The Carenado aircraft were installed using a registry tweak - not the Estonian tool, so this is possibly the issue? My crash occurs using EGPH (Edinburgh UK) and selecting UW (NDB 368) as the first waypoint from a 24 departure. Both EGPH and the UW NDB are old established waypoints (from 1970 something?) so I'm assuming it's not a new WP issue? I can test it on any of the A2A aircraft or let me know if there is a type you want me to try it on. Also using ORBX Global and Scotland scenery as the base layer with UK2000 EGPH layered above. Windows 10 and P3D v3.4.

Share this post


Link to post

Initial feedback on the fix:

I downloaded and replaced the .dll file in my P3D modules folder. I then added "ProvideAIdata=Yes

ProvideAIairports=No" to the FSUIPC4.ini file. The fix works! I'm going to do more testing to make sure everything continues to work, but so far so good. Thanks to all parties involved in the fix, I've been waiting to use my GNS for a while now. 

 

Using A2A Cessna 182. No third party scenery installed right now. Prepar3d 3.4 (without the latest hotfix installed.) Windows 10 64 bit.

Share this post


Link to post

I thought these paramaters were part of the FSUIPC file? Obviously not - I'll adjust and report back.

Gary

Share this post


Link to post

Many many thanks!! PHMUdreamin all sorted now, Ed sorry I didn't realise I had to manually add these to the .ini file.

Great to have the Mindstar GNS back again!!

Share this post


Link to post

Hi,

 

I have the same Problem. I have a CTD with GNS530/430 upon Waypoint entry in FPL. I downloaded suggested Fsuipc and applied the corresponding fixes in the .ini file but it is not working. I am using https://www.aero.sors.fr/navaids3.html as I need corrected frequencies for training purposes. Any suggestions?

 

Regards

Share this post


Link to post

You'll have to remove the navaid stuff from aero.sors.fr as it causes crashes. Nothing we can do to resolve whatever the error in those files are.

Share this post


Link to post

Hi Ed,

 

thanks for the reply. As you know P3D and FSX are both a variation of using multiple add-ons and every now and then an incompatibility pops up. You always try to answer every question asked, thank you for that. But in this case it might be very helpful to ask the aero.sors.fr guy what could cause the problem. For us end-users it is just a crash we see when using the Mindstar GNS, even though it might not even be related -as you stated.

 

Greetings

Share this post


Link to post

As I have stated, the only correction possible on our end is to remove the offending files.  While I appreciate that someone might think we should be helping other companies/individuals fix their products... that is not something we have the time or resources to pursue.

Share this post


Link to post

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this