Military AI Works

Hi Guys

Speaking in the wind as I do not have it installed.

Aircraft that line up and do not take off, usually get onto the runway via a path that has no hold short or the hold short is too far from the runway edge.

Hope this helps.

John

JohnTenn wrote:Hi Guys

Speaking in the wind as I do not have it installed.

Aircraft that line up and do not take off, usually get onto the runway via a path that has no hold short or the hold short is too far from the runway edge.

Hope this helps.

John

Many of the hold shorts in real life are pretty far from the runway and at an angle the runway bearing.

Hello,

FSX SE
Why do I get CTD if I fly over Lemoore?

Zsolt

Zsolt,

If you install any FSX scenery into FSX:SE, then you either:

1. Have to install it into Addon Scenery in FSX:SE's peculiar installation path, or

2. Install it into a folder external to FSX:SE and then point FSX:SE to that folder for scenery.

If you have done either of the two, then see if you can find an error entry in Windows Event Viewer from the time of the crash. In that entry, there should be an exception code, post that code here.

Jorgen

Jorgen wrote: 10 Sep 2024, 10:29 Zsolt,

If you install any FSX scenery into FSX:SE, then you either:

1. Have to install it into Addon Scenery in FSX:SE's peculiar installation path, or

2. Install it into a folder external to FSX:SE and then point FSX:SE to that folder for scenery.

If you have done either of the two, then see if you can find an error entry in Windows Event Viewer from the time of the crash. In that entry, there should be an exception code, post that code here.

Jorgen

Hi Jorgen,

Run time error

Application name causing the error: fsx.exe, version: 10.0.62615.0, timestamp: 0x559f9a9a
Module name causing the error: visualfx.dll, version: 10.0.62615.0, timestamp: 0x559f9ab4
Exception code: 0x40000015
Error position: 0x000054af
Process ID causing the error: 0x1964
Application start time of the application causing the error: 0x01db04373429a8c9
Path to the application causing the error: E:\SteamLibrary\steamapps\common\FSX\fsx.exe
Path to the module causing the error: E:\SteamLibrary\steamapps\common\FSX\visualfx.dll
Report ID: 90f0e9c9-db5a-4039-b123-ccc1d9343078
Full name of the package causing the error:
Relative application identifier of the package causing the error

Translated with DeepL.com (free version)

This can be caused by a corrupted Windows installation, but also by missing system libraries.

Try this first:

Search the web for:

C++ libraries

then get all you find, both the x64 and x86 versions, but from Microsoft only. Install all of these, you may be told that some are already installed.

Then do the same for:

.NET Framework

again get both x64 and x86 versions, and install those.

After this, run Windows Update, and - important - in Update, under "Advanced options", make sure the little switch "Receive updates for other Microsoft products" is set to On. Leave this switch on, this is to ensure that the libraries aare update. You may need to run Update more than once to get everything updated.

Finally, it is time to run the sim again and see if it runs now. If you still have problems, then check for a possible new exception code and report back here.

Jorgen

No change
And only this scenery has this problem

Odd.

Maybe try this: in the search box on your task bar, type

co

and then in the right pane select "Run as administrator".

This brings up the command prompt. At the prompt, type this:

sfc /scannow

and press Enter.

Were any corrupted files found?

Jorgen

This is a MS VC++ error. This is well known with FS. The usual cause is that something at or near the base is using an effect that is not compatible with AI work.

AI effects have to run constantly, even if they don't show. Normally the cause is that you are using an effect from an non-AI released source, i.e. an afterburner effect from a flyable aircraft or smoke from a ship.

What you have to do is check for any aircraft that are at that base that are using non-AI compliant effects and amend them to work constantly.

Please note. FS uses areas when loading traffic. My first issue with this was crashes at Lakenheath when testing was caused by a Jaguar spawning on return to Coltishall.

So what I suggest is check to see if it happens at one specific time or whether it happens at multiple times. If it is multiple times the chances are that the cause is an aircraft operating from there. If it only happens at one time on one day then it is most likely to be a transient aircraft.

Try removing all AI traffic from that base and see if the result changes. Only start to reload things IF you have eliminated the effect issue as a cause.