20,741
edits
Draw masks: Difference between revisions
Jump to navigation
Jump to search
no edit summary
No edit summary |
No edit summary |
||
| Line 19: | Line 19: | ||
{{FGCquote|1= Those draw masks will not prevent stuff from being loaded (=consuming RAM/memory), it will merely disable updates to the already loaded data. Which also applies to other stuff like aircraft.Which is why heavy aircraft like the 777-200 or the extra500 will still perform much worse than comparatively lightweight aircraft like the ufo, ogeL, santa or the default c172p (especially the 2D version is fairly lightweight).|2= {{cite web | url = http://forum.flightgear.org/viewtopic.php?p=214147#p214147 | title = <nowiki>Re: Flatland</nowiki> | author = <nowiki>Hooray</nowiki> | date = Jul 5th, 2014 }}}} | {{FGCquote|1= Those draw masks will not prevent stuff from being loaded (=consuming RAM/memory), it will merely disable updates to the already loaded data. Which also applies to other stuff like aircraft.Which is why heavy aircraft like the 777-200 or the extra500 will still perform much worse than comparatively lightweight aircraft like the ufo, ogeL, santa or the default c172p (especially the 2D version is fairly lightweight).|2= {{cite web | url = http://forum.flightgear.org/viewtopic.php?p=214147#p214147 | title = <nowiki>Re: Flatland</nowiki> | author = <nowiki>Hooray</nowiki> | date = Jul 5th, 2014 }}}} | ||
== Scenery == | |||
{{FGCquote | |||
|1= I'd like to see both LOD range and user settable masks in the .stg file. | |||
|2= {{cite web | |||
| url = http://forum.flightgear.org/viewtopic.php?p=216506#p216506 | |||
| title = <nowiki>Re: No go airports for weak gpus ...</nowiki> | |||
| author = <nowiki>psadro_gm</nowiki> | |||
| date = Aug 12th, 2014 | |||
}} | |||
}} | |||
{{FGCquote | |||
|1= we should probably consider adding a dedicated draw-mask for such features, and maybe even a "factor" attribute to specify how many of those objects/models should be loaded/shown. | |||
Maybe, there is a way to procedurally add a "marker" (tag) to each model so that the loader in fg/sg can dynamically be told to enable, increase/decrease or disable such features ? | |||
|2= {{cite web | |||
| url = http://forum.flightgear.org/viewtopic.php?p=262877#p262877 | |||
| title = <nowiki>Re: Populate 3000 airports in one day</nowiki> | |||
| author = <nowiki>Hooray</nowiki> | |||
| date = Nov 3rd, 2015 | |||
}} | |||
}} | |||
{{FGCquote | |||
|1= I agree. I think this is not very hard to implement. | |||
And I am not surprised that others had the same idea already before me. | |||
|2= {{cite web | |||
| url = http://forum.flightgear.org/viewtopic.php?p=263511#p263511 | |||
| title = <nowiki>Re: Populate 3000 airports in one day</nowiki> | |||
| author = <nowiki>pommesschranke</nowiki> | |||
| date = Nov 8th, 2015 | |||
}} | |||
}} | |||
{{FGCquote | |||
|1= My original response contains links to patches doing this - so you could basically adapt the patch to introduce a new draw-mask for autogen-based features. | |||
That said, psadro_gm definitely is in a much better position to judge if/how the underlying scenery format could encode a corresponding bit pattern to distinguish different features, i.e. something like 4-5 bits would probably do for most purposes (looking at osm2city etc) | |||
Feel free to get in touch if you need help with the C++ side of the draw masks - but like you say, something like that would ideally not just support on/off, but also an attribute to adjust scene complexity, i.e. scale up/down - especially for feature scaling purposes. | |||
|2= {{cite web | |||
| url = http://forum.flightgear.org/viewtopic.php?p=263512#p263512 | |||
| title = <nowiki>Re: Populate 3000 airports in one day</nowiki> | |||
| author = <nowiki>Hooray</nowiki> | |||
| date = Nov 8th, 2015 | |||
}} | |||
}} | |||
{{FGCquote | |||
|1= more and more features would get dedicated properties with draw-masks to disable/enable rendering and optionally customie things - this isn't too difficult to do, and it doesn't necessarily involve touching tons of STG/BTG files - it's mainly a change that would involve SimGear/FG, so that buildings (and other heavy stuff) would be loaded into dedicated sub-scene graph that can be easily disabled using an osg::switch node | |||
|2= {{cite web | |||
| url = http://forum.flightgear.org/viewtopic.php?p=231142#p231142 | |||
| title = <nowiki>Re: No go airports for weak gpus ...</nowiki> | |||
| author = <nowiki>Hooray</nowiki> | |||
| date = Feb 3rd, 2015 | |||
}} | |||
}} | |||
To open a property browser with the corresponding properties, use <code>--prop:browser=/sim/rendering/draw-mask</code> (can be also added to your fgfsrc file) | To open a property browser with the corresponding properties, use <code>--prop:browser=/sim/rendering/draw-mask</code> (can be also added to your fgfsrc file) | ||