There's no hard API differential between mobile and desktop versions, which will in theory ease the porting of cross-platform games and if nothing else reduce version-checking headaches that everybody hates.Validation and diagnostics layers can be independently enabled, allowing in theory for better tools integration with the API (something OpenGL itself has suffered from) and disabling of excessive validation, in theory allowing " the graphics on level three" to be that much more performant.Thread and memory management tasks are left to the application, not the driver, allowing game developers more control over those behaviors and thus potentially more accurate tailoring of those behaviors to their individual game's needs.
#Star trek online unrestricted tailor software
Most high-profile and/or high-performance software built on OpenGL today implement this kind of behavior themselves having the API support this itself means that developers need not implement and maintain that framework themselves, or that they can do so with less effort. This reflects the realities of modern hardware. The API is oriented around asynchronous generation of command buffers across multiple threads and sequenced processing of those buffers to a command pipeline.Vulkan's practical advantages to game developers are primarily about control (as in, allowing more of it, potentially allowing for better optimizations at the cost of significantly more up-front work on the developer's part). Originally referred to "glNext," one can infer that Vulkan was likely going to end up being "OpenGL 5," but that the standards body eventually decided that a new name would better coincide with the relatively clean break the API purports to make from existing OpenGL paradigms. OpenGL will continue to be developed, as it is a higher-level API than Vulkan is intended to be. Vulkan is a new API for hardware-accelerated graphics (and general computation) via traditional GPUs.
0 kommentar(er)
