Bug Report - Into the Pitt

Post by **CourierandWanderer** » Thu Jul 16, 2015 11:53 pm

Curious. The quest "Into the Pitt" is not wanting to start. I got the distress signal from Wernher, but not even that started the quest. I then decided to go to the radio tower, no map marker. I found Wernher and the Raiders attacking him; but when the Raiders are all killed and Wernher is safe, I can't talk to him. All he says is, "We've got to keep moving." This is an issue that I have actually never heard of before. In fact, I can't find any other forum topics relating to this.

Post by **TrickyVein** » Fri Jul 17, 2015 12:37 am

That's funny, because in my last TTW playthrough and indeed even in my TTW playthrough before that I finished The Pitt DLC without any issues, at all.

Once again, you have failed to provide the requisite information that we ask for in order to help you, namely your load order. Perhaps this is because you believe this is actually an issue with TTW itself and not any mods that you are using.

Consider yourself warned: the next time you post a so-called 'bug report' for TTW without providing any info, you are going to be banned. This thread is not at all helpful for the TTW team; it's a nuisance.

Post by **CourierandWanderer** » Fri Jul 17, 2015 12:44 am

And you shall have my load order. This thread will be updated once I put everything together in a list.

Post by **Thenryb** » Fri Jul 17, 2015 1:11 am

Check this thread. http://forums.steampowered.com/forums/showthread.php?t=1313194 It describes the same problem you are having and suggests using the console command "setstage xx00108c 10". This is a vanilla Pitt bug.

Post by **CourierandWanderer** » Fri Jul 17, 2015 1:15 am

Hmm, I'll see if I can try the console command. What numbers would I put in "xx"?

Anyway, you all suggest my load order to be posted, so here it is organized in a .txt file.

Post by **JaxFirehart** » Fri Jul 17, 2015 1:24 am

What would you do if people didn't tell you how to do things?

http://fallout.wikia.com/wiki/Help:Form_IDs

A bit of google goes a long way.

Post by **CourierandWanderer** » Fri Jul 17, 2015 1:30 am

Well, this is weird. Any console commands I type in related to a quest or asset from Fallout 3 will not work. After looking at the page from the Fallout wiki, I typed in "setstage 0100108c 10". I did nothing. Command was invalid. Did I type in something wrong?

Post by **AnvilOfWar** » Fri Jul 17, 2015 1:32 am

[quote=CourierandWanderer]

And you shall have my load order. This thread will be updated once I put everything together in a list.

[/quote]

That is completely irrelevant since this sub-forums sticky post has this to say about getting help: https://taleoftwowastelands.com/content/you-will-get-banned-if-you-dont-read-asking-help

By my estimation, a good 90% of all the "problems" people have are load order, for user error related. The remaining 10% can be accounted for by in game problems that Bethesda/Obsidian NEVER PATCHED themselves, and look at that, the TTW team even COVERS the majority of those by providing a mod to fix vanilla game problems: https://taleoftwowastelands.com/content/ttw-fixes-222-official-bugfix-pack-ttw

TTW itself by its own admission in the change logs: https://taleoftwowastelands.com/content/alpha-download-v294b#changelog

Notice the distinct less and less amounts of changes between versions? The last 4~ or so TTW versions have had between 6-7 changes total per version revision. The possibility of that kind of error being a "TTW problem" is so small as to count as remote, when its very likely some fault with Betheda's own game programming.

TLDR Version: Most problems people have is THEM screwing up their own installs, mod conflicts, or vanilla bugs in the base game.

Post by **CourierandWanderer** » Fri Jul 17, 2015 1:38 am

Turning all the mods off didn't help. This may not be relevant or make any sense, but I'm going to see what happens if I start a new game. You say that it's a vanilla glitch, so let's see what happens. Vanilla glitches don't generally repeat themselves. My theory is that it could be savegame issue related to a mod I had to get rid of because it was causing problems.

UPDATE:

Yep, I just started a new game, and there was the issue, all fixed. Before all of this, I had to remove a few mods that were causing problems; but I think the damage from the faulty mods was still there. This is something new. Be sure to watch out for problems like these. Damn, I have to start all over again; but I love the Fallout games. I can care less if I restart with a new game.

Post by **JaxFirehart** » Fri Jul 17, 2015 6:35 am

01 should not be the load order ID of Fallout3 unless your load order is WAY messed up. Look and try again.