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

MCX Batch broken ?

Messages
607
Country
france
Hi Arno,
I tried this afternoon to convert an old FSX lib into a p3d one using the batch process in order to assign new guids like I 've done often. With yesterday's revision of MCX, the process seems not to be executed like it used to be.
Is there a problem with the revision or you changed the procedure ?
Thank you
 

arno

Administrator
Staff member
FSDevConf team
Resource contributor
Messages
32,884
Country
netherlands
Hi,

I just tried but the batch wizard still seems to work fine here.

Could it be that you are missing the path to xtomdl or bglcomp for the specific version you export to? The batch wizard does not show a nice error for that (it is lost when clearing the event log in the end).
 
Messages
607
Country
france
You were right as usual...
Don't know why, but only the paths for P3dV5 were set. FSX and V4 were erased but I didn't do that, ever !
Anyway, thank you again.
 

tgibson

Resource contributor
Messages
11,343
Country
us-california
 

arno

Administrator
Staff member
FSDevConf team
Resource contributor
Messages
32,884
Country
netherlands
Probably my change to the configuration files and then combined with the FSX and P3D SDK not being in the registry so that MCX could not automatically detect them.
 
Messages
607
Country
france
Thank you Tom. I hadn't watched this thread which is totally relevant.
It's all right now.
 
Top