• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

Borderlands 4

Game is still randomly crashing, often at most annoying parts like right before completing a boss kill, this is f'ed up...this is with everthing at stock. Worse than the CP2077 launch fiasco.
 
Did you see any difference in performance? I just tried this on an ARC B580. I tried it on the badass preset to test just to make sure all the effects were enabled. It definitely did something because the colors are quite different, but shadows are about the same and I don't see any perceivable difference in performance so far.

No there's no difference in performance. I think it's just a matter of which way you prefer the game to look.
 
I’ve had a couple crashes but only while launching the game, and by a couple I mean literally twice. Haven’t had a single one while in game. I turned some settings down and am now in the 90-100 fps range on my dated 4080 desktop at 4K. Again, these numbers should be obtainable at native res but I really don’t care, my experience has been mostly stutter free and it’s fun as hell.
 
I’ve been playing with a friend and it’s been a super fun time, even better than solo I think. I got a legendary sniper rifle that does 270 damage, it one hit and much of the time an instant kill. I really enjoy the Toque shotguns just like previous Borderlands, they have explosive rounds which do a lot of damage, I just can’t use it up close or I can kill myself. 😂
I’m having zero issues running the game, I can maintain over 100 fps on bad ass settings using DLSS quality and FG. Only one crash and that was starting the game before the last patch, no issues since.
 
Well something is definitely up with the game, I am not the only one experiencing major issues. And no other game including UE5 games have the same issue. Ran OCCT for an extended time last night to check stability including 3D and everything was stable as can be.
 
I've not seen stability issues either. Everything stock on badass settings.

I did see my CPU thermal throttle launch day as it compiled shaders for the first time. The game rarely does that though. It will do a short shader compile when you're loading into the game, but that's such a short burst I never see it jump past 95C like it did that first day.

Edit: According to Steam, I'm only 15 hours in.
 
Last edited:
Hit level 22 or 23. About 17 hours in. Played most of the weekend. Before weekend I was about 8 hours in - means I spent like 9 hours on it.

Game is great. Btw I tried the undertaker setting but it made lag hit almost 60 ms. Yeah not for me. I am staying with DLSS Q and FG 2X.
 
You need DLSS at full res and still enable FG4 ^, should be similar since hardware is pretty comparable. Trying a few things now including disabling NV audio drivers that can sometimes cause issues and running a OCCT validated clock at 100% power, +150 core, +1000 mem. Re-enabing all badass settings including DLSS Q + FG 4, stable this morning but will see if it holds up.
 
You need DLSS at full res and still enable FG4 ^, should be similar since hardware is pretty comparable. Trying a few things now including disabling NV audio drivers that can sometimes cause issues and running a OCCT validated clock at 100% power, +150 core, +1000 mem. Re-enabing all badass settings including DLSS Q + FG 4, stable this morning but will see if it holds up.
Post your frameview?
Second photo is DLSS Q FG 2X
First photo is DLSS Full Res FG 4X

There is a huge latency issue. Btw second photo came much better but actual latency was almost hitting 60-70 ms.
 

Attachments

  • Screenshot 2025-09-21 222513.png
    Screenshot 2025-09-21 222513.png
    3.1 MB · Views: 0
  • Screenshot 2025-09-21 222436.png
    Screenshot 2025-09-21 222436.png
    3.1 MB · Views: 0
If you're trying to reduce latency, full resolution will be worse.
 
I really enjoy the Toque shotguns just like previous Borderlands, they have explosive rounds which do a lot of damage, I just can’t use it up close or I can kill myself. 😂
I’m

This is where I love the double jump. Hit it while back pedaling and aim down, boom, boom , boom. So fun!
 
If you're trying to reduce latency, full resolution will be worse.
VSync also adds another frame of latency. Disable VSync and cap your framerate below your display's threshold if you can't stand tearing.
 
That's what G-Sync/FreeSync are for.

You can still tear with VRR if the frametime fluctuates, though it'll probably tear at the very bottom of the screen.

The only way to avoid this is to enable Vsync, which non-intuitively enables a compensation mechanism for this. There is no latency penalty for this.

If you have Reflex enabled with vsync, it will automatically limit framerate to keep you in VRR range and prevent vsync from needing to kick in.

Reflex + Vsync enabled is the lowest latency, smoothest, and completely tear free way you can use gsync.
 
You need V-Sync to eliminate tearing...
True only for certain types of monitors. But even then, likely you need 60fps, which you still might have to work at a bit settings wise. Today, most gaming oriented monitors have some sort of variable refresh capability (freesync/gsync). Sometimes games will do better if they have their own "cap" setting vs. just doing it all with a vsync on monitors that lack VRR.
 
True only for certain types of monitors. But even then, likely you need 60fps, which you still might have to work at a bit settings wise. Today, most gaming oriented monitors have some sort of variable refresh capability (freesync/gsync). Sometimes games will do better if they have their own "cap" setting vs. just doing it all with a vsync on monitors that lack VRR.

You need freesync/gsync…..

This is not entirely sufficient to never tear. You can still tear on a VRR monitor if frametimes aren't steady.

It just tends to be subtle. You will most likely catch it at the very bottom of the screen.

At least on Nvidia, enabling vsync has special behavior in VRR range and instead just enables the feature to compensate for frametime variance.

Again, at least on Nvidia hardware, even on a gsync display, you must enable vsync to absolutely guarantee no tearing under any circumstances. This is free performance wise and the best way to use it. Reflex detects this and will automatically cap your FPS - you do not need another limiter.
 
Again, at least on Nvidia hardware, even on a gsync display, you must enable vsync to absolutely guarantee no tearing under any circumstances. This is free performance wise and the best way to use it. Reflex detects this and will automatically cap your FPS - you do not need another limiter.

Agreed, especially with tearing at the bottom of the screen. In game - disable V-sync. In Nvidia app, enable G-Sync, and enable V-Sync. Your frame rates won't be locked to 30/60/120 if you do this, some people get confused by this.

Also the newer monitors without the physical module have a G-Sync range, the ones with the module typically support from 1 to the max refresh rate. Often it is 40-44 frame rates to max refresh rate for the ones without the module.
 
Screenshots below (the moon on the right is second monitor since I used prtsc), the most stable setting for me is DLSS set to Full Res + FG 4X, frame rates average around 170 and latency around 25 ms. GSync + NV Reflex On, FPS capped to 240 coz that's my monitor's ceiling. DLSS Quality + FG4 usually crashes with an nv event 153, everything else is super stable. For those that are getting no errors wonder if the system is bare-bones i.e. minimal drives and single monitor.
KickAssCop your system is very similar so not sure why your latency is double.
First pic is everything badass + DLSS Q + FG4, around 220-240 fps, latency of 15 ms, second pic is everything badass + DLSS Full Res + FG4, around 170 fps, latency 25 ms.
 

Attachments

  • Screenshot (3).png
    Screenshot (3).png
    1.2 MB · Views: 0
  • Screenshot (2).png
    Screenshot (2).png
    1.3 MB · Views: 0
Last edited:
All I can think of is why all the space
Ssd/hdd deals accumulated over the years..and I'm lazy and never delete stuff. Realized I had the original dying light still installed while playing the beast this weekend 🙃
I'm usually very good about selling any old parts ASAP but with memory and ssds unless you have top end high capacity stuff you want to get rid of, the time to sell them isn't worth the effort. My 840 pro 256 gb still works flawlessly but probably worth nothing now...
 
Screenshots below (the moon on the right is second monitor since I used prtsc), the most stable setting for me is DLSS set to Full Res + FG 4X, frame rates average around 170 and latency around 25 ms. GSync + NV Reflex On, FPS capped to 240 coz that's my monitor's ceiling. DLSS Quality + FG4 usually crashes with an nv event 153, everything else is super stable. For those that are getting no errors wonder if the system is bare-bones i.e. minimal drives and single monitor.
KickAssCop your system is very similar so not sure why your latency is double.
First pic is everything badass + DLSS Q + FG4, around 220-240 fps, latency of 15 ms, second pic is everything badass + DLSS Full Res + FG4, around 170 fps, latency 25 ms.
Post using frame view. I don’t understand these latency numbers and most likely the game numbers are not reliable.

Only other thing can be resolution. I am running 4K. (Can’t see clearly what res you are running because of the moon).
 
Screenshots below (the moon on the right is second monitor since I used prtsc), the most stable setting for me is DLSS set to Full Res + FG 4X, frame rates average around 170 and latency around 25 ms. GSync + NV Reflex On, FPS capped to 240 coz that's my monitor's ceiling. DLSS Quality + FG4 usually crashes with an nv event 153, everything else is super stable. For those that are getting no errors wonder if the system is bare-bones i.e. minimal drives and single monitor.
KickAssCop your system is very similar so not sure why your latency is double.
First pic is everything badass + DLSS Q + FG4, around 220-240 fps, latency of 15 ms, second pic is everything badass + DLSS Full Res + FG4, around 170 fps, latency 25 ms.

Are you sure you're not looking at render latency instead of PC latency? The numbers look impossible for frame gen.

In the first example, your base framerate would be around 60~. Which would be around your 15ms number alone without the frame gen cost on top.

Same with the next. 170/4 is like 43 fps, which would be around 23ms frame time. Again, it's suspiciously close to the actual base frame time.

I'm pretty sure you're seeing the render latency and effectively excluding the frame gen cost.
 
Ssd/hdd deals accumulated over the years..and I'm lazy and never delete stuff. Realized I had the original dying light still installed while playing the beast this weekend 🙃
I'm usually very good about selling any old parts ASAP but with memory and ssds unless you have top end high capacity stuff you want to get rid of, the time to sell them isn't worth the effort. My 840 pro 256 gb still works flawlessly but probably worth nothing now...
I do have some drives laying around, a couple SSD's, one NVME and even a few sata hard drives, I only use a SSD for a clone drive and the rest are not hooked up but in storage.
 
In game - disable V-sync. In Nvidia app, enable G-Sync, and enable V-Sync. Your frame rates won't be locked to 30/60/120 if you do this, some people get confused by this.
Yeah, I'm definitely confused. Unless I'm losing my memory, which is entirely plausible, the old instruction was that V-sync had to be turned off for G-sync.

So we turn it on globally in the Nvidia app? And we're supposed to set G-sync to full screen and window mode on Win 11?
 
Yeah, I'm definitely confused. Unless I'm losing my memory, which is entirely plausible, the old instruction was that V-sync had to be turned off for G-sync.

So we turn it on globally in the Nvidia app? And we're supposed to set G-sync to full screen and window mode on Win 11?

Turn Reflex on, enable Vsync however you want. That's it.

You'll know it's working as intended because the Reflex frame limiter will kick on the second you toggle vsync to keep you in VRR range and prevent vsync from actually needing to engage.

At this point it will pace frames and be properly tear free.

Also the Reflex limiter doesn't just cap you a few FPS below refresh rate. It's frame time based. It's your refresh rate - a 0.4ms buffer. On a 240hz display, it'll cap at like 225.
 
Last edited:
Yeah, I'm definitely confused. Unless I'm losing my memory, which is entirely plausible, the old instruction was that V-sync had to be turned off for G-sync.

So we turn it on globally in the Nvidia app? And we're supposed to set G-sync to full screen and window mode on Win 11?
I’ve been using G-sync for years and always have disabled V-sync.
 
Yeah, I'm definitely confused. Unless I'm losing my memory, which is entirely plausible, the old instruction was that V-sync had to be turned off for G-sync.

So we turn it on globally in the Nvidia app? And we're supposed to set G-sync to full screen and window mode on Win 11?

You can do it globally or per specific game (in driver settings). In the game itself, disable it. Under driver settings I do this:

Untitled.jpg


Works well. I cap FPS at 141 to keep below 144 (max refresh rate on my monitor). If I disable V Sync, I get screen tearing at the bottom of the screen which can be distracting.

You results might be a bit different, my monitor has the physical G Sync module. I am not sure if this behavior changes on monitors that are G Sync certified without the module.
 
You can do it globally or per specific game (in driver settings). In the game itself, disable it. Under driver settings I do this:

View attachment 755692

Works well. I cap FPS at 141 to keep below 144 (max refresh rate on my monitor). If I disable V Sync, I get screen tearing at the bottom of the screen which can be distracting.

You results might be a bit different, my monitor has the physical G Sync module. I am not sure if this behavior changes on monitors that are G Sync certified without the module.

I have a gsync "compatible" OLED and this behavior still holds true.

Just to make sure I'm not talking shit, I went into CS2 and bound a key to rotate in a circle. It's actually pretty hard to spot, but it indeed tears at the bottom. Both the monitor and game say gsync is active. This is with the in-game FPS limiter keeping it in range.

The second you enable vsync, this is resolved. Even at 240hz it looks even smoother. In-game latency stays the same.

CS2 actually even has a notice now telling you to use do this now. If you turn on Gsync, it will pop up a recommendation that you enable Reflex and Vsync as well.
 
If you are using Gsync/Gsync compatible and not exceeding your monitors refresh rate there should be no need to enable Vsync, you can always cap your frames such as I do playing a game like HL2. That's how I've been doing things since 2020 and my first Gsync compatible Dell monitor, I've never had issues with tearing or anything else. Currently I have a 360 refresh rate on my Alienware monitor so I don't worry about anything.
 
If you are using Gsync/Gsync compatible and not exceeding your monitors refresh rate there should be no need to enable Vsync, you can always cap your frames such as I do playing a game like HL2. That's how I've been doing things since 2020 and my first Gsync Dell monitor, I've never had issues with tearing or anything else. Currently I have a 360 refresh rate on my Alienware monitor so I don't worry about anything.

Gsync originally had the same (forced) behavior as the current gsync + vsync combo.

https://blurbusters.com/gsync/gsync101-input-lag-tests-and-settings/

https://blurbusters.com/gsync/gsync101-input-lag-tests-and-settings/2/

Upon its release, G-SYNC’s ability to fall back on fixed refresh rate V-SYNC behavior when exceeding the maximum refresh rate of the display was built-in and non-optional. A 2015 driver update later exposed the option.

This update led to recurring confusion, creating a misconception that G-SYNC and V-SYNC are entirely separate options. However, with G-SYNC enabled, the “Vertical sync” option in the control panel no longer acts as V-SYNC, and actually dictates whether, one, the G-SYNC module compensates for frametime variances output by the system (which prevents tearing at all times. G-SYNC + V-SYNC “Off” disables this behavior


View: https://youtu.be/5mWMP96UdGU
 
Back
Top