Object generation utility

lenidcamper · March 11, 2019 at 2:15 PM

Quote from TomSimMuc

My idea for the far future

A good vision.

Early in my cultivation efforts I went to a tiled approach. I decided on 0.1x0.1 tiles. I created a utility that once I entered the center coordinates of a tile it spat out a set of bat files and power shell scripts to download the OSM file, download image file for tree autodetect, generate elevation contours, run scenProc, run osm2AFSobject, and deploy the results.

I decided on the 0.1 degree tile size because it was more user friendly than the AFS hex tile convention for names and coordinates.

When AeroScenery came out I contemplated switching to the AFS hex tile convention but have not gone there (yet). You really need a map driven interface to give usability and visibility of the cultivation state for hex tiles.

Any cultivation integration framework needs to be highly adaptable. For example as I am flying if I see an annoying cultivation glitch, I use my Flight Path Recorder and Google Earth to determine exactly where in which cultivation tile the discrepancy lies. I can then update the OSM or configuration file as required and add that tile to the Cultivate_These_Tiles batch file to run later. In my experience cultivation is an iterative process that is never really done.

Everybody has their own criteria on what "good enough" means. Or their own idea of what aspects of cultivation are important. For me trees are important. I use auto detect for trees to give a realistic sparse distribution at elevation and elevation contours to vary the tree species with elevation.

But autogen buildings leave me cold. Orbx True Earth is a step in the right direction, but I an not ready yet to give up the rich variation of the ortho image roof textures for the handful of stock textures. Even in commercial DLC's I have replaced most of the ortho images with higher resolution.

osm2AFSobject was developed because significant objects in the landscape are important to me, but again we need to work on the textures.

So in summary, I agree that more automation of scenery development is a good thing , but the core technologies are not yet at the state that there is a one size fits all solution.

A black box approach can only provide average results.

/Stu

TomSimMuc · March 11, 2019 at 3:16 PM

Yes, Stu you are right, one can put a lot of effort into a perfect cultivation.

But then I think to myself: I am not ORBX which needs to earn money with it.

However I am willing to put more efforts to locations that I know and love, then into others.

Do you think such a small size of 0.1 deg (about 5km in Germany) is really needed?

I found that a tile 10 (about 23 km) is still small enough to be loaded on the fly.

lenidcamper · March 11, 2019 at 4:05 PM

The choice of 0.1 was more a question of convenience than anything else. A tile of 1.0 degree was too big and anything in between was awkward for specifying coordinates by hand. Other people seem to have selected the same size for much the same reasons.

If there is support for cultivation from a map driven interface in the style of AeroScenery , then the awkward coordinates are not an issue. It comes down to optimal loading size. There have been discussions on optimal cultivation tile size for scenery load in other threads and I think the consensus is that for dense cultivation (particularly trees) smaller is better (even down to level 13). If the interface and cultivation modules are well integrated it should be irrelevant how many tiles are generated.

On a related topic. Currently the [size] parameter is hard coded to 5000. I should probably expose that in the XML in case people do generate different tile sizes.

/Stu

lenidcamper · March 12, 2019 at 8:00 PM

Released version 0.3

Added concept of derived tags to extract additional OSM data in a form easily used for object model selection.

TomSimMuc · March 13, 2019 at 11:19 AM

Thank you Stu for this update.

What a nice variety of automated assigned possible model sizes!

Am am still working to understand all your new commands / parameters.

I will assign them to my own scripts and will report later about my tries.

If someone prefers the manual in German, I'll attach it here ( .html and .md format).

TomSimMuc · March 14, 2019 at 5:21 PM

Hello Stu,

I played now quite a bit with version 0.3.

Most of it is running very fine!

I think I found a small bug:

if the scenery is small and only contains ways, but no nodes, then I get this error message:

#------------------------------------------------------------------------------------------

# wayId=564837261 building:yes

#------------------------------------------------------------------------------------------

# wayId=595751587 building:yes

#------------------------------------------------------------------------------------------

No nodes detected within bounds. No tsc generated.

The same happens, if nodes are within the OSM, but the XML does not request one.

No tsc is generated then.

I also tried to play with the derivedLenth parameter.

I tried the test.OSM with a modified test.xml:

Code

     <!-- ============================================================================================ -->
  <!-- #0.3.1.2b one object with derived length tag
  
      Expected results:
        
         row of tanks descending in size from the north
  -->
  <wayConfiguration>
    <selectionCriteria>
      <andCriteria>
        <keyValueEntry key="man_made" value="storage_tank" />
        <keyValueEntry key="test:case" value="#0.3.1.2 oneObject with derived diameter tag"/>
      </andCriteria>
    </selectionCriteria>
    <defaultModel name=""/>
    <oneObject>
      <derivedTags>
        <length derivedTagName="derivedLength" roundTo="10"/>
        <diameter derivedTagName ="derivedDiameter" roundTo="10" />
      </derivedTags>
      <modelNameMapping>
        <mapEntry key="derivedLength" value="50" name="StorageTanks\10mflat\10mflat"/>
        <mapEntry key="derivedLength" value="70" name="StorageTanks\20mflat\20mflat"/>
        <mapEntry key="derivedLength" value="90" name="StorageTanks\30mDome\30mdome"/>
        <mapEntry key="derivedLength" value="110" name="StorageTanks\40mDome\40mdome"/>
        <mapEntry key="derivedLength" value="130" name="StorageTanks\50mDome\50mdome"/>
      </modelNameMapping>
    </oneObject>
  </wayConfiguration>

Display More

I looked up the way lenghts of the 4 tanks in JOSM.

They are 129, 98, 81, 56m.

However none of the conditions triggered.

Could you have a look please, what would be the correct parameters?

I do all this in preparition when the building direction is implemented.

I would like to see churches and houses to be replaced by real objects, not cultivation.

With the derivedDiameter parameter I had partial success, but not deterministic:. That means I could not find out, why some houses triggered and others not.

These are xref objects, converted into tmb by Phil for his FScloudPort project.

So all airport objects are available this way.

lenidcamper · March 14, 2019 at 6:19 PM

Quote from TomSimMuc

They are 129, 98, 81, 56m.

Those raw length values would round to 130 100 80 60 assuming my length calculation agrees with JOSM.

So the only valid map entry would be 130, but it should have detected that one at least.

As you might of noticed there were no test cases for derivedLength since I did not think of a scenario.

I'll have a look to if there is any issue

lenidcamper · March 15, 2019 at 7:38 PM

Released version 0.4

Major change is rebranding as ObjectGen (had to sack the entire marketing department )

- Added support for large OSM files. Allows bounding box override to be entered as argument to process subsections of OSM file.

Optimization for large node list processing.

- Added variability percentages for animation attributes to avoid "lock-step" effect on large groups of animated objects (ie wind farms)

See readme and UserGuide

ObjectGen

kenventions · March 16, 2019 at 3:28 AM

or maybe FOG 0.4 for FS2 Object Generator ...

TomB · March 16, 2019 at 9:00 AM

Sorry for the marketing people. Very expensive department.

I would say the tool does not generate objects, it rather places them.

Aerofly Object Placer

TomSimMuc · March 16, 2019 at 9:30 AM

For those interested:

I converted the user guide into a md and html format.

PS: for me the test.bat only works, if the content is modified to:

ObjectGen.exe test.osm test.XML

TomSimMuc · March 16, 2019 at 12:17 PM

Hi Stu,

again a big step forward with the time scale variation in wind parks.

Do I have to understand the Round parameter in the way, that i.e. waylength is devided by the round faktor?

Then you compare the result against the mapEntry value?

Also very nice, the 3D-Digits in the testfile.

Can you tell me how you generated the digit models?

by the way, these two are incidentially swapped:

superb view:

lenidcamper · March 16, 2019 at 1:56 PM

Quote from TomSimMuc

Do I have to understand the Round parameter in the way, that i.e. waylength is devided by the round faktor?
Then you compare the result against the mapEntry value?

For wayLength, Diameter (indirectly via wayLength) and roundedOSMtag the values are divided by the roundTo value, rounded to the nearest integer and multiplied by the roundTo value.

Quote from TomSimMuc

PS: for me the test.bat only works, if the content is modified to:

must be some Windows setting because it runs as shipped for me.

Quote from TomSimMuc

Can you tell me how you generated the digit models?

SketchUp has a 3DText menu/toolbar option. Enter text at origin, paint texture, scale, export as dae, run through modelconverterX to tgi, run through contentConverter to tmb, copy tmb to object library (they all use the same ttx), add entry to xml.

Once I got into batch production mode they took about 15-20 seconds each.

TomSimMuc · March 16, 2019 at 8:46 PM

Thanks Stu for the receipe!

Is there maybe a bug in the derivedWayLenght calculation?

When derivedWayLenght is the only selection, then the final multiplication with the RoundTo value does not seem to happen.

In combination with derivedDiameter however it does. From the tst.tsc:

Code

            #------------------------------------------------------------------------------------------
            # wayId=-365118 building:yes  man_made:storage_tank  test:case:#0.3.1.2 oneObject with derived diameter tag   #:derivedWayLength:57 #:derivedDiameter:20
            #------------------------------------------------------------------------------------------
            <[tmsimulator_scenery_object][element][0] #nodeid = virtual
                <[string8][type][object]>
                <[string8][geometry][..\..\objects\StorageTanks\20mflat\20Mflat]>
                <[vector3_float64][position][6.541427 46.445304 0]>
                <[float64][orientation][]>
                <[int32][autoheight_override][-1]>
            >
           
            #------------------------------------------------------------------------------------------
            # wayId=-922073 building:yes  man_made:storage_tank  test:case:#0.3.1.3 oneObject with derived wayLength tag   #:derivedWayLength:2
            #------------------------------------------------------------------------------------------
            <[tmsimulator_scenery_object][element][0] #nodeid = virtual
                <[string8][type][object]>
                <[string8][geometry][..\..\objects\StorageTanks\20mflat\20Mflat]>
                <[vector3_float64][position][6.54142 46.449164 0]>
                <[float64][orientation][]>
                <[int32][autoheight_override][-1]>
            >

Display More

kenventions · March 16, 2019 at 9:03 PM

Quote from TomSimMuc

PS: The only critical part in the example.xml file, which needs attention is this line:

<relativePathPrefix>"..\..\..\..\objects\"</relativePathPrefix> (correct, if your objects folder is 4 folders higher in your directory tree then the tsc file.)

<relativePathPrefix>"..\objects\"</relativePathPrefix> (if your objects folder is 1 folder higher in your directory tree.)

<relativePathPrefix>"objects\"</relativePathPrefix> (if your objects folder is in the same folder as the tsc file)

everything else can be left alone for the beginning.

Very helpful clarification Tom!

lenidcamper · March 16, 2019 at 9:47 PM

Quote from TomSimMuc

Is there maybe a bug in the derivedWayLenght calculation?

Eagle eyes.

You are correct I missed a multiply after the round.

In my haste to release I adjusted the test case rather than the code to get the expected result.

In test case 0.3.1.1 the wayLength was correct so I incorrectly concluded that I set incorrect test criteria in 0.3.1.2.

pushed a patch with the fix.

TomSimMuc · March 18, 2019 at 12:06 PM

Autogen Ships:

The script looks for the key="seamark:type" value="distance_mark" to position a ship.

I converted the ship models with a 50% ratio to run into the opposite direction.

Code

 <!-- ============================================================================================ -->
  <!-- Chanal scenario, ships adjusted to chanel direction
        Expected results:
      
        - extraneous untagged node is to ignored. 
        - orientation follows tagged node path not extraneous node.  
  -->
  <wayConfiguration>
    <selectionCriteria>
      <andCriteria>
        <keyValueEntry key="waterway" value="canal" />         
      </andCriteria>
    </selectionCriteria>
    <defaultModel name=""/>
    <referencedNodes>
        <selectionCriteria>
            <andCriteria>
                <keyValueEntry key="seamark:type" value="distance_mark" />
            </andCriteria>
        </selectionCriteria>
        <derivedTags>
            <randomInteger derivedTagName ="randomInteger" upperLimit="2" />
        </derivedTags>
        <modelNameMapping>
            <mapEntry key="randomInteger" value="1" name="Ships\ship_channel_open\ship_channel_open"/>
            <mapEntry key="randomInteger" value="2" name="Ships\ship_channel_empty\ship_channel_empty"/>
                        
        </modelNameMapping>
    </referencedNodes>
  </wayConfiguration>

Display More

Storage Tank Script:

Code

<!-- ============================================================================================ -->
  <!-- #0.3.1.2a one object with derived diameter tag
  
      Expected results:
        
         row of tanks descending in size from the north
  -->
  <wayConfiguration>
    <selectionCriteria>
      <andCriteria>
        <keyValueEntry key="man_made" value="storage_tank" />       
      </andCriteria>
    </selectionCriteria>
    <defaultModel name=""/>
    <oneObject>
      <derivedTags>
        <wayLength derivedTagName="derivedLength" roundTo="1"/>
        <diameter derivedTagName ="derivedDiameter" roundTo="5" />
      </derivedTags>
      <modelNameMapping>
        <mapEntry key="derivedDiameter" value="5" name="StorageTanks\10mflat\10mflat"/>
        <mapEntry key="derivedDiameter" value="10" name="StorageTanks\10mflat\10mflat"/>
        <mapEntry key="derivedDiameter" value="15" name="StorageTanks\15mflat\15mflat"/>
        <mapEntry key="derivedDiameter" value="20" name="StorageTanks\20mFlatRailing\20mflatrailing"/>
        <mapEntry key="derivedDiameter" value="25" name="StorageTanks\30mflat\30mflat"/>
        <mapEntry key="derivedDiameter" value="30" name="StorageTanks\30mDome\30mdome"/>
        <mapEntry key="derivedDiameter" value="35" name="StorageTanks\30m_steelDome\30m_steeldome"/>
        <mapEntry key="derivedDiameter" value="40" name="StorageTanks\40mDome\40mdome"/>
        <mapEntry key="derivedDiameter" value="45" name="StorageTanks\40mDome\40mdome"/>
        <mapEntry key="derivedDiameter" value="50" name="StorageTanks\50mDome\50mdome"/>
        <mapEntry key="derivedDiameter" value="55" name="StorageTanks\55mPOL\55mpol"/>
        <mapEntry key="derivedDiameter" value="60" name="StorageTanks\60mPOL\60mpol"/>
        <mapEntry key="derivedDiameter" value="65" name="StorageTanks\65mPOL\65mpol"/>
        <mapEntry key="derivedDiameter" value="70" name="StorageTanks\70mPOL\70mpol"/>
        <mapEntry key="derivedDiameter" value="75" name="StorageTanks\75mPOL\75mpol"/>
        <mapEntry key="derivedDiameter" value="80" name="StorageTanks\80mPOL\80mpol"/>
        <mapEntry key="derivedDiameter" value="85" name="StorageTanks\80mPOL\80mpol"/>
        
      </modelNameMapping>
    </oneObject>
  </wayConfiguration>

Display More

Chimneys:

Code

<!-- ============================================================================================ -->
  <!--  chimney from center point node.
        If no way is defined a single node at the center can be used-->
  <nodeConfiguration>
    <selectionCriteria>
      <andCriteria>
        <keyValueEntry key="man_made" value="chimney" />
      </andCriteria>
    </selectionCriteria>
    <defaultModel name="nl\gen_29p_chimney_05" />
  </nodeConfiguration>

Display More

lenidcamper · March 18, 2019 at 3:46 PM

Quote from TomSimMuc

Autogen Ships:

Tom

I am impressed with what you have been able to do with ObjectGen !!

You have pushed it a lot far than I ever expected (providing great beta testing along the way.)

I guess I will have to hire you as my marketing department.

/Stu

kenventions · March 19, 2019 at 5:48 AM

Stu, would your power pylon orientation algorithm also work for traffic signals?

It looks like traffic signals are just Nodes but those Nodes are included in a street Way. Can your parser locate a Way that contains a traffic_signals Node and then calculate the heading of the Way to be used as a derived tag for the traffic_signals Node?

Seems like it would need 2 levels of parsing, one to get all the traffic_signals Nodes, and a second to find those same nodes in street Ways.

kenventions · March 19, 2019 at 6:10 AM

Maybe an easier option would be to detect other nearby traffic_signals and use those additional nodes to determine orientation:

4 signals in a group = 90 degrees difference for each one

2 signals in a group = 180 degrees difference

1 signal = default North-South

Object generation utility

Similar Threads

Some developments

Learning how to fly the R22

How do you fly an airplane when using Oculus Rift Touch controllers?

Any news from Aero-Expo, IPACS, VRMotion, Aerofly FS2 and the R-22 today?