Addon and couatl errors

[virtuali]

Used basic 737 at the gate position at KSEA ( not any third party airport scenery and the result again the same......

You still haven't indicated a PRECISE reproduction step. What do you mean "used" ? Clearly indicate the precise sequence of operations you did.

[Roman]

Start FSX, choose basic B737-800 from FSX, choose Seatlle, because any of these are not third party software, shout down engines, and then pres press CTRL+F12 for menu of GSX and wnen I wanted call catering or pushback, an error message came, which I sent you already.

When I started using this program, a year(s) ago, everytjing worked absolutelly perfectly......and iam not very hot to reinstall whale FSX, have there a lot of sceneries, etc....

Regards

Roman

[Roman]

And by the way where can I find a manuals to all of yours programs pls?

[virtuali]

Start FSX, choose basic B737-800 from FSX, choose Seatlle, because any of these are not third party software, shout down engines, and then pres press CTRL+F12 for menu of GSX and wnen I wanted call catering or pushback, an error message came, which I sent you already.

Doesn't happen here, of course. And nobody has ever reported it before. Don't you think that, if the program had this problem, happening with something so basic, someone else would have noticed ?

Are you SURE you have installed GSX with the latest updates ?

If not sure, download and install either one of the vehicle updates, or the current full GSX installer.

[virtuali]

And by the way where can I find a manuals to all of yours programs pls?

The products manuals can be found in 3 different ways:

1) From "Open Manual" button in the Addon Manager, after having selected the product you are interested into.

OR

2) By browsing the FSX\fsdreamteam\PRODUCT_NAME folder ( PRODUCT_NAME can be KLAX, KJFK, or Couatl\GSX for GSX )

OR ( GSX only )

3) From the fsdreamteam/GSX program group in the Windows Start button

[Roman]

I downloded the latest version 2 day ago and addon manager, but it is the same version. What the rror log telling you? In which directory should by all the cars and stairs should be locted?

On the of the installation it is sayng something like that is becuping vehivles and installing probably yours, if I right understand....___

You have any idea how to check that all parts of your program are on the right place??

REgards

Roman

[virtuali]

You have any idea how to check that all parts of your program are on the right place??

If you really downloaded and installed the Full GSX installer 2 days ago, then it's SURE that all parts of the programs are in the right place!

The problem is not obviously the program, but some configuration error in your system. For example, could you please check your FSX.CFG, to see if your Simobjects paths are all correct ? Perhaps you have the same problem reported here:

http://www.fsdreamteam.com/forum/index.php/topic,10245.msg80146.html#msg80146

So, try the same solution.

[Roman]

OK I am sending u my fsx.cfg if you can chack it for me.
Thanks very much in advance
R

[virtuali]

OK I am sending u my fsx.cfg if you can chack it for me.

You don't have the problem of the SimobjectsPaths missing.

Try to delete all your GSX preferences, by removing this folder:

%APPDATA%\Virtuali

Then reinstall GSX, using the current Full installer.

[Roman]

Try to delete all your GSX preferences, by removing this folder:

%APPDATA%\Virtuali

Then reinstall GSX, using the current Full installer -

like remove from program and features first and reinstal, or juste delete virtuali and reinstal again full installer?

[virtuali]

juste delete virtuali and reinstal again full installer?

Haven't said anything about uninstalling, so it's this one.

[Roman]

Done as you instructed, B737-800 orbit airlines, KSEA Gate B-10 medium

couatl v2.0 (build 2358)
panic log started on Thu May 29 16:10:58 2014

problem raised by addon <unknown>Traceback (most recent call last):
  File "couatl\common\fsm.py", line 61, in switchToState
  File "couatl\GSX\assistanceServices\__init__.py", line 443, in enter
  File "couatl\common\criticalsection.py", line 23, in _synchronized
  File "couatl\GSX\assistanceServices\__init__.py", line 79, in requestVehicles
  File "couatl\GSX\__init__.py", line 590, in prepareGate
  File "couatl\GSX\assistanceServices\__init__.py", line 843, in setGate
  File "couatl\common\criticalsection.py", line 23, in _synchronized
  File "couatl\GSX\assistanceServices\baggageTrain.py", line 55, in materialize
  File "couatl\GSX\assistanceServices\baggageTrain.py", line 417, in makeTrain
  File "couatl\common\train.py", line 41, in __init__
  File "couatl\common\modelCustomization.py", line 315, in getModelForCouatlType
common.modelCustomization.NoModelInstalled: No model of type BaggageTractor is currently installed

couatl v2.0 (build 2358)
panic log started on Thu May 29 16:12:07 2014

problem raised by addon <unknown>Traceback (most recent call last):


  File "couatl\common\fsm.py", line 67, in executeDoFuncToCompletion
  File "couatl\GSX\assistanceServices\__init__.py", line 654, in do
  File "couatl\common\criticalsection.py", line 23, in _synchronized
  File "couatl\GSX\assistanceServices\__init__.py", line 79, in requestVehicles
  File "couatl\GSX\__init__.py", line 590, in prepareGate
  File "couatl\GSX\assistanceServices\__init__.py", line 843, in setGate
  File "couatl\common\criticalsection.py", line 23, in _synchronized
  File "couatl\GSX\assistanceServices\baggageTrain.py", line 55, in materialize
  File "couatl\GSX\assistanceServices\baggageTrain.py", line 417, in makeTrain
  File "couatl\common\train.py", line 41, in __init__
  File "couatl\common\modelCustomization.py", line 315, in getModelForCouatlType
common.modelCustomization.NoModelInstalled: No model of type BaggageTractor is currently installed

[virtuali]

Done as you instructed, B737-800 orbit airlines, KSEA Gate B-10 medium

Tried that exact situation and, of course, no problems whatsoever. Since you don't say if you started with boarding, deboarding, catering or pushback, I tried them all, and none of them gives any problem.

The only possible explanation left, is that you have FSX folders entirely messed up. Try to enable Logging in the "Troubleshooting" section of the "GSX Settings" menu, and send me the Couatl.LOG that will be produced, in the same folder as the Couatl.ERR you posted.

[Roman]

Hello to you,

see my couatl.log in the attachments.

BR

Roman

[virtuali]

You should posted a Couatl.LOG file AFTER you called for GSX. And please, don't copy&paste it into a Word .DOC file, just ZIP the Couatl.LOG file as it is, it's even easier/faster to do for you.