+- EmuNewz Network (https://www.emunewz.net/forum)
+-- Forum: Official Boards for Emunews Affiliated Emu Projects (https://www.emunewz.net/forum/forumdisplay.php?fid=47)
+--- Forum: Official RPCS3 Forum [archive] (https://www.emunewz.net/forum/forumdisplay.php?fid=172)
+---- Forum: RPCS3 - Commercial Games (https://www.emunewz.net/forum/forumdisplay.php?fid=193)
+----- Forum: RPCS3 - Commercial Games - Nothing (https://www.emunewz.net/forum/forumdisplay.php?fid=227)
+----- Thread: Dragons Crown [NPEB01836] (/showthread.php?tid=160047)
Dragons Crown [NPEB01836] - Ekaseo - 04-04-2014
when i try to run this game, my entire computer freezes, it may be that i dont have enough power to even run it, so im just reporting it and if someone with a better rig tries it and it still freezes, then its a problem of the emu
RE: Dragons Crown NPEB01836 - ssshadow - 04-04-2014
Can you disable logging and try again?
RE: Dragons Crown NPEB01836 - Ekaseo - 04-04-2014
(04-04-2014, 05:37 PM)ssshadow Wrote: Can you disable logging and try again?
i had it disabled
RE: Dragons Crown NPEB01836 - ssshadow - 04-04-2014
I guess this game causes a memory leak...
(Disregarding this little issue, the game still needs spurs
)![[Image: XIjskFX.png]](http://i.imgur.com/XIjskFX.png)
RE: Dragons Crown NPEB01836 - Gundark - 04-04-2014
Different region. For a 2d game awful lot of unimplemented stuff, and after white frame stuck in a loop.
Dragon's Crown [BLUS30767] .rar (Size: 7.11 KB / Downloads: 214)
RE: Dragons Crown [NPEB01836] - Annie - 07-08-2016
Build: 71b21fe
LLE: fiber, resc, spurs_jq, sre, sync2
The game freezes the OS for a few seconds before opening itself
GSFrame opens, throws the following exception:
Code:
·F {PPU[0x6] Thread (main_thread) [0x39800000]} struct vm::access_violation thrown: Access violation reading address 0x39800000
·! {PPU[0x6] Thread (main_thread) [0x39800000]} Thread time: 19.039394 GcRE: Dragons Crown [NPEB01836] - shinox - 12-13-2016
Any fixes yet ?
RE: Dragons Crown [NPEB01836] - KoDa - 05-25-2017
The memory leak issue still persists and takes up over 3Gb of RAM for several seconds, but calms down to 500Mb shortly after. I cannot post the full log because the log is over 200 Mb. Since I can't show the original thing, I cut it down in another version that shows everything except the over 2 million lines of the same code, which is this:
·W 0:00:03.767557 {PPU[0x1000000] Thread (main_thread) [0x00d48130]} cellSysutil: cellVideoOutGetResolutionAvailability(videoOut=0, resolutionId=0x2, aspect=2, option=0)
·W 0:00:03.767563 {PPU[0x1000000] Thread (main_thread) [0x00d48130]} cellSysutil: cellVideoOutGetResolutionAvailability(videoOut=0, resolutionId=0x5, aspect=2, option=0)
·W 0:00:03.767568 {PPU[0x1000000] Thread (main_thread) [0x00d48130]} cellSysutil: cellVideoOutGetResolutionAvailability(videoOut=0, resolutionId=0x5, aspect=1, option=0)
·W 0:00:03.767574 {PPU[0x1000000] Thread (main_thread) [0x00d48130]} cellSysutil: cellVideoOutGetResolutionAvailability(videoOut=0, resolutionId=0x4, aspect=2, option=0)
·W 0:00:03.767579 {PPU[0x1000000] Thread (main_thread) [0x00d48130]} cellSysutil: cellVideoOutGetResolutionAvailability(videoOut=0, resolutionId=0x4, aspect=1, option=0)
In the attached zip file is the edited down version of the log, some images of what happened and so on.
Hope this helps.
*NOTE* - Not all the lines are actually the same, they carry minor differences each line.