Closed oscarbg closed 6 years ago
Thanks for the report @oscarbg ! I also happened to test it yesterday, and we are currently missing support for named specialization constants if I'm not mistaken. This is solvable.
Ok, it wasn't named specialization constants but rather a miscommunication between gfx-hal and gfx-portability, which resulted in a loss of typing information for the constants. It is addressed by https://github.com/gfx-rs/gfx/pull/2381
However, the next blocker is sub-pass support, which vkQuake appears to be using.
Fix is coming in https://github.com/gfx-rs/gfx/pull/2387
nice! thanks.. will test soon and close issue..
We'll close the issue when the build containing the fix is available
On Sep 7, 2018, at 20:34, Oscar Barenys notifications@github.com wrote:
nice! thanks.. will test soon and close issue..
— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.
Hi, I tested vkquake 1.0 and sadly is also failing with shared portability binaries for rpcs3 & dolphin.. recompiled again with your library renamed and located as : /lib/libMoltenVK.dylib changed Makefile to: COMMON_LIBS:= -lm /lib/libMoltenVK.dylib you have to put in ID1 folder pak0.pak at least (I'm using it from shareware version)
first "lame" issue I found with "otool -L vkquake": /Users/dmalyshau/Code/portability/target/release/deps/libportability.dylib (compatibility version 1.0.0, current version 1.0.0) had to create this folders and copy library also there.. can you fix future binary libraries to not a fixed path (like for ex. @rpath I believe).. this issue isn't present on libMoltenVK dylib..
even then fails with: QUAKE ERROR: vkCreateGraphicsPipelines failed
full log:
with moltenvk works ok by overwriting /Users/dmalyshau/Code/portability/target/release/deps/libportability.dylib with that dylib: