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

Failed initialization of Blender

Messages
195
Country
us-ohio
I'm new to Blender and I'm just getting used to it so forgive me if this question has an obvious solution or I'm providing too little information. I recently downloaded the latest version of Blender and the latest compatible FSX/P3D Toolset. I followed the tutorial offeredfsdeveloper.com/wiki/index.php?title=Blender2P3D/FSX but when I get to the "Configure the SDK" step, Blender keeps on giving me an error. I tried autodetect and when that didn't work, I tried manually selecting it. Both times it gave an error message. Help?
shot152.png
 
Hello...

Do you have the FSX SDK installed? and for which FSX is this? Is it FSX-A or is it FSX: Steam?
 
Hello
What were you doing prior to initializing? Were you attempting to compile? Try this,... before initializing make sure you have a friendly name for the model and Quid # as well.
 
Hello
What were you doing prior to initializing? Were you attempting to compile? Try this,... before initializing make sure you have a friendly name for the model and Quid # as well.
I did not do anything to the model, I just had the default cube that you get when you opened Blender. Unfortunately assigning the model a name and quid does not work. Additionally, I tried to run blender as admin and open a saved blender project but that does not solve the problem either.
 
Have you tried to initialize after deleting the default cube and camera etc? Meaning, nothing visible or loaded into the viewport?
 
Have you tried to initialize after deleting the default cube and camera etc? Meaning, nothing visible or loaded into the viewport?
Just tried that and it still is giving me that error. I thought manually finding the SDK might work but when I do so it also gives me an error
 
Hmmm... does your MCX work without any problems? If you haven't tried that please do... try to compile something within MCX...

Hopefully, @Vitus can look at this error too.
 
Hmmm... does your MCX work without any problems? If you haven't tried that please do... try to compile something within MCX...

Hopefully, @Vitus can look at this error too.
All my other programs such as MCX, ADE, and GMAX work. It's just blender at the moment.
 
Hi Jason,
What's the error when you try to manually select the modeldef.xml?
 
When I try to manually select the SDK file path, I also get an error. I don't know if that might help y'all to figure out what is going on but it looks like this:
shot153.png
 
Hello again...

Can We assume that the SDK was installed prior to?

Try this... deactivate the Toolset and delete it. Shut down Blender and then reload it again... Next, re-install the toolset and activate it again.
 
This is odd indeed...
The first error means that the addon can't parse the XML file. The second error makes no sense to me.... It might be a UAC issue or maybe a corrupt installation?
Maybe check if the addon installed correctly. It should be in:
%APPDATA%\Blender Foundation\Blender\2.82\scripts\addons\P3DFSXToolset

You could try to reinstall it again.

Another thing might be to run Blender as Admin and see if that does something.

I really don't know what it could be. I just installed Blender on my Laptop to test this and it picks up the FSX:A SDK with no issues.
 
This is odd indeed...
The first error means that the addon can't parse the XML file. The second error makes no sense to me.... It might be a UAC issue or maybe a corrupt installation?
Maybe check if the addon installed correctly. It should be in:
%APPDATA%\Blender Foundation\Blender\2.82\scripts\addons\P3DFSXToolset

You could try to reinstall it again.

Another thing might be to run Blender as Admin and see if that does something.

I really don't know what it could be. I just installed Blender on my Laptop to test this and it picks up the FSX:A SDK with no issues.
The SDK is correctly installed and has been working for all my other programs. Reinstall of the addon did not work. I also tried reinstalling blender and then reinstalling the addon. It still gave me the error message. In case you wanted to know, here's the Blender Addon in the Appdata folder:
shot155.png
 
I'm still clueless what could cause this. Another thing to try would be to restore the original modeldef.xml and see if the addon can parse it then.
 
Another shot in the dark:
Open the find_modeldef.py file with a text editor, and un-comment line 100. It should look like this afterwards:
Code:
[...]

    def execute(self, context):
        print(' ModelDef.xml File path = ',self.filepath)#setup variable to hold filepath
        bpy.context.scene.fsx_modeldefpath = self.filepath
        print('fsx_modeldefpath =',bpy.context.scene.fsx_modeldefpath)
        
        try:
            tree = etree.parse(bpy.context.scene.fsx_modeldefpath)

[...]

Then open Blender, open the system console (Window->Toggle System Console) and initialize the SDK. Right before the error messages you should get a line printing out the modeldef.xml path. Something like:
fsx_modeldefpath = 'C:\Program Files\Microsoft Games\ [...]'

Does this path match the path to your actual modeldef.xml?
 
Blender should always start up with Administrative Rights.

For this to happen you need to right-click on the Blender Icon. Click on "Properties". From there, click on the "Compatibilities" and click on "Run this program as an administrator". Click on "Apply" and then 'OK'. Blender needs full access to the SDK, so running this program as an administrator is necessary. Is the SDK installed in the default location?

Load up Blender - deactivate the plugin and delete the Toolset.
Close Blender - restart Blender and reinstall the Toolset and activate it.

Did you reinstall the SDK? at all while trying to get the toolset to function? If you did you will need to deactivate and delete and reinstall the toolset again.
 
Back
Top