Is it safe to change the length of the day pass?

[ismaiden666]

I know that we can change the duration of the passage of time with the command "set timescale to" in the command console. I also know that certain values can cause problems in the game. If I change the default timescale by half (30 to 15) I think there is no problem. It was the value they recommended to use in Skyrim. Has anyone of you who has played New Vegas with this altered timescale had any problems?

[Tribe Reimanen]

Originally posted by ismaiden666:

I know that we can change the duration of the passage of time with the command "set timescale to" in the command console. I also know that certain values can cause problems in the game. If I change the default timescale by half (30 to 15) I think there is no problem. It was the value they recommended to use in Skyrim. Has anyone of you who has played New Vegas with this altered timescale had any problems?

for me its never worked in general. I dont recommend any commands that influence the game in the long run. ur best off just finding a bed or matress.

If theres no mattress or bed nearby: Im pretty sure, not 100% sure, but PRETTY sure, you can spawn in assets with the "Player.placeatme" Command. Try this: "Player.placeatme 00015848 1" Which is the console ID for a simple Mattress. It should spawn one in at ur feet. After ur done simply open the console, click on it, and type "Disable" to delete it.

[WillieSea]

Very stable, no problems what-so-ever.

I have a perk in my mod called 'Longer days' that makes days last longer and nights go by really fast, all automatically.

All my time in the game was with that perk active.

[Johnny Casey]

A quote from Roy Batty (=Former project leader for Tale of Two Wastelands)

Originally posted by Roy:

No, it can't be changed without the game breaking in some way at some point. It ranges from Actors doing stuff at the wrong time of day, to quests not progressing, to CTDs.
(...)
It breaks multiple quests in the NV engine, which we've proven time and again with users having difficulties with certain missions.
(...)
Many things in the game are tied to the timescale. You might find AI packages acting weird though and not being performed at the correct time of day and other strange things.

Considering Roy is experienced with this game(both as a player and a developer) way more than any of us here combined, you want to follow his words, rather than anyone else who said "I didn't have any problem".

[WillieSea]

Why would I listen to another 'modder' (not a developer) tell me about timescale and its use. I successfully used that command in FO3, FO:NV, FO4 with absolutely no issues at all.

If you are sane with the timescale you set, there are no issues. You "might" only have a problem with it if you set the timescale way to fast. Setting it slower would actually make the game run better because none of the issue Mr. Batty mentioned would ever occur.

[ismaiden666]

Thanks for the answers. If an experienced modder thinks it's bad to change the timescale, I'll believe him. But I understand why many players believe it does not cause problems. That depends on how well you know the game and its events, if you can tell which events are normal and which are failures caused by user changes.

[Tribe Reimanen]

Originally posted by ismaiden666:

Thanks for the answers. If an experienced modder thinks it's bad to change the timescale, I'll believe him. But I understand why many players believe it does not cause problems. That depends on how well you know the game and its events, if you can tell which events are normal and which are failures caused by user changes.

Were talking mainly logically. games engine is breaking broken in some ways and altering something that influences basically everything is logically not a good idea

[WillieSea]

Originally posted by ✪Reiman:

Originally posted by ismaiden666:

Thanks for the answers. If an experienced modder thinks it's bad to change the timescale, I'll believe him. But I understand why many players believe it does not cause problems. That depends on how well you know the game and its events, if you can tell which events are normal and which are failures caused by user changes.

Were talking mainly logically. games engine is breaking broken in some ways and altering something that influences basically everything is logically not a good idea

First, you have to understand how timed quests work, how AI packages work since many are set to a time of day, and that will logically tell you how timescale changes will affect the game.

As I said above, slowing the timescale will have no adverse effects at all under those conditions because you are giving more time for those events to occur.

Speeding up the timescale a little bit will not cause much problem with timed events. The events will still occur, you just may have less real time to accomplish them in.

Speeding up the timescale to ridiculous amounts will cause many problems.

So, anybody wanting to make timescale changes just has to understand what they are doing and how it effects the game. A whitewash "it is a bad idea" is a bad answer. It is the same with any change, go crazy with the change and the game will be negatively affected.

I have been making mods for the Bethesda games since 2003 starting with Morrowind. I would say I am an experienced modder.

[ismaiden666]

Originally posted by WillieSea:

First, you have to understand how timed quests work, how AI packages work since many are set to a time of day, and that will logically tell you how timescale changes will affect the game....

This answer and yours above bring up an interesting point of view that makes me consider using a shorter timescale. As you said, if many events and actios of NPCs are based on a specific time, they will occur at that moment regardless of whether the time runs fast or not but I understand that a passage of time too slow or too fast would cause problems.

[WillieSea]

Originally posted by ismaiden666:

Originally posted by WillieSea:

First, you have to understand how timed quests work, how AI packages work since many are set to a time of day, and that will logically tell you how timescale changes will affect the game....

This answer and yours above bring up an interesting point of view that makes me consider using a shorter timescale. As you said, if many events and actios of NPCs are based on a specific time, they will occur at that moment regardless of whether the time runs fast or not but I understand that a passage of time too slow or too fast would cause problems.

A shorter timescale, where in-game time passes faster, can make events go buy quicker and make it more difficult as a player to hit the quest/event at the right time.

Remember, I said a faster time passing, especially if it is insanely fast, will cause you problems in the game.

For example, a one hour AI package may go past before the NPC is even at the location the AI package is supposed to occur at. And if you have to interact with the NPC at the location only during that AI package being active, you may never be able to interact with the NPC. And if it is quest related, that can cause problems.

[ismaiden666]

Originally posted by WillieSea:

For example, a one hour AI package may go past before the NPC is even at the location the AI package is supposed to occur at. And if you have to interact with the NPC at the location only during that AI package being active, you may never be able to interact with the NPC. And if it is quest related, that can cause problems.

NV's default "time scale" is 30 right? I was thinking of halving it. I want to have more time to enjoy daylight without having to use mods.

[WillieSea]

That will also give you twice as much night. You would have to enter the timescale all the time since the timescale is not part of the save game file.

So, in my mod, I made it a quest script which once activated, is saved with your save game and implemented during the daylight hours. It also speeds up the time during the nighttime hours. All automatically.

[psychotron666420]

Originally posted by WillieSea:

That will also give you twice as much night. You would have to enter the timescale all the time since the timescale is not part of the save game file.

So, in my mod, I made it a quest script which once activated, is saved with your save game and implemented during the daylight hours. It also speeds up the time during the nighttime hours. All automatically.

If one wants longer timescale, why would they want shorter nights?

That was one of my biggest peeves of farcry 3, they made nights like 2 minutes long and days like 20 minutes. So dumb imo

[ismaiden666]

Originally posted by WillieSea:

That will also give you twice as much night. You would have to enter the timescale all the time since the timescale is not part of the save game file.
So, in my mod, I made it a quest script which once activated, is saved with your save game and implemented during the daylight hours. It also speeds up the time during the nighttime hours. All automatically.

The game has a sleep/wait option so I don't mind the nights being long. Maybe I shouldn't mind short days as all I need is sleep to start doing day missions again. However most players agree that having longer days is better as long as you have an option to advance the time. If there is a possibility that the altered timescale could cause problems then I would not use a variable timescale of longer days and shorter nights. I prefer the passage of time to have a single constant value.

If you change the passage of time with the command "settimescale" in the game console and save your gameplay, the timescale set will always be active in the save used and in new saves. As long as you don't go back to an old save where the timescale hasn't changed yet.

[Aoi Blue]

The wait option is really useful. I use it when waiting around for a scheduled NPC, such as guy at the Novac Gift Shop.

[Tanya☆]

New Vegas is a really delicate beast. For all we know it will make your game crash once or two in the next 30 hours or it may not. Sometimes the game crashes out of nowhere and you won't know if it's one silly thing you changed an hour ago or another you changed 50 hours ago. Generally, the less you mess with commands, the better.