I believe we talked on Discord, but I'll post here just in case anyone else is wondering.
I'm not currently aware of any way to fix random crashes with the base game. Crashes aren't generally a trivial thing that can just be "fixed" unless exactly what causes them is determined and is realistically fixable. Unfortunately, Fable is generally very particular about the underlying system in ways that problems that often occur on one setup under certain conditions may be impossible to duplicate on another setup, and the actual cause is never determined (for example, the "ghost town Oakvale" glitch found by Budget, among many other things).
For documentation's sake, it sounds like your crashes were occurring most frequently during the Orchard Farm quest and only happened when the camera was moved; you were using a mouse and on Windows 11, playing in fullscreen with maxed graphical settings at 1920x1080 on a fully vanilla French copy of the game. Compatibility mode and disabling in-game overlay in Steam still resulted in crashes. While I can't provide any sort of solution right now, I do want to have this all down just in case someone else has a similar issue so that we can maybe determine the cause through further diagnosis. For what it's worth, this is not a sort of crash that I have personally experienced on any setups, across multiple hardware configurations and operating systems, although I have yet to use Windows 11 with Fable.
Everything fixed is listed in the description, and there's been no work an audio. As far as I'm aware, that sounds like a system/setup issue. Fable TLC does support spacial audio, but I believe only Anniversary got proper surround sound support.
Please tell me if the Demon Door at the Abandoned Road will open with this patch instaled, if you wear a Dark Will User's Outfit without the Dark Wizard Hat? (If you have a way to check it to 100% confirm it, that would be great.)
Because that door requies the full Dark Will Set, and this patch is said to include the Dark Wizard Hat into the set.
I was about to play the game and was worried if I can get the door open, if I choose to get a Bright Wizard Hat during the Book Collection quest.
I don't believe so. Suits are basically just templates and nothing really reads them to my understanding. To be honest, I haven't tested this specifically, and I don't know when I'll have the time to do so, but I'll report back any findings.
Well, yes, if the door only checks for the four specific parts of the suit and doesn't check for the actual "pointer to the suit"/template of the suit, then it should be no issue.
Eventually would be great to verify it, as this patch got an update when some other bug was found with a demon door not possible to open (compared to unmodified game) under normal circumstances. It's a similar case.
The entire point of the Frying Pan is that is has the extra enhancement slot... You broke something that wasn't a bug. Any chance of a version without your Frying Pan "Fix"?
The UI only shows 4 slots, and you can only give it 5 augmentations if you do so all at once. You can't give it 5 if you go out of the menu and back in. This is a bug. Believe me, I try to avoid opinionated changes.
That's fair. I know I'm patching out some things people like based on technicality. If there's enough demand, I can create an optional patch that undoes the Frying Pan change. Anyone else can also do it themselves. I don't want this to become Fable's dreaded, overreaching USSEP. But I am going to patch the bugs that I can fix, and the Frying Pan technically is bugged as the menu is hardcoded to check if there are 4 augments when opened to determine if another augmentation can be used, and the UI can only show 4. So 5 augmentation slots is nothing but an oversight.
It's officially approved for frying pan to have 5 augment slots. It was "fixed" at first in Fable Anniversary, but they changed it back with another patch. It's supposed to be like that: https://web.archive.org/web/20151105031614/http://forum.lionhead.com/yaf_postsm38151_Fable-Anniversary-Patch-News.aspx
Interesting, so for Anniversary, it's a UI thing, not a slot thing. Thanks for the research, I even asked a dev and didn't get a conclusive answer. This still doesn't tell me how it was originally supposed to be and what direction the actual "fix" would be in, as it doesn't list this as a fix like it did with other bugs and removing beetles from Summon is definitely an Anniversary change (Anniv also made many other small tweaks that are unique to that release; fishing is a good example), but I'll see what I can do. Unfortunately the UI is quite a janky mess on the PC version (as someone intimately familiar with it, it's a nightmare), so I can't promise anything, but I'll include something pertaining to this in the next update, even if it's just reintroducing the hidden slot bug until I can figure something out. If this project grows much larger, I'll likely split it into different optional files so that people can just use what they like.
I installed the way the description page says, but i'm having a "Microsoft C ++ Runtime Library - runtime error" when i try to continue my save (By the way i'm playing from steam)
It would be cool to fix the morphing. In the original game, the texture of body hair(Strength tree) disappears if you up Skill tree. And this should not be. I would have done it myself, but I did not figure out how. (Sorry for my bad english)
Okay, cool. Indeed, this may not be a bug, but as for me, the hero looks better when they do not disappear. That is, blonde hair and old hair are superimposed on top and it looks like it should be. I took this from an old forum, where one person tried to fix it, but broke it. He made it so that body hair, muscles and will tattoos - all of it only appear if you up Will tree. I can give you a fmp file with this to look if you want
29 comments
I'm not currently aware of any way to fix random crashes with the base game. Crashes aren't generally a trivial thing that can just be "fixed" unless exactly what causes them is determined and is realistically fixable. Unfortunately, Fable is generally very particular about the underlying system in ways that problems that often occur on one setup under certain conditions may be impossible to duplicate on another setup, and the actual cause is never determined (for example, the "ghost town Oakvale" glitch found by Budget, among many other things).
For documentation's sake, it sounds like your crashes were occurring most frequently during the Orchard Farm quest and only happened when the camera was moved; you were using a mouse and on Windows 11, playing in fullscreen with maxed graphical settings at 1920x1080 on a fully vanilla French copy of the game. Compatibility mode and disabling in-game overlay in Steam still resulted in crashes. While I can't provide any sort of solution right now, I do want to have this all down just in case someone else has a similar issue so that we can maybe determine the cause through further diagnosis. For what it's worth, this is not a sort of crash that I have personally experienced on any setups, across multiple hardware configurations and operating systems, although I have yet to use Windows 11 with Fable.
Because that door requies the full Dark Will Set, and this patch is said to include the Dark Wizard Hat into the set.
I was about to play the game and was worried if I can get the door open, if I choose to get a Bright Wizard Hat during the Book Collection quest.
Well, yes, if the door only checks for the four specific parts of the suit and doesn't check for the actual "pointer to the suit"/template of the suit, then it should be no issue.
Eventually would be great to verify it, as this patch got an update when some other bug was found with a demon door not possible to open (compared to unmodified game) under normal circumstances. It's a similar case.
Welp, here is my contribution to the cause, lmao. That optional patch would be really appreciated. Thank you for your efforts anyway
https://web.archive.org/web/20151105031614/http://forum.lionhead.com/yaf_postsm38151_Fable-Anniversary-Patch-News.aspx
Thanks for all the nice fixes otherwise! This is always appreciated!