TheGangster

That's interesting to see how users are utilizing the new vibe coding technologies available. AI is advancing rapidly so the results should improve in the future. Maybe I could look into structuring future versions of the program so that it would be easier for users to use vibe coding to contribute. Like maybe some files that would help copilot/cursor/etc to understand the context and design better.

I would like a linux version too. It's all a work in progress, and I'm just one guy, but hopefully with the new AI agentic coding technologies I can get more work done on my project quicker and get things closer to where i would like them to be.

Thanks for the further details. That's good to hear that the ps1-gpu compute shader works on hardware gpus other than mine (I use AMD integrated graphics). I didn't know Intel uses a subgroup size of 32, which means they have 8 subgroups at 256 shader invocations. I'll keep all this in mind while working on the ps2-gpu compute shader. If anyone else wants to help by posting their data too, and whether it works or not for ps1 or ps2 for them, it would be helpful and I can give credit under special...

Is this only for hps2x64, per the issue you were having with the -3 vkresult error? Or is this also for hps1x64?

Thanks for the bug report. Thanks for letting me know the ps1 version works for you. Haven't seen a -3 error before. Maybe try closing other programs like IE/MSEdge (also from task manager).

But, if you're intentionally trying to compile for the "Debug" configuration (this is important information that you didn't include, otherwise I don't know what you're talking about), then you will get this error when trying to configure the joystick. Just copy the "hps1x64.hcfg" or "hps2x64.hcfg" file (you didn't specify whether this was for hps1 or hps2, but use the corresponding hcfg file) that gets generated by the Release configuration exe or the included binary executable into the folder where...

If you're going to compile from source, make sure to follow the instructions and use the sln file and set it to "Release" configuration. The binary has also been compiled and included for you. Once you change the settings or fail to follow the instructions you're on your own.

Problems with memory model and memory allocation in latest version of MinGW64