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
Atelier Rorona Plus The Alchemist of Arland [BLES02050]
#61
Maybe that's a stupid question, but did your game install correctly? I've found that whenever I have missing textures (including Atelier games in particular) it means some files are actually missing. So I just copy everything over manually, and the problem is solved! I don't know why, but games don't install fully via rpcs3...

And I have frequent crashing, too, in two of Atelier games I've checked (Totori and Ayesha) in OpenGL and Vulkan. No DirectX12 here. The cause is probably the same for us, but I've found that in older builds (early April) there's no crashing.
Reply
#62
It would be *really* helpful if you can narrow down which build broke the game:
https://rpcs3.net/compatibility?b
Asus N55SF, i7-2670QM (~2,8 ghz under typical load), GeForce GT 555M (only OpenGL)
Reply
#63
is it still has problem with PPU LLVM in the middle of the game?
Reply
#64
So, I tested this game on 5446 using Vulcan and compared to an earlier build (early june don't remember the exact version) it got much better. Before I got random crashes every 10 minutes, with an occasional driver crashes.
With the 5446 build random crashes are almost gone, I think I got 2 or 3 during an 8 hours of testing, and I think at lest one was "my fault" I accidentally dc'ed the gamepad, and the game crashed.

Unfortunately there are some "reliable" crashes still. The game reliably crashes at system menu. You go to the system menu and the game will crash usually within a minute or two, sometimes sooner. The same issue persists in the synthesis menu. You don't even need to do anything specific, just open the menu and the game will eventually crash.
Other ingame menus do not have this issue, it is only synthesis and system menus, but it happens very reliably

EDIT: Just tested it with the latest v 0.0.3-5541-c69a05d6 build. Crashes at the synthesis menu are still there. When the game crashes it often gives errors like :
F {PPU[0x1000000] Thread (main_thread) [0x003a9d34]} MEM: Access violation reading location 0x3c3
F {PPU[0x1000000] Thread (main_thread) [0x003a9d34]} MEM: Access violation reading location 0x7
F {PPU[0x1000000] Thread (main_thread) [0x00243a98]} MEM: Access violation reading location 0x3c800090
Reply
#65
5470-bd7c158a

Couldn't replicate any of these crashes. Fooled around in both the synthesis and options menus for some 15 minutes, everything was fine.


Attached Files
.7z   RPCS3.7Z (Size: 134.67 KB / Downloads: 150)
Intel i5-4440 (3.1 GHz), 8GB DDR3-1600, GTX 650 Ti 1GB, Windows 10 Home
Reply
#66
Maybe it was fixed together with Demon's Souls. Try the very latest master build from https://rpcs3.net/download
Asus N55SF, i7-2670QM (~2,8 ghz under typical load), GeForce GT 555M (only OpenGL)
Reply
#67
((Test on RPCS3 v0.0.3-3-bc4d73d Alpha))

-------------------
Recompiler(LLVM) & Recompiler(ASMJIT)
Better in Vulkan
Setting
   
--------------------
The Video


Speed : full (30 FPS)
Movie : Perfect Work
Graphic : Work... But backgrounds is missing in dialogue Screen
Music : Perfect Work

The Log File:-

.rar   BLES02050 - [Atelier Rorona Plus The Alchemist of Arland Plus].rar (Size: 227.34 KB / Downloads: 79)
___________________________________
CPU:- Intel I7-6800K @ 3.40 GHz (OverClock 4.5 GHz)
GPU:- GTX 1080
Motherboards:- ASUS X-99A-II
RAM:- 32.0 GB (2666 MHz)
Reply
#68
I have tried to do something with missing backgrounds in dialog screens and what I've found:
1. You CAN see backgrounds in a couple of cases:
a. In OpenGL mode.
b. In Vulkan mode with both "Write Color Buffers" and "Strict Rendering Mode" options enabled.
2. The backgrounds still not very good: they are reduced in size on a half (see a screenshot).
3. With "Write Color Buffers" option enabled game runs too slowly (15 fps instead of 60 without this option).


Attached Files Thumbnail(s)
   
Reply
#69
In my first try i got a crash in the opening video. Booted again and passed the cutscene without skipping, then in another cutscene there's no bg and I found this flickering here:




(edit: the opening video is really slow, 13fps and some stuttering as well)

Specs and Settings:
RPCS3 V0.0.3-5624-728bd7dd Alpha
____________________________

CPU
____________________________
PPU Decoder: Recompiler (LLMV)
SPU Decoder: Recompiler (ASMJIT)
*Enable SPU loop Detection
____________________________

GPU
____________________________
Renderer: Vulkan
Resolution: 1920x1080
Framelimit: Off
*Invalidate Cache Every Frame
*Use GPU Texture Scaling
*Strict Rendering Mode
____________________________
CPU: i7-7700
GPU: Radeon R9 270X
RAM: 8Gb DDR4 HyperX 2666Ghz
____________________________


Attached Files
.7z   RPCS3.7z (Size: 891.98 KB / Downloads: 101)
i7-7700 3,6Ghz | Radeon R9 270X | 8Gb RAM HyperX 2666MHz | Asus PRIME B250M PLUS
Reply
#70
This game is not playable for me. In Vulkan or OpenGL, I can go in-game and walk around the town, but try synthesis cause crashes:

Tested in two builds: 0.0.3-2017-07-26-00066a3a and 0.0.3-2017-08-15-7f7aecfa

0.0.3-2017-07-26-00066a3a (OpenGL)
F {PPU[0x1000000] Thread (main_thread) [0x004dc858]} MEM: Access violation reading location 0xc2

F {PPU[0x1000000] Thread (main_thread) [0x003a9ec8]} MEM: Access violation reading location 0xd8

0.0.3-2017-07-26-00066a3a (Vulkan)
F {PPU[0x1000000] Thread (main_thread) [0x003a9ec8]} MEM: Access violation reading location 0x3c800090

F {PPU[0x1000000] Thread (main_thread) [0x00243a98]} MEM: Access violation reading location 0x0

0.0.3-2017-08-15-7f7aecfa (OpenGL - more stable, but just made it random)
F {PPU[0x1000000] Thread (main_thread) [0x00062b3c]} MEM: Access violation reading location 0x3c800090

F {PPU[0x1000000] Thread (main_thread) [0x003a9ec8]} MEM: Access violation reading location 0x0

0.0.3-2017-08-15-7f7aecfa (Vulkan)
E {PPU[0x1000000] Thread (main_thread) [0x0043d9b8]} Stat: 'sys_lwmutex_lock' failed with 0x80010005 : CELL_ESRCH [x14]
E {PPU[0x1000000] Thread (main_thread) [0x0043d9b8]} Stat: 'sys_lwmutex_unlock' failed with 0x80010009 : CELL_EPERM [x14]
E {PPU[0x1000018] Thread (_sys_MixerChStripMain) [0x0048f1f4]} Stat: 'sys_lwmutex_lock' failed with 0x80010005 : CELL_ESRCH [x78144]
E {PPU[0x1000018] Thread (_sys_MixerChStripMain) [0x0048f1f4]} Stat: 'sys_lwmutex_unlock' failed with 0x80010009 : CELL_EPERM [x78144]
E {PPU[0x100001a] Thread (_cellsurMixerMain) [0x0048ae10]} Stat: 'sys_mutex_lock' failed with 0x80010008 : CELL_EDEADLK [x9768]
E {PPU[0x1000024] Thread (KtslAt3Decoder) [0x004d7d14]} Stat: 'sys_lwmutex_lock' failed with 0x80010008 : CELL_EDEADLK [x4]
E {PPU[0x1000024] Thread (KtslAt3Decoder) [0x004d7d14]} Stat: 'sys_lwmutex_unlock' failed with 0x80010009 : CELL_EPERM [x4]
E {PPU[0x1000027] Thread (KtslAt3Decoder) [0x004d7d14]} Stat: 'sys_lwmutex_lock' failed with 0x80010008 : CELL_EDEADLK [x4]
E {PPU[0x1000027] Thread (KtslAt3Decoder) [0x004d7d14]} Stat: 'sys_lwmutex_unlock' failed with 0x80010009 : CELL_EPERM [x4]
E {PPU[0x100001b] Thread (KtslSeDriver) [0x004c46ec]} Stat: 'sys_lwmutex_lock' failed with 0x80010008 : CELL_EDEADLK [x44]
E {PPU[0x100001b] Thread (KtslSeDriver) [0x004c46ec]} Stat: 'sys_lwmutex_unlock' failed with 0x80010009 : CELL_EPERM [x44]

E {PPU[0x1000018] Thread (_sys_MixerChStripMain) [0x0048f1f4]} Stat: 'sys_lwmutex_lock' failed with 0x80010005 : CELL_ESRCH [x41088]
E {PPU[0x1000024] Thread (KtslAt3Decoder) [0x004d7d14]} Stat: 'sys_lwmutex_lock' failed with 0x80010008 : CELL_EDEADLK [x4]
E {PPU[0x1000024] Thread (KtslAt3Decoder) [0x004d7d14]} Stat: 'sys_lwmutex_unlock' failed with 0x80010009 : CELL_EPERM [x4]
E {PPU[0x1000027] Thread (KtslAt3Decoder) [0x004d7994]} Stat: 'sys_lwmutex_lock' failed with 0x80010008 : CELL_EDEADLK [x7]
E {PPU[0x1000027] Thread (KtslAt3Decoder) [0x004d7994]} Stat: 'sys_lwmutex_unlock' failed with 0x80010009 : CELL_EPERM [x7]
E {PPU[0x1000000] Thread (main_thread) [0x0043d9b8]} Stat: 'sys_lwmutex_lock' failed with 0x80010005 : CELL_ESRCH [x14]
E {PPU[0x1000000] Thread (main_thread) [0x0043d9b8]} Stat: 'sys_lwmutex_unlock' failed with 0x80010009 : CELL_EPERM [x14]
E {PPU[0x1000018] Thread (_sys_MixerChStripMain) [0x0048f1f4]} Stat: 'sys_lwmutex_unlock' failed with 0x80010009 : CELL_EPERM [x41088]
E {PPU[0x100001a] Thread (_cellsurMixerMain) [0x0048ae10]} Stat: 'sys_mutex_lock' failed with 0x80010008 : CELL_EDEADLK [x5136]
E {PPU[0x100001b] Thread (KtslSeDriver) [0x004c46ec]} Stat: 'sys_lwmutex_lock' failed with 0x80010008 : CELL_EDEADLK [x25]
E {PPU[0x100001b] Thread (KtslSeDriver) [0x004c46ec]} Stat: 'sys_lwmutex_unlock' failed with 0x80010009 : CELL_EPERM [x25]
Reply


Forum Jump:


Users browsing this thread: 4 Guest(s)