Can I see shots of cargo aprons and cargo hangers? I always believe in airport sceneries with superb cargo aprons and cargo hangers.

 

If you go here: http://www.simflight.com/2013/11/09/review-taxi2gate-mmmx-mexico-city-xtreme-fsx/

 

It gives you lots of pics of cargo. 

 

 

I so concur..if I have give an award to a vendor who has improved so much is Taxi2Gate....they pretty much went from Imaginesim to Fly Tampa lite in such a short period. 

 

They need to do a U.S city... New York X by Drzewiecki was horrible, maybe Taxi2gate can use their talents....

It always amazes me that people will pay for software with known problems, and no resolution in sight. It causes problems for the rest of us when people sing the praises of a badly designed product.

 

If I had known about the object collision issues I wouldn't have purchased. The developer didn't even mention in the release notes.

 

My new creed:

I will no longer support/ buy from developers that do not fix/finish their products. It's exhausting reading several forums to determine which patch is imminent, non existent, or DOA.

Ahhhhh... Phoooo.. T_T   I was hoping to get Mexico City for my VA flights that touchdown in Mexico City but this airport would be useless to me as I fly every flight with FSPassengersX turned on and that Add-on forces Crash Detection even if you switch it off when playing in expert mode which I do.   Dang it!  Patch yo STUFF!

 

 

you can turn it off in fs pax..

 

find this file: more option.cfg or something like it

 

here is mine:

// more_option.cfg

// In this file are value that allow you to tune, adjust enable 

// or disable somes function or penality of FsP that are not 

// listed in the setup dialog of FsP because they will be used 

// rarely and only by a few users... (or are CHEAT !!!)

 

// WARNING: DISABLING PENALTIES OR REALISM VALUE MAY COMPLETELY

// DEFEAT THE PURPOSE OF FSPASSENGERS! THERE IS NO GLORY TO WIN 

// WHEN THERE ARE NO CHALLENGES, IT MAY ALSO CAUSE SOME PROBLEMS

// WITH SOME FEATURES (CASE OF CRASH DETECTION FOR EXAMPLE)

 

 

// Penality disable ("=0" penality enabled "=1" penality disabled)

 

Disable250KtsUnder10000ft =0; // disable the 250kts speed below 10'000 ft penalty

DisableRollOutsideLandingStrip =0;   // disable the roll or landing outside landing strip penalty

DisableGearSpeedLimit =0; // disable gear speed penalty

DisableFlapSpeedLimit =0; // disable flap speed penalty

DisableOverspeedLimit =0; // disable overspeed penalty

DisableGLimit =1; // disable G penalty

DisableBankLimit =1; // disable bank penalty

DisableTailStrike =0; // disable tail strike penalty

DisableReverseThrust =1; // disable reverse thrust less than 60kts penalty

DisableDoorCheck =1; // disable door open penalty

DisableFlapCheck =1; // disable flap not set penalty

DisableTimeAccelerationCheck =1; // disable time acceleration reduced bonus

DisableMaxPowerPenaltyWithBrake =1; // disable the penalty for pushing max power with parking brake.

 

 

// FsP force realism value of your aicraft to true even if not set in fsx menu

// you can disable this forcing below by puting "1" instead of "0".

 

DisableForceCrashDetection =1; // disable the "force crash detection" feature of FsP

DisableForceCollideDetection =1; // disable the "force collide detection" feature of FsP

DisableForceStressCauseDamage =0; // disable the "force stress cause damage" feature of FsP

DisableForceGeffect =0; // disable the "force G effect" feature of FsP

 

 

// Other options ("=0" disable "=1" enable)

 

AvionicBusAlwaysPowered =0; // force avionic power to ON for aircraft that may cause problem

EnableTimeModificationInFlight =0; // enable access to Fsx time dialog when in flight

DetectSpeedRollOff =35; // Speed at wich FsP start to detect if you roll off landing strip

 

 

NOTE: Disable payload weight update (for example if you use some PMDG aircraft) has been moved to payload dialog. See "flight & aircraft setting" button.

 

 

 

 

 

 

 

 

 

the parts that are in bold.. change those to a =1

then turn off crash in fsx menus

 

then fly with fspax.. fspax will not force it on..

 

you will still get blown tires if you land to hard and you will know if  you crashed or not.. you can allways check your landing rate in the report.. I've been doing it this way for a while.. and it works well.

Those stupid tire blows! gggrrrr.

Fspassengers is so un-realistic anyways..

Fspassengers is so un-realistic anyways..

 

At what?  @_@   Simulating passengers being onboard?  I think it does that quite nicely as well as the whole business side of the program.  It is a little accident happy.   Even with accidents set at 1% I tend to get them more often than I think I should with a good maintained plane but the alternatives on the market don't do what I need them to do.  Hopefully SimAIR from REX will be a new updated choice but until I there is another program that simulates PAX onboard and allows me to operate the business as well as the host of other features I truly enjoy in FSPAX, that's what I'll be using.      

 

Thanks for the tip on how to turn off the forced detections.  This will allow me to fly on VatSIM one of these days.  However, that is still a crutch and the creator of MMMX needs to patch this shoddy part of the code rather than forcing people to alter other 3rd party programs to accommodate their mistakes.

At what?  @_@   Simulating passengers being onboard?  I think it does that quite nicely as well as the whole business side of the program.  It is a little accident happy.   Even with accidents set at 1% I tend to get them more often than I think I should with a good maintained plane but the alternatives on the market don't do what I need them to do.  Hopefully SimAIR from REX will be a new updated choice but until I there is another program that simulates PAX onboard and allows me to operate the business as well as the host of other features I truly enjoy in FSPAX, that's what I'll be using.      

 

Thanks for the tip on how to turn off the forced detections.  This will allow me to fly on VatSIM one of these days.  However, that is still a crutch and the creator of MMMX needs to patch this shoddy part of the code rather than forcing people to alter other 3rd party programs to accommodate their mistakes.

Agree

Is anyone experiencing ctd/ high vas usage to this airport on flights of 3 hours or more with the NGX?

 

I have made 3 flights from cyvr and a rock stable install with multiple addons and so far I'm 3/3. This is after the update...

Yes, I routinely get FSUIPC warning chimes after landing at this airport with the NGX, although so far I haven't been able to actually crash it (must be staying just on the right side of the edge of an OOM).

 

James

Just a heads up to you all but all Taxi2Gate sceneries (except MCO) are on sale at Simmarket until January.

The problem is that their website has been down for the last couple of days.

 

I cannot buy Mexico City, because the necessary patch is available on their website.

The problem is that their website has been down for the last couple of days.

 

I cannot buy Mexico City, because the necessary patch is available on their website.

 

Or you can just buy it from Simmarket while it is on sale and then wait for the website to come up to get the patch.  The download version from Simmarket may also include the patch.

Yes, I routinely get FSUIPC warning chimes after landing at this airport with the NGX, although so far I haven't been able to actually crash it (must be staying just on the right side of the edge of an OOM).

 

James

Due to the large size of this scenery (1.3GB) it is no wonder you're pushing the VAS limit while using the NGX (or any other complex airliner for that matter)

Due to the large size of this scenery (1.3GB) it is no wonder you're pushing the VAS limit while using the NGX (or any other complex airliner for that matter)

 

Disk space has nothing to do with memory usage...

Disk space has nothing to do with memory usage...

I knew I was walking into this one. And a response like this is why I hate even mentioning anything about VAS. Then the debate that ensues after the fact due to fellow simmers being confused at what VAS really is.

 

Virtual Address Space has nothing to do with memory usage or disk space.

 

So with that out of the way, here we go again....

 

VAS is a limit of the 32bit FSX.EXE application, with a 32bit OS you get 2GB with a 64bit OS you get 4GB. No more, no less....

 

So you can see that a scenery tilting the scales at 1.3GB takes a big chunk out of that maximum 4GB limit (if you're using a 64bit OS like the poster is). Once you run out of your 4GB limit within the FSX.EXE you get an OOM error and crash.

 

An explanation of how this works can be found here

 

http://msdn.microsoft.com/en-us/library/windows/desktop/aa366778(v=vs.85).aspx

 

Why do you think it is everyone is wanting a 64bit version of FSX? The reason is so we can get rid of that dreaded 4GB limit.