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

MSFS20 Possible to remove a certain area from a 3rd party photogrammetry area?

I got the same result before I began refreshing my memory on a need to manually calculate RefPts for ModelPart sub-tiles. :oops:



Quite generous of you to do so; looks like another one of your outstanding scenery packages in process here. :)
As long as the workflow is easy to do when it's known how to do it, I am happy to accommodate several ways to use the sim. Photogrammetry is not for everyone... . :) What I am very happy with with this project is my new workflow by using sketchup as the primary modelling software and then doing the texture work within substance painter. What a wonderful tool to make the models more alive... This has also forced me to enter into the surface of Blender, so I understand the very basics of adjusting materials and UV's - finally.... . The workflow works very well and the models have been tested within the sim, so I know it works. A magnificent relief....!
Yes; but we must manually calculate RefPts for ModelPart sub-tiles.

Green Push-Pins in MCX' Object Placement dialog are RefPts of an entire array.


Note that the ModelPart sub-tile grid array differs between the (2) Alesund addons: 8x8 (as seen previously), versus 4x4.

This morning I am refreshing my memory on how I manually calculate RefPts for ModelPart sub-tiles; stay tuned for updates. :coffee:


Probably I will need some more coffee before I "Do The Math". :scratchch

GaryGB

Looking forward to your math results :D
 
You may note as well that one of the above cited Alesund addons has placements for 3D model objects in addition to scene object tile arrays.


I finally found my work file(s) from ENSX Stavanger, and saw how I derived the Geographic coordinates.


This may take some time to replicate for Alesund, as I test the coordinates derived from consolidation of data via (2) sources.

While I normally would not mind just deriving the required info and simply conveying it to you, you're likely to need this workflow in the future.


Until we have a better / easier updated method, to derive the Geographic coordinates in alphanumeric text, we can get them via (2) utilities.

Otherwise, you will have to transcribe 32-character long strings for object GUIDs from MCX without making mistakes because they are not text.


* MCX (Current 1.8 version preferred) - to load local ENAX objects.bgls from the Alesund addons, and verify info via Object Information dialog


* BGL2XML Gui version 1.10 - to load local ENAX objects.bgls from the Alesund addons, and decompile / output placement XML


Download BGL2XML Gui version 1.10 here:

https://www.fsdeveloper.com/forum/threads/bgl2xml-gui-v-1-10.448225/


We'll need to confirm that BGL2XML Gui version 1.10 has the DLL updated from Patrick Germain to enable de-compilation of MSFS 2020 BGLs.


You'll also need the (2) Alesund addons un-zipped into folder chains using ex: 7-Zip


You can do your derivations with Windows Copy+Paste, NotePad as intermediate data repository, and Windows Calculator in Scientific mode.


Later you can make a basic spreadsheet (MS-Office Excel, Corel Quattro Pro, Open / Libre Office freebies etc.) to do calculation grunt work. ;)


If you would like to learn how to get the data you need for the ModelPart sub-tile RefPts, we could do that interactively to allow questions.


You are 6 Hours ahead of me into your day, so I'll post some initial info in the next few minutes before I must attend to some commitments.

Then I can resume posting again around 8:30 - 9:00 PM in your time zone ...if you wish to connect that late.


If not, I shall endeavor to post more later on this evening, and tomorrow morning ...as time / endurance permits, so you can learn this workflow.


Let me know how you wish to proceed. :)

GaryGB
 
Last edited:
You may note as well that one of the above cited Alesund addons has placements for 3D model objects in addition to scene object tile arrays.


I finally found my work file(s) from ENSX Stavanger, and saw how I derived the Geographic coordinates.


This may take some time to replicate for Alesund, as I test the coordinates derived from consolidation of data via (2) sources.

While I normally would not mind just deriving the required info and simply conveying it to you, you're likely to need this workflow in the future.


Until we have a better / easier updated method, to derive the Geographic coordinates in alphanumeric text, we can get them via (2) utilities.

Otherwise, you will have to transcribe 32-character long strings for object GUIDs from MCX without making mistakes because they are not text.


* MCX (Current 1.8 version preferred) - to load local ENAX objects.bgls from the Alesund addons, and verify info via Object Information dialog


* BGL2XML Gui version 1.10 - to load local ENAX objects.bgls from the Alesund addons, and decompile / output placement XML


Download BGL2XML Gui version 1.10 here:

https://www.fsdeveloper.com/forum/threads/bgl2xml-gui-v-1-10.448225/


We'll need to confirm that BGL2XML Gui version 1.10 has the DLL updated from Patrick Germain to enable de-compilation of MSFS 2020 BGLs.


You'll also need the (2) Alesund addons un-zipped into folder chains using ex: 7-Zip


You can do your derivations with Windows Copy+Paste, NotePad as intermediate data repository, and Windows Calculator in Scientific mode.


Later you can make a basic spreadsheet (MS-Office Excel, Corel Quattro Pro, Open / Libre Office freebies etc.) to do calculation grunt work. ;)


If you would like to learn how to get the data you need for the ModelPart sub-tile RefPts, we could do that interactively to allow questions.


You are 6 Hours ahead of me into your day, so I'll post some initial info in the next few minutes before I must attend to some commitments.

Then I can resume posting again around 8:30 - 9:00 PM in your time zone ...if you wish to connect that late.


If not, I shall endeavor to post more later on this evening, and tomorrow morning ...as time / endurance permits, so you can learn this workflow.


Let me know how you wish to proceed. :)

GaryGB
Thank you so much for helping me out with this, Gary. Do not stress with testing this out quickly. I am not able to follow up that quick anyway 😊.
Probably will not be able to continue before the weekend
 
HI again, Vetle:

I am awaiting a reply by Arno in another thread before I summarize a basic work-flow to derive the info needed to exclude ModelPart sub-tiles.

https://www.fsdeveloper.com/forum/threads/mcx-placement-to-shape-converter-missing.460581/


If it is not feasible for Arno to resolve an issue I reported in MCX, and he also requires time to consider my proposed idea, I'll post "Plan B" info.


I'll try to get a clear work-flow posted here for you to follow before the coming weekend. :)

GaryGB
 
HI again, Vetle:

I am awaiting a reply by Arno in another thread before I summarize a basic work-flow to derive the info needed to exclude ModelPart sub-tiles.

https://www.fsdeveloper.com/forum/threads/mcx-placement-to-shape-converter-missing.460581/


If it is not feasible for Arno to resolve an issue I reported in MCX, and he also requires time to consider my proposed idea, I'll post "Plan B" info.


I'll try to get a clear work-flow posted here for you to follow before the coming weekend. :)

GaryGB
Just so I understand: I do not consider altering others work (by importing Aalesund into MCX and removing tiles within MCX for export into the sim again as a "new/altered" photogrammetry version of Aalesund), but if the idea is to identify where to place exclusionrectangles within the developermode than I am all for it :)
 
Indeed; it would be helpful for MCX to accommodate generation of a data set from the ModelPart ID / selection process in Hierarchy Editor.


We'll see if Arno may find it feasible to add that functionality.

If not (...or if not in the near future), we will need to work from SHP and XML placement code from Objects.bgl's for such 3D 'scenes' as these .


In either case, we only inspect for purposes of Identifying objects / data located in files, then work external to that data ...to derive other data.

Ultimately, we only "Exclude and Replace" 3rd party content. :)

As an example, creation of XML micro-excludes is a function performed by freeware and payware versions of ADE for many years now. ;)

GaryGB
 
Last edited:
Hi Vetle:

I reviewed my data from testing exclusion of selected ModelParts in 3D G-Poly tile array GEDOT scenery library objects with ExclusionRectangles.

I tested placing ExclusionRectangles at calculated Geographic coordinates of selected ModelParts, but I cannot find my results showing it worked.


There may be other options we can test to prevent display of unwanted ModelParts in 3D G-Poly tile array GEDOT scenery library objects.

However, selectively controlling that process may ultimately require copying, exporting, and editing original BGLs containing such objects.


Considering practicalities of time and effort required to research this, it may best for you to plan on making your own replacement objects.

Apparently the intensive work I did for ENSX options into very late hours at night made it challenging to recall all the details (rare for me.)

So I must moderate my attention to wish list items to maintain my ability to function at peak efficiency, and deliver on many commitments.


I also want to be clear on all my test results so that I do not tug on Arno's sleeve to support things not yet adequately documented.

https://www.fsdeveloper.com/forum/threads/mcx-placement-to-shape-converter-missing.460581/


I may still test options for excluding ModelParts without editing original BGLs, but I would not be able to test these options very soon.


If you do not wish to make high detail versions of objects other than ENAX Hospital Heliport, that is quite understandable.


I believe you may find it possible to make building geometry and apply less detailed texture Materials with less work than you normally do.

Considering your work quality on past projects, even a 'generic' building with correct footprint / building segment heights would look great.


I am confident you will produce an outstanding scenery that makes other nearby objects less of a focus for the attention of scenery enthusiasts. :)

GaryGB
 
Last edited:
Hi Vetle:

I reviewed my data from testing exclusion of selected ModelParts in 3D G-Poly tile array GEDOT scenery library objects with ExclusionRectangles.

I tested placing ExclusionRectangles at calculated Geographic coordinates of selected ModelParts, but I cannot find my results showing it worked.


There may be other options we can test to prevent display of unwanted ModelParts in 3D G-Poly tile array GEDOT scenery library objects.

However, selectively controlling that process may ultimately require copying, exporting, and editing original BGLs containing such objects.


Considering practicalities of time and effort required to research this, it may best for you to plan on making your own replacement objects.

Apparently the intensive work I did for ENSX options into very late hours at night made it challenging to recall all the details (rare for me.)

So I must moderate my attention to wish list items to maintain my ability to function at peak efficiency, and deliver on many commitments.


I also want to be clear on all my test results so that I do not tug on Arno's sleeve to support things not yet adequately documented.

https://www.fsdeveloper.com/forum/threads/mcx-placement-to-shape-converter-missing.460581/


I may still test options for excluding ModelParts without editing original BGLs, but I would not be able to test these options very soon.


If you do not wish to make high detail versions of objects other than ENAX Hospital Heliport, that is quite understandable.


I believe you may find it possible to make building geometry and apply less detailed texture Materials with less work than you normally do.

Considering your work quality on past projects, even a 'generic' building with correct footprint / building segment heights would look great.


I am confident that you will produce an outstanding scenery to make nearby objects less of a focus for the attention of scenery enthusiasts. :)

GaryGB
Thanks for trying, Gary! I really appreciate it. please do not stress with the research regarding this issue. A solution will pop up when it pops up :)

I have started making the hospital campus so I will have to see how easy it is to remove the photogrammetry area immediately surrounding the helipad and add the custom made hospital into the leftovers. I suspect it will look weird with that combination, meaning I would need to remove the whole hospital area and more of the surroundings. If that is the case I will make this scenery non-photogrammetry compatible only... . Thanks again!
 
Does MSFS 2024 have default Asobo photogrammetry in the vicinity of the hospital ?

If so, that can be excluded with nearly unlimited granularity of control as it uses TIN geometry rather than 305.8 Meter span, multiple ModelPart 3D models.

...Firing up MSFS 2024 right now to test ENAX with- and without- Asobo's default photogrammtery (if any).

GaryGB
 
Last edited:
OK, ENAX does not yet have default MSFS photogrammetry in either MSFS 2020 or 2024, so one falls back to MSFS Generic Buildings.

They do not look all that bad to someone not familiar with the location; but admittedly Google "faux-Photogrammetry" looks better at "in-flight-altifudes".

I am confident you can make better replacements for the MSFS Generic Buildings. :)

GaryGB
 
Last edited:
OK, ENAX does not yet have default MSFS photogrammetry in either MSFS 2020 or 2024, so one falls back to MSFS Generic Buildings.

They do not look all that bad to someone not familiar with the location; but admittedly Google "faux-Photogrammetry" looks better at "in-flight-altifudes".

I am confident you can make better replacements for the MSFS Generic Buildings. :)

GaryGB
The hospital buildings needs to be adjusted, so that leaves me making the buildings from scratch...unfortunately. Oh well... :rolleyes:
 
Are you referring to building positioning ?

If so, do the MSFS default Generic buildings appear rotated and shifted out of alignment relative to a custom reference aerial image or vector graphic you are using ? :scratchch

GaryGB
 
Are you referring to building positioning ?

If so, do the MSFS default Generic buildings appear rotated and shifted out of alignment relative to a custom reference aerial image or vector graphic you are using ? :scratchch

GaryGB
No, no. Just the looks of them which are off.😄
 
Back
Top