RPCS3 Forums

rpcs3-v0.0.1-2017-02-25-d0afef47_win64

RPCS3 v0.0.4-6223-a1fa10ac Alpha | HEAD
PPU (LLVM):

Quote:·F 0:19:35.970968 {PPU[0x1000006] Thread (Miles Thread) [0x00e90430]} class std::runtime_error thrown: Unregistered PPU function

PPU (fast):

Quote:·F 0:00:07.039130 {PPU[0x1000000] Thread (main_thread) [0x012f9b18]} class std::runtime_error thrown: cellGameContentPermit(): epic fail: directory '/dev_hdd0/game/BLES01478' already exists

RPCS3 v0.0.5-6494-ec0cd9f00 Alpha
Ingame. Requires PPU Interpreter fast and you must delete rpcs3\dev_hdd0\game\BLES01478 folder on each launch.

Same status as the base game.

RPCS3 v0.0.10-10450-26b2e425 Alpha 

nearly 4 hours gameplay in total and no issues so far.

https://youtu.be/_UEhLFfsAh4

System:
CPU Ryzen 5 3600 4,2ghz
GPU: Gigabyte GTX 1070ti
RAM: 16gb DDR4 2800mhz
SSD: 960gb SanDisk Ultra II
HHD: 1TB SG, 2TB Thosiba
MOBO: GA-AB350-Gaming 3

I played about 3 hours and got to the strip to get the chip back from Benny and met with Ambassador Crocket. I encountered a bug that the game stopped saving after exiting the Strip for some reason. I walked all the way to the Nellis AFB and dodged the bombs from the Boomers and talked to Pearl but noticed the message for saving when entering and leaving cells had stopped appearing. I tried to load the save menu, but it just faded to gray but no menu appeared. After that, Save and Load were grayed out, at which point I stopped playing. Because I Had been playing for over 2 hours, the log is absolutely massive. I have uploaded it to Mega.

Aside from the save issue, there seems to be a problem with interior cells. Sometimes they're perfectly fine, sometimes they're a starburst mess. I have included screenshots of some of the interior cells. Since I have well over 1000 hours on the PC version of this game, I could navigate some of the interior cells by memory and everything is still there, it just looks awful. The weird behavior of the game even still occurs when you enter the building of Nipton and the landmines under the body always activate for no reason.

All that being said, I think this game should be upgraded from Ingame to Playable, as I feel you could beat the game in its current state.

The behaviour you described is anything but Playable, the game is correctly in the Ingame status

(07-03-2023, 10:39 AM)Ani Wrote: [ -> ]The behaviour you described is anything but Playable, the game is correctly in the Ingame status

Sorry, yes, as any other game, yes that would be true. However, I suspect you are not familiar with this game or Bethesda games, as the "bugs" I have described are actually quite menial compared to how the game actually plays on real PS3 hardware. You can find numerous anecdotal cases of people complaining about crashes, UI issues and even complete destruction of their PS3 hard drive from this game. That's just the charm a Bethesda game brings. The amount of modding on the PC to bring this game to a playable state requires 6 separate DLL injected mods and 10 ESP (Elder Scrolls Plugin) mods, one of which is over 200MBs of just ESP entries of fixing broken quests/dialog.

Is the PS3 version of Fallout 3 unplayable? - Arqade (stackexchange.com)

Quote:I think I put about 40 hours in to Fallout 3 on the PS3 (not the GOTY edition) - finished the main storyline, plus a bunch of side missions and random wandering. The game froze and required a hard reset of the PS3 about 3 or 4 times, and I got stuck on scenery once which required me to go back to my last save. So that's about one reload every 8 hours of play time.

While it's probably the buggiest PS3 game I've played, I wouldn't call it "unplayable", just annoying. I really enjoyed playing it and I think it's worth putting up with the bugs.

Quote:It still has bugs, even on the PS3 GOTY edition.

The biggest problem with PS3 Fallout (and Fallout New Vegas) is that you have no access to the console (pressing the backquote "`" key) to correct any game breaking bugs that occur. The only recourse is to go back to an earlier save game.

You also do not have access to mods or cheats, which may be important to you.

My seat of the pants impression, having played both the PS3 and PC versions is that the PC version is more buggy, possibly because of my PC configuration, but any quest bugs are correctible via console commands. Furthermore after completion I can play with the console to spawn items and adjust statistics for fun and to try out different things.

Fallout: New Vegas bugs | Fallout Wiki | Fandom.

Quote:(PS3)Excessive save games in memory may cause crashes
(All Platforms) Sometimes when trying to continue or load the game from the main menu, the game will begin loading, but stays loading forever. Slides will still change, and the roulette wheel will still spin, but the game never actually loads - tested up to 25 minutes. For PS3 users, the only option when this occurs is to force close and restart the game.

Now, the only thing I really see that isn't included with the original game is the interior cells exploding into starburst patterns. However, like I said, it's extremely tolerable, nowhere near game breaking. I'm 99% certain that save issue I encountered is just Fallout being just a very well programmed game.

---

OK so the starburst problem seems to have been causing by setting the Resolution Scale Threshold too high. I set it back to default and it doesn't do it anymore, so that's cool. I played the game for about 6 hours last night and didn't run into a single problem, besides stuff like my gun disappearing and characters floating in the air, you know typical FONV crap.

Anyway, I ported my PC trainer to the patch system. If you'd like to incorporate it into the official patch list that'd be cool. There's already a list of cheats by one of the testers named Aphelion. The offsets he found are also the same for the BLES01475 (EU) and BLES01478 (German) version of the game. I checked the EBOOT.BIN and compared the offsets in memory, and they appear to be the same. However, I couldn't find the other versions listed on redump.org for the like French/Spanish/Italian versions, however, I suspect they are also the same. The way the PC version handles localization is that it just overwrites the main ESM packages with the text and voice data needed for the translation, the main EXE stays the same. It's highly likely the PS3 version does the same exact thing. 

Here is the patch list for my trainer.