Fallout 3 [BLES00400] - Printable Version

Fallout 3 [BLES00400] - Printable Version

+- RPCS3 Forums (https://forums.rpcs3.net)
+-- Forum: PS3 Commercial Games (https://forums.rpcs3.net/forumdisplay.php?fid=4)
+--- Forum: Ingame (https://forums.rpcs3.net/forumdisplay.php?fid=6)
+--- Thread: Fallout 3 [BLES00400] (/showthread.php?tid=179895)

RE: 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] - Blast Processing - 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] - Ani - 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...

RE: Fallout 3 [BLES00400] - GrantKane - 11-20-2017

RPCS3 v0.0.4-6095-222c0e0f Alpha | HEAD

Quote:·F 0:12:36.692132 {PPU[0x1000005] Thread (Miles Thread) [0x010aaa50]} class std::runtime_error thrown: Unregistered PPU function

RE: Fallout 3 [BLES00400] - digitaldude - 11-20-2017

Try using ppu fast instead of llvm, it doesnt go ingame with llvm.

RE: Fallout 3 [BLES00400] - GrantKane - 11-20-2017

RPCS3 v0.0.4-6107-380f90b0 Alpha | HEAD
Ingame with PPU fast.
[Image: AwQLerN.jpg]