20,741
edits
Graphics card profiles: Difference between revisions
Jump to navigation
Jump to search
→Issues
m (→Status: https://sourceforge.net/p/flightgear/flightgear/ci/e1bb47bc8938dd51a6159209665ce0575aac1bbc/) |
(→Issues) |
||
| Line 154: | Line 154: | ||
== Issues == | == Issues == | ||
When preferences.xml, autosave.xml etc are loaded, the gl-vendor properties are not yet initialized, because that requires an actual GC (OSG graphics context), so that loading the overlay may need to be delayed or the initialization sequence changed accordingly. | When preferences.xml, autosave.xml etc are loaded, the gl-vendor properties are not yet initialized, because that requires an actual GC (OSG graphics context), so that loading the XML overlay may need to be delayed or the initialization sequence changed accordingly. | ||
We could also store a copy of the rendering specific state from autosave.xml and apply that within the GC::run() method, i.e. after loading graphics profiles there (straightforward). | We could also store a copy of the rendering specific state from autosave.xml and apply that within the GC::run() method, i.e. after loading graphics profiles there (straightforward). | ||