jorgen.s.andersen

WoAI creates standard .bgls, so they are not a problem here. I need to think a bit about this one.. Jorgen

Those two will exclude traffic from specified locations - at least that's what they are supposed to do. Did you no-traffic issue begin with the installation of either (or both) of those two sceneries? Jorgen

Like I said before, if you have run that convert function in AIFP, then what is in \Scenery\World\Scenery is OK. What you're looking for now is a .bgl traffic file not located in \Scenery\World\Scenery. It has to have the string "traffic" in the file name, and the extension has to be .bgl. Jorgen

Neither of those two you mention is IT. I should have said that a traffic file like we're looking for will have the file extension .bgl. Jorgen

In the right-hand pane of the AIFP screenshot, you see all the aircraft are in black. That means AIFP sees them as installed. That you have no AI traffic at all in my experience means that somehow, somewhere within the scope of your FSX installation there is a FS9 traffic file lurking, that has evaded your converting all FS9 traffic to FSX. This converting was the right thing to do, but it only converts what files are in the \Scenery\World\Scenery folder - the normal traffic file folder. If there is a traffic file in an add-on scenery folder, for example, then that will not be converted. It is such a file that you're looking for. What I would do here is to use File Explorer, and direct it to C:\Program Files(x86)\Steam\steamapps\common\FSX. Then enter "traffic" without the quotes in the search box. This will find all the files with "traffic" in their file name, then go through them and find the ones not located in \Scenery\World\Scenery. Then you have the culprit. Jorgen

Dan is da man! Jorgen

The exception code here: Exception code: 0xc0000005 says that "something" attempted to write to an area of RAM where it had no access rights. There is nothing to say what this "something" is, but in all the cases I have seen, it has proven to be a badly programmed or incompatible add-on. Jorgen

See, I just knew he would turn up! You sure you're not John Wayne in disguise? And note the exception code in Zippy's example. If all else fails, that's the one that will tell us what's going on. Jorgen

The best indicator for what os going on here is actually found in the Windows Event Viewer. What you do is first of all note down the (approximate) time of a crash. If you don't remember one, provoke a new crash and note the time. Then right-click on your Windows Start button and select Event Viewer, third item in the menu from the top. Click on the little arrow next to "Windows Logs", then click on "Application". Now, in the top center pane you'll see a lot of events with time stamps. Scroll down to the time of your crash, and then there should be one or two with the title "Error" on the left. Click on them, and the error information we need will then be in the bottom center pane. Copy and paste that information into a post here. If you cannot do that, then find the "Exception code" in the error information and post that here. Our resident U.S. Cavalryman (aka Mr. Zippy) has a nice graph that show how to get there, if he can post that here. Jorgen

Try SODE, available here: https://sode.12bpilot.ch/?page_id=9 Jorgen

They are both compatible, but when you say "AIG", do you mean the AIG flight plans themselves, or the flight plan bgl files created by the AIG Manager? Jorgen

DX9.0c Redistributable! That's the one. And it actually works.... and it does not get overwritten by Windows Update. Jorgen

Rhys, That your Windows has DX12 does not mean a thing for FSX, which wants DX9c, and for FSX your hardware is just fine - I used to run it on a much less powerful machine. In case you want to make sure you have DX9c, there's a DX updater available somewhere, but I forgot the link to it. And just remember - everything that you can do with the "old" FSX, you can do with the Steam Edition, it's just its location that changed with Steam. And there's no fixed place for where the tweaks should go, just place them "somewhere" where it makes sense to you, and you can find them again easily, in case you want to change something later. Jorgen

You're lucky with a good lady that appreciated flightsimming!!! You can install the Steam edition for her also - in fact, you can install Steam on as many computers as you want. It's like this - download once, install as many copies as you want. Jorgen

And you can also turn UAC off. Jorgen

Hit "Take no action" and then just leave everything alone until the smoke has died down, but do not remove the DVD - and I take it that the reader IS able to read DVDs? Then go to File Explorer, open the DVD drive and maneuver to the installer. Then right-click on it etc etc. But- the big question: the Steam edition does not come as a DVD set, but as a download, so why this question? Jorgen

Find the installer (which can have many names, unfortunately, but maybe (if you're lucky) is called something like install.exe). Right-click on that, and select "Run as administrator" from the menu. Jorgen

And, to a degree, the tweaks are even appliccable in P3D! Jorgen

Welcome back! I'm still around, even though I don't have FSX any more, "only" P3D Jorgen

Yes to both, it's only the path to the Steam edition that is different from the "old" FSX. Jorgen

Paul, I do not understand why you have to wait 45 minutes to one hour every time you want to run FSX:SE. I just install it once and for all, then run it as I please, with further no downloads necessary. And you can do everything in SE that you could do in the "old" FSX, the only issue I have is with the long file path. Jorgen

For cleaning the registry, I use the Eusing Free Registry Cleaner. There are many others out there, bith freeware and payware, but some of them are really aggressive in what they do. As always, back up before you attempt such a cleaning. Jorgen

Paul, it does make some sense. How did you get the first set of disks? And please DO NOT attempt to install the new set, until we have cleaned up the "old" installation. For that, uninstall everythig FSX-related through the Windows Control Panel - FSX itself last. Then delete all the folders related to FSX. A registry cleaner would come in handy here - do you have one? If you do, use it as you normally would, if you don't have one then STOP here and tell us. Now this is where others would be very welcome to chime in with their recommendations, as I have not had FSX on my system for ages, and my knowledge of that topic will be somewhat rustic, to put it nicely.... Jorgen

I have never seen this before, but you micht try to rename the file instead of deleting it, by adding for example '.old' to it, so the file name would be: aircraft traffic.bgl.old Jorgen

Windows 10 is actually up to 22H2 now. And regarding FS9, I never had it. Jorgen