Fallout 3 [BLES00400] - 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 - Nothing (https://www.emunewz.net/forum/forumdisplay.php?fid=227) +----- Thread: Fallout 3 [BLES00400] (/showthread.php?tid=179895) |
Fallout 3 [BLES00400] - GrantKane - 03-01-2017 RPCS3 v0.0.1-3-01ef9ec Pre-Alpha Quote:·F 0:00:07.012338 {PPU[0x1000000] Thread (main_thread) [0x0086ffdc]} struct vm::access_violation thrown: Access violation writing address 0x40000000 RE: Fallout 3 [BLES00400] - blastprocessing - 03-23-2017 Don't change this to in-game yet, using a hacked build. Just wanted to show off what it looks like in the emulator. RE: Fallout 3 [BLES00400] - Annie - 03-23-2017 Just a reminder we don't take results from hacked builds unless the hack is something that is not intrusive and can easily be properly fixed. One has to list the used hacks for those to be checked and taken or not in account RE: Fallout 3 [BLES00400] - ssshadow - 03-25-2017 Depends. Who hacked what? If it is WIP stuff by say kd-11 it's ok I think. If it is someone just removing exceptions and hoping for the best however... |