20,741
edits
Effects: Difference between revisions
Jump to navigation
Jump to search
no edit summary
No edit summary |
No edit summary |
||
| Line 16: | Line 16: | ||
|script_version = 0.40 | |script_version = 0.40 | ||
}}</ref> | }}</ref> | ||
Thus, favor a proper implementation FGData-side, but if that's not an option, copies of the relevant effects and shaders completely residing aircraft-side would be harmless as far as breakage is concerned and would 'freeze' the current state of the effect for teh <ref>{{cite web | |||
|url = https://sourceforge.net/p/flightgear/mailman/message/35389912/ | |||
|title = <nowiki> Re: [Flightgear-devel] SR71-BlackBird updates </nowiki> | |||
|author = <nowiki> Thorsten Renk </nowiki> | |||
|date = Sep 25th, 2016 | |||
|added = Sep 25th, 2016 | |||
|script_version = 0.40 | |||
}}</ref> | |||
What's really bad is overriding the FGData-side effect selection scheme scheme aircraft-side because that can cause unexpected breakage when FGData changes. If it's all completely aircraft-side, FGData maintenance doesn't affect it.<ref>{{cite web | What's really bad is overriding the FGData-side effect selection scheme scheme aircraft-side because that can cause unexpected breakage when FGData changes. If it's all completely aircraft-side, FGData maintenance doesn't affect it.<ref>{{cite web | ||
|url = https://sourceforge.net/p/flightgear/mailman/message/35389912/ | |url = https://sourceforge.net/p/flightgear/mailman/message/35389912/ | ||