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

P3Dv2_XtoMDL Path?

falcon409

falcon409

Messages
687
Country
us-texas
I am getting ready to compile objects used in an FSX scenery to work in P3D. In setting the path for the P3D XtoMDL, I have yet to find one that MCX will accept.

C:\Program Files (x86)\Lockheed Martin\Prepar3D v2 SDK 2.5.12945.0\Modeling SDK\3DSM7\Plugins\XtoMDL.exe

This is the current path I tried but there are also other folders holding versions of XtoMDL.exe. . . .which one is MCX expecting to find considering none of them work?

MCX_Error.jpg
 
Hi,

Not sure where that xtomdl crash comes from. The error message doesn't really help.

If you just use xtomdl from the command prompt does it work then?

The different versions in the different gamepacks should all be the same.
 
arno said:
Hi,
Not sure where that xtomdl crash comes from. The error message doesn't really help.
If you just use xtomdl from the command prompt does it work then?
The different versions in the different gamepacks should all be the same.
Click to expand...
I have no idea, I've never used it outside the functions set in MCX.

I've tried importing the original FSX "Scenery Object bgl" that I compiled from the dae/sketchup model and then compiling it for P3d_V2. I've also started over with the Collada file, processed it as a totally new object and then tried to compile for P3D_V2 and the results are the same. Just frustrating that at this point what should be a simple process has become a major stumbling block and no one seems to know why. Probably something quite simple but that's not much help when I know nothing of how any of this works beyond plugging in paths in the options setup.
 
arno said:
Hi,

Not sure where that xtomdl crash comes from. The error message doesn't really help.

If you just use xtomdl from the command prompt does it work then?

The different versions in the different gamepacks should all be the same.
[/QUOTE

Hi Arno:

So, for Ed's current purposes of filling in the file / folder path in the MCX "Options" field, one need not use the XtoMDL which is part of the P3D SDK (...if the P3D MDL output version is 1.4) ?

I do know that P3D version 1.4 and FSX SP2 / Acceleration reportedly have identical MDLs, but although I do not yet use P3D, ISTR reading that there were substantial differences in the MDL format for P3D version 2.x.

IIUC, Ed is exporting MDLs of his Sketchup 3D scenery objects for both FSX and P3Dv2.x


Is this correct, Ed ? :scratchch

GaryGB
Click to expand...
 
Last edited:
Hello...

Could this be a permission error by Windows?

What OS are you running? and was the first attempt?
 
GaryGB said:
So for Ed's current purposes of filling in the file / folder path in the MCX "Options" field, one need not use the XtoMDL which is part of the P3D SDK (...if the P3D MDL output version is 1.4) ?
I do know that P3D version 1.4 and FSX SP2 / Acceleration reportedly have identical MDLs, but although I do not yet use P3D, ISTR reading that there were substantial differences in the MDL format for P3D version 2.x.
IIUC, Ed is exporting MDLs of his Sketchup 3D scenery objects for both FSX and P3Dv2.x

Is this correct, Ed ? :scratchch
GaryGB
Click to expand...
That's correct Gary. The compile process for FSX works fine, but switch to compiling for P3D and I get the error message shown in the screenshot above. P3D_V1.4 was really just an extension of FSX with some minor improvements ie; they had not yet implemented cloud shadowing, self-shadowing to the extent it is now (HDR Lighting) and moving all texture processing to the Graphics Card which was a major step forward and basically eliminated the blurries.
 
Hi Arno:

Does Ed need to run MCX with "Administrative permissions" to access / read the P3Dv2.x SDK folders ? :scratchch

GaryGB
 
GaryGB said:
Hi Arno:
Does Ed need to run MCX with "Administrative permissions" to access / read the P3Dv2.x SDK folders ? :scratchch
GaryGB
Click to expand...
"Doug/GaryGB", exactly right. Good grief. . . .really? Time for a cup of coffee to ponder that ridiculous outcome, lol
 
Hi Ed:

That necessity really has more to do with the P.I.T.A. (notice how "I.T." is in the middle of that abbreviation ? :stirthepo) file / folder security hurdles imposed above and beyond the pervasive User Access Control (aka "UAC") we've had forced onto us since Windows Vista.


The C:\Program Files (x86)\Lockheed Martin\Prepar3D v2 SDK 2.5.12945.0\Modeling SDK\3DSM7\Plugins\XtoMDL.exe path is likely to be regarded by any version of Windows since Vista as a "system" folder subject to additional 'protection' (IMHO, in the real world, more-so blocking access by the end user ...than by any minimally-sophisticated malware).


So, IIUC, because of the equally pervasive menace of malware (and inadequate functionality of "anti-malware" software), even if we 'login' to Windows each time we start it, we may still have to jump through hoops to get at our own "authorized" program installations in the C:\Program Files (x86)\ and/or C:\Program Files\ folder chains. :banghead:


And sometimes if we create a "shortcut" to any executable program file, and edit its [Security] or [Compatibility] tab under 'Properties' to "run with administrative permission" for our logged-in account / profile user name, we may still have to manually grant permission each time, for such a program to actually run ...at yet another pop-up prompt ! o_O


Perhaps another P3D user might tell us whether there is an option in the otherwise reportedly 'over-the-top' P3D installers from Lockheed-Martin, which may be different for the P3Dv2.x SDK (as compared to the main P3D 'sim' package) ...by allowing one to choose a target folder path somewhere other than the default 'system' folder chain at ex: :scratchch

C:\Program Files (x86)\Lockheed Martin\Prepar3D v2 SDK 2.5.12945.0\Modeling SDK\3DSM7\Plugins\XtoMDL.exe


And perhaps Arno can tell us whether and/or how he implements security access to that folder chain ...when users follow the default LM P3D 2.x SDK installation protocol. ;)

GaryGB
 
Last edited:
The easiest method is to take ownership of those folders.

I have full access all "protected" folders in W7 across the network on XP.
 
GaryGB said:
Perhaps another P3D user might tell us whether there is an option in the otherwise reportedly 'over-the-top' P3D installers from Lockheed-Martin, which may be different for the P3Dv2.x SDK (as compared to the main P3D 'sim' package) ...by allowing one to choose a target folder path somewhere other than the default 'system' folder chain at ex: :scratchch

C:\Program Files (x86)\Lockheed Martin\Prepar3D v2 SDK 2.5.12945.0\Modeling SDK\3DSM7\Plugins\XtoMDL.exe
GaryGB
Click to expand...
I have my P3D v2 SDK installed in "C:\P3D2\SDK", nice and short (and it works nicely with MCX!). :)

The SDK installer allows you to pick any path you like. Same with the "Main" P3D v2 installer. My P3D v2 is installed in "F:\P3D2".

Hope that answers your question.

- JP
 
Last edited:
JP "Penz" Pedersen said:
I have my P3D v2 SDK installed in "C:\P3D2\SDK", nice and short (and it works nicely with MCX!). :)

The SDK installer allows you to pick any path you like. Same with the "Main" P3D v2 installer. My P3D v2 is installed in "F:\P3D2".

Hope that answers your question.

- JP
Click to expand...

Many thanks for posting that info ! :)


Golf-HotelDelta said:
The easiest method is to take ownership of those folders.

I have full access all "protected" folders in W7 across the network on XP.
Click to expand...

Thanks, George ! :)



BTW: I have found and tried 3 different versions of a "Take Ownership" script or executable GUI routine on various "apparently trustworthy" websites and forums, but results still seem variable in successfully implementing unrestricted access through both Windows Explorer and a legacy Symantec file manager I prefer to continue using in Win-7.

Do you know of a particular "Take Ownership" script or executable routine which might merit use by fellow FS developers here who are trying to get some work done with minimal distractions and "gotchas", and do you have any links for same which you could post here as well ? :scratchch


Thanks in advance for any insight you might offer on this latter inquiry ! :wave:

GaryGB
 
GaryGB said:
Does Ed need to run MCX with "Administrative permissions" to access / read the P3Dv2.x SDK folders ? :scratchch
Click to expand...

No, that shouldn't be needed. As long as the output is put in a folder where the user has permission to write, calling xtomdl shouldn't be the problem.
 
arno said:
No, that shouldn't be needed. As long as the output is put in a folder where the user has permission to write, calling xtomdl shouldn't be the problem.
Click to expand...
Arno, did you see my post several levels up? It wasn't until I set MCX to run as an administrator that I was able to compile the models for P3D. Oddly the output was going to a folder that I had been using all along for the FSX compiles. Why it stalled with P3D is a mystery.
 
But can you call xtomdl from the command prompt without admin rights?

On my machine I never have to run MCX as admin.
 
arno said:
But can you call xtomdl from the command prompt without admin rights?
On my machine I never have to run MCX as admin.
Click to expand...
To be honest, If I knew how I might give it a try. I'm a slave to the "plug-in" mentality. If the program can't do it I'm lost, using the tools outside of the main program is something I have never done. Sorry. For me, as long as it compiles (and I don't mean this to be taken as rude or condescending Arno) I don't really care what the sub-programs do or how they do it as a separate entity. I do basic scenery with just enough flair that it looks better than the average but not near as good as the more accomplished and serious scenery developers and that's all I care to be really.
 
arno said:
But can you call xtomdl from the command prompt without admin rights?

On my machine I never have to run MCX as admin.
Click to expand...
Windows 10 prevents modification of the Program Flies directory without admin authority. MCX nor xtomdl will be able to compile into that directory without it.
 
=rk= said:
Windows 10 prevents modification of the Program Flies directory without admin authority. MCX nor xtomdl will be able to compile into that directory without it.
Click to expand...
But MCX is never compiling in that folder, it will only execute the compiler. As far as I know that should be possible without admin rights.
 
Hi Ed:

Have you considered simply re-installing the P3Dv2.x SDK into a user-created folder path outside the Windows "system-type" folder chains ? ;)

ex: :idea:

C:\P3Dv2x_SDK\

GaryGB
 
I would still like to understand what is going on with the default location. Maybe I can change something in MCX. The tool is supposed to work without admin rights.
 
You must log in or register to reply here.
Back
Top