Asenna Steam
kirjaudu sisään
|
kieli
简体中文 (yksinkertaistettu kiina)
繁體中文 (perinteinen kiina)
日本語 (japani)
한국어 (korea)
ไทย (thai)
български (bulgaria)
Čeština (tšekki)
Dansk (tanska)
Deutsch (saksa)
English (englanti)
Español – España (espanja – Espanja)
Español – Latinoamérica (espanja – Lat. Am.)
Ελληνικά (kreikka)
Français (ranska)
Italiano (italia)
Bahasa Indonesia (indonesia)
Magyar (unkari)
Nederlands (hollanti)
Norsk (norja)
Polski (puola)
Português (portugali – Portugali)
Português – Brasil (portugali – Brasilia)
Română (romania)
Русский (venäjä)
Svenska (ruotsi)
Türkçe (turkki)
Tiếng Việt (vietnam)
Українська (ukraina)
Ilmoita käännösongelmasta
A lot of folks have run into this problem... it's one of the great mysteries of mankind.
I run, and have played over 4200 hours, launching through a mod manager. I use MO2.
You NEED to have certain mods in place to stabilise the game, mods like NVSE (New Vegas Script Extender) the 4GB Extender (because the game only looks to use 2GB of RAM and that's not enough. You need NVTF (New Vegas Tick Fix) to keep the glitches down.
There are several good guides to setting up and running the game on YouTube, you should take a look at them, they'll help but, as I said, use a remote launcher from a mod manager.
You can find the running/system and stability mods on Nexus Mods.
There is a pinned list of recommended mods at the top of the Fallout New Vegas discussion forum as well.
It takes a bit of setting up these days because of the old Bethesda engine. Take a look and come back with any other questions.
Cheers,
T
Ok thanks, I'll try that and see if it works
https://vivanewvegas.moddinglinked.com/
Even their new games don't launch in working condition.
That said, very few publishers maintain 13-year-old games that are essentially just paid DLCs for 15-year-old games. If you were trying to run most games from 1997 in 2010 when NV came out, you'd have even more trouble. It's a fact of old games - they simply don't play well with all modern system configurations.
neither steam nor the game installer nor the game make any changes to windows security.
check antivirus log? might be blocking game/game launcher.
check windows security/controlled folder access.
if on add exceptions for game launcher/game.
running Windows One Drive? One Drive moves the ini/preference files to the one drive.
modify one drive to exclude the game folder.
run game from game folder .exe and NOT from steam library or an icon.
sometimes an error msg (missing library) appears not hidden by steam
check windows event viewer and also windows reliability history. might be an error msg.
game in a launcher loop - no permission to create folder
Documents\My Games\FalloutNV
or create any files in it
OR windows one drive moving the .ini files out of the folder
How do I stop One drive from moving the ini files out of the root file?
Good news, I finally managed to run Fallout new vegas on my gaming PC rather than my old PC, all I had to do was take the ini files from my one drive and then unlink the account from my current PC. I feel like the one drive is more annoying than it's worth, anyways I'll be running the bethesda launcher shortcut on compatibility mode since that will stop the crashing from damaging my computer. I used this method and the crashing would just boot me out of the game instead of hard freezing everything.
Thanks for the lead Cheshirm, you really helped me out