Jump to content
Sign in to follow this  
Mapex

Back to square one

Recommended Posts

I'm going to try to stay as calm as possible about this but it's quite frankly unbelievable...

So after the whole Navigraph shenanigans before v1.2.2.3 I was pretty happy to find out that the issue had been sorted but coming back to the CRJ in v.1.2.3.0 with the AIRAC1902 and to find that the FMC has AGAIN stopped taking my Origin Airport in the FPLN Page, as pre v1.2.2.3, is just a joke.

I guess there is not much to add except that I'm running on FSX Boxed and unlike with others I'm not getting a CTD. It just takes the ICAO for half a second, pops the EXEC message for half a second and then deletes the entrance.

If you need anymore info feel free to ask while I bang my head against the wall and think of what I could've done with those 50€ and the many hours of lost time during the last 2 years.

I'd like to add that it did work perfectly fine before v.1.2.3.0 having the time of my life in this (when it works) fantastic add-on but that a reinstallation of the product hasn't fixed the problem.

I also guess that Aerosoft will not allow me to get my hands on the old version I suppose, since that would be too easy.

 

Sorry for the passive aggressiveness but even the most calm people will lose their patience and I've been very patient for 2 years now.

Share this post


Link to post

I'm not sure what to say, but I tested it and it works just fine. Here's a video with FSX SP2, CRJ SP1a (1.3), FSUIPC 4.974 and Navigraph AIRAC 1902. The default situation is a Cessna 172 at Münster/Osnabrück (EDDG). The only other add-on installed is Ultimate Traffic live.

 

Video proof:

 

As you can see, it works just fine on a clean FSX. If it doesn't on your system, then it's something non-standard or a configuration issue. I attached the situation files as well as all information about my system. May be you can find something.

 

FSX version info:

FSX_Version.PNG

 

My startup situation files: C172 EDDG 07.zip

 

And finally the whole set of version information for my PC: ASVersionInfo.TXT

 

 

 

Share this post


Link to post

Got myself a cup of tea and got myself calmed down.

Thanks for the quick reply.

I loaded your scenario up and the CRJ did indeed respond, as expected so it definitely seems to be a problem on how my sim starts up. I guess it's time to take back all the mean things I said 😅

It gets more interesting though. I was able to find the cause for the problems.

 

So after about an hour of testing and loading and closing FSX down over a dozen times with different variations (FSX native standard flight / your situation defined as the standard flight) I was able to figure out that the positioning of the Aircraft was off by .1 on the POS INT page. I was also able to figure out that this only happens, when the parking brake is not automatically triggered on loading in to the sim. The difference between those two "standard flight situations" is, that with the trike the parking brake is not triggered automatically while it is on the Cessna. FSX seems to load up the start up procedure of the default aircraft regardless of if it's ever been loaded up into the sim.

 

I guess it sounds a bit confusing (since I am terrible at explaining) so I'll quickly record a video and show my findings off.

But basically my guess is that the CRJ is having issues dealing with that very first load up, because the aircraft was still moving while initializing the systems.

So the work around for this is to use the Cessna as the default aircraft in the User interface. It doesn't even have to be used for the first load in to the sim.

 

I'll post the video as soon as possible to clarify what I am trying to say.

Share this post


Link to post

It still doesn't explain to me, why the update made the add-on break on this unfortunately though.

Here is the video:

 

 

 

Share this post


Link to post

Yes, FSX acts a bit weird on startup. It seems that if you load a complex aircraft from the Free Flight window, the simulator is not completely initialized and running when the aircraft becomes active. That can cause some strange behavior and seems to have been fixed in Prepar3D. The easiest solution to this kind of problem is to simply load the default C172 at some airport first and then switch to the aircraft and airport you actually want to fly.

Share this post


Link to post

Starting FSX SP2 in the default Cessna the best practice to avoid problems with add-on aircraft.

 

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  

×
×
  • Create New...