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

Convert 'SCASM' scenery item to FS2004 mdl?

tgibson said:
I have occasionally encountered such objects- what I do is go to the MCX Hierarchy Editor, find then in the list, and click Remove. Hopefully they have not been combined with other objects by MCX - if so, there is a setting called something like CollapseAll or CollapseParts that can help with that. Make it false. Only works when Importing a new object though.
Click to expand...
Thanks ... I'm going to have to settle down and work through the supplied PDF to figure out what options are available, what they're called, (Hierarchy Editor means nothing to me), what they do and how to use them to my advantage.
I really was hoping initially for a "import-click export-click" solution with maybe a tick-box or two to get it to all work ... it's proved to be rather more complex!
 
The Hierarchy Editor is a button at the top (or now side?) of the screen. Click it, click the Highlighted button, go through the list on the left until the undesired object turns red (and hopefully nothing else), then click Remove.
 
tgibson said:
The Hierarchy Editor is a button at the top (or now side?) of the screen. Click it, click the Highlighted button, go through the list on the left until the undesired object turns red (and hopefully nothing else), then click Remove.
Click to expand...
Thanks ... unfortunately, in this instance, most of the undercarraige disappears as well, but I'll bear it in mind for future reference :)
 
Hi,

Here is a quick summary of two ways to handle this kind of conversion in the future.

Option 1: import with UserSpecified variables
  1. When importing the SCA object in the import file dialog make sure that "use conditions" is set to UserSpecified.
    1763144990593.png
  2. On the dialog that follows enter the correct value for the variables that influence the conditions. For many older objects the default valye of 5for image_complexity does not work, change it to 4 to get the object in that image complexity state.
    1763145037073.png
  3. Now you have an object without visibility conditions in MCX and you can export it to a FS2004 MDL or BGL file without issues.
Option 2: Remove visibility conditions
This second approach will be available from the next development release, as I just implemented some changes for it. With this approach you can leave "use conditions" at the default value of "VisibilityConditions".
  1. Import the SCA file with the default settings.
  2. When exporting the scenery make that on the export file dialog the option "remove all visibility conditions" has been selected. This will ensure that all visibility conditions are removed before the object is saved.
    1763145383419.png

  3. Now you have an object without visibility conditions in MCX and you can export it to a FS2004 MDL or BGL file without issues.
 
Thanks :) ... I'm getting the impression you're using a later/newer version of MCX than I am, my screen looks completely different ... I'll have to look into that as well!
 
I'm using the development release, which is version 1.8. The options in the export dialog are indeed a recent change.

If you are using version 1.7 you can still do approach 1, but you need to change the options I mentioned in the settings dialog instead.
 
arno said:
I'm using the development release, which is version 1.8. The options in the export dialog are indeed a recent change.

If you are using version 1.7 you can still do approach 1, but you need to change the options I mentioned in the settings dialog instead.
Click to expand...
Thanks ... found it :)
I did a search for UserSpecified in the PDF and worked backwards from there.
As is so often the case, it's not that the answers aren't there, it's knowing what the question should be in the first place ;)
Keep up the good work!
 
You must log in or register to reply here.
Back
Top