Pace Yourself

[DoctaSax]

Pace Yourself

View File

---

WHAT IT IS

 

Pace Yourself is a small utility that you can use to remind yourself you've been playing for a certain amount of time and should probably stop for a while. You can then simply dimiss the message, choose to be reminded again later, or leave yourself a note that will be displayed next time you start the game in order to remember what you were about to do.

 

REQUIREMENTS

NVSE 5.1.4
JIP 55+
JohnnyGuitar 2+

 

CUSTOMIZABLE

Both the messages you send yourself, and when they should be displayed, are easily customizable in the .ini file that comes with it. You can be as passive-aggressive to yourself as you like.

Every section in the ini comes with the following fields:
Msg=the actual message that is displayed to you.
Time=after how many minutes it should be displayed since game start (FirstMsg) or the last time you got a message (the Reminders).
DismissOption=the text for the button where you simpy want the message to go away
SnoozeOption=the text for the button where you ask to be reminded again later
NoteOption=the text for the button where you want to leave a note

By default, there is one first message, and 3 reminding messages for when you hit the proverbial snooze button before. You can actually add more reminding messages if you want: simply follow the conventions of the previous ones, and leave the SnoozeOption empty for the last one.

 

PERMS
Dedicated to the public domain with CC.0

 

DISCLAIMER
Whipped this up in about an hour. Untested, I have other things to do. Should be fine. If not, I'll hear about it. If you want it to do more, or less, or do things differently, you're welcome to do it yourself, see Perms.

 

CREDITS
As always, kudos to the coders who made the script functions I use.

 

---

• Submitter
  DoctaSax
• Submitted
  09/29/2019
• Category
  Other
• Requires
  NVSE 5.1.4, JIP 55+, JohnnyGuitar 2+

 

[Harry Smackmeat]

I was under the impression this is already built into the engine in the form of it constantly crashing, causing me to look at the clock and sigh, and say out loud "it was only running for 30 minutes!"

[dongding]

^
Came here to post this. lmao

[DoctaSax]

Well, if you guys ever get yourselves a stable game, you have this to look forward to (and probably throw it entirely out of whack).

[Fredas]

It's funny, but I actually just two days ago finally finagled to get New Vegas running on Windows 10 without crashing.  Yes, it never crashes, full stop -- same behavior as what I always had on Windows 7 before I was forced to "upgrade".  So I could actually get some legitimate use out of this mod, now that I'm doing 5+ hour sessions again.

 

I can only speak for myself, of course, but I think this could be useful information for at least someone.

 

Key #1: Using either NVSR or New Vegas Tick Fix.  If NVSR, the one thing that absolutely matters is this: bHookCriticalSections = 0.  At 0, no crashes.  At 1, guaranteed crash -- the more often you change cells, the sooner it'll happen.  Now, having this at 0 will cause the game to stutter pretty badly whenever anything at all loads.  So it's particularly noticeable when traveling, as new grids in the distance constantly load in.  Oh well!  It doesn't stutter at all when nothing's loading.  That all said, I did at least sort out three variations.

 

1: bReplaceHeap = 0.  Bad stutters.  This is identical to the behavior exhibited by New Vegas Tick Fix so I assume said mod achieves basically the same thing as these settings.

2: bReplaceHeap = 1.  Stutters are lessened.  However!  Menus develop a lag problem that seems to be dictated by the complexity of the given menu.  Long lists, like the loading screen with several hundred saves, or "Notes" in the Pip-Boy with hundreds of entries, take about a full second of waiting to resolve, even if you simply move to a different menu and back; it pauses every time.  Pretty awful.

3: bReplaceHeap = 1, and iHeapSize = 512 (rather than 450).  Stutters are lessened, and the menu problem does not manifest.  This is the best result I've gotten under Windows 10.

 

Key #2: Something else may still cause crashes.  It's one or several of your mods.  (Or you may luck out and not have this particular issue; plenty of folks have.)  Much of the confusion arises from the fact that bad NVSR settings or "bad" mods (or both, obviously) can cause pretty much the same crashing phenomenon, thoroughly obfuscating the issue and preventing a lot of folks from arriving at any kind of solution.  Now, what is a "bad mod"?  I don't know.  What dictates that a given mod will cause NV in Win10 to crash like this but not in Win7?  I don't know!  But the good news is that once you get NVSR's settings sorted out per above, theoretically, if you then begin systematically removing mods from your load order until the crashes no longer occur, then you can whittle the problem down.  I actually don't know for certain what my problem was, though signs point to possibly one of my LOD mods.  What I do know is that I played New Vegas for about 400 hours on Windows 10... in 10-minute increments... and now I get to play the rest of this playthrough in relative peace.

 

The stuttering is annoying AF, don't get me wrong.  I'd love for there to be a more comprehensive solution that takes into account Windows 10's failures (supposedly introduced by the so-called "Creator's Update").  But NVSR was last updated in 2014, and nobody with that kind of expertise is stepping forward.