Everything's soooooo sloooow.

[Yggdrasilion]

I recently installed all of F&LNV by the book, including creating texture optimization for the big mods and the FNV textures themselves.

 

So I start the game, and immediately notice that while the menus work just fine, everything animation-wise about the game (movement is especially bad in conversations) is incredibly slow. Unplayable, really.

 

My laptop isn't exactly a monster rig, but I had not anticipated it being so bothered by it, especially since it runs Skyrim Revisited with ENB without a hitch.

 

I am at wit's end. I tried ditching the big texture mods, thinking they might slow the game down the most, but that did nothing.

 

Sorry for bothering you,

 

Ygg

[EssArrBee]

Remove ENBoost and see if that helps. ENB/ENBoost is hit or miss, so you don't know if it is any good until you use it.

 

Just go to the FNV folder and move the d3d9.dll to the desktop and then start the game through MO and play for a bit to check if it was ENBoost.

[Audley]

I would remove ENB boost and turn off V-sync. Then cap the frame rate using the Stutter Remover. See what that does. Do not play the game at a higher FPS than 60 or it will mess up the physics. 

[Yggdrasilion]

Tried doing all of that, and while looking at my .ini files in MO, I found what might be the root of all evil - both .ini files look exactly the same, as if some idiot (me) accidentally copied one into the other without noticing.

 

What do I do?

[Nozzer66]

Delete them both and restart the game through the launcher once. That should remake the vanilla inis for you.

[hishutup]

And then redo the ini edits for F&L

As for being slow... Do you feel that your card powerful enough to run it

Are you maxing VRAM

Edited September 20, 2014 by hishutup

[Yggdrasilion]

Yeah, now the 4GB loader doesn't load NVSE anymore, and when I try starting the game, it freezes on the main screen.

 

I give up. Can't do it.

[EssArrBee]

Start the main launcher through MO to regenerate the INIs. Then start 4gb loader.

[hishutup]

Wow, you gave up quick... I don't think I've ever seen someone quit before... Well not in writing

[Audley]

Actually, as I just did a completely new install of NV I noticed that both .ini's ARE the same. One is pretty much an exact copy of the other. It did not used to be this way (at least that I can remember). It should not affect anything. 

 

My suggestion: 

 

• Go to mygames/falloutnv and delete both .ini files
• Then, go to mod organizer/profiles/(whatever your profile is) and delete both .ini files
• Restart New Vegas using the launcher (NOT through MO) To generate the .ini files
• Then, start MO. This should generate two new .ini files making copies of the original ones

I think your game could have crashed for two reasons: 

 

One is that you did not delete the .ini files for the profile and now you have the Darn UI fonts installed but not the mod itself

 

Two is that you perhaps did not add the command line to the FalloutNV 4GB .exe

 

Either way I don't think you should give up because once you figure it out you can avoid this issue in the future. Not to mention that there are a lot of people willing to help you. 

[Audley]

Note: Fallout 3 and New Vegas have some strange physics glitches that can be caused by FPS. 

 

For example, if your FPS is capped at 60FPS but your computer is not powerful enough to run at that FPS, sometimes the game engine will try to compensate (poorly) by slowing down the games engine. Making everything happen at half the regular speed or even slower.

 

The opposite is also true. If you set no cap on the games FPS and you are running at a frame rate higher than 60, this will mess up the physics. The game will run at a much faster speed i.e. Your character will run faster, the lip syncing will be off. 

 

Both of these will cause the game to be unplayable. The fix is to really make sure the game is capped to what your computer can handle. There is nothing wrong turning off v-sync and capping your frame rate to 40 or even 30 if you need to. 

 

Extra Note: This is from my experience so yours will differ obviously. You may or may not have these issues.

Also, if you could post your computer specs it would be helpful. 

[hishutup]

just to fill it out

If it runs better without enb

try this in enblocal.ini

[MEMORY]ExpandSystemMemoryX64=trueReduceSystemMemoryUsage=falseDisableDriverMemoryManager=trueDisablePreloadToVRAM=falseEnableUnsafeMemoryHacks=falseReservedMemorySizeMb=256EnableCompression=false

Edited September 20, 2014 by hishutup

[Yggdrasilion]

Hey there.

Sorry for having been childish - long week full of unfortunate events, venting here was inappropriate. I've been trying to get this to work for a while on my own and only came here today because I was at an impasse.

I checked every step of properly installing the 4GB loader, but whatever I do, it keeps going to the launcher instead of NVSE. I do NOT understand why.

 

My specs:Processor - Intel Core i5-3230M CPU @ 2.60 GHz Quad-CoreRAM: 4.00 GB (3.84 GB useable)Video Card 1: Intel HD Graphics 4000 128 MB Dedicated Memory 1.7 GB Total MemoryVideo Card 2: NVIDIA GeForce GT 650M   2.0 GB Dedicated Memory   3.6 GB Total MemoryOS: Microsoft Windows 7 Home Premium Edition Service Pack 1 (build 7601), 64-bit 

[hishutup]

In the Executables menu type FNV 4GB Loader into the Title text box.Next to the Binary text box, click [...], and navigate to the "...Fallout New Vegas" folder, select "fnv4gb.exe" and click [Open].In the arguments text box type in "-laaexe .FalloutMO.exe", without quotations.Click [Add], then [Close].

taken directly from F&L

[Yggdrasilion]

In the Executables menu type FNV 4GB Loader into the Title text box.Next to the Binary text box, click [...], and navigate to the "...Fallout New Vegas" folder, select "fnv4gb.exe" and click [Open].In the arguments text box type in "-laaexe .FalloutMO.exe", without quotations.Click [Add], then [Close].

taken directly from F&L

 

I did that. Still goes to launcher instead of NVSE.

[Audley]

Generally when NV starts the launcher instead of using NVSE it usually means it is not detecting the .ini information right and it is trying to generate a new one. 

 

Start the 4GB launcher outside of MO so we can see if it starts properly.  If it does, then we can determine that it is something with MO and not the game itself.