Page 1 of 1

PostPosted: Mon Jul 28, 2014 11:48 am
by omitchell
Having an issue with ORBX NZQN and FSDT GSX. The issue is, it won't go active and goes into demo mode at this airport for some reason. Seems to be the only airport I am having an issue with, everything else is working fine. Anyone else had an issue with Queenstown? Googles not helping, have deleted and recreated the .pye, restarted couatl, still the same.

EDIT: Oh not totally true forgot couatl crashes anytime I try to load Flightbeams KSFO (Which oddly enough is one of their default airprots in GSX)

PostPosted: Mon Jul 28, 2014 2:44 pm
by Ian Warren
I'm about to reinstall NZSI .. have funny feeling this maybe an issue, I'm in no rush but with orbx products , everyone seems to get different issue and most of it is due to having the programs install previous and the required computer get rebuilt then in come the problems .

Currently flying and checking .. one big issue is if you FSX on a secondary HD example 'D' .. my FSX is now on a 'I' HD .. even directing it to that drive it still search's for that old placing , I believe this is were orbx switch really get mucked up and some cases simply will not do what they are spose to do.

PostPosted: Mon Jul 28, 2014 3:07 pm
by omitchell
Ian Warren wrote:
QUOTE (Ian Warren @ Jul 28 2014,2:44 PM) <{POST_SNAPBACK}>
I'm about to reinstall NZSI .. have funny feeling this maybe an issue, I'm in no rush but with orbx products , everyone seems to get different issue and most of it is due to having the programs install previous and the required computer get rebuilt then in come the problems .

Currently flying and checking .. one big issue is if you FSX on a secondary HD example 'D' .. my FSX is now on a 'I' HD .. even directing it to that drive it still search's for that old placing , I believe this is were orbx switch really get mucked up and some cases simply will not do what they are spose to do.


Prob is GSX not ORBX, NZQN is working perfectly (Even the apron textures), It's GSX that's not...

PostPosted: Mon Jul 28, 2014 3:18 pm
by Ian Warren
GSX do build on current scenery, biggest problem and the major cause issue with most is the elevation and your mesh settings, one thing you may want to play around with.

PostPosted: Mon Jul 28, 2014 3:58 pm
by omitchell
Ian Warren wrote:
QUOTE (Ian Warren @ Jul 28 2014,3:18 PM) <{POST_SNAPBACK}>
GSX do build on current scenery, biggest problem and the major cause issue with most is the elevation and your mesh settings, one thing you may want to play around with.


Ian, the problem is Couatl isn't recognizing the .pye file for the airport in it's own folder. It's nothing to do with the mesh or anything else, it's not even getting to that stage, it's the GSX engine.

PostPosted: Mon Jul 28, 2014 4:04 pm
by Ian Warren
omitchell wrote:
QUOTE (omitchell @ Jul 28 2014,4:58 PM) <{POST_SNAPBACK}>
It's nothing to do with the mesh or anything else, it's not even getting to that stage, it's the GSX engine.

I had it working fine after first release, it is the connection conflict and GSX/obrx and mesh's without realizing it you probably find GXS running underground .

PostPosted: Mon Jul 28, 2014 4:28 pm
by omitchell
Ian Warren wrote:
QUOTE (Ian Warren @ Jul 28 2014,4:04 PM) <{POST_SNAPBACK}>
I had it working fine after first release, it is the connection conflict and GSX/obrx and mesh's without realizing it you probably find GXS running underground .


It's working fine at every other ORBX airport I have running (And to test I resized a parking spot at Milford, parked a 737 and called a baggage loader). Apart from Flightbeam KSFO this is the only airport giving me an issue.

PostPosted: Mon Jul 28, 2014 4:36 pm
by Ian Warren
Solution : remove ORBX Queenstown , and you would GSX operating , elevations at Milford because close to water would be kept correct ... few have it running you want to ask what there mess settings are , this is what you find as the major cause orbx .

Have you your Mesh density settings ?

PostPosted: Mon Jul 28, 2014 4:50 pm
by NZ255
What do you mean by demo mode? It could be because QN is built with 2 AFCADs. One for GA (QZ) and one for commercial traffic (QN). So depending on the day GSX might select NZQN or NZQZ

PostPosted: Mon Jul 28, 2014 4:53 pm
by omitchell
NZ255 wrote:
QUOTE (NZ255 @ Jul 28 2014,4:50 PM) <{POST_SNAPBACK}>
What do you mean by demo mode? It could be because QN is built with 2 AFCADs. One for GA (QZ) and one for commercial traffic (QN). So depending on the day GSX might select NZQN or NZQZ


That could be something. The .pye is set for nzqn but if theres a double afcad working it could be getting confused... And by demo mode it means when you go to an airport you only get the 3 default airports as options on the menu not the actual GSX Airport services options you would with a fully functioning GSX.

PostPosted: Mon Jul 28, 2014 6:28 pm
by omitchell
NZ255 wrote:
QUOTE (NZ255 @ Jul 28 2014,4:50 PM) <{POST_SNAPBACK}>
What do you mean by demo mode? It could be because QN is built with 2 AFCADs. One for GA (QZ) and one for commercial traffic (QN). So depending on the day GSX might select NZQN or NZQZ


^^ DING DING DING ^^ We have a winner. I added a .pye for NZQZ as well as NZQN and presto, NZQN is now working perfectly. It was the double afcad hiccuping it. Thanks for spotting that one. Didn't know they had used two files for that airport.