Jump to content

Installing FNV4GB


DickyDee

Recommended Posts

I've been having serious issues trying to actually boot up FNV4GB. I followed the instructions and got this:

 

http://i.imgur.com/Pm9uX3d.png

 

I tried the other suggested numbers like 22380 but no cigar. The full target was:

 

"C:\program files (x86)\steam\steamapps\common\Fallout New Vegas\fnv4gb.exe -SteamAppID 33972"

 

I also get this message when I try to open it up normally.

 

http://i.imgur.com/4UfZXt3.png

Link to comment
Share on other sites

last image looks like if u didnt place on nv folder fnv4gb exe and dll but im not an expert im having issues aswell on a post below urs lol.

 

also if your not using an enb u could just use the original fnv4gb exe u can bound it to ur mod manager or w.e it auto loads nsve when detected so if u dont have an enb i think theres no need of comands but like i said im not an expert having issues aswell

 

make sure the original exe along with the helper.dll was placed on C:\Program Files (x86)\Steam\steamapps\common\Fallout New Vegas

 

make sure you ran the exe by itself no shortcuts just the exe after it was properly placed on the correct destiny so it will generate an exe folder with a file on it

 

then create ur shortcut to desktop

 

make sure the text you are placing is on destiny and the test is correct according to what you have place there it haves minimal errors that wouldnt allow you to save changes .

 

example "C:\program files (x86)\steam\steamapps\common\Fallout New Vegas\fnv4gb.exe" -laaexe .\FalloutNV4GB.exe -SteamAppID 33972

 

on the red section if you miss the " <- just with that missing after fnv4gb.exe will prompt a message that the destination is not correct so make sure all parameters are 100% correct even small details.

 

heres a video of the mod author i think

https://www.youtube.com/watch?v=gt-m3gx9Pos

Edited by nasomaniac
Link to comment
Share on other sites

33972 is not a valid appid for fallout new vegas. , 22380 (North America, Europe) or 22490 (Eastern Europe) are the valid ones.

 

Command line/Launch options go after the closing quotes, with a space between them.

 

The bink error, is because you've installed some crap codec pack that has put binkw32.dll into windows\system32 , go there and delete it.

Link to comment
Share on other sites

  • Recently Browsing   0 members

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