by Xaser » Tue May 08, 2018 10:52 am
Related post of mine -- I'll quote the relevant bit so it's in context:
Xaser wrote:What we could really use here is a new feature: a set of MAPINFO flags that declare "I require feature 'x'", e.g. sloped 3D Floors or Truecolor, and have the engine output a warning if a user starts up the map with a renderer that doesn't support one of the declared features. This doesn't expose anything to ZScript, and since it's detecting the feature, not the renderer, it's future-proof -- e.g. if the Carmack renderer magically gets sloped 3D floors, it's marked as supported internally and the warning goes away for maps that declare it.
Works a bit differently since there's no ZScript exposure, and I'm not sure about your specific use case enough to know if this fits, but there it is.
[url=https://forum.zdoom.org/viewtopic.php?p=1053279#p1053279]Related post of mine[/url] -- I'll quote the relevant bit so it's in context:
[quote="Xaser"]What we could really use here is a new feature: a set of MAPINFO flags that declare "I require feature 'x'", e.g. sloped 3D Floors or Truecolor, and have the [i]engine[/i] output a warning if a user starts up the map with a renderer that doesn't support one of the declared features. This doesn't expose anything to ZScript, and since it's detecting the [i]feature[/i], not the renderer, it's future-proof -- e.g. if the Carmack renderer magically gets sloped 3D floors, it's marked as supported internally and the warning goes away for maps that declare it.[/quote]
Works a bit differently since there's no ZScript exposure, and I'm not sure about your specific use case enough to know if this fits, but there it is.