Borderlands .INI Stuff

[Draegan]

All this is from the Borderlands thread.  I'm merely grouping it all together.  


FOV Stuff

Some things you should know about the FOV

Apparently when playing single player, once you change the FOV it'll stay at that setting no matter what you do (like sprinting). However, when you are in a multiplayer game, sprinting will reset your FOV to their default (which is apparently very, very low). Someone earlier in the thread suggested adding the FOV command to your sprint bind, which mostly works... but since sprinting is not really a toggle or press/release thing... it's a turn on while moving forward by tapping it thing... you end up sprinting, then stopping, then looking at an awful FOV. The solution?

Put the FOV command you want on not only your sprint key, but also all your movement keys. It'll look something like this in your ...\My Documents\My Games\Borderlands\WillowGame\Config\WillowInput.ini file under the heading [WillowGame.WillowPlayerInput]



Bindings=(Name="E",Command="MoveForward | Axis aGas Speed=+1.0 | FOV 106",Control=False,Shift=False,Alt=False,LeftTrigger=False,RightTrigger=False,bIgnoreCtrl=False,bIgnoreShift=False,bIgnoreAlt=False)
Bindings=(Name="D",Command="MoveBackward | Axis aBrake Speed=+1.0 | FOV 106",Control=False,Shift=False,Alt=False,LeftTrigger=False,RightTrigger=False,bIgnoreCtrl=False,bIgnoreShift=False,bIgnoreAlt=False)
Bindings=(Name="S",Command="StrafeLeft | FOV 106",Control=False,Shift=False,Alt=False,LeftTrigger=False,RightTrigger=False,bIgnoreCtrl=False,bIgnoreShift=False,bIgnoreAlt=False)
Bindings=(Name="F",Command="StrafeRight | FOV 106",Control=False,Shift=False,Alt=False,LeftTrigger=False,RightTrigger=False,bIgnoreCtrl=False,bIgnoreShift=False,bIgnoreAlt=False)
Bindings=(Name="SpaceBar",Command="advancedbutton bAdvancedButtonAux6 | FOV 106",Control=False,Shift=False,Alt=False,LeftTrigger=False,RightTrigger=False,bIgnoreCtrl=False,bIgnoreShift=False,bIgnoreAlt=False)


Note that I play with ESDF for movement keys, and Spacebar as Sprint. Also note that I like an FOV of 106 for my 1920x1200 resolution. Alter to taste.

Keybindings for FOV:

Go to my documents\games\borderlands\willowgame

open willowinput.ini
add
Bindings=(Name="F10",Command="FOV 90",Control=False,Shift=False,Alt=False)
Bindings=(Name="F11",Command="FOV 110",Control=False,Shift=False,Alt=False)

FOV Issues/Fix

FOV Key Causing All Keys to Do Nothing Fix
This works for steam players for sure, and after you do this your custom configs will work like the retail guys, nothing fancy you need to do because you are on steam.

Goto My Documents\My Games\Borderlands\WillowGame\Config\
1. (Optional?) Delete WillowInput.ini and then start and exit Borderlands to set everything to default.
2. Add a custom keybinding to WillowInput.ini's [WillowGame.WillowPlayerInput], its going to blank all your other inputs but THATS OKAY!
3. Start Borderlands and go to the Options menu on the title screen, Mouse/Keyboard, then Keybindings. You will notice they are all blank, press Reset To Defaults.
4. Exit Borderlands, and now open up your WillowInput.ini, you will notice the game has now stashed all of the default keybindings under [WillowGame.WillowPlayerInput] that weren't there before.
5. Add your custom FOV or whatever keybindings and you're good to go! No more adding something and having all of your keys not work.

Getting Rid of the Stupid Movies

To disable the startup movies:
-----------------------------
Within WillowEngine.ini:

Find:
[FullScreenMovie]
StartupMovies=2K_logo
StartupMovies=Gearbox_logo
StartupMovies=NVidia
StartupMovies=Loading
SkippableMovies=2K_logo
SkippableMovies=Gearbox_logo
SkippableMovies=Attract
SkippableMovies=NVidia

and comment out lines like so:

[FullScreenMovie]
;StartupMovies=2K_logo
;StartupMovies=Gearbox_logo
;StartupMovies=NVidia
;StartupMovies=Loading
;SkippableMovies=2K_logo
;SkippableMovies=Gearbox_logo
;SkippableMovies=Attract
;SkippableMovies=NVidia

Another solution:

Editing My Documents > MyGames> Borderlands > WillowGame > WillowEngine.ini

And changed the section FullScreenMovie to:

[FullScreenMovie]
SkippableMovies=2K_logo
SkippableMovies=Gearbox_logo
SkippableMovies=Attract
SkippableMovies=NVidia

Weaponbob

To disable/adjust weapon view bob:
----------------------------------
Within WillowGame.ini:
Search for "bWeaponBob" and you should come across the following lines:

bWeaponBob=TRUE
Bob=0.005

Enabling VSync

Within WillowEngine.ini:
Search for "UseVsync" and you should come across the following line:

UseVsync=False

Change to TRUE.

Disabling Voicechat

Within WillowEngine.ini:
Search for "bHasVoiceEnabled" and you should come across the following line:

bHasVoiceEnabled=True

Change to FALSE.

Mousesmoothing

Within WillowInput.ini:
Search for "bEnableMouseSmoothing" and you should come across the following line:

bEnableMouseSmoothing=True

Change to FALSE. Should improve the feel of the mouse when looking around and navigating the UI.

Port Forwarding Tips

I just hosted 5 hours of 4 player co-op on my own PC and to get it to work, all I needed to do was port forward the following (2Wire DSL Modem/Router):
7777 (TCP/UDP)
28900 (TCP)
27900 (UDP)
28910 (TCP)



However, a few minutes ago we decided to use my brothers PC to host instead, which is on a totally separate ISP but sits 6 feet away from me (yes, we have 2 separate ISP's in our home).

We could NOT connect to my brothers system, despite Ports being forwarded properly (Cable Modem to Linksys Router).

The fix was this:
-Go into Windows 7 Firewall (Control Panel -> System and Security -> Allow a program through Windows Firewall
-Click the Change Settings button at the top right.
-Make sure Borderlands has access to the PUBLIC.



This fixed the problem with using my brothers PC as a Server.

More Ports:

3783 (Voice Chat Port)
27900 (Master Server UDP Heartbeat)
28900 (Master Server List Request)
29900 (GP Connection Manager)
29901 (GP Search Manager)
13139 (Custom UDP Pings)
6515 (Dplay UDP)
6500 (Query Port)

Quest Box Scrolling (Full of Win)

Within WillowInput.ini

Search for all instances of the following (there should only be two instances):

InputKeyName="MouseScrollUp",ModifierKeyFlags=42
InputKeyName="MouseScrollDown",ModifierKeyFlags=42

remove the ",ModifierKeyFlags=42" so they look like:

InputKeyName="MouseScrollUp"
InputKeyName="MouseScrollDown"

[fuser]

Solution someone found from gbxforums

To enable scroll wheel in text boxes:
-----------------------------------
Within WillowInput.ini

Search for all instances of the following (there should only be two instances):

InputKeyName="MouseScrollUp",ModifierKeyFlags=42
InputKeyName="MouseScrollDown",ModifierKeyFlags=42

remove the ",ModifierKeyFlags=42" so they look like:

InputKeyName="MouseScrollUp"
InputKeyName="MouseScrollDown"

[Segoris]

Port forwarding tips, these are the right ports to forward and just took the first item on a google search so be warned: Link = vnboards

 

Solution someone found from gbxforums

To enable scroll wheel in text boxes:

 

[bhodi]

Additional ports you need to add... those on top aren't enough

EDIT: It's these two ports are important, the rest don't matter

6515 (Dplay UDP)
6500 (Query Port)


Also, I had to do this:

FOV Key Causing All Keys to Do Nothing Fix
This works for steam players for sure, and after you do this your custom configs will work like the retail guys, nothing fancy you need to do because you are on steam.

Goto My Documents\My Games\Borderlands\WillowGame\Config\
1. (Optional?) Delete WillowInput.ini and then start and exit Borderlands to set everything to default.
2. Add a custom keybinding to WillowInput.ini's [WillowGame.WillowPlayerInput], its going to blank all your other inputs but THATS OKAY!
3. Start Borderlands and go to the Options menu on the title screen, Mouse/Keyboard, then Keybindings. You will notice they are all blank, press Reset To Defaults.
4. Exit Borderlands, and now open up your WillowInput.ini, you will notice the game has now stashed all of the default keybindings under [WillowGame.WillowPlayerInput] that weren't there before.
5. Add your custom FOV or whatever keybindings and you're good to go! No more adding something and having all of your keys not work.

[Rasix]

Know of anyway to get the POV movement binds up there to play nice with vehicles? It constantly switches in and out.

[Hoax]

I tried to get mouse wheel scroll working and I think I removed the right lines but still no go.

[Draegan]

It worked for me alright.

[waffel]

The FOV fix is a huge pain in the ass. Binding it to movement keys makes is making me nauseous because of the constant zooming FOV in/out buggyness.

[schild]

There's 2 sets of INI, user and base in America. I could find nothing with the word Willow before it. Which confused the hell out of me the first time I read this stuff.

[Draegan]

This might be a cheat so I'll spoiler it, but I havn't tried it. 

I just found it on another forum:

[Morfiend]

I REALLY want the FOV fix, but it gives me motion sickness. I just want it to stick nice and large.

[Azazel]

This might be a cheat so I'll spoiler it, but I havn't tried it.  

I just found it on another forum:

Anyone tried this? I hate inventory juggling.

edit-

With regard to the port forwarding, it's bullshit to have to do this, and my lack of understanding makes me want to put my fist through my fucking monitor. And punch the gearbox people in the fucking throat.

Especially since I want to have BL installed on more than 1 machine, I assume I have to do this shit again for each machine? If I even fully understood what to type in where.

fucking clownshoes.

edit for Murgos - I've been playing various PC MP games for about 10 years now, and I've never had to manually screw around with my routers, which I've had for most of that time.

[Murgos]

I'm confused.  Port Forwarding was standard for a multiplayer game less then 2 years ago, why has everyone suddenly forgotten what that is or how to do it?

[Engels]

I think people might be confusing two things. One is opening up various ports in one's firewall. That's not Port Forwarding. Port forwarding is done on your router, dsl or cable modems. A brief rundown, for those who care:

You have your external IP and your LAN IP. Say you have two computers on your modem. They get IPs of, for example 192.168.0.10 and 192.168.0.11. Now, your machines are essentially hidden from the rest of the internet because all the internet knows is the IP of your modem, assigned by your ISP. Say its 122.44.22.56 (random number I made up).  In port forwarding, you tell the incoming packet stream to 122.44.22.56 on a specific port that the stream is meant to be directed to a specific LAN-side IP (192.168.0.11 for example). If you do not specify the request to forward that incoming packet to a specific IP, routers will ditch it outright.

At least that's my understanding of the mess.

[Segoris]

I found hardcore mode!

[WillowGame.WillowCoopGameInfo]
bIgnoreFriendlyFire=true

Anyone up for trying FF games? And now to fairly determine who plays Brick

1.2.3. not it!

[fuser]

I found hardcore mode!

I wonder how this effects rolands healing bullet talent, they damage and heal so it balances out? 

[Segoris]

All these are in the same game.ini as the inventory/friendly fire stuff, but here's some additional things:

[Engine.GameInfo]
bAdminCanPause=false
MaxPlayers=4
GameDifficulty=+1.0

[WillowGame.WillowPlayerController]
WeaponHandPreference=HAND_Right

The following are closer to cheats. But if anyone wants them:


Edited to add what I've tested in the spoiler in case anyone else wants to test different settings.

[Segoris]

I found hardcore mode!

I wonder how this effects rolands healing bullet talent, they damage and heal so it balances out? 

Also Mord's hawk and Roland's turret, do they aim for players as they'd most likely be the closest targets? Would be interesting to find out

[Draegan]

Here you go:

Third Person Camera (courtesy of [BoX]SteroidFreud):
----------------------------------------------------
Within WillowInput.ini:

Search for [WillowGame.WillowPlayerInput]. Below the chunk of bindings, add the following:

Bindings=(Name="F3",Command="Camera ThirdPerson",Control=False,Shift=False,Alt=False)
Bindings=(Name="F4",Command="Camera FirstPerson",Control=False,Shift=False,Alt=False)

F3 goes into third person, F4 switches back to first person. As such, you can swap out the keys (F3 and F4) to the keys of your liking.

[Draegan]

One more:

To make crouch momentary (instead of toggle, courtesy of siberx):
-----------------------------------------------------------------
Within WillowInput.ini:

Search for the following line under [WillowGame.WillowPlayerInput]:

advancedbutton bAdvancedButtonAux1 | SwitchSeats
and change to

Duck | SwitchSeats
You can remove the SwitchSeats variable if you do not wish to have the key switch seats as well.

If this doesn't work, make sure this line exists under [WillowGame.WillowPlayerInput], otherwise add it:

Bindings=(Name="Duck",Command="Button bDuck | Axis aUp Speed=-1.0 AbsoluteAxis=100",Control=False,Shift=False,Alt=Fa lse,LeftTrigger=False,RightTrigger=False,bIgnoreCt rl=False,bIgnoreShift=False,bIgnoreAlt=False)

[Morfiend]

Since you seem on top of this Dreagan, any word on a better fix for the FOV stuff?

The super close FOV is actually giving me nausea. In fact I played a bunch the other day and it was so bad I had to vomit and couldnt play the rest of the day.

[Draegan]

What kind of fix?  The above works ok with me.

I've heard that some issue may be solved if you sent the FOV keys to your strafe keys rather than your back and forth or W/S keys... instead of all four.

[Hoax]

I have to say the FOV fix is probably worse then not having it.  The constant shifting when I run or stop is a big fucking pain.  I haven't bothered with making the 2nd set of changes because from what I read you still get the in and out shit from vehicles and the like.  Gearbox said anything about a PC patch to take some of the console suck out of this "PC First" game? 

[Rasix]

Only thing that still bothers me is the vehicle FOV changing. Other than that, it's pretty much imperceptible to me on the ground (using the full tweak).  Would like a nice patch though to make it an ingame permanent setting.

[ezrast]

MaxPlayers=4

I'm sure that doesn't do what I first thought when I saw it, but we can dream, right?

Anyone up for trying FF games?

Pretty sure even on default mode I would be constantly dancing the line between being an asset and a detriment to the team, and FF would push me waaay over the boundary, but, yes. Yes I am.

[Engels]

Here you go:

Third Person Camera (courtesy of [BoX]SteroidFreud):
----------------------------------------------------
Within WillowInput.ini:

Search for [WillowGame.WillowPlayerInput]. Below the chunk of bindings, add the following:

Bindings=(Name="F3",Command="Camera ThirdPerson",Control=False,Shift=False,Alt=False)
Bindings=(Name="F4",Command="Camera FirstPerson",Control=False,Shift=False,Alt=False)

F3 goes into third person, F4 switches back to first person. As such, you can swap out the keys (F3 and F4) to the keys of your liking.

Hmm, I tried this, and the result was all keyboard keys and mouse were disabled -except for F3 and F4. What does Control, Shift and Alt =False mean?

[Sky]

For some reason all my ini tweaks got reset this morning. Re-applying them, I noticed a line about d3d10 when setting my vsync. A quick google later:

If you're running Borderlands on a Windows 7 platform, chances are you aren't actually running the game in DirectX 10. Why? Who knows. However, there is a very easy fix that will switch to the DirectX 10 render path and a few tweaks that will give you more visual eye candy to gawk at.

    1. Go to the directory --> C:\Users\[Your user Name]\Documents\My Games\Borderlands\WillowGame\Config
    a. Find the file WillowEngine.ini (make a copy and rename it as a backup)

    2. Find the section [SystemSettings]
    Change the following settings to True, you will see if you are currently in DX9 as well.

    - AllowD3D10=True (this is the key one to enable the DX10 render engine)
    Also change the following

    - MotionBlur=True

    - DepthOfField=True

    - Bloom=True

    - UseHighQualityBloom=True

    - FogVolumes=True

Also: bDisablePhysXHardwareSupport=False for physx on your gpu, if supported.

[rattran]

I've been running in dx10 for a while, the smoke/fog effects are damn nice, but I turned off depth of field, seems to blur stuff at too close a range.

[Yegolev]

The bit where it forgets that I set my resolution to 1680x1050 is bothersome.  I'm going to have to save an original and a modified version of the ini files, for great justice.

[Sky]

I've been running in dx10 for a while, the smoke/fog effects are damn nice, but I turned off depth of field, seems to blur stuff at too close a range.

I like how the blur will change depending on where you're pointing your gun with the iron sites pulled up.

[Murgos]

The bit where it forgets that I set my resolution to 1680x1050 is bothersome.  I'm going to have to save an original and a modified version of the ini files, for great justice.

Sunday, when we went to Daylight Savings Time, caused Borderlands to delete any .ini files with changed timestamps and recreate them.

[Sky]

 

[rattran]

I had to redo all my .ini fixes as well.

Finding some annoying bugs are cropping up, one toon has 5 equippable weapon slots now, and ones carry capacity has reverted from 36 to 18 for no discernable reason.

[Sky]

I had an odd bug pop up, my weapons don't scroll in order anymore. They always scroll in the same order, just not 1-2-3-4, it's like 3-2-4-1 or something.

Welcome to the big leagues, gearbox!

[ezrast]

They scroll in the order that you equip them, not by what slot they're in. So switching out a weapon in slot 2 means you have to re-equip 3 and 4 for it to be in the right order.