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

New Patch 1.10.7.0

Messages
19
Country
mexico
Good day!

I was reading the release notes for the patch and the first paragraph says:

Some packages in your community folder may not have been updated and, as a result, may have an unexpected impact on the title’s performance and behavior. Please move your community package(s) to another folder before relaunching the title if you suffer from stability issues or long loading times.

I am still downloading the patch, and I read that there is no new SDK with this patch.

So what does it mean?? do we need tu update the scenery we have made or what do we need to do ??

Cheers!
 
And for me, this patch boke the moddev compiler.
DevMode compiler stop working with this patch...
i cant back for the old version.....is a shame, mandatory patchs...
 
Also had CTD when compiling package. But after deleting Packages and _PackageInt folders and clean compile all works fine as before. Help-Download SDK the same version 0.6.1.
 
This morning in Europe, we can download SDK 0.7.0.0. A few modification and no documentation updated.

For CDT, we can make some investigations following this topic: https://forums.flightsimulator.com/t/ctd-after-latest-update-update-5/309576/310
FIXED WITHOUT REINSTALL, but still a PITA. (MS Store Version…Can’t comment on steam)

Goto c:/users/(username)/AppData/Local/Packages/Microsoft.FlightSimulator_8wekyb3d8bbwe/SystemAppData/wgs folder
There should be two folders there, one called “t” and the other with a huge alphanumeric name like 000901F6… Open that one.
Under that folder, there are a bunch of other Alpha Numeric (ie 69D9FE4C2AB94940B11A4D26A23A9561) name folders. Open each one, and you’ll find a container. file, and then another “file” with another huge alpha numeric name (i.e. A1036E4CDAAB21882AD5630E81466F). Open that file up with NOTEPAD or NOTEPAD ++. If you get nothing but screen barf, exit out and go to the next folder. Don’t touch that folder.
Go to the next numbered folder and continue opening the alpha numeric files. As you go through these folders, some of those alpha numeric files will contain your controller data that’s easily readable… If you find one, exit the editor and delete the folder it’s in.
Delete all the folders that reveal they belong to a controller until the only thing left are Number folders with alpha numeric files that can’t be read.
Restart Flight sim. All your previous profiles will be gone, but now you can plug in peripherals and use the DEFAULT profile. You can EDIT the default profile and save it, as long as it has at least ONE assignment, If you try to save an empty profile it will crash. (will update as I experiment further)

Like I said, huge PITA, and you have to careful, but it beats a complete reinstall.
 
Other information:
At the begining of October, I have release a development version of CYMX-Mirabel (v0.3.0 and MSFS native) compiled for MSFS v1.8.3.0. This afternoon, I have been surprised: my excludes aren't functionnal since the last upgrade in v1.10.7.0
I think that some modifications are been made in the simu and excludes for our scenery should be recompiled to be in conformity ... so I have to make another version.
 
I am also experiencing CTDs when building a package. So far it seems it is due to some of the models in the package source. No pattern found so far. Will try to update the SDK once I am at my PC and will report back.
 
OK, so installing a new version of SDK did not help.

But I have noticed that the CTDs happened when the compiles was about to compile objects converted to gltf prior to certain date (18 Oct in my case). So I re-converted them with current version of MCX and all is OK now.
 
The update screwed up my click spots in the VC.
Some clicks trigger switches far away from the click spot, others don't work at all.
Recompiling with the updated SDK doesn't fix it either.
 
Has anyone found a solution to the CTD issue in the SDK? I can no longer build packages that worked fine before the update.
 
Never mind, I tried what apollon01 did. Re-compiling my models with the newest version of MCX has fixed the issue and the SDK and sim no longer crash. For some reason, older models no longer seem to work with the package builder, so they need to be re-exported.
 
Back
Top