This forum uses cookies
This forum makes use of cookies to store your login information if you are registered, and your last visit if you are not. Cookies are small text documents stored on your computer; the cookies set by this forum can only be used on this website and pose no security risk. Cookies on this forum also track the specific topics you have read and when you last read them. Please confirm whether you accept or reject these cookies being set.

A cookie will be stored in your browser regardless of choice to prevent you being asked this question again. You will be able to change your cookie settings at any time using the link in the footer.

Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Clannad JPN -ULJM05338+ULJM05339
#11
Attached
(05-28-2020, 07:20 AM)gid15 Wrote: OK, it would be helpful to have a log at DEBUG level when the performance is low. I do not need the DEBUG level from the beginning, only enable it when reaching the low performance screens and just keep it for 2 or 3 seconds.
I just need to see how one screen is being rendered in detail.

Thank you!


Attached Files
.7z   debuglog.7z (Size: 56.55 KB / Downloads: 113)
Reply
#12
(05-28-2020, 11:13 AM)sum2012 Wrote: Attached
(05-28-2020, 07:20 AM)gid15 Wrote: OK, it would be helpful to have a log at DEBUG level when the performance is low. I do not need the DEBUG level from the beginning, only enable it when reaching the low performance screens and just keep it for 2 or 3 seconds.
I just need to see how one screen is being rendered in detail.

Thank you!
Hmmm, it didn't capture any screen frame. Lets try it in a different way: press "Pause" when a slow performance screen is reached, select the menu "Debug / Tools / Debugger" and then under the "Misc" tab, press "Capture next frame". Then Press "Run" to restart the emulation. It will just run for one display frame but now, the log file should have captured the information I need. Images will also be created under the "tmp" directory, but I do not need them, just the log file.

Thank you!
Always include a complete log file at INFO level in your reports. Thanks! How to post a log
Reply
#13
Attached.
The misc button is hard to find.
(05-28-2020, 11:36 AM)gid15 Wrote:
(05-28-2020, 11:13 AM)sum2012 Wrote: Attached
(05-28-2020, 07:20 AM)gid15 Wrote: OK, it would be helpful to have a log at DEBUG level when the performance is low. I do not need the DEBUG level from the beginning, only enable it when reaching the low performance screens and just keep it for 2 or 3 seconds.
I just need to see how one screen is being rendered in detail.

Thank you!
Hmmm, it didn't capture any screen frame. Lets try it in a different way: press "Pause" when a slow performance screen is reached, select the menu "Debug / Tools / Debugger" and then under the "Misc" tab, press "Capture next frame". Then Press "Run" to restart the emulation. It will just run for one display frame but now, the log file should have captured the information I need. Images will also be created under the "tmp" directory, but I do not need them, just the log file.

Thank you!


Attached Files
.7z   captionlog.7z (Size: 6.05 KB / Downloads: 120)
Reply
#14
OK, the application is using large textures in RAM (not VRAM), but those textures are 8BIT or 4BIT indexed. I will test this situation, but they probably should be excluded from the change in 8afa36f as their size in RAM is not so large than in 8888 format.
Code:
21:11:10 DEBUG       ge - GUI - tflush 0x097F2280, buffer_width=480 (512,512)
21:11:10 DEBUG       ge - GUI - tflush texture_storage=0x5(PSM_8BIT_INDEXED), tex_clut_mode=0x3, tex_clut_addr=0x097F1E00, texture_swizzle=true
21:11:10 DEBUG       ge - GUI -   sprite (0,0)-(480,272) at (0,0,0)-(480,272,0)
...
21:11:10 DEBUG       ge - GUI - tflush 0x096244C0, buffer_width=480 (512,128)
21:11:10 DEBUG       ge - GUI - tflush texture_storage=0x5(PSM_8BIT_INDEXED), tex_clut_mode=0x3, tex_clut_addr=0x09624040, texture_swizzle=true
21:11:10 DEBUG       ge - GUI -   sprite (3,0)-(4,80) at (0,199,0)-(480,279,0)
...
21:11:10 DEBUG       ge - GUI - tflush 0x088D6810, buffer_width=512 (512,512)
21:11:10 DEBUG       ge - GUI - tflush texture_storage=0x4(PSM_4BIT_INDEXED), tex_clut_mode=0x2, tex_clut_addr=0x0885DC10, texture_swizzle=false
21:11:10 DEBUG       ge - GUI -   sprite (0,0)-(512,512) at (16,207,0)-(528,719,0)
...
21:11:10 DEBUG       ge - GUI - tflush 0x095B5C40, buffer_width=128 (128,16)
21:11:10 DEBUG       ge - GUI - tflush texture_storage=0x5(PSM_8BIT_INDEXED), tex_clut_mode=0x3, tex_clut_addr=0x095B57C0, texture_swizzle=true
21:11:10 DEBUG       ge - GUI -   sprite (16,0)-(32,16) at (460,253,0)-(476,269,0)
Always include a complete log file at INFO level in your reports. Thanks! How to post a log
Reply
#15
(05-28-2020, 03:32 PM)gid15 Wrote: OK, the application is using large textures in RAM (not VRAM), but those textures are 8BIT or 4BIT indexed. I will test this situation, but they probably should be excluded from the change in 8afa36f as their size in RAM is not so large than in 8888 format.
The indexed and compressed textures are now excluded from the timing settings in e24da20.
I guess this will return the performance for this application to what it was before 8afa36f.
Always include a complete log file at INFO level in your reports. Thanks! How to post a log
Reply
#16
e24da20 version
The performance restore.

Remain case 3 in
https://www.emunewz.net/forum/showthread...#pid364849
Reply
#17
For the "Aborting current list processing due to too many errors"

Last good 82dad98
First bad 1f7ff95
It mean https://github.com/jpcsp/jpcsp/commit/1f...c0edf12d91
have problem


Attached Files
.txt   1f7ff95log.txt (Size: 10.65 KB / Downloads: 101)
.txt   82dad98log.txt (Size: 14.63 KB / Downloads: 102)
Reply
#18
Could you please try to generate a log file reproducing the issue, at INFO level but with the following lines added to LogSettings.xml:
Code:
<logger name='hle.sceGe_user'> <level value='debug' /> </logger>
<logger name='hle.sceUtility'> <level value='debug' /> </logger>
<logger name='hle.sceDisplay'> <level value='debug' /> </logger>
Always include a complete log file at INFO level in your reports. Thanks! How to post a log
Reply
#19
(06-01-2020, 05:02 PM)gid15 Wrote: Could you please try to generate a log file reproducing the issue, at INFO level but with the following lines added to LogSettings.xml:
Code:
<logger name='hle.sceGe_user'> <level value='debug' /> </logger>
<logger name='hle.sceUtility'> <level value='debug' /> </logger>
<logger name='hle.sceDisplay'> <level value='debug' /> </logger>
Were you able to generate a log with those settings?
Always include a complete log file at INFO level in your reports. Thanks! How to post a log
Reply
#20
Sorry for late reply
The game 100% no problem with these setting.
(06-03-2020, 04:23 PM)gid15 Wrote:
(06-01-2020, 05:02 PM)gid15 Wrote: Could you please try to generate a log file reproducing the issue, at INFO level but with the following lines added to LogSettings.xml:
Code:
<logger name='hle.sceGe_user'> <level value='debug' /> </logger>
<logger name='hle.sceUtility'> <level value='debug' /> </logger>
<logger name='hle.sceDisplay'> <level value='debug' /> </logger>
Were you able to generate a log with those settings?


Attached Files
.7z   goodlog.7z (Size: 26.1 KB / Downloads: 107)
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)