• 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.

Introducing General Release 3.4.3.6

Status
Not open for further replies.

gadgets

Resource contributor
Further to my post of yesterday, in the third paragraph I either didn't give you enough info or too much regarding the need to disable certain ORBX files to ensure AIFP selects your add-on rather than the ORBX one.

AIFP has two modes when specifying the add-ons to be collected: Scenery Library or Folder Tree. If you choose the former and your add-on(s) are of higher priority than any ORBX Library, AIFP will (should) always pick your add-on. On the other hand, Folder Tree has no inherent priority other than file/folder name which governs the order the folders are presented in the tree. So long as you don't include any ORBX libraries in your selection, there's no issue. But, if you do select an ORBX library that also includes the same ICAO as your add-on, you may have to take further action as noted in the earlier post. So, do yourselves a favor and use the Scenery Library method when you can.

But, I have had situations with my own airports whereby the ORBX library was either of lower priority in the Scenery Library than my airports or was not active, but FS nonetheless displayed the ORBX airport. In those cases, The only way I could correct the situation was to take the type of action described above. I have no idea whether this was the fault of ORBX or FS/P3D, and it may not matter any more since this issue may no longer exist in later versions of FS/P3D and ORBX libraries.

Sorry if I mislead you. I was simply tring to be helpful.

Don
 

gadgets

Resource contributor
I have just posted General Release 3.4.2.3 to http://stuff4fs.com.

It was recently discovered that, while AIFP properly handled most P3D add-on packages, if an add-on package saved in, say, ...\Documents\Prepar3d v4 Addons contained only add-on.xml, the balance of the project being saved elsewhere, AIFP ignored the addon entirely. AIFP now handles such add-ons properly.

Also, as some of you realize, many websites now require cookie-validation, making automatic download of aircraft repaints by AIFP from such sites a more difficult task. Due to the numerous repaint formats with which AIFP must cope, repaint processing is already VERY complex and I am hesitant to undertake further major modifications. I was hopeful that a fairly simple, straightfoward mechanism for cookie-validation would reveal itself. But, so far my search has been fruitless - perhaps because cookie-validation is inherently complex.

Consequently, while automatic repaint download remains active in AIFP, it will only work with sites that don't enforce cookie-validation. For the sites that do require it, you will receive some sort of error message, and you'll have to download the desired repaint manually. Those repaints should be saved to whatever folder you have nominated for "Repaints". Once downloaded, repaints will be processed as before. I'll keep looking, but I'm not hopeful.

EDIT: Oops! Forgot something in 3.4.2.3. It's now 3.4.2.4

EDIT2: I have temporarily reverted to Release 3.4.2.2. 3.4.2.4 has a major shortcoming.
 
Last edited:

gadgets

Resource contributor
The issue with 3.4.2.4 has been resolved. I have posted Development Release 3.4.2.4(a) at http://stuff4fs.com. 3.4.2.2 remains the General Release.

There have been a couple other issue reported with 3.4.2.4 for which I am awaiting supplementary information. Once these issues have been addressed, I'll make a new general release. In the meantime, if you want to take advantage of the new capability advertised in 3.4.2.4, please download the Development Release.
 

gadgets

Resource contributor
Please disregard the development release announced yesterday. It doesn't solve the complete issue.

Another one ASAP.
 

gadgets

Resource contributor
It wasn't as difficult as I had feared to correct the earlier development release.

Development Release 3.4.2.5(b) is now available from http://stuff4fs.com. It will be automatically discovered by AIFP 3.4.2.5 or later (provided you have detection of new development releases enabled).
 

gadgets

Resource contributor
I have just posted Development Release 3.4.2.7 to http://stuff4fs.com. Depending on the version of AIFP you are currently using, 3.4.2.7 should be discovered automatically.

This release is necessary to correct an issue with the recently-introduced feature to use all add-ons that are Active in the Scenery Library.
 

gadgets

Resource contributor
I have just posted Development Release 3.4.2.8 to http://stuff4fs.com. Depending on the version of AIFP you are currently using, 3.4.2.8 should be discovered automatically. If not, please download it directly from the website

There have been several issues (and non-issues) reported over the last couple of weeks. I believe all these have been fixed. Also, while investigating those reports, I discovered a couple other things that needed attention - two of which were long standing. These too have been fixed.

I would very much appreciate some of you "power users" giving this new release a quick "once over" and reporting. Thanks in advance. Barring adverse reports over the weekend, I plan to re-release generally early next week.
 

gadgets

Resource contributor
if you are using Development Release 3.4.2.13, please download and install Development Release 3.4.2.14 from http://stuff4fs.com. Be sure to install all files in the .zip, not just the .exe. 3.4.2.13 contains an updated set of MCX.dlls but does not include the full set of required files. 3.4.2.14 includes the missing files.
 

gadgets

Resource contributor
General Release 3.4.3.0 is now available at http://stuff4fs.com. If you are using a recent development release, the new general release should be discovered automatically. Otherwise, you'll have to download it manually (hopefully for the last time).

The new release includes several fixes, as detailed in the included Version History. One fix you will notice immediately upon opening AIFP is that the Main Panel is disabled (greyed-out) whenever AIFP is re-generating the airport database. I recently discovered that inputs made while the airport database was being regenerated often were ignored or, worse, resulted in an exception being thrown.

As well, you will notice a new sub-folder named DLLs in your AIFP folder. AIFP uses the .dlls from ModelConverterX in several of its functions. Previously, a selection of those .dlls were saved in the AIFP main folder - an approach that more than once has resulted in incomplete application updates. The full set of MCX .dlls are now saved in their own sub-folder. If you like to keep your application folders tidy, you may delete all the .dlls from your main AIFP folder; they are no longer used.

Finally, I had hoped AIFP's aircraft viewer (which rely on the MCX .dlls) would be MSFS2020-compatible in this release. Unfortunately, the extent of the updates needed to the .dlls was greater than Arno anticipated and he needs more time. As soon as Arno finishes his updates, I'll re-release.
 

gadgets

Resource contributor
If you like to keep your application folders tidy, you may delete all the .dlls from your main AIFP folder; they are no longer used.
This was bad advice. You can do this soon, but there will be a problem with 3.4.3.0 is you do it now. If you've already done it and you can't retrieve the deleted files, copy all the .dlls from your DLLs sub-folder back into, your main AIFP folder.

I hope to have a fix shortly.
 

gadgets

Resource contributor
General Release 3.4.3.1 fixes the issue with 3.4.3.0.1. Once installed, you can safely remove the .dlls from your main AIFP folder.

Sorry for the false start earlier.
 

gadgets

Resource contributor
It seems the startup-issue in 3.4.3.0 is still not fixed.

It WILL be fixed in 3.4.3.2.

In the meantime, I have designated Release 3.4.2.14 as the general release. If you have already loaded 3.4.3.1 and can't wait for 3.4.3.2, then go to http://stuff4fs.com, navigate to AI Flight Planner and select Latest General Release from the menu.
 

gadgets

Resource contributor
3.4.3.2 is now available as the AIFP General release at http://stuff4fs.com.

My attempt to "clean-up the main folder by moving all the .dlls into a separate folder was at fault. Don't know why. All the .dlls are back in the main folder and must remain there.
 

gadgets

Resource contributor
3.4.3.6 is now available as the AIFP General Release at http://stuff4fs.com. (It should be discovered automatically by recent AIFP releases.)

The new release includes an updated Aircraft Viewer and several changes to the Aircraft Editor, including a fix for a possible exception on systems having both FSX/P3D and MSFS2020.
 
Status
Not open for further replies.
Top