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

P3D v4 CTD upon loading compiled model

euroastar350

Resource contributor
Messages
863
Country
us-delaware
Hi guys,

Has anyone encountered this issue? I'm bringing in my Bell 206 in native P3DV4 format and the sim will automatically CTD when loading the model for flight. All animations, materials are the same as the FSX version, although I do get an error flagging me that I have 2 cubemaps applied for reflective materials, even though I'm only using the default cubemap from FSX for reflections. I'm trying to learn the ropes on P3DV4 development, although it's pretty much the same as FSX development. Any ideas on what's causing this?
 
Ok, so presumably you are able to see the model rotate in the vehicle selection preview, you are not trying to load it from a saved flight, correct? Also, have you tried, as an experiment, just replacing the .mdl file with a helicopter known to work in v4? If that then the .air file, the panel, etc?

lEbJsthl.jpg

Nemeth As350 for FS9 converted to work in P3Dv4
 
I can see the model in the preview window and it's not being loaded from a saved flight. I will experiment and see if swapping models make a difference
 
I specifically know of instances where a panel folder and (of course) a non-compliant model prevented loading, but those prevented preview. I also remember a report of a saved flight crashing for reasons not related to the model.
 
So after experimenting with swapping the model with a different one, I still get CTD upon loading. So it's not the model that's causing this issue. Gauges shouldn't be an issue as they are in FS2004 XML and properly formatted. The Trislander is not a native P3DV4 aircraft, yet it loads just fine with all FS2004 XML gauges. Any ideas on how to remedy this issue?
 
swap your air file with working one or change your Airframe code (trial error) with other code that working inside air file.
 
swap your air file with working one or change your Airframe code (trial error) with other code that working inside air file.


That has been done as well with continued crashes, the Trislander uses the same code as the FSX version and exports/compiles/loads just fine. I am using Max 2012 32-bit with P3DV4 SDK installed and used for exporting and the error for the custom cube map keeps popping up when exporting, not sure if this is what is causing the CTDs.
 
If it is not working, then you must systematically replace components until you isolate the cause.
Gauges shouldn't be an issue as they are in FS2004 XML and properly formatted.
Gauges should be an issue until you have actually confirmed they work in v4 because, as I've already shared, I know of a specific case where the model would not load until I swapped the panel folder with that from one that was known to work. On no other occasions has replacing a panel folder allowed a previous version model to work in a current version of the sim, but it does when converting a FS2004 model to work in P3Dv4 and logic implies those gauges had also been formatted with FS2004 XML.
the error for the custom cube map keeps popping up when exporting, not sure if this is what is causing the CTDs.
You can find out pretty quick by unselecting that cube map, compiling the model and testing. P3Dv4 loads so incredibly fast, both the selection screen and the rendered scene. For a while I was having trouble with collapsed animations, which would be revealed by the wheels protruding from the fairings. I could see it in the selection screen and could make adjustments without waiting for the scene to load. So now it is practical to have your compiler software open, push a build, visually inspect the selected model/reload the rendered scene, make incremental changes and repeat.
 
That has been done as well with continued crashes, the Trislander uses the same code as the FSX version and exports/compiles/loads just fine. I am using Max 2012 32-bit with P3DV4 SDK installed and used for exporting and the error for the custom cube map keeps popping up when exporting, not sure if this is what is causing the CTDs.

for model test
1. I do use FSX compiler xtomdl x64 version, Sean author I believe. even it x64 but it present long before P3D v4. use it on Osprey, so far no issue with model.
2. compile simple box and insert the box in default v4 aircraft ( you know how), see it work or not. if CTD that could be wrong with compiler.
3. compile you aircraft model and insert to default aircraft, work or not? if CTD then something wrong with your model and could be modeldef.xml.
4. check and recheck your model attached with fx file, better compile without it for test.

if model check passed, then you could find another culprit. always test individual part to find which part cause CTD.
 
The model will now load, there is something in the gauges being used that causes the CTDs. I have since removed all gauge references and loading each of them, one by one until I find the culprit.
 
Back
Top