- Messages
- 64
- Country

Hi all,
We have run into the usual system.outofmemory nonsense that always seems to blight our high-poly models. However, we weren't expecting to see this again as we are using all the latest tools, i.e. Max 2014 64bit with the P3Dv2 plugins and the P3Dv1.4 XtoMDL exporter. But here we are again, exports result in either vertex buffer errors or system.outofmemory errors.
It would appear from reading other posts on the subject here that the /WRITETOFILE is the magic bullet to make all these problems go away. However, adding it to the compiler command line causes it to spit out a 0kb MDL in a under a second, so it's obviously falling over before it begins to compile anything.
Anyone know why adding the /WRITETOFILE line causes it to fall over?
This is the full command line, run via a bat file:
"D:\Prepar3D SDK 1.4.4747.0\Environment Kit\Modeling SDK\3DSM2012\Plugins\xtomdl.exe" /XANIM /WRITETOFILE "D:\Tornado GR1\TornadoGR1.X" /dict:"D:\Microsoft Flight Simulator X SDK\SDK\Environment Kit\Modeling SDK\bin\modeldef.xml" > D:\Compile\buildlog.txt
It works fine without the /WRITETOFILE instruction.
This is the buildlog output:
Found dictionary file: D:\Microsoft Flight Simulator X SDK\SDK\Environment Kit\Modeling SDK\bin\modeldef.xml
OutputFile: D:\Tornado GR1\TornadoGR1.MDL
Output file after modification: D:\Tornado GR1\TornadoGR1.MDL
Usage: XToMDL.exe /KEEP /NOGUI /BATCH /NOCRASH /BMP2DDS /XMLSAMPLE /XANIM /BULLET /DICT
ictFileName /OUT:OutfileName Filename.X
Any input gratefully received...
We have run into the usual system.outofmemory nonsense that always seems to blight our high-poly models. However, we weren't expecting to see this again as we are using all the latest tools, i.e. Max 2014 64bit with the P3Dv2 plugins and the P3Dv1.4 XtoMDL exporter. But here we are again, exports result in either vertex buffer errors or system.outofmemory errors.
It would appear from reading other posts on the subject here that the /WRITETOFILE is the magic bullet to make all these problems go away. However, adding it to the compiler command line causes it to spit out a 0kb MDL in a under a second, so it's obviously falling over before it begins to compile anything.
Anyone know why adding the /WRITETOFILE line causes it to fall over?
This is the full command line, run via a bat file:
"D:\Prepar3D SDK 1.4.4747.0\Environment Kit\Modeling SDK\3DSM2012\Plugins\xtomdl.exe" /XANIM /WRITETOFILE "D:\Tornado GR1\TornadoGR1.X" /dict:"D:\Microsoft Flight Simulator X SDK\SDK\Environment Kit\Modeling SDK\bin\modeldef.xml" > D:\Compile\buildlog.txt
It works fine without the /WRITETOFILE instruction.
This is the buildlog output:
Found dictionary file: D:\Microsoft Flight Simulator X SDK\SDK\Environment Kit\Modeling SDK\bin\modeldef.xml
OutputFile: D:\Tornado GR1\TornadoGR1.MDL
Output file after modification: D:\Tornado GR1\TornadoGR1.MDL
Usage: XToMDL.exe /KEEP /NOGUI /BATCH /NOCRASH /BMP2DDS /XMLSAMPLE /XANIM /BULLET /DICT
Any input gratefully received...
