Tyler Jaacks

I found something interesting with the ```-platform windows:fontengine=freetype``` command line argument, I get something like this  Without the ```-platform windows:fontengine=freetype``` command line argument, I get this  I noticed...

 v0.0.35-17700-76c069e8 which uses Qt 6.8.2  v0.0.35-17701-6921684c which uses Qt 6.8.3 https://github.com/RPCS3/rpcs3/pull/16935/

@digant73 it appears to be fixed what commit fixed this?

I have a AMD Ryzen 5950X, 64GB RAM, and a RTX 4090, and I am also having this issue and that this build does indeed work for me.

> The only documented solution (excluding reverting shadPS4 back to builds where [#1659](https://github.com/shadps4-emu/shadPS4/pull/1659) was not merged) is to downgrade Windows. Recent versions broke the way we create threads. Is there...

@polybiusproxy what would you need to test, I could do that?

if the user who mentioned that the https://github.com/shadps4-emu/shadPS4/pull/1659 is the culprit, that would make sense as there are various pthread changes in this merge. I'm going to try to compile...

So I was looking at this https://github.com/winsiderss/phnt/blob/master/ntpsapi.h and there are some changes with 24H2, but I don't think they would make a difference. So the result of this ```return NtCreateThread(&native_handle,...

So I fixed, this issue, so it appears that it has to do with a Windows Security migitation that was probably triggered by using the raw Windows NtCreateThread syscall.

You will have to remove CFG mitigations on the binary.