Tales of Xillia 2 [BLJS10188]
Started by aniruddh




8 posts in this topic
aniruddh
Unregistered


 
08-09-2014, 04:46 AM -
#1
shows black screen and also loads trophies

i think the jap lines says installing trophies

log
aniruddh
Unregistered


 
08-15-2014, 03:25 PM -
#2
Tales of xilla (japanese) does the same install trophies and the same log
diari
Member


1
6 posts 1 threads Joined: Oct 2017
11-28-2017, 08:41 AM -
#3
The game is now playable / in-game

Version identifier: RPCS3 v0.0.4-6136-45aa4959 Alpha
Video demonstrating it: https://www.youtube.com/watch?v=SrYxEK1G...0s&index=1

Problems: 
1. Sound cut off and plays again randomly
2. ime-jp and/or libl10n not implemented so Tales games show no text / garbled text
3. game doesn't switch between 30 / 60 fps automatically. Real PS3 battles are 60 fps, everything else is 30 fps

Log included, because it is too big I uploaded it externally.
https://ufile.io/ulfyl (lasts 30 days)
This post was last modified: 11-29-2017, 11:08 AM by diari.
chjr1982
Member


0
14 posts 0 threads Joined: Sep 2017
11-28-2017, 10:59 AM -
#4
Yes,I saw this video,you can move to PLayable...
This post was last modified: 11-28-2017, 11:00 AM by chjr1982.
digitaldude
RPCS3 Tester


4
3,031 posts 559 threads Joined: Aug 2017
11-28-2017, 03:56 PM -
#5
Where is build name used?
Asinine
Moderator
*****


4
2,060 posts 83 threads Joined: Aug 2017
11-28-2017, 08:17 PM -
#6
Also need log file
diari
Member


1
6 posts 1 threads Joined: Oct 2017
11-29-2017, 09:50 AM -
#7
Updated with logs and version number.
Asinine
Moderator
*****


4
2,060 posts 83 threads Joined: Aug 2017
12-22-2017, 01:36 AM -
#8
That build is not master, all compatibility reports must be performed on master. also don't use services where the log will be deleted after 30 days.

If the log file is too big do the following:
Make sure you have a fresh run of the game before generating a log, if you ran a different game previously just restart rpcs3 before launching the game you are going to generate a log for.
Re-compress the log with 7-zip using the LZMA Ultra compression. If the file is too big
If all else fails: Restart the game and just play for a minute or so and then the log will be very small, however if the game does crash or exhibits some strange errors it's best to include a log of those.

In preparation for upcoming changes to the compatibility database, this thread is being moved to Ingame. Due to other threads for the same media (Disc or PSN) already being in that category.

If you find a specific game ID that performs differently than others for the same game+edition of the same format (PSN or Disc) even when tested with the same build and settings then please discuss it in the relevant thread(s) and PM a moderator so we can look into it.

Tested with: v0.0.2-6-4d2dbdb
This post was last modified: 12-22-2017, 01:43 AM by Asinine.
Ani
Administrator
*******


16
4,263 posts 105 threads Joined: Aug 2017
12-01-2020, 08:01 AM -
#9
Current commit: 2aa5c437
Requires "Vblank rate" to be changed in order to be Playable

Moving back to Ingame until this issue is solved
    Desktop: Ryzen 7 5800X,   Radeon RX 6800 XT, 2x8G DDR4 3600MHz, Manjaro Linux
     Laptop: Ryzen 9 5900HX,  Radeon RX 6700M,   2x8G DDR4 3200MHz, Manjaro Linux
Old Desktop: AMD FX-8350,     Radeon R9 280X,    2x4G DDR3 1600MHz, Manjaro Linux


Forum Jump:


Users browsing this thread: 1 Guest(s)