Hello I use New Vegas Mod Manager and there is an option in it to enable extended scripts. I also have a tool that lets New Vegas use 4 gigabytes of RAM instead of 2.

Is it possible to run both at the same time and if so how would I go about it?

You can try asking in http://www.gamesas.com/index.php?/topic/1146021-beta-new-vegas-script-extender-nvse-v1/

Unless there has been a change to NV4GB in the past couple days, no. You can load them both but NVSE doesn't work properly.

I see that's too bad.

Thank you barretsfloyd and Waerlogan:)

I asked this question in the now locked first NVSE thread (page 8) and it was ignored. So, either the NVSE peeps cannot or will not fix NVSE to run with the 4Gb utility.

NVSE is ok, but not a 'must use' utility for me, I can live without the mods that use it.
However, the 4Gb utility is a 'must use' for any 64bit system user who needs a lag fix.

Wouldn't that only have a use if the FalloutNV.exe program would ever be close to taking up 2 GB of ram?

If you use any texture packs, like 4Aces's, you can easily exceed 2 gig.

Yup ... I use NMC's Fallout 3 HD texture packs ported over to FONV plus various other texture packs on a Win7 64bit system.
Since I prefer the eye-candy mods over mods that use NVSE, the 4Gb utility is a 'must use' to avoid lag issues.

EDIT: Also wanted to add that it seems NV4GB helps reduce lag on 64bit systems even if you are not running HD texture packs.

NV4GB greatly reduces lag, and stuttering.

I would imagine that it would easy enough to incorporate 4NVGB's changes to the .exe into NVSE.

Where do you find NV4GB? I ran some searches and came up empty...

http://www.newvegasnexus.com/downloads/file.php?id=35262

I really think that this is a problem that needs to be addressed. My vote goes in for making this a top priority for NVSE!

NV4GB only sets the LARGEADDRESSAWARE flag. A whole plethora of utilities are available to do this to any random executable. NVSE is badly coded if it trips on a single flag being set.

It doesn't just do that though. It does something similar, but it does it without modifying the original file because Steam won't work if the original file is modified. The problem is that both NVSE and NV4GB can't modify the file in memory at the same time since both rely on the original file being unaltered when they do their work.

I believe the NVSE team has already spoken about adding a 4GB patch, but have put it off for now. They shouldn't have to bother as Bethesda should have provided one from the beginning.

Ah yes, that makes sense. Sorry, I was thinking about the un-DRMed FO3 for some reason.

The fact that NV is a Steam application makes setting the 4GB-aware flag overly complex. The flag effectively needs to be set on disk, since it's read by the PE loader (in other words before nvse_loader can do anything about it). However, Steam checksums executables at launch, so changing the flag breaks the game and it won't launch properly. The 4GB loader bypasses the checksumming process via some interesting code that unfortunately breaks the way that we integrate with Steam. We also have a problem with loading directly (bypassing the launcher screen) that this also triggers, but I haven't been able to debug what's breaking yet.

So, to summarize: if you have an EXE where you can just set the large-address-aware flag and have everything work, continue using nvse_loader as normal, everything will work. If you can't do that, then right now I don't have a solution for you yet. Currently busy with IRL work (and the patch that's coming soon according to http://www.gamesas.com/index.php?/topic/1123616-game-updates/).