Forum Discussion
rezanourai
11 years agoHonored Guest
It appears the issue is if the same process tries to tear down one rendering stack (ex: GL) and then reinitialize with another (ex: D3D) we don't fully work in all cases (ex; Gl -> D3D, but we work the other way).
I've created a task to track this, but given that it's not a common case for apps to use 2 rendering architectures and expect hot-swap between them, it doesn't meet the bar for squeezing into this release. Exiting the application and relaunching it afterwards should work around the problem.
We'll get this prioritized accordingly and fixed in a future release. Thanks again!
I've created a task to track this, but given that it's not a common case for apps to use 2 rendering architectures and expect hot-swap between them, it doesn't meet the bar for squeezing into this release. Exiting the application and relaunching it afterwards should work around the problem.
We'll get this prioritized accordingly and fixed in a future release. Thanks again!
Related Content
- 5 months ago
- 10 years ago
- 4 years ago