-
Notifications
You must be signed in to change notification settings - Fork 2.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Phantasy Star Portable 2 US] Debug Console Spam E[G3D] : Gpucommon.cpp:613 #1785
Comments
@unknownbrackets
If I enable "read from framebuffer to memory", a known bug will appear and I will see many things like:
If a game does not need "read from framebuffer to memory" to run fine, but the game has problem with this option enabled, is it an emulator bug? |
I think they could be important since it may be a bug in hiding. For example, it might cause random events to never happen, or etc. But some log entries are completely innocent (like missing files, often), so it's hard to say. I've noticed sceKernelReferGlobalProfiler in another game too I think, it could be important. sceMpegAvcInitYCbCr / sceMpegAvcDecodeFlush are maybe actually implemented mostly. glReadPixels: GL_INVALID_OPERATION probably means a bad component order or something, or just that the error flag was not cleared before the call. As far as read to memory breaking things - well, that's why I see the option as a hack. On the PSP, a game can say "my canvas is 1024 pixels tall", and then only draw to the top 24 pixels of it. The other 1000 rows will not be modified. In PPSSPP with that option, the memory for the other 1000 rows will be wiped. It might've had something important in it, in which case the game will likely be broken or glitchy. The game may have just been lazy since it didn't matter if it said the correct number or not anyway. To combat this, we could do something like reading framebuffer data from memory the current operation writes framebuffer data to memory, it's confusingly named), which would probably cripple performance. Might still be faster than the softgpu. Personally, I am only really concerned with "buffered rendering" bugs. Most of them are solvable. I think static analysis (detecting a function the game uses to blit vram, for example, as in Trails in the Sky) could even detect many types of pixel poking and work fine in buffered rendering, and be fast too. That's not to say any of it is easy. -[Unknown] |
Any need for this issue to stay open now that the original error message in the first post has been reduced to a debug log? |
When I started the Debug Console with the game Phantasy Star Portable 2 US the console got filled with these :
I'm running 0.7.6 - 547
30:56:857 user_main E[G3D]: GPUCommon.cpp:613 Signal without wait. signal/end: 0001 0000
30:56:858 idle0 E[G3D]: GPUCommon.cpp:613 Signal without wait. signal/end: 0004 0000
30:56:858 idle0 E[G3D]: GPUCommon.cpp:613 Signal without wait. signal/end: 0005 0000
30:56:858 idle0 E[G3D]: GPUCommon.cpp:613 Signal without wait. signal/end: 0006 0000
30:56:858 idle0 E[G3D]: GPUCommon.cpp:613 Signal without wait. signal/end: 0007 0000
30:56:858 idle0 E[G3D]: GPUCommon.cpp:613 Signal without wait. signal/end: 0008 0000
30:56:891 user_main E[G3D]: GPUCommon.cpp:613 Signal without wait. signal/end: 0001 0000
30:56:891 idle0 E[G3D]: GPUCommon.cpp:613 Signal without wait. signal/end: 0004 0000
30:56:891 idle0 E[G3D]: GPUCommon.cpp:613 Signal without wait. signal/end: 0005 0000
30:56:891 idle0 E[G3D]: GPUCommon.cpp:613 Signal without wait. signal/end: 0006 0000
30:56:891 idle0 E[G3D]: GPUCommon.cpp:613 Signal without wait. signal/end: 0007 0000
30:56:891 idle0 E[G3D]: GPUCommon.cpp:613 Signal without wait. signal/end: 0008 0000
The text was updated successfully, but these errors were encountered: