MSFS20 Error with sdk version 0.8.0 during the build package

[F-SERG]

Good evening,
Very big concerns appeared after the last update of msfs and sdk 0.8.0, I had the unpleasant surprise that my projects in the Community directory were no longer recognized. I therefore resumed under msfs in the Dev my projects part, the scene was loaded in the simulator but during the build package a lot of errors appeared and therefore impossible to build correctly..
Have you encountered these difficulties? for me everything worked fine before.
Thank you in advance for your help

cordially

(translate with google)

-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Erreur avec la version sdk 0.8.0 lors du build package

Bonsoir,
De très gros soucis sont apparus après la dernière mise à jour de msfs et des sdk 0.8.0, j'ai eu la désagréable surprise que mes projets dans le répertoire Community n'étaient plus reconnus. J'ai donc repris sous msfs dans la partie Dev mes projets, la scene à bien été chargée dans le simulateur mais lors du build package beaucoup d'erreurs sont apparues et donc impossible à builder correctement.
Avez-vous rencontré ces difficultés? pour moi tout fonctionnait très bien avant.
Merci part avance de votre aide

Cordialement

 

[clements]

I have not encountered this problem. The patch’s release notes say that it may cause issues with the Community folder. Asobo suggests removing contents of the Community folder and run MSFS. Assuming MSFS runs, exit the flight simulator and then move files back into the Community folder.

Je n'ai pas rencontré ce problème. Les notes de version du correctif indiquent que cela peut entraîner des problèmes avec le dossier Communauté. Asobo suggère de supprimer le contenu du dossier Community et d'exécuter MSFS. En supposant que MSFS s'exécute, quittez le simulateur de vol, puis replacez les fichiers dans le dossier Communauté.

 

[ronh]

Did everyone see this in the SDK notes:

Developer mode changes​

• Project Editor:
  • Export All button created to properly export the packages for Community and Marketplace.
    The associated documentation is available in the Export Window section.

• Note: Without using this button, the generated packages may not work as expected.

 

[geeman72]

I've got an issue with latest in that all my models no longer show and get vfs errors, was fine previously and have tried rebuilding them but same problem. So essentially have a project that has lost all my models and can't get them back!

 

[Andrew]

I also got these problems, then solved it. I post here what I posted at Flightsim.to in the article about renaming model libs. The first section is not so relevant here, but the rest is:

There is more to this than just renaming the library and recompiling. As already mentioned, you will get a lot of red lines. I have found a few things that are important to get this right. Before renaming the library, delete the package from both the Community folder and your Projects folder. Then rename the library. Even if you see the correct path for the library in the Editor, still point to your new library, then save, then compile. My new model libs are named like “li-modelLib” for my ENLI project.

Now make shure you have the assets in your PackageDefinitions xml like this: First the ContentInfo assets, then the ICAO assets, then the ArtProj assets. I show here mye ENLI xml:

<AssetPackage Name=”at-enli” Version=”0.1.0″>
<ItemSettings>
<ContentType>SCENERY</ContentType>
<Title>ENLI – Farsund Lista</Title>
<Manufacturer/>
<Creator>A.Thomsen</Creator>
</ItemSettings>
<Flags>
<VisibleInStore>false</VisibleInStore>
<CanBeReferenced>false</CanBeReferenced>
</Flags>
<AssetGroups>
<AssetGroup Name=”ContentInfo”>
<Type>ContentInfo</Type>
<Flags>
<FSXCompatibility>false</FSXCompatibility>
</Flags>
<AssetDir>PackageDefinitions\at-enli\ContentInfo\</AssetDir>
<OutputDir>ContentInfo\at-enli\</OutputDir>
</AssetGroup>
<AssetGroup Name=”ENLI”>
<Type>BGL</Type>
<Flags>
<FSXCompatibility>false</FSXCompatibility>
</Flags>
<AssetDir>scene\</AssetDir>
<OutputDir>scenery/world/scenery\</OutputDir>
</AssetGroup>
<AssetGroup Name=”Listamodels”>
<Type>ArtProj</Type>
<Flags>
<FSXCompatibility>false</FSXCompatibility>
</Flags>
<AssetDir>PackageSources\li-modelLib</AssetDir>
<OutputDir>scenery/global/scenery\</OutputDir>
</AssetGroup>
</AssetGroups>
</AssetPackage>

Compile this, copy your scenery to Community, then recompile.

With the USA Update and SDK version 8, my three projects now compile without ANY red or orange lines.

Today I tried the "export all" button. Still no red lines, and the scenery ended up as a zip in a Community folder. Since I do not need it to be zipped, I still use the normal Build button, and my three sceneries are working perfectly. So I do not understand why I have to use the export all button.

PS; ronh: Your link is not working. I would very much like to read that stuff myself ;-)

 

[rhumbaflappy]

I had a project with some polygons of different types. The new build's DevMode displayed perhaps 40 'ghost' polys with errors. I had to delete them, save the scenery, and build the package to get rid of them. Now all is working as before. No Idea what these polys were.

 

[GaryGB]

Did everyone see this in the SDK notes:

Developer mode changes​

• Project Editor:
  • Export All button created to properly export the packages for Community and Marketplace.
    The associated documentation is available in the Export Window section.

PS; ronh: Your link is not working. I would very much like to read that stuff myself ;-)

Hi Andrew:

Browse in Windows Explorer (aka "My Computer" / "Computer" / "This PC") to the root folder where MSFS SDK 0.8.0.0 is installed

Double-click on Index.html, so it opens in your default web browser

[MSFS_SDK_0_8_0_0 install path]\Documentation\index.html <-- (path on disk)


AFAIK the info displayed / accessed in the web page on disk, matches the info displayed / accessed in the *.CHM file on disk.

Browse - via Left Side Menu Bar Links:

Getting Started >

Release notes >

SDK release 0.8.0 > Developer mode changes > Project Editor


Browse - via Left Side Menu Bar Links:

Developer Tools >

Package Tool >

Project editor > Export Window

[MSFS_SDK_0_8_0_0 install path]\Documentation\04-Developer_Tools\Project_editor\Export_Window.html <-- (path on disk)

GaryGB


PS: A bit of humor as we learn "new" methods of working with "old" technology:

BTW: Perhaps the funniest part of that scene is when they refer to the Macintosh Pro as a "Computer".

 

[ronh]

PS; ronh: Your link is not working. I would very much like to read that stuff myself ;-)

Didn't mean to link - just copy paste of the NOTE part - they made a breaking change I would assume.

 

[Andrew]

Hi Andrew:

Browse in Windows Explorer (aka "My Computer" / "Computer" / "This PC") to the root folder where MSFS SDK 0.8.0.0 is installed

Thanks Gary; that SDK is not easy to navigate. I see now I can use export all to validate, but keep on using the build button, as I like to rename my sceneries and zip them myself.

PS,

That Star Trek scene is one of the finest ever

 

[Luisfvillani]

Good Morning !!
I need help after doing nine successful projects, yesterday after the update my SDK is no longer compiling, the Apron function is not changing textures.

Thanks...

 

[Andrew]

Apron textures are now drag and drop. Drag the texture you want from the material editor into the property window for your apron - done!

 

[Luisfvillani]

Apron textures ok, thanks Andrew. But now my biggest problem that after the update I can't generate new scenarios, but when I generate my old projects everything is normal and I follow the same line of the scenarios already ready ....

 

[F-SERG]

Hello,

First of all thank you for your answers, I tried according to your advice the modification of the packages etc ... but nothing helped, I am going in circles, maybe there is one thing that I do not have not well understood in maneuvers. My project is an airport of my own design that I installed near my home, everything was working fine until this last update.

I am ready to send (if possible privately) a zip from my original airport so that it can be modified accordingly. So if there is a nice member who would like to make this change and send it back to me so that I look as it was done and with the final package, I will be very happy because it has been several hours that I have been leaning on this problem without much success.
A big thank you in advance

cordially

Serge
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Bonjour,

Tout d'abord merci pour vos réponses, j’ai essayé selon vos conseils la modification du packages etc.… mais rien n'y fait, je tourne en rond, peut-être qu'il y a une chose que je n'ai pas bien compris dans les manœuvres.
Mon projet est un aéroport de ma conception que j'ai installé près de chez moi, tout fonctionnait bien jusqu'à cette dernière mise à jour.

Je suis prêt à faire parvenir (si possible en privé) un zip de mon aéroport original afin qu'il soit modifié en conséquence. Alors s'il y a un sympathique membre qui voudrais bien apporter cette modification et me la renvoyé afin que je regarde comme cela a été fait et avec le package final, j'en serai très heureux car cela fait plusieurs heures que je suis penché sur ce problème sans grand succès.
Un grand merci par avance

Cordialement

Serge