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

Crash Boxes Off

GaryGB said:
Hi again:

How many scenery library object placements do you need to use the NoCrash attribute with that involve unique and distinct MDLs ?

GaryGB
Click to expand...

Quite a few placements of about a dozen models. From what Arno has stated it doesn't sound like there is a simple solution to the problem since the BGLComp NoCrash option is FSX only.

Again, I appreciate all the assistance and responses to my questions.

Greg
 
arno said:
http://www.fsdeveloper.com/forum/threads/crash-boxes-off.435008/#post-778724

Hi,

You are right, MCX doesn't support the NoCrash part attribute at the moment. It would not be an attachpoint in MCX, but would have to be an attribute of the ModelPart itself. Might be interesting to check if this can be supported as well. I'll have a look.

For the moment all you can do in MCX is toggle the crash box for the entire object with the settings.
Click to expand...

Thanks for the clarification and for looking into how "NoCrash" might be additionally implemented in MCX for FS9 MDLs via a "ModelPart attribute" as well as possibly BGLComp_XML-based scenery library object / placement output code. :)

GaryGB
 
gaputz said:
http://www.fsdeveloper.com/forum/threads/crash-boxes-off.435008/page-2#post-778754

Quite a few placements of about a dozen models. From what Arno has stated it doesn't sound like there is a simple solution to the problem since the BGLComp NoCrash option is FSX only.

Again, I appreciate all the assistance and responses to my questions.

Greg
Click to expand...

Hopefully Arno may have an opportunity to implement something more convenient to use for toggling "NoCrash" in FS9 MDLs within the near future.

But, in the mean time, assuming this is for a "personal use only" project and/or if this for a public release involving MDLs which are either your own, or are MDLs for which you have author permission to duplicate using a new GUID in a separate BGL, you could, for this specific project: :teacher:

1.) Import a COPY of the BGL containing the currently "Crash-Enabled" MDLs into MCX

2.) Enable NoCrash for each exported FS9 MDL via:

MCX Menu > Options > Exporter settings > MDLWriter > NoCrash = True


3.) Change the GUID for all MDLs in the BGL containing the currently "Crash-Enabled" MDLs:

MCX Menu > Wizards > Batch Convert... > Batch Process dialog


a.) Input: [Add...] button > Browse / Select (FS9 BGL containing currently "Crash-Enabled" MDLs)

b.) Operator: [Add...] button > Select "Assign New GUID"

c.) Output: Check "Export Files" check-box

d.) Folder: Select output folder path < must be different than the original source BGL >

e.) Writer: FS2004 BGL file (BGL) < this should retain existing placement information >


4.) Manually re-name exported "NoCrash" FS9 scenery BGL to a distinct file name different than the original source BGL.


The new FS9 scenery BGL 'should' retain all texture mappings etc. as well as any placement information. :pushpin:

Because their GUIDs are different, the MDLs output into the new "geo-locked" scenery object library / placement should not conflict with the original MDLs elsewhere in FS9, although their intended "NoCrash" placement may overlap those of the original "Crash-Enabled" MDLs as scenery library objects, so the placement BGL for the original "Crash-Enabled" MDLs should be de-activated in FS9.

The alternate "NoCrash" MDLs output into the new "geo-locked" scenery object library / placement BGL will not be use-able at any other geographic location in FS9 (without special procedures ;)), but should be able to replace your existing original "Crash-Enabled" MDLs with a semi-automatic 'minimal' effort via MCX. :wizard:


Hope this helps ! :)

GaryGB
 
Last edited:
Hi,

I had a bit of time this evening, so I started to implement the per part no crash. I seem to have it working for FSX/P3D now. But I still need to test it for FS2004 (on the machine I develop at the moment I have no FS2004 SDK installed to test). So hopefully tomorrow after a bit more testing I can finish this.
 
GaryGB said:
Hopefully Arno may have an opportunity to implement something more convenient to use for toggling "NoCrash" in FS9 MDLs within the near future.

But, in the mean time, assuming this is for a "personal use only" project and/or if this for a public release involving MDLs which are either your own, or are MDLs for which you have author permission to duplicate using a new GUID in a separate BGL, you could, for this specific project: :teacher:
{snip}
The alternate "NoCrash" MDLs output into the new "geo-locked" scenery object library / placement BGL will not be use-able at any other geographic location in FS9 (without special procedures ;)), but should be able to replace your existing original "Crash-Enabled" MDLs with a semi-automatic 'minimal' effort via MCX. :wizard:


Hope this helps ! :)

GaryGB
Click to expand...

This worked beautifully Gary. You are a genius!

Greg
 
Glad you have an initial result to test. :)

That work-flow would not have been possible had it not been for Arno's years of learning and hard work ! :wizard:


Perhaps you could also do a test run using Arno's new MCX FS9 "NoCrash" toggle feature upon release ? ;)

GaryGB
 
Last edited:
I was remiss in not mentioning Arno. There should be a flight simulation hall of fame and Arno should be inducted immediately!

Greg
 
Hi,

I just finished the feature, so it will be in the next development release. In the Hierarchy Editor you will see a NoCrash option for ModelPart nodes. If you set that to True that part will be excluded from the crash box generation. I'll try to make a video tutorial about it soon as well.
 
And here is the video tutorial, the feature will be in the development release that I will build right now :)

 
Arno, thanks for both of your recent enhancements to MCX, both will be very useful.

Regarding reimporting the Nocrash setting, could a spare texture entry in that particular parts material properties be set to "NoCrash$" or similar, as a flag? I realise this may mean duplicate materials, but MCX could then reapply the Nocrash setting automatically.
 
Essex said:
Arno, thanks for both of your recent enhancements to MCX, both will be very useful.

Regarding reimporting the Nocrash setting, could a spare texture entry in that particular parts material properties be set to "NoCrash$" or similar, as a flag? I realise this may mean duplicate materials, but MCX could then reapply the Nocrash setting automatically.
Click to expand...

I'm not sure which material setting I could use for that, since all texture slots could already be used by a model. But it's an interesting idea to somehow flag the parts that have no crash. Another option would be to analyze the crash tree on import and check which model is inside it or outside.
 
Yes, different texture slots would have to be used for different parts, still not 100%.

arno said:
Another option would be to analyze the crash tree on import and check which model is inside it or outside.
Click to expand...

I think with animated parts the crash boxes end up in strange positions, so very difficult. Is an option of NoCrash on all animations worth considering?

How about attaching a non-existent effect to the nocrash parts, as a flag?
 
Adding dummy attachpoints would work, I use that for the earth curve correction as well. But in this case that could become quite a lot of attachpoints. Not sure if that impacts performance. It would be the easiest implementation though.

Animations and crashboxes are tricky anyway, because the crash boxes are static. A quick way to add NoCrash to all animated parts (or in general to multiple parts) might be useful.
 
You must log in or register to reply here.
Back
Top