Author Topic: Two problems with GSX  (Read 7485 times)

Wildhawk

  • Newbie
  • *
  • Posts: 6
Two problems with GSX
« on: January 30, 2015, 02:52:20 pm »
Hi virtuali,

I was hoping you could give me advice on how to solve the following two problems:

1. De-icing
I ran the full installer of GSX (ver 1.9.0.2),  and everything works fine,  except that I never get the option for the de-icing.
- I don't use any weather programs at all (ASN, Opus, etc)...have never installed such programs on my PC
- I go to FSX weather settings,  enter a temperature manually,  ensuring it is under 4 deg Celsius
- There is only one temperature layer,  and the temperature is then displaying correctly on the aircraft panel

2. Aerosoft Airbus A319 compatibility
I use the latest Aerosoft A319 (CFM version),  which should be covered by GSX ver 1.9 when looking at the compatibility list,  but it is not working properly.  When I request catering,  it will only start if I open the cargo hold. It asks for "exit 1", "exit 2" etc,  which I learned means it is not using the build in values.
- I went into the aircraft configurator and reset everything (have not done any customization anyway)
- There are no "gsx.cfg" files in the aircraft's main folder under Simobjects/Airplanes
- definitely no files under the Roaming/Virtuali/GSX folder,  in fact I do not even have an Airplanes subfolder here at all.

Is there anything I perhaps overlooked?

virtuali

  • Administrator
  • Hero Member
  • *****
  • Posts: 51462
    • VIRTUALI Sagl
Re: Two problems with GSX
« Reply #1 on: January 30, 2015, 03:00:52 pm »
I ran the full installer of GSX (ver 1.9.0.2),  and everything works fine,  except that I never get the option for the de-icing.

That's an old version ( current one is 1.9.0.6 ), but it should work just the same. Is the airplane you are using too small, with a wingspan of LESS than 22 meters ? If yes, you can't have deicing with it, for the time being.

Quote
When I request catering,  it will only start if I open the cargo hold. It asks for "exit 1", "exit 2" etc,  which I learned means it is not using the build in values.

This means the airplane hasn't been recognized. Do you use a new airplane variant ? What's the precise name of the airplane folder ?

Wildhawk

  • Newbie
  • *
  • Posts: 6
Re: Two problems with GSX
« Reply #2 on: January 30, 2015, 03:17:15 pm »
Thank you for the quick response...

No,  the aircraft I have tested so far are the PMDG NGX and Aerosoft A319. So it should work,  no?
I can try ver 1.9.0.6 but since 1.9.0.2 should also work,  as you say,  but I wonder if whatever is preventing the de-icing from appearing,  will not do the same with the newer version as well.

Is there anything else I can double check with regards to this issue?


To be specific I use Aerosoft's Airbus A319 version 1.2 which was released recently (I think last month sometime?),  the name of the aircraft folder is "Aerosoft Airbus A319 CFM"
(Does this corresponds with the name that GSX looks for?)

virtuali

  • Administrator
  • Hero Member
  • *****
  • Posts: 51462
    • VIRTUALI Sagl
Re: Two problems with GSX
« Reply #3 on: January 30, 2015, 03:22:15 pm »
No,  the aircraft I have tested so far are the PMDG NGX and Aerosoft A319. So it should work,  no?

Yes, all of them will work.

Quote
I can try ver 1.9.0.6 but since 1.9.0.2 should also work,  as you say,  but I wonder if whatever is preventing the de-icing from appearing,  will not do the same with the newer version as well.

I don't think that's the issue, however it's always best to be sure you have the very latest version. Try to trash ALL your GSX preferences, by removing this folder:

%APPDATA%\Virtuali

Then reinstall, and use only the current version of the installer.

Quote
To be specific I use Aerosoft's Airbus A319 version 1.2 which was released recently (I think last month sometime?),  the name of the aircraft folder is "Aerosoft Airbus A319 CFM"

That's exactly the folder name GSX expects. I'm sorry, but the only possible explanation the airplane is not recognized, is that you still have a GSX.CFG you made (or downloaded), either in the %APPDATA%\Virtuali folder OR in the airplane root folder, alongside the aircraft.cfg

You can verify this by enabling Logging in the "Troubleshooting" section of the "GSX - Settings" page. Select the airplane, then exit from FSX and check the Couatl.LOG file, it will tell you from which source the airplane configuration comes from.

Wildhawk

  • Newbie
  • *
  • Posts: 6
Re: Two problems with GSX
« Reply #4 on: January 30, 2015, 04:57:08 pm »
I have now done the following:

I installed GSX version 1.9.0.6
I also deleted the complete "Virtuali" folder under Roaming
I also checked the couatl log file,  and sure enough it matches the aircraft's folder name exactly

Yet both of my problems persist

I definitely have never created or downloaded any custom files for any aircraft on my system,  I am 100% sure of that.

Interestingly,  under the Airbus' folder (where the aircraft.cfg is),  there is also a file called intelliscene.cfg...this file gets installed as part of the installation,  it is part of the product itself.  I removed the file to experiment,  what happens then is that all the vehicles (catering and baggage loaders) then stop in completely wrong positions,  but do not request an exit to be opened.

In any case,  what more can I do? I desperately want this to work.


virtuali

  • Administrator
  • Hero Member
  • *****
  • Posts: 51462
    • VIRTUALI Sagl
Re: Two problems with GSX
« Reply #5 on: January 30, 2015, 05:04:22 pm »
Interestingly,  under the Airbus' folder (where the aircraft.cfg is),  there is also a file called intelliscene.cfg...this file gets installed as part of the installation,  it is part of the product itself.  I removed the file to experiment,  what happens then is that all the vehicles (catering and baggage loaders) then stop in completely wrong positions,  but do not request an exit to be opened.

It seems that GSX is reading from the intelliscene.cfg, which is not normal, since the GSX internal database has an higher priority.

As I've said in my previous message: You can verify this by enabling Logging in the "Troubleshooting" section of the "GSX - Settings" page. Select the airplane, then exit from FSX and check the Couatl.LOG file, it will tell you from which source the airplane configuration comes from.

Wildhawk

  • Newbie
  • *
  • Posts: 6
Re: Two problems with GSX
« Reply #6 on: January 30, 2015, 05:20:34 pm »
The couatl.log file indicates that it is reading from intelliscene.cfg

Do you reckon this file should not be there?

But as mentioned,  when I remove this file,  things are even worse.  So what do I do now? Should I consider using custom files as shared by another member?

With regards to the de-icing problem,  will it definitely give you the option everytime,  anywhere,  as long as the aircraft has a wingspan greater than 22m and the ambient temp is less than 4 deg C? Or are there more conditions that need to be satisfied?


virtuali

  • Administrator
  • Hero Member
  • *****
  • Posts: 51462
    • VIRTUALI Sagl
Re: Two problems with GSX
« Reply #7 on: January 30, 2015, 05:32:10 pm »
The couatl.log file indicates that it is reading from intelliscene.cfg

I would like to see the Log file.

Quote
Do you reckon this file should not be there?

It should be there, and it won't cause this problem because, as I've said, the GSX internal database has an higher priority. The intelliscene.cfg file is read ONLY when the airplane is not found in the GSX internal database.

Quote
But as mentioned,  when I remove this file,  things are even worse.

That's normal, because if there's no intelliscene.cfg, GSX will revert to the aircraft.cfg, which is even less precise.

Quote
So what do I do now?

Post your Couatl.LOG file.

Quote
With regards to the de-icing problem,  will it definitely give you the option everytime,  anywhere,  as long as the aircraft has a wingspan greater than 22m and the ambient temp is less than 4 deg C? Or are there more conditions that need to be satisfied?

Sure. I take for granted that you know how to use it: during Pushback. It's not supposed to be a separate menu option.

Wildhawk

  • Newbie
  • *
  • Posts: 6
Re: Two problems with GSX
« Reply #8 on: January 30, 2015, 06:09:32 pm »
I am posting the entire log file here,   hope it is alright like this...

Also,  touching on the de-icing problem,   what else can I do to try and solve it?  I make sure the temperature is less than 4 deg C,  but when selecting "prepare for pushback and departure",  I never get asked to de-ice.  This happens with both the A319 and the PMDG NGX.


=======================================================================

couatl v2.0 (build 2360)
log started on Fri Jan 30 18:49:19 2015

connecting to SimConnect...
connected to FSX
bglmanx non ready yet, waiting.
connected to bglmanx
Loading addons
requesting AddOn list to bglmanx
bglmanx list contains 22 AddOn(s)
Loading addon ENBR
Addon ENBR not installed or missing one or more files, skipping
Loading addon OHareX
Addon OHareX loaded
Loading addon KDFW
Addon KDFW loaded
Loading addon LSGG
Addon LSGG loaded
Loading addon GSX
Initializing audio...
Available devices:
  Generic Software on Speakers (Realtek High Definition Audio) (47656e6572696320536f667477617265206f6e20537065616b65727320285265616c74656b204869676820446566696e6974696f6e20417564696f29)
  Generic Software on Realtek Digital Output (Realtek High Definition Audio) (47656e6572696320536f667477617265206f6e205265616c74656b204469676974616c204f757470757420285265616c74656b204869676820446566696e6974696f6e20417564696f29)
Created OpenAL device: Generic Software on Speakers (Realtek High Definition Audio)

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 sim directory is C:/FSX
Looking for scenery.cfg in C:/ProgramData/Microsoft/FSX/scenery.cfg
  using Scenery/World/scenery (layer 1)
  using Scenery/BASE/scenery (layer 2)
  using Scenery/0000/scenery (layer 3)
  using Scenery/0001/scenery (layer 4)
  using Scenery/0002/scenery (layer 5)
  using Scenery/0003/scenery (layer 6)
  using Scenery/0004/scenery (layer 7)
  using Scenery/0005/scenery (layer 8)
  using Scenery/0006/scenery (layer 9)
  using Scenery/0007/scenery (layer 10)
  using Scenery/0100/scenery (layer 11)
  using Scenery/0101/scenery (layer 12)
  using Scenery/0102/scenery (layer 13)
  using Scenery/0103/scenery (layer 14)
  using Scenery/0104/scenery (layer 15)
  using Scenery/0105/scenery (layer 16)
  using Scenery/0106/scenery (layer 17)
  using Scenery/0107/scenery (layer 18)
  using Scenery/0200/scenery (layer 19)
  using Scenery/0201/scenery (layer 20)
  using Scenery/0202/scenery (layer 21)
  using Scenery/0203/scenery (layer 22)
  using Scenery/0204/scenery (layer 23)
  using Scenery/0205/scenery (layer 24)
  using Scenery/0206/scenery (layer 25)
  using Scenery/0207/scenery (layer 26)
  using Scenery/0300/scenery (layer 27)
  using Scenery/0301/scenery (layer 28)
  using Scenery/0302/scenery (layer 29)
  using Scenery/0303/scenery (layer 30)
  using Scenery/0304/scenery (layer 31)
  using Scenery/0305/scenery (layer 32)
  using Scenery/0306/scenery (layer 33)
  using Scenery/0307/scenery (layer 34)
  using Scenery/0400/scenery (layer 35)
  using Scenery/0401/scenery (layer 36)
  using Scenery/0402/scenery (layer 37)
  using Scenery/0403/scenery (layer 38)
  using Scenery/0404/scenery (layer 39)
  using Scenery/0405/scenery (layer 40)
  using Scenery/0406/scenery (layer 41)
  using Scenery/0407/scenery (layer 42)
  using Scenery/0500/scenery (layer 43)
  using Scenery/0501/scenery (layer 44)
  using Scenery/0502/scenery (layer 45)
  using Scenery/0503/scenery (layer 46)
  using Scenery/0504/scenery (layer 47)
  using Scenery/0505/scenery (layer 48)
  using Scenery/0506/scenery (layer 49)
  using Scenery/0507/scenery (layer 50)
  using Scenery/0600/scenery (layer 51)
  using Scenery/0601/scenery (layer 52)
  using Scenery/0602/scenery (layer 53)
  using Scenery/0603/scenery (layer 54)
  using Scenery/0604/scenery (layer 55)
  using Scenery/0605/scenery (layer 56)
  using Scenery/0606/scenery (layer 57)
  using Scenery/0607/scenery (layer 58)
  using Scenery/0700/scenery (layer 59)
  using Scenery/0701/scenery (layer 60)
  using Scenery/0702/scenery (layer 61)
  using Scenery/0703/scenery (layer 62)
  using Scenery/0704/scenery (layer 63)
  using Scenery/0705/scenery (layer 64)
  using Scenery/0706/scenery (layer 65)
  using Scenery/0707/scenery (layer 66)
  using Scenery/0800/scenery (layer 67)
  using Scenery/0801/scenery (layer 68)
  using Scenery/0802/scenery (layer 69)
  using Scenery/0803/scenery (layer 70)
  using Scenery/0804/scenery (layer 71)
  using Scenery/0805/scenery (layer 72)
  using Scenery/0806/scenery (layer 73)
  using Scenery/0807/scenery (layer 74)
  using Scenery/0900/scenery (layer 75)
  using Scenery/0901/scenery (layer 76)
  using Scenery/0902/scenery (layer 77)
  using Scenery/0903/scenery (layer 78)
  using Scenery/0904/scenery (layer 79)
  using Scenery/0905/scenery (layer 80)
  using Scenery/0906/scenery (layer 81)
  using Scenery/0907/scenery (layer 82)
  using Scenery/1000/scenery (layer 83)
  using Scenery/1001/scenery (layer 84)
  using Scenery/1002/scenery (layer 85)
  using Scenery/1003/scenery (layer 86)
  using Scenery/1004/scenery (layer 87)
  using Scenery/1005/scenery (layer 88)
  using Scenery/1006/scenery (layer 89)
  using Scenery/1007/scenery (layer 90)
  using Scenery/1100/scenery (layer 91)
  using Scenery/1101/scenery (layer 92)
  using Scenery/1102/scenery (layer 93)
  using Scenery/1103/scenery (layer 94)
  using Scenery/1104/scenery (layer 95)
  using Scenery/1105/scenery (layer 96)
  using Scenery/1106/scenery (layer 97)
  using Scenery/1107/scenery (layer 98)
  using Scenery/AFRI/scenery (layer 99)
  using Scenery/ASIA/scenery (layer 100)
  using Scenery/AUST/scenery (layer 101)
  using Scenery/EURE/scenery (layer 102)
  using Scenery/EURW/scenery (layer 103)
  using Scenery/NAMC/scenery (layer 104)
  using Scenery/NAME/scenery (layer 105)
  using Scenery/NAMW/scenery (layer 106)
  using Scenery/OCEN/scenery (layer 107)
  using Scenery/SAME/scenery (layer 108)
  using Scenery/Cities/Oshkosh/scenery (layer 109)
  using Scenery/Cities/StMaarten/scenery (layer 110)
  using Scenery/Cities/Rio/scenery (layer 111)
  using Scenery/Cities/LasVegas/scenery (layer 112)
  using Scenery/Global/scenery (layer 113)
  using Scenery/Props/scenery (layer 114)
  IGNORING Addon Scenery/scenery (layer 115): directory not found
  using Scenery/Cities/Reno/scenery (layer 116)
  using Scenery/Cities/Istanbul/scenery (layer 117)
  using Scenery/Cities/Longleat/scenery (layer 118)
  using Scenery/Cities/Berlin/scenery (layer 119)
  using Scenery/Cities/Edwards_AFB/scenery (layer 120)
  using ORBX/FTX_NA/FTX_NA_PNW08_CUSTOM/scenery (layer 121)
  using ORBX/FTX_NA/FTX_NA_PNW07_MESH/scenery (layer 122)
  using ORBX/FTX_NA/FTX_NA_PNW06_CVX/scenery (layer 123)
  using ORBX/FTX_NA/FTX_NA_PNW05_SCENERY/scenery (layer 124)
  using ORBX/FTX_NA/FTX_NA_NCA08_CUSTOM/scenery (layer 125)
  using ORBX/FTX_NA/FTX_NA_NCA07_MESH/scenery (layer 126)
  using ORBX/FTX_NA/FTX_NA_NCA06_CVX/scenery (layer 127)
  using ORBX/FTX_NA/FTX_NA_NCA05_SCENERY/scenery (layer 128)
  using ORBX/FTX_NA/FTX_NA_CRM08_CUSTOM/scenery (layer 129)
  using ORBX/FTX_NA/FTX_NA_CRM07_MESH/scenery (layer 130)
  using ORBX/FTX_NA/FTX_NA_CRM06_CVX/scenery (layer 131)
  using ORBX/FTX_NA/FTX_NA_CRM05_SCENERY/scenery (layer 132)
  using ORBX/FTX_EU/FTX_EU_WLS_08_CUSTOM/scenery (layer 133)
  using ORBX/FTX_EU/FTX_EU_WLS_07_MESH/scenery (layer 134)
  using ORBX/FTX_EU/FTX_EU_WLS_06_CVX/scenery (layer 135)
  using ORBX/FTX_EU/FTX_EU_WLS_05_SCENERY/scenery (layer 136)
  using ORBX/FTX_EU/FTX_EU_SCO_08_CUSTOM/scenery (layer 137)
  using ORBX/FTX_EU/FTX_EU_SCO_07_MESH/scenery (layer 138)
  using ORBX/FTX_EU/FTX_EU_SCO_06_CVX/scenery (layer 139)
  using ORBX/FTX_EU/FTX_EU_SCO_05_SCENERY/scenery (layer 140)
  using ORBX/FTX_EU/FTX_EU_NOR_08_CUSTOM/scenery (layer 141)
  using ORBX/FTX_EU/FTX_EU_NOR_07_MESH/scenery (layer 142)
  using ORBX/FTX_EU/FTX_EU_NOR_06_CVX/scenery (layer 143)
  using ORBX/FTX_EU/FTX_EU_NOR_05_SCENERY/scenery (layer 144)
  using ORBX/FTX_EU/FTX_EU_ENG_08_CUSTOM/scenery (layer 145)
  using ORBX/FTX_EU/FTX_EU_ENG_07_MESH/scenery (layer 146)
  using ORBX/FTX_EU/FTX_EU_ENG_06_CVX/scenery (layer 147)
  using ORBX/FTX_EU/FTX_EU_ENG_05_SCENERY/scenery (layer 148)
  using ORBX/FTX_NA/FTX_AA_YOSEMITE/scenery (layer 149)
  using ORBX/FTX_NA/FTX_AA_W16/scenery (layer 150)
  using ORBX/FTX_NA/FTX_AA_KPSP/scenery (layer 151)
  using ORBX/FTX_NA/FTX_AA_KJAC/scenery (layer 152)
  using ORBX/FTX_EU/FTX_AA_EGPB/scenery (layer 153)
  using ORBX/FTX_EU/FTX_AA_EGFF/scenery (layer 154)
  using ORBX/FTX_PI/FTX_AA_AYPY/scenery (layer 155)
  using ORBX/FTX_NA/FTX_AA_0S9/scenery (layer 156)
  using ORBX/FTX_AU/FTXAU48_CUSTOM/scenery (layer 157)
  using ORBX/FTX_AU/FTXAU46_SHORES/scenery (layer 158)
  using ORBX/FTX_AU/FTXAU45_SCENERY/scenery (layer 159)
  using ORBX/FTX_AU/FTXAU38_CUSTOM/scenery (layer 160)
  using ORBX/FTX_AU/FTXAU36_SHORES/scenery (layer 161)
  using ORBX/FTX_AU/FTXAU35_SCENERY/scenery (layer 162)
  using ORBX/FTX_AU/FTXAU28_CUSTOM/scenery (layer 163)
  using ORBX/FTX_AU/FTXAU26_SHORES/scenery (layer 164)
  using ORBX/FTX_AU/FTXAU25_SCENERY/scenery (layer 165)
  using ORBX/FTX_AU/FTXAU18_CUSTOM/scenery (layer 166)
  using ORBX/FTX_AU/FTXAU16_SHORES/scenery (layer 167)
  using ORBX/FTX_AU/FTXAU15_SCENERY/scenery (layer 168)
  using ORBX/FTX_AU/FTXAU05_ROADS/scenery (layer 169)
  using ORBX/FTX_AU/FTXAA_YSCH/scenery (layer 170)
  using ORBX/FTX_AU/FTXAA_YPMQ/scenery (layer 171)
  using ORBX/FTX_AU/FTXAA_YMML/scenery (layer 172)
  using ORBX/FTX_AU/FTXAA_YMMB/scenery (layer 173)
  using ORBX/FTX_AU/FTXAA_YMEN/scenery (layer 174)
  using ORBX/FTX_AU/FTXAA_YMAV/scenery (layer 175)
  using ORBX/FTX_PI/FTXAA_PNG_HOLGERMESH/scenery (layer 176)
  using ORBX/FTX_AU/FTXAA_ORBXLIBS/scenery (layer 177)
  using ORBX/FTX_OLC/OLC_AA/scenery (layer 178)
  using ORBX/FTX_OLC/OLC_EU1/scenery (layer 179)
  using ORBX/FTX_OLC/OLC_NA1/scenery (layer 180)
  using C:/FSX/UK2000 scenery/UK2000 Common Library/scenery (layer 181)
  using C:/FSX/UK2000 scenery/UK2000 Glasgow Xtreme/scenery (layer 182)
  using FsDreamTeam/OHareX/scenery (layer 183)
  using FsDreamTeam/kdfw/scenery (layer 184)
  using FsDreamTeam/KFLL/scenery (layer 185)
  using FsDreamTeam/LSGG/scenery (layer 186)
  using FsDreamTeam/PHLI/scenery (layer 187)
  using FsDreamTeam/PHTO/scenery (layer 188)
  using FsDreamTeam/PHOG/scenery (layer 189)
  using FsDreamTeam/PHKO/scenery (layer 190)
  using FsDreamTeam/PHNL/scenery (layer 191)
  using FsDreamTeam/KJFK/scenery (layer 192)
  using FsDreamTeam/KLAS/scenery (layer 193)
  using FsDreamTeam/KLAX_V2/scenery (layer 194)
  using FsDreamTeam/ZurichX/scenery (layer 195)
  using FsDreamTeam/CYVR/scenery (layer 196)
  using Flightbeam/KDEN/scenery (layer 197)
  using FlightBeam/KPHX/scenery (layer 198)
  using FlightBeam/KSFO/scenery (layer 199)
  using C:/FSX/UK2000 scenery/UK2000 Manchester Xtreme/scenery (layer 202)
  using aerosoft/Mega-Airport-London-Heathrow-Xtended_Terrain/scenery (layer 203)
  using aerosoft/Mega-Airport-London-Heathrow-Xtended_Airport/scenery (layer 204)
  using C:/FSX/UK2000 scenery/UK2000 Edinburgh Xtreme/scenery (layer 205)
  using UK2000 scenery/UK2000 Jersey Xtreme/scenery (layer 206)
  using C:/FSX/Addon Scenery/FlyTampa-Maarten/scenery (layer 207)
  using C:/FSX/Addon Scenery/LatinVFR/San Juan_TJSJ/scenery (layer 208)
  using C:/FSX/Addon Scenery/NinoyAquinoIntl/scenery (layer 209)
  using Addon Scenery/KLIA_landclass/scenery (layer 210)
  using Addon Scenery/Kuala Lumpur International/scenery (layer 211)
  using Addon Scenery/KLIA_tunnel/scenery (layer 212)
  using TropicalSim/MDPC2014/scenery (layer 213)
  using Addon Scenery/TAG_MyrtleBeach/scenery (layer 214)
  using Aerosoft/Lukla - Mount Everest X/LuklaX_LC/scenery (layer 215)
  using Aerosoft/Lukla - Mount Everest X/LuklaX/scenery (layer 216)
  using Aerosoft/Lord Howe Island X/scenery (layer 217)
  using Aerosoft/African Airstrip Adventures/scenery (layer 218)
  using aerosoft/Antarctica X/scenery (layer 219)
  using C:/FSX/Addon Scenery/FlyTampa-Copenhagen_LC/scenery (layer 220)
  using C:/FSX/Addon Scenery/FlyTampa-Copenhagen/scenery (layer 221)
  using aerosoft/Kamchatka - The Lost World/scenery (layer 222)
  using C:/FSX/UK2000 scenery/UK2000 Prestwick Xtreme/scenery (layer 223)
  using C:/FSX/Addon Scenery/VHHH-FSX/VHHH-TERRAIN/scenery (layer 224)
  using C:/FSX/Addon Scenery/VHHH-FSX/VHHH/scenery (layer 225)
  using aerosoft/F-14A/CV_63/scenery (layer 226)
  using Scenery/NMG_FACT_2012/scenery (layer 227)
  using aerosoft/Sahara_Desert_FlyIn/scenery (layer 228)
  using Imagine Simulation/KAUS Austin 2014 FSX/scenery (layer 229)
  using aerosoft/Mega Airport Oslo 2.0/scenery (layer 232)
  using aerosoft/Tromso X/scenery (layer 233)
  using aerosoft/Stavanger X/scenery (layer 234)
  using FsDreamTeam/KIAH/scenery (layer 235)
  using Flightbeam/KIAD/scenery (layer 236)
Airport cache not valid: scenery.cfg has changed since last time
Regenerating airport cache, looking for scenery files under C:/FSX/
Worker thread started
Addon GSX loaded
Loading addon HAWAII1
Addon HAWAII1 loaded
Loading addon HAWAII2
Addon HAWAII2 loaded
Loading addon PHNL
Addon PHNL loaded
Loading addon JFK
Addon JFK not installed or missing one or more files, skipping
Loading addon JFK2
Addon JFK2 loaded
Loading addon KFLL
Addon KFLL loaded
Loading addon KIAH
Addon KIAH loaded
Loading addon KLAS
Addon KLAS loaded
Loading addon KLAX
Addon KLAX loaded
Loading addon ParkMe
Addon ParkMe not installed or missing one or more files, skipping
Loading addon CYVR
Addon CYVR loaded
Loading addon XPOI
Addon XPOI not installed or missing one or more files, skipping
Loading addon ZurichX
Addon ZurichX loaded
Loading addon KSFO
Addon KSFO loaded
Loading addon KPHX
Addon KPHX loaded
Loading addon KIAD
Addon KIAD loaded
Loading addon KDEN
Addon KDEN loaded
Starting system monitors
Current locale is English_United States.1252
SharedMemInterface connected
Loading aircraft data from Airplanes\Aerosoft Airbus A319 CFM
Entering KIAD area...
main_a.MDL size =  8958281
Found KIAD 1.2
intelliscene.cfg provides aircraft data with priority 1
Using aircraft data from intelliscene.cfg
Live Update Error: Couldn't resolve host name
Live Update Error: Couldn't resolve host name
Airport cache regeneration warnings:
Warning: airport ENGM described in multiple BGL files without proper DeleteAirport record
Airport cache regeneration completed with success in 89 seconds
Loading airport KIAD from C:/FSX/Flightbeam/KIAD/scenery/KIAD.BGL
Using airport customization from GSX.airports.kiad_fbeam
Loading user customizations from C:/FSX/Flightbeam/KIAD/scenery\kiad-flightbeam.ini (file is designer-provided and won't be modified in-place)

========================================================================================

virtuali

  • Administrator
  • Hero Member
  • *****
  • Posts: 51462
    • VIRTUALI Sagl
Re: Two problems with GSX
« Reply #9 on: January 30, 2015, 09:31:11 pm »
Also,  touching on the de-icing problem,   what else can I do to try and solve it?  I make sure the temperature is less than 4 deg C,  but when selecting "prepare for pushback and departure",  I never get asked to de-ice.  This happens with both the A319 and the PMDG NGX.

I can only confirm it works.

Quote
Live Update Error: Couldn't resolve host name

This error message is a bit suspicious, and together with this one:

Quote
couatl v2.0 (build 2360)

Which indicates you are several versions behind ( current version of the Couatl.exe program is 2378 ), seems to indicate you must have some kind of connection problem when accessing our server, that might explain why you are not getting the latest files, which might explain the issue.

It's not normally possible to run an installer and not getting the latest files, since all installers automatically downloads the current files, so I think you must have seen some kind of connection error message from the installer.

Be sure you turn off ALL software like firewalls, anti-virus, anti-spyware, etc, when installing, so nothing gets blocked.

Or, if you can't do that, downloading and installing the *CURRENT* version of the full GSX installer should also work, because that one contains the latest files, so if some software is blocking online access to the latest files, they are contained in the full installer anyway.

Wildhawk

  • Newbie
  • *
  • Posts: 6
Re: Two problems with GSX
« Reply #10 on: January 30, 2015, 10:46:15 pm »
Thanks Umberto,  I appreciate it that you are trying to assist.

Yes,  my internet connection is not at its best quality at the moment,  and my FSX pc is not connected at the moment.

What I will try to do,  is to get a decent connection to the machine and see if I can't properly update everything once and for all - I am sure it is something small causing the problems.