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

SDK 0.14

Messages
202
Country
england
Having downloaded the latest SDK, the installer Browse button is greyed out so I can't select my desired location, anyone else?
 

=rk=

Resource contributor
Messages
3,561
Country
us-washington
As in, "automatically detecting previous versions," greyed out? You are desiring to save the previous?
 
Messages
95
Country
russia
The new SDK did not fix any of the problems. Objects also disappear after Build all. A complete mess in the editor hierarchy. And CTD....CTD...
 
Messages
202
Country
england
I just need to install the SDK in my D drive so I need to select this but the browse button is greyed out. We had a similar thing when an Options button was used to enable selection of location, many people missed this. .?
 

rhumbaflappy

Administrator
Staff member
Resource contributor
Messages
5,237
Country
us-wisconsin
The SDK is now in 2 parts. MSFS_SDK_Documentation_Installer and MSFS_SDK_Core_Installer. I'm not sure you get a choice where to put these inastallations. Mine ended up on my C: drive in the root folder... bad idea.
 

Rotornut44

Resource contributor
Messages
537
Country
us-florida
I just need to install the SDK in my D drive so I need to select this but the browse button is greyed out. We had a similar thing when an Options button was used to enable selection of location, many people missed this. .?
The download button on the SDK changelog popup window doesn't even work for me. You can download the SDK from the help menu, but it's broken into "Core" and "Documentation" installers now. A launcher is no longer used, so it doesn't seem that installation path can be changed.

Edit: Looks like Dick beat me to it. After confirmation that it goes on the C: drive, it looks like I'll have to pass this update up. My C: drive barely has enough room to breath on it.. need that reserved for temp files and such. :rolleyes:
 
Messages
202
Country
england
The SDK is now in 2 parts. MSFS_SDK_Documentation_Installer and MSFS_SDK_Core_Installer. I'm not sure you get a choice where to put these inastallations. Mine ended up on my C: drive in the root folder... bad idea.
Seems strange as the installer discusses having disk space and choosing where to put it!
 

rhumbaflappy

Administrator
Staff member
Resource contributor
Messages
5,237
Country
us-wisconsin
I copied the SDK folder to a nice location on my D: drive (where I used to have it). I then uninstalled the SDK documentation and then the Core elements, and the new SDK is now on my D: drive where it belongs. With all the oddities of the new MSFS version, I wonder if Asobo underwent a massive staff change, as there is only nominal continuity of some basic things, like choosing where to install the SDK, and needlessly splitting it into 2 parts.
 

Lagaffe

Resource contributor
Messages
715
Country
france
You can also (if you have some place on C:\) install it and after move the directory on the good letter: C:\MSFS SDK => Z:\Tools\SDK_MSFS
Then you should define the new value for the environment variable used by the SDK.
This environment variable can be defined in the registry or via the Configuration Pannel - Advanced properties - Environment variables.

I confirm : only one sample WwiseSampleProject no more ! But it is possible that this one was installed with DA62 project (v0.1.7.0.msi the last one)

I confirm: Samples are in an other msi and has to be downloaded separately via the DEV Mode interface (Menu Help - Samples - Samples and Help - Samples - DA62)
 
Last edited:

Paavo

Resource contributor
Messages
192
Country
estonia
Yes. Samples are available separately from Dev menu > Help > Samples > Samples.

Installers were buggy previously. If I manually uninstalled older SDKs, then I could choose install path when installing the new SDK. Now the Browse button remains grayed out in both cases.
 

scruffyduck

Administrator
Staff member
FSDevConf team
Resource contributor
Messages
34,597
Country
unitedkingdom
I have asked Asobo whether the loss of setting a custom path to the SDK is intended or a bug
 

scruffyduck

Administrator
Staff member
FSDevConf team
Resource contributor
Messages
34,597
Country
unitedkingdom
Looks like its a bug. We should be able to set the path for the Core installer and then the other components will install in the same place. But the Browse button in the Core installer is greyed out

1627728704491.png


ASB know about it now so maybe they will issue an update. Waiting on them
 
Messages
927
Country
australia
There is a post on the MSFS forums which gives details how to change the install path. Basically, you call msiexec and parse the install directory as one of the parameters.

msiexec /i "path_to_.msi file" INSTALLDIR="path_to_install_directory" /qb

An example:
msiexec /i "T:\MSFS_SDK_Core_Installer_0.14.0.0.msi" INSTALLDIR="T:\MSFS SDK" /qb

See post in this thread:


Disclaimer: I haven't tried this myself.
 
Messages
95
Country
russia
How are you doing with reviewing the changes you made? I have to restart the simulator. Is there any solution to see the results without rebooting?
 
Last edited:

scruffyduck

Administrator
Staff member
FSDevConf team
Resource contributor
Messages
34,597
Country
unitedkingdom
There is a post on the MSFS forums which gives details how to change the install path. Basically, you call msiexec and parse the install directory as one of the parameters.

msiexec /i "path_to_.msi file" INSTALLDIR="path_to_install_directory" /qb

An example:
msiexec /i "T:\MSFS_SDK_Core_Installer_0.14.0.0.msi" INSTALLDIR="T:\MSFS SDK" /qb

See post in this thread:


Disclaimer: I haven't tried this myself.

Asobo have recognized the bug and should fix it
 
Messages
6,912
Country
us-illinois
I do not see an option to change target install folder path (yet), but this method Anthony31 linked to ...worked flawlessly for me (YMMV):


Paste the command string (edited for your desired target install path) into the Windows RUN dialog ...for example:

Code:
msiexec /i "c:\Users\Admin\Downloads\MSFS_SDK_Core_Installer_0.14.0.0.msi" INSTALLDIR="D:\MSFS SDK 0_14_0_0\" /qb


msiexec /i "c:\Users\Admin\Downloads\MSFS_SDK_Documentation_Installer_0.14.0.0.msi" INSTALLDIR="D:\MSFS SDK 0_14_0_0\Documentation\" /qb

Results:

Code:
__D\:
  |__MSFS SDK 0_14_0_0
     |__Documentation
     |__Licenses
     |__Schemas
     |__SimConnect SDK
     |__Tools
     |__WASM

GaryGB
 
Last edited:
Top