kd-11
kd-11
I can reproduce. However this is not the same cause of the device lost error observed elsewhere. This is just a hang (shader end could not be found within X...
At the very least these new files should not live in the rpcs3 code folder. Maybe add a config/udev folder to the repo root and add them there. No idea...
Btw how does this work without root access?
The more I think about this the less it seems useful. The udev rules need to go into the system udev folder, not the rpcs3 install dir, or even the...
> I'm not sure I follow. The system udev folder would usually be /usr/lib/udev/rules.d (assuming a fairly standard setup with PREFIX=/usr) 1. This folder doesn't exist by default. Default system...
> I think it would exist on all systemd-based distributions I double-checked, you're right. I was checking the cmake lib directory (/lib/x86_64-linux-gnu) which doesn't have the udev folder. As for...
About automated testing - we can easily use RSX captures to recreate scenarios for RSX to run. This isn't the hard part. One of the limitations is that for something...
Performance is low because all the memory consumed by a draw call is reset for every individual draw call. This invalidates the caches and slows things down. It doesn't need...
I haven't experienced issue 3 in a few years and issue 4 mysteriously appeared randomly after some management code was updated outside RSX. Either way, behavior is going to change...
We added unit testing. Integration and feature testing requires more planning (and money) than we have bandwidth for at the moment.