Jump to content

Bug when ending Lonesome Road


CaptainNapalm123

Recommended Posts

I'm having the exact same issue, and apparently a lot of other people have to, and I can't find a straight answer from anyone. Some people say it's because you have a SPECIAL set to 10, but that doesn't seem to matter in some cases

 

 

 

EDIT: Don't know about you, but for me it turned out to be a conflict with the mod Nevada Skies. I disabled it and it fixed this issue.

Edited by AndarielHalo
Link to comment
Share on other sites

  • 2 weeks later...
  • 2 weeks later...

wow thank god I found this thread because I have been trying to fix that bug for two hours now. It was actually the Nevada skies that screwed up the ending. I wonder why the modder never released a patch for it. Oh and thanks! :D

Edited by bajs11
Link to comment
Share on other sites

  • 4 weeks later...

Its nice to confirm this. I had a hunch it had something to do with Nevada Skies as the mod wants to kick up a storm every time the cutscene is over. I had the issue twice in a row before I was off googling it. Thank ya thank ya.

Link to comment
Share on other sites

  • 3 weeks later...
  • 2 weeks later...
  • 1 year later...
  • 2 years later...

Please note the date of the previous post, and see the Nexus "Terms of Service" about not resurrecting old threads. The primary reason is that the original thread participants are seldom still around, and it is unlikely that you have exactly the same setup. Details matter.

Edit: Please see 'Issue: Lonesome Road (or other DLC) hangs after cutscene' in the wiki "Fallout NV Mod Conflict Troubleshooting" guide for some additional possible solutions.

 

That said, if none of those solutions work then despite appearances, in your case it likely is not the same issue. Exactly when are you getting hung? Please provide ALL the information requested in the wiki "How to ask for help" article in a new post. Don't forget to identify things that do not appear in the "load order", such as NVSE and it's related plugins, texture replacements (specifically their larger image sizes: 1024x1024, etc.), and "post-processors" like ENB or SweetFX.

 

We are interested in what your "load order" was at the time the problem occurred. Did you make any changes to the "timescale" from the default of "30:1"?

-Dubious-

Link to comment
Share on other sites

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...