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

Autogen road night lighting

kevinfirth

kevinfirth

Messages
203
Country
unitedkingdom
OrbX have confirmed that the no FPS Los night lighting included with FTXG and to be rolled out retrospectively to their existing FTX regions is autogen. I wonder therefore if there is the possibility of using this to annotate photoreal scenery automatically somehow?
 
Hi Kevin:

We will know more about the light objects, their GUIDs, and how they are placed when FTX Global (aka "FTXG") is updated, presumably in the near future. :idea:


BTW: At this time, IMHO, significant aspects of the methodology used to implement scenery in that package are in question by some members of the FS Community.

AFAIK, this may be due to reports that, FTXG installation results in arbitrary changes which effectively prevent other FS scenery developers from implementing their own "SDK-compatible" scenery features.

FYI: In its current form, the FTXG scenery package does not provide a means for reverting back to default FSX scenery, nor does it provide a function to- or explanation of how to-...uninstall it.


IIUC, "the word on the street" is that 3rd party 'work-arounds' for- and interventions intended to prevent in the future such arbitrary methodology from- installing non-SDK compatible changes onto users FS computers ...are in active development at this time.


I presume that OrbX may be working diligently to find alternate methods to adapt current and future installations of the FTXG scenery package to:

* allow options for a return to FSX default without a full FTXG un-install

* un-install FTXG entirely

* allow other FS scenery developers to implement their own "SDK-compatible" scenery features on a "side-by-side" basis when FTG is 'active'

So, IMHO, it would be premature to allocate time to developing custom scenery using anything from an OrbX scenery package (which IIUC, technically is prohibited by their EULA even if for use only on one's own FS computer anyway).


It will be interesting to see how this situation evolves, and to see what OrbX can achieve in advance of and/or in spite of ...any 3rd party solutions / interventions which may be forthcoming in the future. :rolleyes:

GaryGB
 
Last edited:
GaryGB said:
So, IMHO, it would be premature to allocate time to developing custom scenery using anything from an OrbX scenery package (which IIUC, technically is prohibited by their EULA even if for use only on one's own FS computer anyway).
GaryGB
Click to expand...

Which explains why I stop distributing Orbx compatible scenery; the onus placed on the developer to ensure 100% compliance with their EULA just wasn't worth it. :(
 
You must log in or register to reply here.
Back
Top