People have to admit it, a killer bug related to a fucking cowboy hat is kind of hilarous.
http://fidgit.com/archives/2010/11/the_cowboy_hat_that_killed_fal.php
But honestly, it sounds like the type of super obscure bug that slips easily Q&A, even the best ones. “There is a hard lockup that occurs if you do sidequest X doing action Z and then in the moment A you give item B to npc C and then if you visit place D it crashes”.
Are they supposed to try all the possible permutation of actions possible in the game? Because i think the average half-life of the protons in this universe wouldn’t permit that approach to testing. The universe would decay before trying every possible combination.
Why bother searching forums, when wiki has nice list of all found bugs with solutions for every quests, like
only after reading these can you really appreciate how broken these games are - Oblivion, Fallout 3 and Fallout NV - all three of them have just about every single quest bugged (although most people will not encounter most bugs of course).
The system crash bug is apparently common to a wide variety of player action combinations.
Edit: I’m referring to the Strip and the cowboy hat, not the debt collector quest, sorry.
The strip and cowboy had occurs during the Debt Collector quest - you take a hat as a proof of kill and get it back to lady in Freeside, and when you go back to strip, it should crash.
I say should, because literally 2 minutes ago I did this quest - talked the guy into giving me his hat without killing him, gave the hat to the lady, quest finished, went back to the strip and no crash happened. And I do not have any old hats on me, only Power Armor T-51.
Miramon
3185
Oh yeah, that actually explains one of my crashes. Nice one.
Sarkus
3186
Which demonstrates that fixing stuff isn’t as simple as some people (like Tom, apparently) might make it out to be. If the hat issue crashed everyone then its a simple fix. Since it doesn’t, that means there are other factors involved then just the hat. Tracking that down takes time, and changes always ripple out in other ways, meaning you have to go look for unexpected consequences.
Just got an update via Steam. Patch notes, she say:
Fallout: New Vegas - Version 1.1.1
Companions now show up as waypoints on the map
Companions will always fast travel with you, unless told to wait or sent away
Fix: DLC error/save corruption
Fix: Stuttering with water effects
Fix: Severe performance issues with DirectX.
Fix: Controls temporarily disabled after reloading Cowboy Repeater while crouched
Fixed crash using the Euclid C-Finder while having the Heave Ho perk
Fix: Entering the strip after Debt Collector causes crash and autosave corruption
Fix: Using Mojave Express dropbox can cause DLC warnings
Fixed crash when buying duplicate caravan cards from a vendor in a single transaction
Crafting menu should filter valid (bright) recipes to the top of the list
Fix: Sitting down while looking down a weapon’s ironsights leaves player control locked
Fix: If a companion is knocked unconscious with broken limbs they stay broken on respawn
Fix for varmint night scope effect persisting in kill cam
Fix for giving companions armor that adds STR does not increase their carry weight
Fix NPC Repair menu displays DAM as DPS
Having NPC repair service rifle with forged receiver decreases CND
yeah so Tom’s crash should be fixed for good, on PC that is.
And DX finally fixed, whoa.
Also, this already contains more fixes then Bethesda ever did for FO3. Their patch notes always read “added support for next DLC”.
Companions now show up as waypoints on the map
Companions will always fast travel with you, unless told to wait or sent away
Dear God yes. Best changes ever.
Good patch, but i am surprised with the lack of fixes for some quests, some of them already fixed easily by modders with the game editor. Maybe that will come when they release the console patch.
I killed that guy and turned in his hat maybe fifteen or twenty hours of playtime ago and haven’t had this problem so far.
pilonv1
3192
Fix: Controls temporarily disabled after reloading Cowboy Repeater while crouched
This was driving me insane.
Quick testing shows that the nVidia fixes seem to have worked. I’ve removed the fix .dll, redetected my real graphics card and maxed everything out (including water) and it’s all working fine. No more slowdown near faces.
OH NOES
There appear to have been a few problems with the patch, including setting some monsters to become essential (unkillable) - I’ve seen this in a save loaded at Camp Forlorn Hope. There’s a bunch of zombie bloatflies there that just go unconscious and then wake up after you kill them. This is widespread apparently.
Grifman
3195
Unfortunately, this did not work for me. I still have the exact same problem :(
Yeah, was just coming here to say now there are a couple of unkillable Fire Geckos inside Vault 19. I kill em dead and they just go unconscious for about 10 seconds, then they pop back up.
Plus the first time I saw them they were stuck in the floor.
Plus, now I’ve had the controls go unresponsive when I’ve used an elevator while crouched (using a pistol) - E wouldn’t open a door or search a corpse, but when I went out of and back into stealth mode it started working.
So for me it seems that the patch broke more than it fixed. :/
Edit to add: seems I’m re-downloading the patch right now from Steam? Just read the fix for the patch is live, so I guess that’s what it is.
The strangest thing I’ve had happen so far is when I was killing fiends in their vault, the robot that dug me up in the beginning descended through the ceiling and wished me luck. He stayed stuck there for quite some time. Very odd.
Yeah, I had that problem with a couple of fire geckos, too. Until I shotgun-punched them off a cliff.
Yessiree, that’ll fix ya up, I reckon.
TurinTur
3199
Oh, great, i defend thier Q&A in one of my posts yesterday, and now they make this blunder, which proves an almost 0 amount of testing from the Q&A.
Nice job, Obsidian/Bethesda.
TurinTur
3200
Oh, great, i defend thier Q&A in one of my posts yesterday, and now they make this blunder, which proves an almost 0 amount of testing from the Q&A.
Nice job, Obsidian/Bethesda.
