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

FSX Autogen Missing

Bavarello

Bavarello

Messages
172
Country
italy
Hello Arno, many thanks for MCX. I'm learning how to exploit it a little at a time ... is the dream that materializes!

I imported a modell.DAE in FSX, and I've encountered this problem as you can see in the picture below in the file zip. The area covered by the bounding box eliminates the autogen. This happens when the bunding box is very wide in the horizontal plane. I ask you if you can change this in MCX, just enough to not have the cancellation dell'autogen?
 

Attachments

Hi,

The bounding box as calculated by modelconverterx should match the size of your objects. So to make it smaller you usually have to split your object.

Or for fsx you can use the placement option to have no autogen suppression in your XML code. I should add that option to modelconverterx when doing placement there :)
 
Oh and for this object it would also help to rotate the bridge so that it is aligned with an axis. And then rotate it again when placing it in the scenery. Then the bounding box is more optimal.
 
arno said:
Oh and for this object it would also help to rotate the bridge so that it is aligned with an axis. And then rotate it again when placing it in the scenery. Then the bounding box is more optimal.
Click to expand...

It can be a solution the rotation, but I have some doubts. The other option to export to xml and then transfer it in FSX, a bit more complicated. There is the problem then do no wrong orientation.

Now I take the data from kml file

<? xml version = '1 .0 'encoding =' UTF-8 '?>
<kml xmlns='http://earth.google.com/kml/2.1'>
<Folder>
<name> model </ name>
<description> <! [CDATA [<a href="http://sketchup.google.com/"> Created with Google 3D Warehouse 1.0 </ a>]]> </ description>
<DocumentSource> SketchUp </ DocumentSource>
<visibility> 1 </ visibility>
<LookAt>
<heading> 27.6697 </ heading>
<tilt> 83.1951 </ tilt>
<latitude> 57.67548502848321 </ latitude>
<longitude> 39.85300988412595 </ longitude>
<range> 657.0576449647173 </ range>
<altitude> 74.06983080375207 </ altitude>
</ LookAt>
<Folder>
<name> Tour </ name>
<Placemark>
<name> <! [CDATA [Camera]]> </ name>
<visibility> 1 </ visibility>
<LookAt>
<heading> 27.6697 </ heading>
<tilt> 83.1951 </ tilt>
<latitude> 57.67548502848321 </ latitude>
<longitude> 39.85300988412595 </ longitude>
<range> 657.0576449647173 </ range>
<altitude> 74.06983080375207 </ altitude>
</ LookAt>
</ Placemark>
</ Folder>
<Placemark>
<name> Model </ name>
<description> <! [CDATA []]> </ description>
<style id='default'>
</ Style>
<Model>
<altitudeMode> relativeToGround </ altitudeMode>
<Location>
<longitude> 39.856260864627 </ longitude>
<latitude> 57.674501692910 </ latitude>
<altitude> 0.000000000000 </ altitude>
</ Location>
<Orientation>
<heading> 0.723643005067 </ heading>
<tilt> 0 </ tilt>
<roll> 0 </ roll>
</ Orientation>
<scale>
<x> 1.0 </ x>
<y> 1.0 </ y>
<z> 1.0 </ z>
</ Scale>
<Link>
<href> models / model.dae </ href>
</ Link>
</ Model>
</ Placemark> </ Folder>
</ kml>

even though I did not understand in what format are inserted
<heading> 0.723643005067 </ heading> I use these

If I measure in Google Earth is 55.67 ° -

But the result is excellent. The object is positioned very accurately without errors.

Sorry for the delay in responding but I have to help with the translated language.
 
;)
Ciao Bavarelllo, ho avuto lo stesso problema con molti oggetti piazzandoli con SbuilderX soppressione autogen.
Se puoi posiziona l'oggetto con SbuilderX e poi aggiungi al file XML da ridare al
resample :
imageComplexity="NORMAL">
modifica aggiungendo
imageComplexity="NORMAL"> <NoAutogenSuppression/>
a me ha funzionato ora si vede tutto l'autogen.
Come ti ha suggerito Arno al secondo post...

Antonio.

Bavarelllo Hello, I had the same problem with many objects placing them with SbuilderX autogen suppression.
If you can place the object SbuilderX and then add the XML file to be given to
resample:
imageComplexity = "NORMAL">
modified by adding
imageComplexity = "NORMAL"> <NoAutogenSuppression/>
I worked now you see all the autogen.
As you suggested Arno second post ...
 
Last edited:
Hi,

I have just updated ModelConverterX. So from tomorrow the development release will have more options in the object placement form. You can now also set the NoAutogenSuppression flag.
 

Attachments

  • Image2013-02-11 2029.31.825.jpg
    Image2013-02-11 2029.31.825.jpg
    104.9 KB · Views: 540
Anto80 said:
;)
If you can place the object SbuilderX and then add the XML file to be given to
resample:
imageComplexity = "NORMAL">
modified by adding
imageComplexity = "NORMAL"> <NoAutogenSuppression/>
I worked now you see all the autogen.
As you suggested Arno second post ...
Click to expand...

Hello Anto,
I tried as you suggested, but they are not able to get the new bgl!

INTERNAL COMPILER ERROR: #C2033: XML Parse Error (line, column, error) ERROR: 4, 192, enumeration constraint failed.
The attribute: 'imageComplexity' has an invalid value according to its data type.
INTERNAL COMPILER ERROR: #C2038: Failed to process image complexity!
INTERNAL COMPILER ERROR: #C2031: Failed element parse <SceneryObject> INTERNAL COMPILER ERROR: #C2032: XML Parse Error! Element tree follows:

ERROR: <FSData
ERROR: version = 9.0
ERROR: >
ERROR: <SceneryObject
ERROR: lat = 57.674501692910
ERROR: lon = 39.856260864627
ERROR: alt = 0.0M
ERROR: altitudeIsAgl = TRUE
ERROR: pitch = 0
ERROR: bank = 0
ERROR: heading = 0.723643005067
ERROR: imageComplexity = NORMAL <NoAutogenSuppression/>
ERROR: >

etc.
 
OK has already solved Arno ...

This may be the syntax if the offending line is that the error

imageComplexity = NORMAL <NoAutogenSuppression/>
so if it was written in the XML file is wrong
must be written exactly as below with quotes "" and> <
"NORMAL"> <NoAutogenSuppression/>
it works for me without problems, but I put the XML file in the folder where else is the resample
C: \ Program Files (x86) \ Microsoft Games \ Microsoft Flight Simulator X SDK \ SDK \ Environment Kit \ BGL Compiler SDK and put it on the resample .....

Among other things, this suggestion I had found on this forum .....

Hello.
Antonio.
 
Hi Arno,
I tried the new feature of MCX. There is a second unpleasant "side of the coin." :confused:
With Object Placement \ set various parameters in No AutogenSuppresion \ True, and then Export Scenery with the results is that the autogen "enter" into the exported object. And another problem is the choir transfer of texture on the object exported. :banghead:

Doing the operation with the Wizards \ Convert object and place the textures are properly exported.

This picture gives an idea of the result.
 

Attachments

  • Mig_016.jpg
    Mig_016.jpg
    697.6 KB · Views: 504
Well, you can suppress Autogen or you can't. There is no middle setting. :)

You probably should now just exclude the autogen from the area of the bridge. The cleanest way to do that is to place a VTP terrain polygon the shape of the bridge under it. If you use a landclass texture that does not include autogen, then your bridge will be "clean". You can place terrain polygons with ADE (if part of an airport), or SBuilderX.

Hope this helps,
 
Hi,

I think for this bridge it would be easier to jump model is along the x or y axis. In that case the bounding box will fit well around the object and hardly any autogen is excluded.
 
tgibson said:
If you use a landclass texture that does not include autogen, then your bridge will be "clean". You can place terrain polygons with ADE (if part of an airport), or SBuilderX.

Hope this helps,
Click to expand...

Hi tgibson, this can be a good solution. I'll try to do this as soon as possible.

Hi Arno, first rotate as I got this in the picture, then by trial and error I found the correct heading.

There is still the problem of texture. As I reported earlier with wizards \ convert the problem does not exist.

Gio
 

Attachments

  • Mig_017.jpg
    Mig_017.jpg
    130.3 KB · Views: 416
  • Mig_018.jpg
    Mig_018.jpg
    372.4 KB · Views: 416
  • Mig_019.jpg
    Mig_019.jpg
    521.9 KB · Views: 471
Hi,

The convert and place object wizard does automatically convert textures for the format needed by fsx. But if you don't use the wizard you have to do it yourself. You can do so from the material editor.
 
You must log in or register to reply here.
Back
Top