Dragons Crown [NPEB01836]
|
04-04-2014, 04:58 PM
(This post was last modified: 07-27-2015 02:10 PM by tambre.)
Post: #1
|
|||
|
|||
Dragons Crown [NPEB01836]
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
![]() ![]() |
|||
04-04-2014, 05:37 PM
Post: #2
|
|||
|
|||
RE: Dragons Crown NPEB01836
Can you disable logging and try again?
Asus N55SF, i7-2670QM (~2,8 ghz under typical load), GeForce GT 555M (only OpenGL) |
|||
04-04-2014, 05:39 PM
Post: #3
|
|||
|
|||
RE: Dragons Crown NPEB01836
![]() ![]() |
|||
04-04-2014, 06:36 PM
(This post was last modified: 04-04-2014 06:37 PM by ssshadow.)
Post: #4
|
|||
|
|||
RE: Dragons Crown NPEB01836
I guess this game causes a memory leak...
(Disregarding this little issue, the game still needs spurs ![]() ![]() Asus N55SF, i7-2670QM (~2,8 ghz under typical load), GeForce GT 555M (only OpenGL) |
|||
04-04-2014, 07:33 PM
Post: #5
|
|||
|
|||
RE: Dragons Crown NPEB01836
Different region. For a 2d game awful lot of unimplemented stuff, and after white frame stuck in a loop.
![]() |
|||
07-08-2016, 05:48 PM
Post: #6
|
|||
|
|||
RE: Dragons Crown [NPEB01836]
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 Desktop: Ryzen 7 5800X, Radeon RX 6800 XT, 2x8G 3600MHz, Manjaro Linux Laptop: Intel i7 6700HQ, Intel HD 530, 2x8G 2133MHz, Manjaro Linux Old Desktop: FX-8350, R9 280X, 2x4G 1600MHz, Manjaro Linux |
|||
12-13-2016, 02:41 AM
Post: #7
|
|||
|
|||
RE: Dragons Crown [NPEB01836]
Any fixes yet ?
|
|||
05-25-2017, 10:01 PM
Post: #8
|
|||
|
|||
RE: Dragons Crown [NPEB01836]
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. |
|||
« Next Oldest | Next Newest »
|
User(s) browsing this thread: 1 Guest(s)