This repository has been archived by the owner on Apr 17, 2022. It is now read-only.
[RFC]Preliminary Vulkan support #4523
Milestone
Comments
|
Vincent uploaded file |
|
Per changed blocking which not transferred by tractive |
|
Per changed blockedby which not transferred by tractive |
|
Per commented Very impressive. Sorry I've been late merging stuff, been held up on an unrelated bug fix and general lack of time. Is there any chance we could use one set of shaders, with some #ifdefs to distinguish between shaders for OpenGL 3.2 core profile and for Vulkan? |
|
Berserk Cyborg changed status from |
|
Berserk Cyborg changed resolution from `` to |
|
Berserk Cyborg commented Closing since Warzone2100/warzone2100#489 takes its place. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
resolution_closedtype_patch (an actual patch, not a request for one)| by VincentThis patch adds a Vulkan backend to WZ2100.
It's based on commits removing fixed function calls and commits adding per pixel lighting so it won't apply on master.
I'm posting it here to gather comments on the implementation since the code is very invasive.
I used auto in a lot of place, I think I will turn them into proper type in a final patch ; Almost Always Auto codestyle is very nice when creating a new abstraction or refactoring code but it's quite hard to read without IDE support.
Vulkan is a very verbose API and even if I throwed in vulkan HPP and generic lambdas at it it's still 1500 of code. And there's no mipmaping support of shader cache functionnalities at the moment.
Issue migrated from trac:4523 at 2022-04-16 12:38:00 -0700
The text was updated successfully, but these errors were encountered: