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

MSFS20 ADE 2020 Alpha 21 HotFix 4

FlyingAxx said:
EDIT: Is there any way selecting a different folder for the fianlly copied package, instead of the MSFS community one?
Click to expand...
Not specifically but I think some folks have found a way round it and might reply
 
scruffyduck said:
Not specifically but I think some folks have found a way round it and might reply
Click to expand...
My approach is straight-forward. Set the desired location for ADE projects with the Program Options Project tab and on the General tab be sure "Show Copy To Community Folder" is unchecked. Now the compiled package stays with the project in your ADE projects location and I use MSFS_Addon Linker to link the package to MSFS community. Simple.
 
Hi Jon. I get this when using the LOM to rebuild the library:
Untitled.png

This is from asobo-airport-kcof-patrickafb
 
Have tried everything from opening as administrator to changing folder attributes to not read only and not hide but I cannot get any stock airports to generate with this app. I'm using the latest version with HF4. Any help will be much appreciated. Thanks.
 

Attachments

  • basefile.jpg
    basefile.jpg
    139.4 KB · Views: 145
I replied to your PM but if you are using SU9 then Asobo moved the base files and ADE needs to be updated. This will not be available for a week or so since I am currently on vacation
 
Good day All, don’t know if anyone else is experiencing the same. After MSFS updated earlier this morning when I build my project it does not fail nor skip anything but there is a message noting that “ASOBO normal map convention” not found. I worked on the same project last night and build the project and all were fine. This morning MSFS updated I re-build the same project to test and this happened.
1.jpg
 
I get those. They aren't actually warnings, but notices about the material texture it is compiling. You can ignore it.
 
rhumbaflappy said:
I get those. They aren't actually warnings, but notices about the material texture it is compiling. You can ignore it.
Click to expand...
There is definitely something wrong after the update. I added some new library objects and some models to the project today, it builds correctly, but only the library and models prior to the update shows in the sim the newly added once does not show when in the sim.
 
You must log in or register to reply here.
Back
Top