12-25-2015, 10:50 AM (This post was last modified: 12-25-2015, 10:54 AM by tambre.)
Hi, just tested this with the newest build right now and i got ingame. Well its just a black screen, but whats interesting is that sound works and pause menu works. The main menu sort of works too, but its not readable. there is one unsupported color format that this game needs in order to display the menu properly. Ingame i can hear steps and fire burning.
Settings:
OpenGL
1280x720
PPU int 2 + SPU recompiler
(12-26-2015, 01:00 AM)ssshadow Wrote: Can someone test on DX12? This game is on a completely different level to what usually runs.
noone even cares to download the log file to take a look at it, huh...
As a precaution, could you try running only Tales of Xillia in a single session? Though mostly fixed, there might still be inconsistencies, when run many games in one session.
(12-26-2015, 01:00 AM)ssshadow Wrote: Can someone test on DX12? This game is on a completely different level to what usually runs.
noone even cares to download the log file to take a look at it, huh...
As a precaution, could you try running only Tales of Xillia in a single session? Though mostly fixed, there might still be inconsistencies, when run many games in one session.
I only runned this one game, always displays the same stuff, so there should be no inconsistecies
(12-26-2015, 01:00 AM)ssshadow Wrote: Can someone test on DX12? This game is on a completely different level to what usually runs.
noone even cares to download the log file to take a look at it, huh...
As a precaution, could you try running only Tales of Xillia in a single session? Though mostly fixed, there might still be inconsistencies, when run many games in one session.
I only runned this one game, always displays the same stuff, so there should be no inconsistecies
After taking a second look, the log indicates that you start the game "PixelJunk™ Monsters" two times. Are you sure you posted the right log?
Yes, it was the wrong log file... but its strange, since when did the log file name got changed? its now in "program.log" ... well, either way, here it is:
09-10-2016, 10:46 PM (This post was last modified: 09-10-2016, 10:47 PM by ssshadow.)
Maybe it looks a bit less broken now, but on OpenGL it quickly crashes with some explicit error messages. I have redacted an endless spam of "·E {PPU[0x70000000] Thread (main_thread) [0x010b1874]} sys_memory: sys_memory_get_page_attribute(addr=0xd000f510, attr=*0xd000f470)" and similar from the log.