Aerosoft CRJ 700/900 CTD

[Jer029]

Pete,

Sorry if this was asked elsewhere but couldn't find it.  I've been using the P3d V4 Aerosoft CRJ 700/900.  Clicking on the various PFD MFD screens can result in a sudden CTD without any error message or module listing in my windows error logs.  Aerosoft claims that this is related to FSUIPC and not their aircraft.  Can you enlighten me as to the status of this and where I should look for a solution?  It sounds like Aerosoft is done dealing with it.

On a likely unrelated note, I found and shared with Aerosoft continuous events occurring:

When checking fsuipc logging I've noted that the following items continually log for CRJ700:

 

480483 ***  AXIS: Cntrl= 65786 (0x000100fa), Param= 5406 (0x0000151e) SPOILERS_SET
480545 ***  AXIS: Cntrl= 65786 (0x000100fa), Param= 5406 (0x0000151e) SPOILERS_SET
480592 ***  AXIS: Cntrl= 65786 (0x000100fa), Param= 5406 (0x0000151e) SPOILERS_SET
480670 ***  AXIS: Cntrl= 65786 (0x000100fa), Param= 5406 (0x0000151e) SPOILERS_SET
480701 ***  AXIS: Cntrl= 65786 (0x000100fa), Param= 5406 (0x0000151e) SPOILERS_SET

.

.

.

and

 513695 *** EVENT: Cntrl= 65715 (0x000100b3), Param= 4608 (0x00001200) XPNDR_SET
 513742 *** EVENT: Cntrl= 66036 (0x000101f4), Param= 0 (0x00000000) AP_VS_VAR_SET_ENGLISH
 513742 *** EVENT: Cntrl= 66705 (0x00010491), Param= 0 (0x00000000) APU_OFF_SWITCH
 513742 *** EVENT: Cntrl= 65715 (0x000100b3), Param= 4608 (0x00001200) XPNDR_SET
 513773 *** EVENT: Cntrl= 66036 (0x000101f4), Param= 0 (0x00000000) AP_VS_VAR_SET_ENGLISH
 513773 *** EVENT: Cntrl= 66705 (0x00010491), Param= 0 (0x00000000) APU_OFF_SWITCH
 513773 *** EVENT: Cntrl= 65715 (0x000100b3), Param= 4608 (0x00001200) XPNDR_SET
 513851 *** EVENT: Cntrl= 66036 (0x000101f4), Param= 0 (0x00000000) AP_VS_VAR_SET_ENGLISH

They told me it's supposed to do that and just don't log them as the logging uses more processing than the events - then promptly closed my topic to further discussion.  Of course I knew that, but question the reasoning for continuous events occurring without me pressing any keys, and was a bit put off by their terse response and this CTD issue.

 

These things make me wonder if the AS CRJ 700/900 is worth keeping in my hangar.

Does the latest FSUIPC release address the CTD issue with the AS CRJ 700/900 ?

 

Thanks,

John

 

 

 

 

[Thomas Richter]

Hi,

FSUIPC doesn't know AS CRJ 700/900 aircraft. So it cannot handle anything of it. If, as aerosoft claims, FSUIPC is the problem why it doesn't happen with other add-on AC's?

Anyway. First thing to do is to disable FSUIPC and test the aerosoft aircraft. Disable FSUIPC you can do in the XML.dll or just by renaming the FSUIPC5.dll to i.e. FSUIPC5.old , so it will not be loaded.

Thomas

[Jer029]

Thanks Thomas,  I know how to disable files and where to find them.  Below is a post from another CRJ user and Aerosoft's response.  

So am I to understand it's an "either -  or" option on what we use?  

After writing an ACARS program that uses FSUIPC interface, am I to just tell my VA's pilots not to use FSUIPC or our ACARS program with Aerosoft CRJ and to manually file pireps?  Perhaps I need to rewrite my code to use only simconnect and leave FSUIPC.

Is this a dead issue for Lockheed Martin, Aerosoft and FSUIPC?

John

 

 

Posted yesterday at 02:22 PM

I have not been able to complete one flight yet using the new version 1.0.1.  The crash this time was attributed to menus.dll error.  Over at LM forums they say it may have something to do with FSUIPC and to try disabling this utility.  Seriously?  They also mentioned that the next hot fix may alleviate this error.  Anyone else experienced this?

 

Thanks.

 

Ilya

 

Yes, Lockheed traced that issue back to FSUIPC. I can confirm that. I never had that issue after disabling FSUIPC. It's NOT related to the CRJ in any way.

Mathijs Kok    22672

• Aerosoft Forum Administrator
•  

[Pete Dowson]

On 9/3/2017 at 3:56 PM, Jer029 said:

Of course I knew that, but question the reasoning for continuous events occurring without me pressing any keys

There are some add-on aircraft which operate many aspects of their relationship with the base simulation facilities in the simulator using the SimConnect EVENT system.  It can seem very inefficient (and does to me), especially when the repeated events are for the same values. It's as it it is trying to prevent external interference with thse values.

PMDG aircraft were always very heavy indeed with the numbers of events generated, which flooded the log so much as to make it unusable to find odd events more related to external programsor devices. That is why I added INI parameters to allow sepcific Events to be ignored.

On 9/4/2017 at 0:59 AM, Jer029 said:

Yes, Lockheed traced that issue back to FSUIPC. I can confirm that. I never had that issue after disabling FSUIPC. It's NOT related to the CRJ in any way.

No one has notified me of this -- neither Mathijs nor L-M!!!

I've no idea how it is possible for FSUIPC to cause an add-on aircraft to CTD. I've written to Mathijs asking for an explanation.

Pete

 

[Jer029]

Thanks Pete!

That last quote was from a post from Mathijs himself on his AS CRJ 700/900 forum.

Like many FSUIPC users, I have many addons that use this, and can work around the AS CRJ problem using EZdok Camera views to zoom in on the PFD, MFD, MCDU rather than clicking on them (which seems cause the random CTD for me).

 

I was simply trying to figure out who might still be looking into this and which forum to watch for a solution.  Based on the above quote from AS and related posts on their forum where they are encouraging the disabling of FSUIPC when using CRJ, I'm fairly certain that they have placed the issue squarely with FSUIPC and washed their hands of it so to speak.

Welcome back,

 

John