f13.net

f13.net General Forums => Gaming => Topic started by: Draegan on October 27, 2009, 11:09:27 AM



Title: Borderlands .INI Stuff
Post by: Draegan on October 27, 2009, 11:09:27 AM
All this is from the Borderlands thread.  I'm merely grouping it all together.  


FOV Stuff

Quote
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:
Quote
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
Quote
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
Quote
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:
Quote
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
Quote
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
Quote
Within WillowEngine.ini:
Search for "UseVsync" and you should come across the following line:

UseVsync=False

Change to TRUE.

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

bHasVoiceEnabled=True

Change to FALSE.

Mousesmoothing
Quote
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
Quote
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:
Quote
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)
Quote
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"


Title: Re: Borderlands .INI Stuff
Post by: fuser on October 27, 2009, 11:17:07 AM
Solution someone found from gbxforums
Quote
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"


Title: Re: Borderlands .INI Stuff
Post by: Segoris on October 27, 2009, 11:18:27 AM
Port forwarding tips (http://boards.ign.com/pc_general_board/b5027/186362501/p1/?6), 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
Quote
To enable scroll wheel in text boxes:

 :heart:


Title: Re: Borderlands .INI Stuff
Post by: bhodi on October 27, 2009, 12:11:22 PM
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.


Title: Re: Borderlands .INI Stuff
Post by: Rasix on October 27, 2009, 02:06:33 PM
Know of anyway to get the POV movement binds up there to play nice with vehicles? It constantly switches in and out.


Title: Re: Borderlands .INI Stuff
Post by: Hoax on October 27, 2009, 05:56:54 PM
I tried to get mouse wheel scroll working and I think I removed the right lines but still no go.


Title: Re: Borderlands .INI Stuff
Post by: Draegan on October 27, 2009, 09:35:31 PM
It worked for me alright.


Title: Re: Borderlands .INI Stuff
Post by: waffel on October 27, 2009, 10:08:37 PM
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.


Title: Re: Borderlands .INI Stuff
Post by: schild on October 27, 2009, 11:01:17 PM
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.


Title: Re: Borderlands .INI Stuff
Post by: Draegan on October 28, 2009, 06:12:58 AM
This might be a cheat so I'll spoiler it, but I havn't tried it. 

I just found it on another forum:



Title: Re: Borderlands .INI Stuff
Post by: Morfiend on October 28, 2009, 02:19:45 PM
I REALLY want the FOV fix, but it gives me motion sickness. I just want it to stick nice and large.


Title: Re: Borderlands .INI Stuff
Post by: Azazel on October 30, 2009, 02:11:23 AM
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.


Title: Re: Borderlands .INI Stuff
Post by: Murgos on October 30, 2009, 06:25:45 AM
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?


Title: Re: Borderlands .INI Stuff
Post by: Engels on October 30, 2009, 09:05:20 AM
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.


Title: Re: Borderlands .INI Stuff
Post by: Segoris on October 30, 2009, 09:46:43 AM
I found hardcore mode!

Quote
[WillowGame.WillowCoopGameInfo]
bIgnoreFriendlyFire=true
Anyone up for trying FF games? And now to fairly determine who plays Brick

1.2.3. not it!


Title: Re: Borderlands .INI Stuff
Post by: fuser on October 30, 2009, 09:51:35 AM
I found hardcore mode!

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


Title: Re: Borderlands .INI Stuff
Post by: Segoris on October 30, 2009, 09:56:24 AM
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.


Title: Re: Borderlands .INI Stuff
Post by: Segoris on October 30, 2009, 09:57:37 AM
I found hardcore mode!

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

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


Title: Re: Borderlands .INI Stuff
Post by: Draegan on October 30, 2009, 12:31:43 PM
Here you go:

Quote
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.


Title: Re: Borderlands .INI Stuff
Post by: Draegan on October 30, 2009, 12:32:54 PM
One more:

Quote
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)


Title: Re: Borderlands .INI Stuff
Post by: Morfiend on October 30, 2009, 04:22:03 PM
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.


Title: Re: Borderlands .INI Stuff
Post by: Draegan on October 30, 2009, 05:46:34 PM
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.


Title: Re: Borderlands .INI Stuff
Post by: Hoax on October 30, 2009, 10:46:08 PM
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?  :awesome_for_real:


Title: Re: Borderlands .INI Stuff
Post by: Rasix on October 30, 2009, 11:15:31 PM
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.


Title: Re: Borderlands .INI Stuff
Post by: ezrast on October 31, 2009, 10:29:02 AM
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.


Title: Re: Borderlands .INI Stuff
Post by: Engels on October 31, 2009, 11:45:06 AM
Here you go:

Quote
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?


Title: Re: Borderlands .INI Stuff
Post by: Sky on November 01, 2009, 08:35:35 AM
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:
Quote
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.


Title: Re: Borderlands .INI Stuff
Post by: rattran on November 01, 2009, 03:31:04 PM
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.


Title: Re: Borderlands .INI Stuff
Post by: Yegolev on November 02, 2009, 06:50:06 AM
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.


Title: Re: Borderlands .INI Stuff
Post by: Sky on November 02, 2009, 07:12:15 AM
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.


Title: Re: Borderlands .INI Stuff
Post by: Murgos on November 02, 2009, 08:07:08 AM
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.


Title: Re: Borderlands .INI Stuff
Post by: Sky on November 02, 2009, 09:03:18 AM
 :oh_i_see:


Title: Re: Borderlands .INI Stuff
Post by: rattran on November 02, 2009, 10:57:27 AM
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.


Title: Re: Borderlands .INI Stuff
Post by: Sky on November 02, 2009, 11:21:33 AM
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!


Title: Re: Borderlands .INI Stuff
Post by: ezrast on November 02, 2009, 01:06:28 PM
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.


Title: Re: Borderlands .INI Stuff
Post by: Sky on November 02, 2009, 01:25:48 PM
It never did that before, slot 1 was always my rotating slot for situational weapons. 2 has always been my MG and 3 my sniper, now 4 is my RPG.


Title: Re: Borderlands .INI Stuff
Post by: Hoax on November 16, 2009, 03:05:10 PM
Ok, so is there a fov fix that works all the time yet?  I haven't changed my ini since it got reset because its better just having the crap fov then having it zoom in and out all the damn time.

Also anyone had luck with the font hack so that you can see more weapon text?


Title: Re: Borderlands .INI Stuff
Post by: Lantyssa on November 16, 2009, 03:51:47 PM
The font hack works fine for me (as my screenshots show).  I didn't do anything special.


Title: Re: Borderlands .INI Stuff
Post by: Hoax on November 19, 2009, 09:31:33 PM
Quote
I noticed when I was tweaking shadows versus no shadows, ambient occlusion versus none, etc, that even when Fraps showed 50 fps, the game still felt pretty unresponsive.

Then I came across two ini settings that made a pretty big difference, and now I'm sharing.

1) There's a bool setting in WillowEngine.ini: "OneFrameThreadLag=true"
Change it to false if you don't want one frame of lag between your mouse motion and rendering. This made heaps of difference for me and finally made 50fps feel like 50fps. (Edit: oh and I also have mouse smoothing turned off, I've never used it in games and it just sounds like more "add lag please").


2) There are settings for "framerate smoothing" also in WillowEngine.ini. It's probably something like:

bSmoothFrameRate=TRUE
MinSmoothedFrameRate=22
MaxSmoothedFrameRate=62

I suggest simply changing it to bSmoothFrameRate=FALSE, or at least setting MaxSmoothedFrameRate really high.

As far as I can tell, the default settings try to do a few things:

a) enforce a max framerate. Even if the game can run at 70 fps, you'll only get 62.
b) tries to enforce a min framerate, presumably by dropping effects or something.
c) tries to "smooth" framerate changes. Now this one is perplexing, but here is what I saw: When using Fraps to look at fps, with smoothing on, toggling shadows (which massively kills my framerate) would drop me to 30 fps, then turning it off would slowly ramp back up to my max for the scene, say 60fps. Now, if you turn off smoothing, it will immediately go to 60 if possible. This also means that if you're in a huge battle with a slow framerate, and look another direction where you'd potentially get a good framerate, then look back, it will actually give you a crap framerate the entire time in an attempt to "smooth" the transition.

Hope this helps

This worked for me, this fucking game...


Title: Re: Borderlands .INI Stuff
Post by: fuser on November 20, 2009, 06:53:24 AM
I really wish someone had the time to write a app to adjust this stuff, perhaps time to attempt to learn c#?


Title: Re: Borderlands .INI Stuff
Post by: Yegolev on November 20, 2009, 08:35:05 AM
I really wish someone had the time to write a app to adjust this stuff, perhaps time to attempt to learn c#?

This sort of shit was a big impetus for me to take up C#, unfortunately I don't have the time or brainpower to diverge from my work-related learnings.  However in principle it should be easy enough to do... I'm led to believe C# has "robust" search/replace.


Title: Re: Borderlands .INI Stuff
Post by: Lantyssa on November 20, 2009, 09:46:23 AM
Could be done in just about any language if you just want a script to rewrite stuff.  It's all distinct variables.


Title: Re: Borderlands .INI Stuff
Post by: Yegolev on November 20, 2009, 11:00:57 AM
True, if it was just for me I'd do it in perl, but installing/configuring/rawr.rawr.rawr AS Perl seems like more work than just editing the file directly.


Title: Re: Borderlands .INI Stuff
Post by: Quinton on July 04, 2010, 09:15:06 PM
I'm awful late to the party here (just bought Borderlands today for $11 on Steam)... the game looks fantastic but it seems to have some rending weirdness when I'm moving -- like the background ripples a bit as I move that's seriously messing with me (worse even than the crazy FOV I think).  Anybody else seen this?  Win7, Quadcore i7, Nvidia Geforce GTX 260.

Turning on vsync helped fix the tearing but the ripple business is seriously making me feel ill.  Bleah!


Title: Re: Borderlands .INI Stuff
Post by: Shrike on July 04, 2010, 10:36:53 PM
I have similar hardware (only difference is I run an i5-750). I have vsync enabled, but haven't seen any sort of other visual artifacts like you've described.

The only thing I can think of offhand is something I saw in ME. There was a motion blur effect in the game by default that drove me nuts until I turned it off. Perhaps something like that is enabled.


Title: Re: Borderlands .INI Stuff
Post by: Quinton on July 04, 2010, 10:53:09 PM
After playing a bit more, I've noticed that the juddering/rippling only happens when I'm moving the mouse.  If I just walk with the WASD keys, things are fine (and not motion-sickness-inducing).  It's like the mouse tracking is kinda off.  I've tried turning off mouse smoothing in the ini but it doesn't seem to make much difference.  Weird.


Title: Re: Borderlands .INI Stuff
Post by: Engels on July 04, 2010, 11:14:13 PM
When Borderlands first came out, there were a ton of .ini and other tweaks that had to be done to fix any number of wierdnesses. I -thought- mouse tracking was one of them, but there are others.  I would check steam forums and maybe back pages here, although I don't envy you the task of sifting through our clutter.


Title: Re: Borderlands .INI Stuff
Post by: Sheepherder on July 04, 2010, 11:35:13 PM
Is it some sort of Bilinear / Trilinear / Anisotropic Filtering issue?


Title: Re: Borderlands .INI Stuff
Post by: Engels on July 05, 2010, 01:18:38 PM
Might have to do with V-Sync. I doubt that filtering would affect mouse movement.


Title: Re: Borderlands .INI Stuff
Post by: Lantyssa on July 05, 2010, 08:06:18 PM
I was getting weird shadow effects yesterday when I was fine the last time I played.  Turning off dynamic shadows fixed my issue.


Title: Re: Borderlands .INI Stuff
Post by: Sheepherder on July 06, 2010, 03:07:55 PM
Might have to do with V-Sync. I doubt that filtering would affect mouse movement.

His isn't.  He said the problem is caused by mouse movement.  And that textures is the distance seem to be rippling and distorting.  Sounds like texture crawling.  Which usually means something is wrong with texture filtering.


Title: Re: Borderlands .INI Stuff
Post by: Quinton on July 06, 2010, 10:48:07 PM
Disabling dynamic shadows and some of the other bells and whistles helped.  Adjusting texture quality has no impact (HIGH is fine).

I think the more severe issue for me may actually just be the unreal engine and the 90 degree FOV -- I haven't been this motion-sick since I played UT years ago.  I love the game but it makes me ill.  No fun.


Title: Re: Borderlands .INI Stuff
Post by: Sheepherder on July 07, 2010, 11:23:09 PM
Texture quality is likely mipmapping level of detail, which isn't the same thing.


Title: Re: Borderlands .INI Stuff
Post by: Sky on July 08, 2010, 07:34:10 AM
I think the more severe issue for me may actually just be the unreal engine and the 90 degree FOV -- I haven't been this motion-sick since I played UT years ago.  I love the game but it makes me ill.  No fun.
There is an fov hack in this thread.

Game hates my computer in 3D, first game I found unplayable due to gpu lag, even on my old 8800gtx. Probably because there's so much going on, but my guess is there's some poor optimization lurking in there, too.