MyAAS not recording properly

[AS618 Jon Cronin]

I recently started having a problem that came out of nowhere. MyAAs wont record, i clicked start flight(not paused and parking break is on) and it immediatly stops. I uninstalled it and downloaded Version 2. When i start flight on Version 2 it only records time, it wont record fuel, speed, takeoff, Altitude, and cant pirep so lately i had to do manual pireps.

[AS380 Mark Richards]

What version of FSUIPC are you using Jon??

[AS618 Jon Cronin]

4.90

[AS 2 Tom Little]

I recently started having a problem that came out of nowhere. MyAAs wont record, i clicked start flight(not paused and parking break is on) and it immediatly stops. I uninstalled it and downloaded Version 2. When i start flight on Version 2 it only records time, it wont record fuel, speed, takeoff, Altitude, and cant pirep so lately i had to do manual pireps.

This does seem like an FSUIPC problem. Any error messages coming up from FSX, FSUIPC or myAAS 2?

Always back up before making any changes such as a reinstall of FSUIPC, etc.

[AS618 Jon Cronin]

Kinda weird, im not getting any error messages at all, i reinstalled FSUIPC, but its still not recording anything(except the time), i also noticed that MyAAS 2 doesnt install into program files like the other version, im running 2 off a desktop folder and theres only 2 files, unlike the other version it had all these other files, with a log and stuff. And i have Myaas 1 completly uninstalled since that wouldnt function either, ive had no problems until the past 3 days and havent changed anything that would cause a conflict. Oh and i also tried to install it into the program files folder to see if that would fix it and still no luck

[AS 2 Tom Little]

Yes one of the big things Joe and I planned was to have a simple program that would not have to rely on a bunch of files to run or even install. So no "install" is necessary.

Anyhow this is a bit of a strange scenario. Have you checked the FSUIPC menu within FSX to see if all your settings there look normal? I would even go as far as suggesting to BACKUP your fsuipc.ini file and then delete the existing one and let fsuipc build a new one, but I doubt that would do much of anyhting. (remember if you try this to BACK UP that file!) It is located in the fsx/modules folder if you do try that.

[AS201 Joe]

I agree that it definitely seems to be an FSUIPC problem as neither version of myAAS is working. myAAS2 does at least detect it or you wouldn't be able to start the flight.

Looks like you are using FSX (FSUIPC version 4), can you post your dll.xml file? Found at Users\*YOU*\AppData\Roaming\Microsoft\FSX (granted this is for Win7 but others should be similar).

Also, look in your FSX\modules forlder for a fsuipc.log file. See if that says anything.

Did you install anything into FSX around the time this started happening?

Yes, myAAS2 is just put it somewhere and go (preferably not in Program Files for Vista and above). Alot easier than an installer.

[AS618 Jon Cronin]

<?xml version="1.0" encoding="WINDOWS-1252"?>
-<SimBase.Document version="1,0" Type="Launch"> <Descr>Launch</Descr> <Filename>dll.xml</Filename> <Disabled>False</Disabled> <Launch.ManualLoad>False</Launch.ManualLoad> -<Launch.Addon> <Name>Object Placement Tool</Name> <Disabled>True</Disabled> <ManualLoad>False</ManualLoad> <Path>..\Microsoft Flight Simulator X SDK\SDK\Mission Creation Kit\object_placement.dll</Path> </Launch.Addon> -<Launch.Addon> <Name>Traffic Toolbox</Name> <Disabled>True</Disabled> <ManualLoad>False</ManualLoad> <Path>..\Microsoft Flight Simulator X SDK\SDK\Environment Kit\Traffic Toolbox SDK\traffictoolbox.dll</Path> </Launch.Addon> -<Launch.Addon> <Name>Visual Effects Tool</Name> <Disabled>True</Disabled> <ManualLoad>False</ManualLoad> <Path>..\Microsoft Flight Simulator X SDK\SDK\Environment Kit\Special Effects SDK\visualfxtool.dll</Path> </Launch.Addon> -<Launch.Addon> <Name>VistaMare Core</Name> <Disabled>False</Disabled> <ManualLoad>False</ManualLoad> <Path>VistaMare\ViMaCoreX.dll</Path> </Launch.Addon> -<Launch.Addon> <Name>FSUIPC 4</Name> <Disabled>False</Disabled> <Path>Modules\FSUIPC4.dll</Path> </Launch.Addon> </SimBase.Document>

[AS618 Jon Cronin]

really not sure what all that means but i noticed alot of disabled stuff, this is how it appeared as of last night since i havent started up FSX yet today

[AS201 Joe]

Just out of curiosity, make a backup of your dll.xml then change it to this and see if it helps.

Code: Select all

<?xml version="1.0" encoding="WINDOWS-1252"?>
<SimBase.Document version="1,0" Type="Launch">
   <Descr>Launch</Descr>
   <Filename>dll.xml</Filename>
   <Disabled>False</Disabled>
   <Launch.ManualLoad>False</Launch.ManualLoad>
   <Launch.Addon>
      <Name>Object Placement Tool</Name>
      <Disabled>True</Disabled>
      <ManualLoad>False</ManualLoad>
      <Path>..\Microsoft Flight Simulator X SDK\SDK\Mission Creation Kit\object_placement.dll</Path>
   </Launch.Addon>
   <Launch.Addon>
      <Name>Traffic Toolbox</Name>
      <Disabled>True</Disabled>
      <ManualLoad>False</ManualLoad>
      <Path>..\Microsoft Flight Simulator X SDK\SDK\Environment Kit\Traffic Toolbox SDK\traffictoolbox.dll</Path>
   </Launch.Addon>
   <Launch.Addon>
      <Name>Visual Effects Tool</Name>
      <Disabled>True</Disabled>
      <ManualLoad>False</ManualLoad>
      <Path>..\Microsoft Flight Simulator X SDK\SDK\Environment Kit\Special Effects SDK\visualfxtool.dll</Path>
   </Launch.Addon>
   <Launch.Addon>
      <Name>VistaMare Core</Name>
      <Disabled>True</Disabled>
      <ManualLoad>False</ManualLoad>
      <Path>VistaMare\ViMaCoreX.dll</Path>
   </Launch.Addon>
   <Launch.Addon>
      <Name>FSUIPC 4</Name>
      <Disabled>False</Disabled>
      <Path>Modules\FSUIPC4.dll</Path>
   </Launch.Addon>
</SimBase.Document>


[AS618 Jon Cronin]

Yay!!! i did what you suggested(copied that into my xml file) and it actually worked

[AS380 Mark Richards]

Glad you got it working Jon.


Sent from my iPad using Tapatalk HD

[AS201 Joe]

Great to hear that it worked, Jon.

If you want to try and narrow the problem down, find this section

Code: Select all

 <Launch.Addon>
      <Name>VistaMare Core</Name>
      <Disabled>True</Disabled>
      <ManualLoad>False</ManualLoad>
      <Path>VistaMare\ViMaCoreX.dll</Path>
   </Launch.Addon>


and change the disabled value back to False and see if it still works.

If it does still work, your xml.dll file just got a little corrupted.
If it doesn't work, whatever installed the VistaMare stuff might need to be reinstalled.

[AS 2 Tom Little]

Excellent work Joe! Glad to see another member getting back on to myAAS

[AS618 Jon Cronin]

Im now having the same problem again that xml thing only worked for 1 flight. Now it went back to only detecting the time.