Wolfgang Steiner
Wolfgang Steiner
That's right @matiwinnetou I switched to 8.4.0 for Android because 8.2.1 seemed very flaky to try and compile on Android (especially [this problem](https://github.com/nodejs/node/issues/9707) and related issues about mkpeephole). I did...
@matiwinnetou I put a table with the current results in the first post just now. I got 8.4.0 to compile on pretty much all platforms ... but something seems to...
The problems running the tests on Linux & MacOS seem to all have the same origin, which I was not able to figure out yet. @matiwinnetou @irbull Have you done...
@hurol02 I think the most recent parts that I added to get node 8.4.x to compile are not yet available in the repo, since I didn't want to put it...
I have done some research on this (focusing on #188 and #289) IMO there are two problems that need to be solved well: 1) a distinctive file naming scheme is...
Thanks for testing the file permissions @Kernle32DLL > The only remark I have is that I don't know if it is necessary to enforce the vendor part. Because if we...
vkCmdPushConstants() in MatrixStack::record() can sometimes cause Vulkan validation-error VUID-01795
I now added a stripped down version of the `VUID-01795` error repro-code to the repository: * [vsg-View-PushConst-bug-minimal.cpp](https://github.com/drywolf/vsg-View-vkCmdPushConstants-bug/blob/main/vsg-View-PushConst-bug-minimal.cpp) The original [vsg-View-PushConst-bug.cpp](https://github.com/drywolf/vsg-View-vkCmdPushConstants-bug/blob/main/vsg-View-PushConst-bug.cpp) code has some additional code for experimentation + it also...
vkCmdPushConstants() in MatrixStack::record() can sometimes cause Vulkan validation-error VUID-01795
> how this ought to be configured/controlled from the C++ code needs to be discussed ?! I imagine the most correct & least invasive way to fix this, would be...
I apologize if I was unable to communicate the issue at hand clearly enough. > I think it's important to differentiate between rendering on the GPU and copying of data...
Thanks @Mikalai for testing ❤️ Fedora behaving so differently might indicate an issue in the AMD Windows driver. I will contact AMD and let them know about this.