+- RPCS3 Forums (https://forums.rpcs3.net)
+-- Forum: PS3 Commercial Games (https://forums.rpcs3.net/forumdisplay.php?fid=4)
+--- Forum: Playable (https://forums.rpcs3.net/forumdisplay.php?fid=5)
+--- Thread: Peggle [NPUA30005] (/showthread.php?tid=158956)
RE: Peggle [NPUA30005] - jacky400 - 06-18-2014
If you see in RSX debugger , the image is correct and we flipped them.
[raven02]
RE: Peggle [NPUA30005] - Ani - 07-31-2016
Doesn't boot in latest master (190fc43)
LLE: libsysutil_np_trophy
F {PPU[0x2] Thread (main_thread) [0x00c42ce4]} class fmt::exception thrown: cellSysutilRegisterCallbackDispatcher():
(in file C:\rpcs3\rpcs3\Emu\Cell\Modules\cellSysutil.cpp:387)
Without LLE it finds an access violation and also doesn't boot.
RE: Peggle [NPUA30005] - flashmozzg - 08-01-2016
(07-31-2016, 04:47 PM)Annie Wrote: Doesn't boot in latest master (190fc43)
LLE: libsysutil_np_trophy
F {PPU[0x2] Thread (main_thread) [0x00c42ce4]} class fmt::exception thrown: cellSysutilRegisterCallbackDispatcher():
(in file C:\rpcs3\rpcs3\Emu\Cell\Modules\cellSysutil.cpp:387)
Without LLE it finds an access violation and also doesn't boot.
I think libsysutil_np_trophy can't be LLEd atm.
RE: Peggle [NPUA30005] - Etokapa - 05-28-2017
RPCS3 Version:
0.0.2-3-83ffd7c Alpha | 19 May, 2017 | FW 4.81
Specs:
i7-4770 | GTX 1080 | 32GB DDR3 | Windows 10 x64
Status:
Nothing
Settings:
Core
--Automatically load required libraries
Graphics
--1280x720
--16x9
--Frame limit Off
--Use GPU texture scaling
Audio
--XAudio2
Input/Output
--XInput (Using an official PS3 controller with SCPToolkit drivers)
Tested on 3 combinations of the Renderer, PPU, and SPU configurations. Not sure if problem is related to the icon issue or something else.
OPENGL
OGL+Int(f)+Int(p): Can't boot. White Screen. Stuck on E {PPU[0x1000000] Thread (main_thread) [0x00c46090]} 'sys_fs_open' failed with 0x80010006 : CELL_ENOENT. RPCS3 does not respond and crashes when Stop is pressed.
OGL+Int(f)+Int(f): Can't boot. White Screen. Stuck on E {PPU[0x1000000] Thread (main_thread) [0x00c46090]} 'sys_fs_open' failed with 0x80010006 : CELL_ENOENT RPCS3 does not respond and crashes when Stop is pressed.
OGL+Int(f)+Rec(ASMJIT): Can't boot. White Screen. Stuck on E {PPU[0x1000000] Thread (main_thread) [0x00c46090]} 'sys_fs_open' failed with 0x80010006 : CELL_ENOENT RPCS3 does not respond and crashes when Stop is pressed.
RE: Peggle [NPUA30005] - money123451 - 11-13-2017
someone needs to retest this nickz on the old forum post on this game had some screen shots that looked the same as what heavy weapon at that time and heavy weapon now goes ingame so its in need of a retest.
RE: Peggle [NPUA30005] - Asinine - 11-14-2017
This is nothing for me and has been for awhile:
U {PPU[0x1000000] Thread (main_thread) [0x00c42530]} sceNp TODO: sceNpBasicRegisterContextSensitiveHandler
U {PPU[0x1000000] Thread (main_thread) [0x00c42888]} sceNp TODO: sceNpManagerGetNpId(npId=*0x200a2f5c)
E {PPU[0x1000000] Thread (main_thread) [0x00c3d018]} sceNpTrophy: sceNpTrophyRegisterContext(context=0x1, handle=0x1, statusCb=*0x9ca920, arg=*0x0, options=0x0)
F {PPU[0x1000000] Thread (main_thread) [0x0044e830]} MEM: Access violation reading location 0x4e9
RE: Peggle [NPUA30005] - Asinine - 12-03-2017
RPCS3 v0.0.4-6200-8f314c51 Alpha still nothing.
RE: Peggle [NPUA30005] - digitaldude - 01-20-2018
rpcs3-v0.0.4-2018-01-19-49e64b9e_win64
Playable.
RE: Peggle [NPUA30005] - legend80 - 01-21-2018
Full version cannot be accessed. With the EDAT file in the EXDATA dir and changed to .rap extension (this is what you do for C00 titles), you get an error trying to boot:
F {PPU[0x1000000] Thread (main_thread) [0x00446484]} MEM: Access violation reading location 0x4e9
(even on PPU Interpreter)
Note:
Framelimitor OFF will prevent proper menu controls.
OpenGL gets rid of some flickering.
RE: Peggle [NPUA30005] - legend80 - 03-17-2018
Can anyone confirm that the full version is not working? Even on today's build, no change.
Just get this immediately on launch with the full version rap/edat:
F {PPU[0x1000000] Thread (main_thread) [0x00446410]} MEM: Access violation reading location 0x4e9
Trial is fine. If the full version can just boot, it looks like it'll be perfect!