The following warnings occurred:
Warning [2] Undefined variable $thumblist - Line: 1021 - File: inc/functions_post.php PHP 8.2.26 (Linux)
File Line Function
/inc/class_error.php 153 errorHandler->error
/inc/functions_post.php 1021 errorHandler->error_callback
/inc/functions_post.php 822 get_post_attachments
/showthread.php 1118 build_postbit



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.
EmuNewz Network › PSP Emulation › JPCSP Official Forum › Commercial Game Discussion › JPCSP - Playable Games v
Digivice Ver. Portable - NPJH00126

Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Threaded Mode
Digivice Ver. Portable - NPJH00126
DragonNeos Offline
Moderator
*****
Posts: 591
Threads: 59
Joined: Dec 2011
Reputation: 3
#1
08-26-2013, 03:59 AM (This post was last modified: 08-26-2013, 08:21 AM by DragonNeos.)
This game was tested with JPCSP v0.7 r3369 and PPSSPP v0.9.1-150-g49d41ab. The main problem for this game is that it can not display the image inside the Digivice. For JPCSP and PPSSPP, there is a black display inside the Digivice when it is supposed to be gray with the Digimon displayed in LED pixels. There is no setting in either emulator that can make the screen inside the Digivice visible. The image that is shown when creating SAVEDATA is not accurate (4th Image = JPCSP, 5th Image = PPSSPP).


Attached Files Thumbnail(s)
                   

.7z   NPJH00126DATA.7z (Size: 176.63 KB / Downloads: 175)
.zip   Log_r3369(64bit)_INFO.zip (Size: 1.14 MB / Downloads: 191)
Find
Reply
gid15 Offline
Dev team
**********
Posts: 2,420
Threads: 30
Joined: Dec 2009
Reputation: 50
#2
08-26-2013, 04:55 PM
From the profiler info:
Code:
trxkick: called 4681 times, average 1.0 per GE list
This game is using quite often the video command trxkick. Is there any change using r3371?
Always include a complete log file at INFO level in your reports. Thanks! How to post a log
Find
Reply
DragonNeos Offline
Moderator
*****
Posts: 591
Threads: 59
Joined: Dec 2011
Reputation: 3
#3
08-27-2013, 08:44 AM (This post was last modified: 09-06-2013, 03:52 AM by DragonNeos.)
The screen inside the Digivice is now visible with r3372. Other than the creating SAVEDATA image problem, the game is now playable. Thank you for fixing this game, gid15!

EDIT: When loading SAVEDATA, the image that appears is not accurate. I forgot to test this function because I was so happy that this game became playable. (5th Image = JPCSP, 6th Image = PPSSPP)


Attached Files Thumbnail(s)
                       

.zip   Log_r3372(64bit)_INFO.zip (Size: 118.15 KB / Downloads: 173)
Find
Reply
Zekro Offline
Last seen as Virgil94
*****
Posts: 1,017
Threads: 17
Joined: Jan 2011
Reputation: 12
#4
08-27-2013, 09:00 AM
Moved to playable
Am I the only one with this cool sig?
[Image: ji6WX.png]
[Image: 2404362.png]
Find
Reply
DragonNeos Offline
Moderator
*****
Posts: 591
Threads: 59
Joined: Dec 2011
Reputation: 3
#5
11-25-2017, 11:01 AM (This post was last modified: 11-25-2017, 11:09 AM by DragonNeos.)
This game was tested with revision b16aa64. On the title screen, after pressing the circle button on the first option to enter the game, the emulator will freeze with the following error:
Code:
05:21:54 ERROR  runtime - CRI Server Manager - Catched Throwable in RuntimeThread:
java.lang.IncompatibleClassChangeError: Expected static field jpcsp.Allegrex.VfpuState.memory
    at jpcsp.Allegrex.VfpuState.doSVRQ(VfpuState.java:3248)
    at jpcsp.Allegrex.Instructions$126.interpret(Instructions.java:4786)
    at _S1_2_0x08896754.s(_S1_2_0x08896754.java:328)
    at _S1_2_0x088956D8.s(_S1_2_0x088956D8.java:396)
    at _S1_2_0x0889446C.s(_S1_2_0x0889446C.java:52)
    at _S1_2_0x08893734.s(_S1_2_0x08893734.java:88)
    at _S1_2_0x08893320.s(_S1_2_0x08893320.java:268)
    at _S1_2_0x08893048.s(_S1_2_0x08893048.java:24)
    at _S1_2_0x0888FCF4.s(_S1_2_0x0888FCF4.java:1172)
    at _S1_2_0x0888FCF4.exec(_S1_2_0x0888FCF4.java)
    at jpcsp.Allegrex.compiler.RuntimeContext.jumpCall(RuntimeContext.java:174)
    at jpcsp.Allegrex.compiler.RuntimeContext.call(RuntimeContext.java:227)
    at _S1_2_0x08869370.s(_S1_2_0x08869370.java:28)
    at _S1_2_0x0887A268.s(_S1_2_0x0887A268.java:276)
    at _S1_2_0x08879EC0.s(_S1_2_0x08879EC0.java:312)
    at _S1_2_0x08879CF8.s(_S1_2_0x08879CF8.java:424)
    at _S1_2_0x08879CF8.exec(_S1_2_0x08879CF8.java)
    at jpcsp.Allegrex.compiler.RuntimeContext.jumpCall(RuntimeContext.java:174)
    at jpcsp.Allegrex.compiler.RuntimeContext.call(RuntimeContext.java:227)
    at _S1_2_0x0889A2F8.s(_S1_2_0x0889A2F8.java:52)
    at _S1_2_0x08879C70.s(_S1_2_0x08879C70.java:108)
    at _S1_2_0x08879C54.s(_S1_2_0x08879C54.java:12)
    at _S1_2_0x08848FE8.s(_S1_2_0x08848FE8.java:84)
    at _S1_2_0x0885B24C.s(_S1_2_0x0885B24C.java:92)
    at _S1_2_0x0885B1E4.s(_S1_2_0x0885B1E4.java:72)
    at _S1_2_0x0885B1C8.s(_S1_2_0x0885B1C8.java:12)
    at _S1_2_0x0885B1C8.exec(_S1_2_0x0885B1C8.java)
    at jpcsp.Allegrex.compiler.RuntimeContext.jumpCall(RuntimeContext.java:174)
    at jpcsp.Allegrex.compiler.RuntimeContext.call(RuntimeContext.java:227)
    at _S1_2_0x0889E380.s(_S1_2_0x0889E380.java:284)
    at _S1_2_0x0889E62C.s(_S1_2_0x0889E62C.java:12)
    at _S1_2_0x0889E62C.exec(_S1_2_0x0889E62C.java)
    at jpcsp.Allegrex.compiler.RuntimeContext.jumpCall(RuntimeContext.java:174)
    at jpcsp.Allegrex.compiler.RuntimeContext.call(RuntimeContext.java:227)
    at _S1_2_0x0889B7E8.s(_S1_2_0x0889B7E8.java:100)
    at _S1_2_0x0889B7E8.exec(_S1_2_0x0889B7E8.java)
    at jpcsp.Allegrex.compiler.RuntimeContext.jumpCall(RuntimeContext.java:174)
    at jpcsp.Allegrex.compiler.RuntimeContext.call(RuntimeContext.java:227)
    at _S1_2_0x0889E9F4.s(_S1_2_0x0889E9F4.java:68)
    at _S1_2_0x0889E9F4.exec(_S1_2_0x0889E9F4.java)
    at jpcsp.Allegrex.compiler.RuntimeContext.execWithReturnAddress(RuntimeContext.java:773)
    at jpcsp.Allegrex.compiler.RuntimeContext.runThread(RuntimeContext.java:836)
    at jpcsp.Allegrex.compiler.RuntimeThread.run(RuntimeThread.java:50)
Other games that are affected by this error are Digimon World: ReBig Grinigitize and Yu-Gi-Oh! ARC-V Tag Force Special.


Attached Files
.zip   Log_rb16aa64(64bit)_INFO.zip (Size: 121.5 KB / Downloads: 159)
Find
Reply
gid15 Offline
Dev team
**********
Posts: 2,420
Threads: 30
Joined: Dec 2009
Reputation: 50
#6
11-25-2017, 05:43 PM
(11-25-2017, 11:01 AM)DragonNeos Wrote: This game was tested with revision b16aa64. On the title screen, after pressing the circle button on the first option to enter the game, the emulator will freeze with the following error:
Code:
05:21:54 ERROR  runtime - CRI Server Manager - Catched Throwable in RuntimeThread:
java.lang.IncompatibleClassChangeError: Expected static field jpcsp.Allegrex.VfpuState.memory
    at jpcsp.Allegrex.VfpuState.doSVRQ(VfpuState.java:3248)
    at jpcsp.Allegrex.Instructions$126.interpret(Instructions.java:4786)
    at _S1_2_0x08896754.s(_S1_2_0x08896754.java:328)
    at _S1_2_0x088956D8.s(_S1_2_0x088956D8.java:396)
    at _S1_2_0x0889446C.s(_S1_2_0x0889446C.java:52)
    at _S1_2_0x08893734.s(_S1_2_0x08893734.java:88)
    at _S1_2_0x08893320.s(_S1_2_0x08893320.java:268)
    at _S1_2_0x08893048.s(_S1_2_0x08893048.java:24)
    at _S1_2_0x0888FCF4.s(_S1_2_0x0888FCF4.java:1172)
    at _S1_2_0x0888FCF4.exec(_S1_2_0x0888FCF4.java)
    at jpcsp.Allegrex.compiler.RuntimeContext.jumpCall(RuntimeContext.java:174)
    at jpcsp.Allegrex.compiler.RuntimeContext.call(RuntimeContext.java:227)
    at _S1_2_0x08869370.s(_S1_2_0x08869370.java:28)
    at _S1_2_0x0887A268.s(_S1_2_0x0887A268.java:276)
    at _S1_2_0x08879EC0.s(_S1_2_0x08879EC0.java:312)
    at _S1_2_0x08879CF8.s(_S1_2_0x08879CF8.java:424)
    at _S1_2_0x08879CF8.exec(_S1_2_0x08879CF8.java)
    at jpcsp.Allegrex.compiler.RuntimeContext.jumpCall(RuntimeContext.java:174)
    at jpcsp.Allegrex.compiler.RuntimeContext.call(RuntimeContext.java:227)
    at _S1_2_0x0889A2F8.s(_S1_2_0x0889A2F8.java:52)
    at _S1_2_0x08879C70.s(_S1_2_0x08879C70.java:108)
    at _S1_2_0x08879C54.s(_S1_2_0x08879C54.java:12)
    at _S1_2_0x08848FE8.s(_S1_2_0x08848FE8.java:84)
    at _S1_2_0x0885B24C.s(_S1_2_0x0885B24C.java:92)
    at _S1_2_0x0885B1E4.s(_S1_2_0x0885B1E4.java:72)
    at _S1_2_0x0885B1C8.s(_S1_2_0x0885B1C8.java:12)
    at _S1_2_0x0885B1C8.exec(_S1_2_0x0885B1C8.java)
    at jpcsp.Allegrex.compiler.RuntimeContext.jumpCall(RuntimeContext.java:174)
    at jpcsp.Allegrex.compiler.RuntimeContext.call(RuntimeContext.java:227)
    at _S1_2_0x0889E380.s(_S1_2_0x0889E380.java:284)
    at _S1_2_0x0889E62C.s(_S1_2_0x0889E62C.java:12)
    at _S1_2_0x0889E62C.exec(_S1_2_0x0889E62C.java)
    at jpcsp.Allegrex.compiler.RuntimeContext.jumpCall(RuntimeContext.java:174)
    at jpcsp.Allegrex.compiler.RuntimeContext.call(RuntimeContext.java:227)
    at _S1_2_0x0889B7E8.s(_S1_2_0x0889B7E8.java:100)
    at _S1_2_0x0889B7E8.exec(_S1_2_0x0889B7E8.java)
    at jpcsp.Allegrex.compiler.RuntimeContext.jumpCall(RuntimeContext.java:174)
    at jpcsp.Allegrex.compiler.RuntimeContext.call(RuntimeContext.java:227)
    at _S1_2_0x0889E9F4.s(_S1_2_0x0889E9F4.java:68)
    at _S1_2_0x0889E9F4.exec(_S1_2_0x0889E9F4.java)
    at jpcsp.Allegrex.compiler.RuntimeContext.execWithReturnAddress(RuntimeContext.java:773)
    at jpcsp.Allegrex.compiler.RuntimeContext.runThread(RuntimeContext.java:836)
    at jpcsp.Allegrex.compiler.RuntimeThread.run(RuntimeThread.java:50)
Other games that are affected by this error are Digimon World: ReBig Grinigitize and Yu-Gi-Oh! ARC-V Tag Force Special.
Have you compiled Jpcsp yourself? If so, please try to rebuild completely the project (with Eclipse, try the menu Project/Clean...)
Always include a complete log file at INFO level in your reports. Thanks! How to post a log
Find
Reply
DragonNeos Offline
Moderator
*****
Posts: 591
Threads: 59
Joined: Dec 2011
Reputation: 3
#7
11-27-2017, 08:25 AM
I usually build JPCSP with Apache Ant using command line. Running the following command and rebuilding the emulator allows the game to work fine:
Code:
ant -f build-auto.xml cleanall

The game's performance on JPCSP is pretty bad on both graphics renderers (OpenGL/External Software Renderer) at 8-9 FPS.


Attached Files
.zip   Log_rb16aa64(64bit)_INFO.zip (Size: 206.58 KB / Downloads: 160)
Find
Reply
gid15 Offline
Dev team
**********
Posts: 2,420
Threads: 30
Joined: Dec 2009
Reputation: 50
#8
11-30-2017, 07:47 PM
(11-27-2017, 08:25 AM)DragonNeos Wrote: The game's performance on JPCSP is pretty bad on both graphics renderers (OpenGL/External Software Renderer) at 8-9 FPS.
Could you please generate a profiler using the OpenGL renderer? The external software renderer does not generate any profiler information for the graphics.
Always include a complete log file at INFO level in your reports. Thanks! How to post a log
Find
Reply
DragonNeos Offline
Moderator
*****
Posts: 591
Threads: 59
Joined: Dec 2011
Reputation: 3
#9
12-01-2017, 11:39 AM
Using revision 19b470a, after getting past the title screen, I clicked on "Reset profiler information" and waited for 10 seconds before closing the emulator.


Attached Files
.zip   Log_r19b470a(64bit)_INFO.zip (Size: 57.78 KB / Downloads: 175)
Find
Reply
gid15 Offline
Dev team
**********
Posts: 2,420
Threads: 30
Joined: Dec 2009
Reputation: 50
#10
12-01-2017, 01:53 PM
(12-01-2017, 11:39 AM)DragonNeos Wrote: Using revision 19b470a, after getting past the title screen, I clicked on "Reset profiler information" and waited for 10 seconds before closing the emulator.

Code:
GE list duration: 1195ms, average 12.6ms per GE list, max FPS is 79.5
OK, the performance is not limited by the graphics... so the limitation is from somewhere else. I see a lot of VFPU instructions in the profiler output, but that should not explain such a degradation. Does it actually run faster on a real PSP? Can you see the difference?
Always include a complete log file at INFO level in your reports. Thanks! How to post a log
Find
Reply


Forum Jump:


Users browsing this thread: 4 Guest(s)