The Legend of Heroes: Trails of Cold Steel [BLUS31572] - Printable Version +- 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 - Playable (https://www.emunewz.net/forum/forumdisplay.php?fid=195) +----- Thread: The Legend of Heroes: Trails of Cold Steel [BLUS31572] (/showthread.php?tid=174368) |
RE: The Legend of Heroes: Trails of Cold Steel [BLUS31572] - Green - 07-25-2017 https://github.com/RPCS3/rpcs3/pull/3075 The 'fbo check failed' log spam is still present as of 1bef748. Code: E {rsx::thread} RSX: FBO check failed: 0x8cd6 x1272 I haven't encountered the 'MEM: Access violation' for over the past week. (The game will run for at least three hours.) RE: The Legend of Heroes: Trails of Cold Steel [BLUS31572] - BLACKSAMA - 07-25-2017 (07-25-2017, 12:23 AM)Green Wrote: https://github.com/RPCS3/rpcs3/pull/3075 Mem error still present as of https://github.com/RPCS3/rpcs3/pull/3070 unfortunately . E {rsx::thread} RSX: FBO check failed: 0x8cd6 x5070 spam still present sadly, this game is extremely buggy but is improving I think, I doubt any developer has the game though so this may take a long while to fix. RE: The Legend of Heroes: Trails of Cold Steel [BLUS31572] - Green - 07-25-2017 (07-25-2017, 01:08 AM)BLACKSAMA Wrote:I still get crackling sound issues after a while, and bad or incorrectly called for textures.(07-25-2017, 12:23 AM)Green Wrote: https://github.com/RPCS3/rpcs3/pull/3075 I can't tell if my poker face is showing. RPCS3.log.7z (Size: 1.43 MB / Downloads: 134) RE: The Legend of Heroes: Trails of Cold Steel [BLUS31572] - BLACKSAMA - 07-26-2017 The second game behaves exactly the same fully playable at full speed but after a while there is graphic corruption everywhere . Is funny how a graphic can end up replacing another like Rean face can end up being made of Rean faces. Edit: Resized Image RE: The Legend of Heroes: Trails of Cold Steel [BLUS31572] - Jhon1234 - 07-26-2017 I have the game with all dlc but with many bugs game is not fun to play at all. Going buy the pc version next month to play smoothly. RE: The Legend of Heroes: Trails of Cold Steel [BLUS31572] - Green - 07-27-2017 (07-26-2017, 08:24 PM)Jhon1234 Wrote: I have the game with all dlc but with many bugs game is not fun to play at all.The PC version will still be worth the buy. You'll be missing out on the RPCS3 extra special non-PC features though. Like when was the last time that anyone had played a game anywhere that had the village noble children run around to terrorize everyone while dressed in blackface? RE: The Legend of Heroes: Trails of Cold Steel [BLUS31572] - BLACKSAMA - 07-28-2017 Yea face disfigured Rean, never fails to give me a scare, is almost Meme material RE: The Legend of Heroes: Trails of Cold Steel [BLUS31572] - gin99 - 07-28-2017 Can somebody help me? When i try boot game it show me massage: E LDR: SELF: Failed to decrypt metadata info! E LDR: SELF: Failed to load SELF file metadata! F LDR: class std::logic_error thrown: fs::file is null S LDR: Boot from gamelist per Boot: done what i should do? RE: The Legend of Heroes: Trails of Cold Steel [BLUS31572] - Annie - 07-28-2017 (07-28-2017, 11:49 AM)gin99 Wrote: Can somebody help me? https://github.com/RPCS3/rpcs3/wiki/How-to-ask-for-Support RE: The Legend of Heroes: Trails of Cold Steel [BLUS31572] - BLACKSAMA - 07-30-2017 The new version is showing a different error, is this a regression? never seen that error before: F {rsx::thread} class gl::glsl::link_exception thrown: linkage failed: 'Vertex info ----------- 0(38) : error C0000: syntax error, unexpected '.', expecting ')' at token "." 0(39) : error C0000: syntax error, unexpected '.', expecting "::" at token "." (0) : error C2003: incompatible options for link I am not sure if this is the same mem error we had before but now is getting a more explanation from log or is a brand new error. |