The A2A Simulations Community

Ian,

Thanks for chiming in. I spoke too soon and it now seems that AICarriers is not the culprit but instead my FSX Traffic Settings. I had reduced my Traffic Settings to minimal before removing AICarriers and I just ran a test and it seems my Traffic settings are what is impacting the 'lights off' condition. I am using WOAI (World of AI) as my traffic program (bgl are reexported to FSX native). MY Traffic Settings were previously set at 'Ultra High'

OS: Windows 7 64 bit

My config:

dll.xml:
<SimBase.Document Type="Launch" version="1,0">
<Descr>Launch</Descr>
<Filename>dll.xml</Filename>
<Disabled>False</Disabled>
<Launch.ManualLoad>False</Launch.ManualLoad>
<Launch.Addon>
<Name>Addon Manager</Name>
<Disabled>False</Disabled>
<ManualLoad>False</ManualLoad>
<Path>bglmanx.dll</Path>
</Launch.Addon>
<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>PMDG Options</Name>
<Disabled>False</Disabled>
<Path>PMDG\DLLs\PMDGOptions.dll</Path>
</Launch.Addon>
<Launch.Addon>
<Name>PMDG Events</Name>
<Disabled>False</Disabled>
<Path>PMDG\DLLs\PMDGEvents.dll</Path>
</Launch.Addon>
<Launch.Addon>
<Name>PMDG Sounds</Name>
<Disabled>False</Disabled>
<Path>PMDG\DLLs\PMDGSounds.dll</Path>
</Launch.Addon>
<Launch.Addon>
<Name>VistaMare Core</Name>
<Disabled>False</Disabled>
<ManualLoad>False</ManualLoad>
<Path>D:\FlightSim\Microsoft Flight Simulator X\VistaMare\ViMaCoreX.dll</Path>
</Launch.Addon>
<Launch.Addon>
<Name>A2A Service</Name>
<Disabled>False</Disabled>
<Path>A2A\Shared\A2A_Service.dll</Path>
<DllStartName>module_init</DllStartName>
<DllStopName>module_deinit</DllStopName>
</Launch.Addon>
<Launch.Addon>
<Name>FSLOptions</Name>
<Disabled>False</Disabled>
<ManualLoad>False</ManualLoad>
<Path>FSLabs\DLLs\FSLOptions.dll</Path>
</Launch.Addon>
<Launch.Addon>
<Name>FSLEvents</Name>
<Disabled>False</Disabled>
<ManualLoad>False</ManualLoad>
<Path>FSLabs\DLLs\FSLEvents.dll</Path>
</Launch.Addon>
<Launch.Addon>
<Name>FSLSounds</Name>
<Disabled>False</Disabled>
<ManualLoad>False</ManualLoad>
<Path>FSLabs\DLLs\FSLSounds.dll</Path>
</Launch.Addon>
<Launch.Addon>
<Name>FSUIPC 4</Name>
<Disabled>False</Disabled>
<Path>Modules\FSUIPC4.dll</Path>
</Launch.Addon>
</SimBase.Document>

exe.xml:
<SimBase.Document Type="Launch" version="1,0">
<Descr>Launch</Descr>
<Filename>exe.xml</Filename>
<Disabled>False</Disabled>
<Launch.ManualLoad>False</Launch.ManualLoad>
<Launch.Addon>
<Name>Couatl</Name>
<Disabled>False</Disabled>
<ManualLoad>False</ManualLoad>
<Path>fsdreamteam\couatl\couatl.exe</Path>
</Launch.Addon>
<Launch.Addon>
<Disabled>True</Disabled>
<ManualLoad>False</ManualLoad>
<Name>UT2</Name>
<Path>D:\FlightSim\Microsoft Flight Simulator X\\Flight One Software\Ultimate Traffic 2\UT2Services.exe</Path>
<NewConsole>True</NewConsole>
</Launch.Addon>
<Launch.Addon>
<Disabled>True</Disabled>
<ManualLoad>False</ManualLoad>
<Name>AICarriers</Name>
<Path>C:\Program Files (x86)\AICarriers\aicarriers.exe</Path>
<CommandLine>-nogui</CommandLine>
</Launch.Addon>
</SimBase.Document>

Before I read the post, I went out and downloaded that carrierAI exe, ran it, and tried to reproduce but still not happening here.

I also tried keeping traffic on Ultra High, but we don't have any of these traffic programs.

We may be running into a situation where running so many addons is pushing some systems over their limit. The 3rd party traffic programs seem to be the biggest culprit.

Scott.

_________________
A2A Simulations Inc.

I'm running 1% AI, Scott. There's hardly anything in the skies.

Ian P.

One of our coders has an idea he would like to try, so we're going to put together a little test patch to see if we can circumvent this issue.

Scott.

_________________
A2A Simulations Inc.

This has just started happening to me .. after trying to startup the Spit on the tarmac after a successful landing/shutdown.

Symptoms: Position lights refuse to come on (cockpit lights do though).

Now ... rapidly flicking the "L" keyboard lights switch shows that something *is* happening ... the lights are being turned on/off but they're positioned somewhere near/inside the engine cowling (!!). At first I thought it was the engine backfiring).

Is this a clue?

_________________




www.nzfsim.org

Hello everybody. I come from Germany, so my english is not so good... Whatever...
I've flown lots of patterns yesterday around Rostock-Laage in northern Germany.
Start the engine, fly a pattern, land and turn of the engine. After a few minutes, same problems as described the pages before.
Someones idea was "maybe not enough memory" or something like that
So I opened up my task manager and ended the "explorer.exe" (during the whole procedures written below, my fsx and the situation was running)
Reload the plane via "STRG+Ü" within the situation. (thats the key for german keyboard and fsx)
Flying again a pattern, shut down the engine and wait a few minutes: same problem again
Then I turned of java.exe (wich also stops aicarriers.exe) via task manager, reload the plane, pattern, shut down: nothing new
Then I turned of UT2 via fsx menu, reload the plane, pattern, shut down: nothing new
Then I turned of UT2 via task manager, reload the plane, and it works!!!!!
As long as UT2 is not running on my system, I can start up and shut down the engine as often as I want.
I don't know what that means, but hopefully it helps to fix the problem, because I would like to fly this great plane with UT2

Not to forget: I work with windows xp professional, fsx acceleration

If you need further information, please ask, A2A should have my e-mail

Happens with me as well Scott. A couple things that I have that are not mentioned so far:

Go-Flight modules
Tracker IR

I say the Go-Flight because that has given me problems with your planes and Aerosoft as well. I have a button set for starter 1 and one for starter 2. If I try to hand prop the cub I see that light flicker on the Go-Flight module.

I cancelled out the Go-Flight but cant remember if I also reloaded the plane last time in order to get it to work. But I wanted to add that t othe mix as well.

I also have Ultimate Traffic X and have AI at 20%.

I've got a rather new system with 6 gigs of ram just to add.

_________________

i7-3820 OC 4.7 |P9X79 LE | 16GB DDR3/2133MHz Corsair Vengeance | EVGA GTX 680 2GB | 480 GB Intel SSD | Window7 64 Pro | Liquid Cooling Kit 360MM w/ Triple Fan powered by Koolance

It was said before - it's not UT2 problem. I don't have any traffic addon and I experience "the bug" we are talking about here. Give A2A some time - they are preparing some update.

_________________
[url=http://a2asimulations.com]

Me and my mate had it happen us as well now during a multiplayer session with the two MkIs. We landed, completely shut down, did some maintenance like refueling etc. and when we tried to leave again our Spitfires were stuck. Reloading the aircraft didn't help either, because that gave us the issue of the crazy landing light switch, the generator switch not moving and the Accusim menus failing to work as well. On both planes at the same time, on completely different systems, mind you.

The strange thing is: we did the same kind of procedure (landing, shutdown, startup, take off) several times during our previous multiplayer sessions and it didn't occur then.

Traffic is off by default in multiplayer, so that shouldn't be the culprit. Also, I never had that happen to me in single player, at least not with the MkII which I use mostly when flying alone.

_________________
Happy Landings
- Patrick

I have this same problem, but only on the MkI. I don't use any weather, traffic or other add ons like them, and my default traffic is only set to about 25%. Reloading the aircraft fixes it. I think loading the default flight first would probly work too, I had to do that for the Flight 1 Mustang as well, but I only used that preload once and it seemed like it wasn't needed anymore for the Stang. They called the file Loading for complex aircraft or something like that. I think they explain how to make the flight on their forum.

Rockitglider

_________________

OK, for anyone experiencing this issue:

In your Aircraft.cfg file,
change:

starter1 = 0, 20, 17
to:
starter1 = 0, 20, 0


I believe this will confirm that the issue is your FSX battery dying. We can then make a change in our next update to override this setting directly so this edit is not necessary.

Scott.

_________________
A2A Simulations Inc.

OK to add to this, we strongly suspect some other system is controlling the FSX battery and overriding the aircraft.cfg settings. Does anyone have any software installed, like FSUIPC, that may have settings to control the FSX battery life? To find what software is creating this issue would be the true fix.

Scott.

_________________
A2A Simulations Inc.

Yes - in my case I *do* have the full FSUIPC and have it set (by default) to over-ride the default FSX battery behaviour and force it to "Extend battery life (indefinitely)".

So ... I should turn this function in FSUIPC *off*?

UPDATE: I modified aircraft.cfg and UNticked the FSUIPC battery checkbox. I have no lights (but everything else works) (((

1. Start up FSX with my default C-172 *cold and dark* (ie. everything off).
2. Sit on the runway in my (dead) Cessna ... then load up the MkIIb.
3. Without going into the hangar, set up the aircraft (SHIFT-4 and SHIFT-3).

I get no lights showing at all when switched to "on".

4. Do a COLD START or an AUTO start from the sub-panel. No luck.
5. Reload the aircraft (the inbuilt FSX command - not from the select aircraft menu). Still no luck.
6. Go to the hangar, fiddle with stuff, then repeat 4) and 5). No lights (but everything else works).
7. Jump back into my "dead" Cessna, to find the all lights/avionics are ON (I'd left the the lights on in the Spit).
8. Start the engine (in the Cessna) then jump back into the "live" Spit. Still no lights.

Just to confirm - this is with:

a) Edit to aircraft.cfg
b) FSUIPC battery function UNticked
c) Default FSX startup as C172, cold & dark
d) Jumping into the C172 then then selecting the MkIIb from the top menu

I'll save a default C172 but with avionics/battery set to ON and see what happens.

_________________




www.nzfsim.org

I cannot speak top FSUIPC, just not sure what they are doing. What if you just leave it as is, and only make the change to the aircraft.cfg? The lights should be unaffected and the FSX engine should always start (have power).

Scott.

_________________
A2A Simulations Inc.