• Which the release of FS2020 we see an explosition of activity on the forun and of course we are very happy to see this. But having all questions about FS2020 in one forum becomes a bit messy. So therefore we would like to ask you all to use the following guidelines when posting your questions:

    • Tag FS2020 specific questions with the MSFS2020 tag.
    • Questions about making 3D assets can be posted in the 3D asset design forum. Either post them in the subforum of the modelling tool you use or in the general forum if they are general.
    • Questions about aircraft design can be posted in the Aircraft design forum
    • Questions about airport design can be posted in the FS2020 airport design forum. Once airport development tools have been updated for FS2020 you can post tool speciifc questions in the subforums of those tools as well of course.
    • Questions about terrain design can be posted in the FS2020 terrain design forum.
    • Questions about SimConnect can be posted in the SimConnect forum.

    Any other question that is not specific to an aspect of development or tool can be posted in the General chat forum.

    By following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.

Simconnect

I've fixed the cause of the exception when leaving an airport area.

Please copy the attached file into your AFLT\P3D Files folder and either recompile your airport or also copy it into Documents\Prepar 3d v4 Add-ons\AFLT to P3D (in that order)

Once Prepar3d is running, open the Connect/Disconnect dialog. You'll notice it's somewhat different from before but don't worry about that. Just check the title bar to ensure is says version 4.0.03.
 

Attachments

gadgets said:
Now I'm almost certain you didn't use the latest version, because it should have thrown an exception when you left the airport area. So, please limit your checks to approaching the airport from > 25 nm.
Click to expand...

I checked the date in my Documents folder and it is 4-25. I then added the update you gave me yesterday and the Documents folder showed 5-3. I then opened AFLT and compiled my airport and saved the placement data again (no changes). After this I then went back and checked the date in my Documents folder, it was changed back to 4-25.
 
You need to copy the file I sent you into your AFLT\P3D Files folder before recompiling. (When you re-compiled, you overwrote the new file with the old) But, there's no need to recompile if you have copied the update directly into the Documents folder.
 
gadgets said:
You need to copy the file I sent you into your AFLT\P3D Files folder before recompiling. (When you re-compiled, you overwrote the new file with the old) But, there's no need to recompile if you have copied the update directly into the Documents folder.
Click to expand...

I did. There are two files in my main AFLT folder -

1. AFLT (Simconnect) - 5/03/2020 96kb This is the same file that is in my Documents folder.

2. AFLT - 4/25/2020 838 kb This is what I use to start AFLT

My computer -

Gigabyte Aorus Z270x Gaming 7 Processor:
Intel Core i7 7700 Quad Core CPU
System Memory: 32GB (2 x 8GB) Trident DDR4 SDRAM
Primary SSD: 500GB Intel Solid State Drive (Newest Gen)
8GB Nvidia GeForce GTX 1070
Windows 10- 64 (Pro) 1909
nVidia Driver - latest
 
AFLT (SimObjects).exe must go into your AFLT\P3D Files folder, not the main AFLT folder.

Clearly, processing power is not the issue.
 
gadgets said:
AFLT (SimObjects).exe must go into your AFLT\P3D Files folder, not the main AFLT folder.

Clearly, processing power is not the issue.
Click to expand...

I made the changes as you have instructed and made the identical flights that I did earlier and there were no problems. 4.0.0.3 displayed with our any issues.

As I flew over the airport I noticed a couple of items I needed to correct. I make the changes using AFLT and then compile and saved the airport. I then go out to my Documents file and AFLT(SimObjects) has been changed to the earlier version (04/25/2020). Before I made the airport changes I verified in my Documents file that AFLT(SimObjects) had today's date. At least on my machine running the Compile in AFLT appears to overwrite AFLT(SimObjects) in the Documents file. :confused:
 
4.0.0.3 displayed with our any issues.
Click to expand...
Glad to hear it. It was a struggle, but now Simconnect is in complete control of the activation and deactivation of simobjects.

Before I made the airport changes I verified in my Documents file that AFLT(SimObjects) had today's date. At least on my machine running the Compile in AFLT appears to overwrite AFLT(SimObjects) in the Documents file
Click to expand...
Yes, that's why I gave you a couple alternatives. AFLT (SimObjects).exe normally "lives" in two folders:
  • AFLT\P3D Files, and
  • Documents\Prepar3D vn\Add-ons\AFLT for P3D - from which it executes.
When you compile for P3D, as part of the setup process AFLT copies AFLT (SimObjects).exe from AFLT\P3D Files to the Documents folder. Since you saved AFLT (SimObjects).exe to your main AFLT folder and not the P3D Files subfolder, every time you compiled you overwrote the fresh copy you had placed in the Documents folder with the old version.

Anyway, all's well that ends well, you are now able to "fly" without AFLT overloading SImconnect - at least you will when you save AFLT (SimObjects).exe to the correct folder.
 
You must log in or register to reply here.
Back
Top