Timescale adjustments on FNV

[RoyBatty]

It breaks multiple quests in the NV engine, which we've proven time and again with users having difficulties with certain missions. It breaks specifically Finding the Garden of Eden, Take it Back, and the Beginning of Broken Steel.

It caused broken quests for me in Fallout 3 too in several playthroughs so I stopped using it. An exact example would be Head of State, after leaving the Temple of the Union the slaves would never reach The Mall.

[Arkngt]

OK about NV, I've almost never played it. But I must have done Head of State 10 times with timescale 8 w/o issues. But, nevermind, if it messes with the NV engine I'll not temper with it.

[Gribbleshnibit8]

There was a mod for FNV that had a solution to this. Whenever certain stages of certain quests were active, it would automatically set the timescale back to 30 until those parts were done. The problem with this solution is it requires knowing exactly what stages of what quests to work on, which for FNV alone is a pretty big task, and adding in FO3 makes it even more work.

[RoyBatty]

Maybe it's a combination of sutter remover and time scale changes that cause the problem. Internal game clocks becoming out of sync... who knows.

[DoctorEvil]

So basically another solution would be to just switch the timescale back to 30 for the duration of those missions? I'd prefer that to having to deal with a 30 timescale the whole game

[Dood]

[quote=DoctorEvil]

So basically another solution would be to just switch the timescale back to 30 for the duration of those missions? I'd prefer that to having to deal with a 30 timescale the whole game

[/quote]

That plus remember autosaves and manual saves in case anything goes wrong.

[rickerhk]

In Project Brazil we set a timescale of eight. All our quests have been developed and tested with that setting. However, I don't use Stutter remover or NVAC when working on the quests in the mod. I have a feeling that NVSR does indeed mess with NPC AI at times. There was a time in FO3 where it would cause random NPC deaths - now it's more random and subtle. PCB mods mess with AI even more - especially background processing. Anyway there isn't any script or quest in Project Brazil that depends on background NPC AI package processing - because I believe it's pretty much busted - or if not busted then the lower timescale busted it :)

When playing TTW, FNV or just FO3 I leave the timescale at 30 because I prefer that setting anyway.

 

[Raygereio]

[quote=RoyBatty]It broke things for me, I used to try and play with timescale 12. It screwed up quests with timer stuff like Contreres and the girl that goes to the Boomers.[/quote]

In what way did things break for you? And do you know for certain it was caused by you messing with the timescale?

I ask because I've been reading doomsday stories about how messing with the timescale will screw up your game and possible blow up your computer since the early days of Oblivion modding. However I played New Vegas several times with mod I made myself that changed the timescale to 20 normally, 10 when in town areas and 3 when indoors or in combat. And I noticed no bugs caused by it.

[Risewild]

[quote=RoyBatty]

 

It breaks multiple quests in the NV engine, which we've proven time and again with users having difficulties with certain missions. It breaks specifically Finding the Garden of Eden, Take it Back, and the Beginning of Broken Steel.

It caused broken quests for me in Fallout 3 too in several playthroughs so I stopped using it. An exact example would be Head of State, after leaving the Temple of the Union the slaves would never reach The Mall.

[/quote]

[RoyBatty]

With Contreres he would be stuck in "I'm not ready yet, come back tomorrow" and I could never complete the quest.

With what's her head, she disappeared into limbo and died.

This was repeatable when loading an old save. If I went back before starting that stage of the quest, and set timescale to 30, they would function normally. At that point I stopped changing the time scale. :P