FSDreamTeam forum

General Category => General Discussion => Topic started by: kozmicelly on December 18, 2012, 07:36:30 pm

Title: GSX seems to be working on other AFCAD than FSDT
Post by: kozmicelly on December 18, 2012, 07:36:30 pm
Hi Virtuali,

GSX seems to be working on other AFCAD than FSDT's.

What I've done recently are as follows;

1. Changed the OS XP32 to Win7,64. (clean install on SSD)
2. Installed FSX+Accelerator.
3. Installed All FSDT airports but Hawiians which I don't have.
4. Installed UTX-USA and GEX-North America.

What happened then, (KLAX B68)

1. Follow Me Car goes through buildings to the gate.
2. Marshaller is standing about 10~20ft right from the yellow line.
3. Select KLAX B68 from FSX airport menu, then a aircraft sits on the right place, meaning on the yellow line.
4. Disabled UTX and GEX, but didn't work.
[Added] 5. At KFLL I got a GSX message saying "Could't find valid AFCAD data.....".

I know this seems to be happening because of other AFCAD installed.
But I didn't install any other sceneries except UTX and GEX.
I tried to check duplicate(s) by Airport scanner, it worked on XP32 but not on Win7, I got error messages.

What, do you think, is my option(s) to take to solve this problem?  

Thank you in advance.

Kozmic (RJTT)
Title: Re: GSX seems to be working on other AFCAD than FSDT
Post by: kozmicelly on December 19, 2012, 08:23:22 am
Hi again,

Today I uninstalled every software relating to FSX and FSX itself.
And freshly installed only FSX, KLAX and GSX.
Tested the same procedure as my post above.
The result was the same, which means;

Using the airport menu of FSX, I went to KLAX B68 and tried to use GSX.
But GSX says something like "can't use GSX service in this position".

Then using GSX the gate menu, jumped to B68.
I could use GSX servies there, BUT I found my default A321 sitting about 45deg to the yellow line.

I can't guess what's the cause of this issue.

Any ideas?

Thank you

Kozmic
Title: Re: GSX seems to be working on other AFCAD than FSDT
Post by: virtuali on December 19, 2012, 01:06:57 pm
The "Customize parking position" option in GSX will tell you which AFCAD is in use by GSX.
Title: Re: GSX seems to be working on other AFCAD than FSDT
Post by: kozmicelly on December 19, 2012, 03:32:49 pm
Thanx !!

I'll give it a try and report it back.

Elly
Title: Re: GSX seems to be working on other AFCAD than FSDT
Post by: kozmicelly on December 19, 2012, 03:50:52 pm
At KLAX, the scenery file "APX16190.bgl" of FSX is used.

I know this file shouldn't be disabled, but I've tried it anyway.
As I guessed it, lots of error messege popped up, and the airport editor disappeared from the GSX menu.

What can I do ?

As for the airport scanner, there are 32bit version and 64bit version?
As I said in the first post, my AP Scanner gives me an error message.
Does this error message come from the wrong version?

If it's the case, how can I get another version?

Title: Re: GSX seems to be working on other AFCAD than FSDT
Post by: kozmicelly on December 19, 2012, 04:01:23 pm
OK, it was so simple. :-\

Used it as admin, it worked.

Thank you.
Title: Re: GSX seems to be working on other AFCAD than FSDT
Post by: kozmicelly on December 19, 2012, 04:27:25 pm
Sorry for posting so many times.

Airport Scanner shows no duplicate.
But the problem happens again.
Default A321 sits 45deg to the yellow line.

I'm at a loss. ???

What can I do?

Thank you.
Title: Re: GSX seems to be working on other AFCAD than FSDT
Post by: virtuali on December 19, 2012, 07:43:09 pm
Airport Scanner shows no duplicate.

That simply means your duplicate is a duplicate that the FSX airport scanner can't find.

Quote
But the problem happens again. Default A321 sits 45deg to the yellow line.

As I've said, ANY positioning problem it's ALWAYS a problem with a conflicting AFCAD. If the FSX Airport scanner can't find it, you must find it manually. Of course, my first reply already included a suggestion how to find it:

Quote
The "Customize parking position" option in GSX will tell you which AFCAD is in use by GSX.
Title: Re: GSX seems to be working on other AFCAD than FSDT
Post by: kozmicelly on December 19, 2012, 08:13:24 pm
As I wrote above,

 Quote : [At KLAX, the scenery file "APX16190.bgl" of FSX is used.
I know this file shouldn't be disabled, but I've tried it anyway.
As I guessed it, lots of error messeges popped up, and the airport editor disappeared from the GSX menu.]

Everything was all right on XP32bit, I wonder how come this happens on Win7 64bit. ???

If nothing can be done to solve this problem, I can only use FSDT KLAX or GSX, can't use both of them at a time.

Ummmmmmmmmm
Title: Re: GSX seems to be working on other AFCAD than FSDT
Post by: virtuali on December 19, 2012, 08:43:35 pm
Quote : [At KLAX, the scenery file "APX16190.bgl" of FSX is used.

Which explains why everything is off, that's the default AFCAD.

Quote
I know this file shouldn't be disabled, but I've tried it anyway.

It shouldn't be disabled because it contains default navaids and approaches.

Quote
Everything was all right on XP32bit, I wonder how come this happens on Win7 64bit. ???

Windows 7 is not a problem, we all use Windows 7 and most of users too.

Quote
If nothing can be done to solve this problem, I can only use FSDT KLAX or GSX, can't use both of them at a time.

As I've said, the problem doesn't have anything to do with GSX, if the positioning inside FSX is wrong, it's FSX that is being confused by the wrong AFCAD, way before and independently by the fact you install GSX or not. You will STILL have positioning errors, even without GSX.

It's possible you have a permissions account, which is causing problems with the scenery cache. Try this:

- Remove the folder C:\ProgramData\Microsoft\FSX\SceneryIndexes.

- Execute FSX As Administrator. You should see FSX rebuilding its cache at start. Then, GSX will do the same to rebuild its own. Let it finish, exit from FSX, enter it again, and check if it's now using the correct AFCAD.
Title: Re: GSX seems to be working on other AFCAD than FSDT
Post by: kozmicelly on December 19, 2012, 11:10:14 pm
I followed your instruction.

1. Delete the SceneryIndexes folder.
2. As administrator execute FSX.
3. FSX build SceneryIndes.

So far it went as your instruction.

4. Using default A321, went to KLAX.

I've seen so many times, before changing the OS, that GSX builds its own airport index, but this time GSX didn't build it.

I don't mean the cause of this trouble might be GSX or OS.
I just want to know the cause and the way to solve this problem.

It's 7:00 am, I've got to go to bed.
When I get up, I'll give it a try again.

Title: Re: GSX seems to be working on other AFCAD than FSDT
Post by: kozmicelly on December 20, 2012, 10:19:25 am
Continued :

The procedure you instructed didn't work today either.
Without any logical reasons, I installed about 20 payware sceneries except FSDTs (just because FSDTs take time to install), and tried the same procedure.
But the result was the same.

In the Couatl.log, there is a line, "Looking for scenery.cfg in C:/ProgramData/Microsoft/FSX/scenery.cfg"
and the list of the installed sceneries from the scenery.cfg.
But the list in the Couatl.log contains only FSX default sceneries, no payware sceneries.
Is this normal?

Just after the list, there are lines as follows;

Airport cache loaded
Addon GSX loaded
Loading addon ENBR
Addon ENBR not installed or missing one or more files, skipping
Loading addon KSFO
Addon KSFO not installed or missing one or more files, skipping
Loading addon KPHX
Addon KPHX not installed or missing one or more files, skipping
Starting system monitors
Current locale is Japanese_Japan.932
SharedMemInterface connected
Loading aircraft data from Airplanes\C172
aircraftDb.py provides aircraft data with priority 2
Using aircraft data from aircraftDb.py
Section [contact_points] contains invalid data at entry point.4
Loading airport KLAS from E:/Microsoft Flight Simulator X/Scenery/0202/scenery/APX17190.bgl
Loading airport LOWI from E:/Microsoft Flight Simulator X/Scenery/0601/scenery/APX51150.bgl
Loading aircraft data from Airplanes\Flight One ATR 72-500
Using aircraft data from SimConnect
Loading aircraft data from Airplanes\CLS_BAe146_200
intelliscene.cfg provides aircraft data with priority 1
Using aircraft data from intelliscene.cfg
Loading aircraft data from Airplanes\Flight One ATR 72-500
Using aircraft data from SimConnect
Loading airport LFPG from E:/Microsoft Flight Simulator X/Scenery/0601/scenery/APX48140.bgl

All the Loaded airport were FSX default bgls.
The payware LOWI and LFPG are installed, but used ones are FSX default bgls.

Are there any cues in this log file?

Thank you.
Title: Re: GSX seems to be working on other AFCAD than FSDT
Post by: virtuali on December 20, 2012, 11:08:09 am
But the list in the Couatl.log contains only FSX default sceneries, no payware sceneries.

Are you running FSX in "Compatibility mode" maybe ? If yes, turn it off, because it's wrong and it cause such issues with all folders becoming wrong.
Title: Re: GSX seems to be working on other AFCAD than FSDT
Post by: kozmicelly on December 20, 2012, 02:18:24 pm
"Are you running FSX in "Compatibility mode" maybe ?"

I've checked it now.
No, not in "Compatibility mode".
I never touched that tab.
Title: Re: GSX seems to be working on other AFCAD than FSDT
Post by: kozmicelly on December 22, 2012, 05:54:30 am
This issue seems to come from 2 problems. It's just my guess.

Judging from the Couatl.log ;
1. GSX reads only default bgls from the scenery.cfg.
2. What makes GSX do so is the second problem.

I think if my guess 2 is solved, this issue will be solved.

What do you think about my guess (or deduction) ?
Title: Re: GSX seems to be working on other AFCAD than FSDT
Post by: virtuali on December 22, 2012, 09:24:23 am
1. GSX reads only default bgls from the scenery.cfg.

No, GSX is reading the whole scenery.cfg, but it's reading the wrong one.

Quote
2. What makes GSX do so is the second problem.

Running FSX in compatibility mode might cause this. But also a permission problem with your account, that is writing scenery.cfg changes in the wrong folder.
Title: Re: GSX seems to be working on other AFCAD than FSDT
Post by: kozmicelly on December 22, 2012, 01:53:07 pm
Quote
No, GSX is reading the whole scenery.cfg, but it's reading the <wrong one>

Quote
Running FSX in compatibility mode might cause this. But also a permission problem with your account, that is writing scenery.cfg changes in the wrong folder

I've never run FSX in compatibility mode since Dec.14 2012, this is the date of having changed OS to Win7-64 and having installed FSX.

I searched all my SSD and HDDs, there are two scenery.cfgs.
One is in C:\ProgramData\Microsoft\FSX.
The other is in E:\Microsoft Flight Simulator X\. (this is the original cfg created when I installed FSX)

So, GSX doesn't read the "wrong one" .

As for permission, the files related to this issue are in "full control".

And FSX\SceneryIndexes contains 183 DAT files, the last one (Filelist00183.DAT) is about KSFO (Flightbeam).
The fact that the last one is about KSFO is the same as  the last one in scenery.cfg.

It's a little bit long, but permit me to C&P the latest Couatl.log ;

couatl v2.0 (build 2322)
log started on Sat Dec 22 21:11:50 2012 (of couse this is Japan Standard Time)

connecting to SimConnect...
connected to FSX
bglmanx non ready yet, waiting.
connected to bglmanx
Loading addons
requesting AddOn list to bglmanx
bglmanx list contains 17 AddOn(s)
Loading addon ZurichX
Addon ZurichX loaded
Loading addon OHareX
Addon OHareX loaded
Loading addon JFK
Addon JFK loaded
Loading addon XPOI
Addon XPOI loaded
Loading addon LSGG
Addon LSGG loaded
Loading addon KLAS
Addon KLAS loaded
Loading addon KFLL
Addon KFLL loaded
Loading addon PHNL
Addon PHNL not installed or missing one or more files, skipping
Loading addon KDFW
Addon KDFW loaded
Loading addon HAWAII1
Addon HAWAII1 not installed or missing one or more files, skipping
Loading addon HAWAII2
Addon HAWAII2 not installed or missing one or more files, skipping
Loading addon KLAX
Addon KLAX loaded
Loading addon ParkMe
Addon ParkMe loaded
Loading addon GSX
Initializing audio...
Available devices:
  Generic Software on ƒXƒs[ƒJ[ (High Definition Audio ƒfƒoƒCƒX)
Created OpenAL device: Generic Software on ƒXƒs[ƒJ[ (High Definition Audio ƒfƒoƒCƒX)

Device info:
   Major version: 1
   Minor version: 1
   Frequency: 44100
   Refresh: 40
   Sync: 0
   Mono sources: 255
   Stereo sources: 1
   Extensions: ALC_ENUMERATE_ALL_EXT ALC_ENUMERATION_EXT ALC_EXT_CAPTURE ALC_EXT_EFX

Context info:
   Vendor: Creative Labs Inc.
   Version: 1.1
   Renderer: Software
   Extensions: EAX EAX2.0 EAX3.0 EAX4.0 EAX5.0 EAX3.0EMULATED EAX4.0EMULATED AL_EXT_OFFSET AL_EXT_LINEAR_DISTANCE AL_EXT_EXPONENT_DISTANCE

Using EFX 1.0 extension, with 1 auxiliary send(s)
Using EAX reverb
Current directory is E:/Microsoft Flight Simulator X
Looking for scenery.cfg in C:/ProgramData/Microsoft/FSX/scenery.cfg
  using Scenery/World (layer 1)
  using Scenery/BASE (layer 2)
  using Scenery/0000 (layer 3)
  using Scenery/0001 (layer 4)
  using Scenery/0002 (layer 5)
  using Scenery/0003 (layer 6)
  using Scenery/0004 (layer 7)
  using Scenery/0005 (layer 8)
  using Scenery/0006 (layer 9)
  using Scenery/0007 (layer 10)
  using Scenery/0100 (layer 11)
  using Scenery/0101 (layer 12)
  using Scenery/0102 (layer 13)
  using Scenery/0103 (layer 14)
  using Scenery/0104 (layer 15)
  using Scenery/0105 (layer 16)
  using Scenery/0106 (layer 17)
  using Scenery/0107 (layer 18)
  using Scenery/0200 (layer 19)
  using Scenery/0201 (layer 20)
  using Scenery/0202 (layer 21)
  using Scenery/0203 (layer 22)
  using Scenery/0204 (layer 23)
  using Scenery/0205 (layer 24)
  using Scenery/0206 (layer 25)
  using Scenery/0207 (layer 26)
  using Scenery/0300 (layer 27)
  using Scenery/0301 (layer 28)
  using Scenery/0302 (layer 29)
  using Scenery/0303 (layer 30)
  using Scenery/0304 (layer 31)
  using Scenery/0305 (layer 32)
  using Scenery/0306 (layer 33)
  using Scenery/0307 (layer 34)
  using Scenery/0400 (layer 35)
  using Scenery/0401 (layer 36)
  using Scenery/0402 (layer 37)
  using Scenery/0403 (layer 38)
  using Scenery/0404 (layer 39)
  using Scenery/0405 (layer 40)
  using Scenery/0406 (layer 41)
  using Scenery/0407 (layer 42)
  using Scenery/0500 (layer 43)
  using Scenery/0501 (layer 44)
  using Scenery/0502 (layer 45)
  using Scenery/0503 (layer 46)
  using Scenery/0504 (layer 47)
  using Scenery/0505 (layer 48)
  using Scenery/0506 (layer 49)
  using Scenery/0507 (layer 50)
  using Scenery/0600 (layer 51)
  using Scenery/0601 (layer 52)
  using Scenery/0602 (layer 53)
  using Scenery/0603 (layer 54)
  using Scenery/0604 (layer 55)
  using Scenery/0605 (layer 56)
  using Scenery/0606 (layer 57)
  using Scenery/0607 (layer 58)
  using Scenery/0700 (layer 59)
  using Scenery/0701 (layer 60)
  using Scenery/0702 (layer 61)
  using Scenery/0703 (layer 62)
  using Scenery/0704 (layer 63)
  using Scenery/0705 (layer 64)
  using Scenery/0706 (layer 65)
  using Scenery/0707 (layer 66)
  using Scenery/0800 (layer 67)
  using Scenery/0801 (layer 68)
  using Scenery/0802 (layer 69)
  using Scenery/0803 (layer 70)
  using Scenery/0804 (layer 71)
  using Scenery/0805 (layer 72)
  using Scenery/0806 (layer 73)
  using Scenery/0807 (layer 74)
  using Scenery/0900 (layer 75)
  using Scenery/0901 (layer 76)
  using Scenery/0902 (layer 77)
  using Scenery/0903 (layer 78)
  using Scenery/0904 (layer 79)
  using Scenery/0905 (layer 80)
  using Scenery/0906 (layer 81)
  using Scenery/0907 (layer 82)
  using Scenery/1000 (layer 83)
  using Scenery/1001 (layer 84)
  using Scenery/1002 (layer 85)
  using Scenery/1003 (layer 86)
  using Scenery/1004 (layer 87)
  using Scenery/1005 (layer 88)
  using Scenery/1006 (layer 89)
  using Scenery/1007 (layer 90)
  using Scenery/1100 (layer 91)
  using Scenery/1101 (layer 92)
  using Scenery/1102 (layer 93)
  using Scenery/1103 (layer 94)
  using Scenery/1104 (layer 95)
  using Scenery/1105 (layer 96)
  using Scenery/1106 (layer 97)
  using Scenery/1107 (layer 98)
  using Scenery/AFRI (layer 99)
  using Scenery/ASIA (layer 100)
  using Scenery/AUST (layer 101)
  using Scenery/EURE (layer 102)
  using Scenery/EURW (layer 103)
  using Scenery/NAMC (layer 104)
  using Scenery/NAME (layer 105)
  using Scenery/NAMW (layer 106)
  using Scenery/OCEN (layer 107)
  using Scenery/SAME (layer 108)
  using Scenery/Cities/Oshkosh (layer 109)
  using Scenery/Cities/StMaarten (layer 110)
Airport cache loaded
Addon GSX loaded
Loading addon ENBR
Addon ENBR not installed or missing one or more files, skipping
Loading addon KSFO
Addon KSFO loaded
Loading addon KPHX
Addon KPHX loaded
Starting system monitors
Current locale is Japanese_Japan.932
SharedMemInterface connected
Loading airport KLAS from E:/Microsoft Flight Simulator X/Scenery/0202/scenery/APX17190.bgl
Loading aircraft data from Airplanes\C172
aircraftDb.py provides aircraft data with priority 2
Using aircraft data from aircraftDb.py
Section [contact_points] contains invalid data at entry point.4
updating working set
size of current working set: 0
size of queried working set: 100
number of obsolete pois:     0
number of pois kept from ws: 0
size of new working set:     100

The mystery goes deeper and deeper. ???
Title: Re: GSX seems to be working on other AFCAD than FSDT
Post by: virtuali on December 22, 2012, 02:05:22 pm
Quote
I've never run FSX in compatibility mode since Dec.14 2012, this is the date of having changed OS to Win7-64 and having installed FSX.

If you ran in compatibility mode when you installed those sceneries, they were installed into a different one.

Quote
So, GSX doesn't read the "wrong one" .

Yes, it does. Or, more precisely, it's reading the correct one at this time (when compatibility is not enabled), but that one doesn't contain the installed sceneries, because they were installed when FSX was running in compatibility mode.

Try to reinstall a scenery now, with FSX not running in compatibility mode, and see if the correct scenery.cfg gets updated and if GSX can read it.
Title: Re: GSX seems to be working on other AFCAD than FSDT
Post by: kozmicelly on December 22, 2012, 02:55:53 pm
Installed a little scenery, but no luck.

C&P the last few [Area]s in the new scenery.cfg.
The last one called "Whitehouse Lawn" is the one I've installed now.

[Area.206]
Title=FSDreamTeam Fort Lauderdale-Hollywood
Local=FsDreamTeam\KFLL
Active=TRUE
Required=FALSE
Layer=181

[Area.207]
Title=FSDreamTeam Chicago OHareX
Local=FsDreamTeam\OHareX
Active=TRUE
Required=FALSE
Layer=182

[Area.208]
Title=FlightBeam Phoenix Sky Harbor HD
Local=FlightBeam\KPHX
Active=TRUE
Required=FALSE
Layer=183

[Area.209]
Title=FSDreamTeam ZurichX
Local=FsDreamTeam\ZurichX
Active=TRUE
Required=FALSE
Layer=184

[Area.152]
Local=Flightbeam\KSFO
Title=FlightBeam KSFO
Required=FALSE
Active=TRUE
Layer=185

[Area.210]
Title=Whitehouse Lawn
Local=Addon Scenery\Whitehouse Lawn
Active=TRUE
Required=FALSE
Layer=186
...................................

As you can see, scenery files installed before "Whitehouse Lawn" were correctly installed and recognized by FSX.

Title: Re: GSX seems to be working on other AFCAD than FSDT (Solved!!)
Post by: kozmicelly on December 23, 2012, 02:45:23 pm
Solved  :D

As the last resort, I used the backed up scenery.cfg I had used when my OS was XP32.
And tweaked it deleting some Scenery Areas I didn't installed on newly installed FSX.

It worked !!

I don't know a logical explanation why this method worked.
Maybe something was wrong in the new scenery.cfg, but I don't know what it is.

Thank you so much, Vertuali, for taking your time and your effort, anyway.

Elly