Screen Tearing and Stuttering/Skipping

[pinkdogfan]

I started playing this game last night and it ran just fine. Today when I load the save or even start a new game there is constant screen tearing on the same display lines constantly and the framerate is incredibly low and will skip ahead at times. I tried deleting the game and reinstalling but still have the issues. Any help is appreciated.

[Fruity Snacks]

First thing: Whats your computer specs?
Second thing: Right click Black Mesa in your Steam Library. Click "Properties" Then click "Set Launch options" in that type -windowed -fullscreen -borderless and launch the game, tell me if that helps.

[pinkdogfan]

Computer: LENOVO 10122
CPU: Intel Core i7-3820 (Sandy Bridge-E, M1)
3600 MHz (36.00x100.0) @ 1199 MHz (12.00x100.0)
Motherboard: LENOVO
Chipset: Intel C600/X79 (Patsburg)
Memory: 12288 MBytes @ 799 MHz, 11.0-11-11-28
- 4096 MB PC12800 DDR3 SDRAM - SK Hynix HMT451U6AFR8C-PB
- 4096 MB PC12800 DDR3 SDRAM - SK Hynix HMT451U6AFR8C-PB
- 4096 MB PC12800 DDR3 SDRAM - SK Hynix HMT451U6AFR8C-PB
Graphics: EVGA e-GeForce GTX 770
NVIDIA GeForce GTX 770, 4096 MB GDDR5 SDRAM
Drive: WDC WD10EURX-73FH1Y0, 976.8 GB, Serial ATA 6Gb/s @ 6Gb/s
Drive: ST3000DM001-1CH166, 2930.3 GB, Serial ATA 6Gb/s @ 6Gb/s
Drive: SAMSUNG MZ7TD128HAFV-000L1, 125.0 GB, Serial ATA 6Gb/s @ 6Gb/s
Drive: HL-DT-ST DVD-RAM GHA2N, DVD+R DL
Sound: Intel Patsburg PCH - High Definition Audio Controller [C1]
Sound: NVIDIA GK104 - High Definition Audio Controller
Network: RealTek Semiconductor RTL8188CE Wireless LAN 802.11n PCI-E Network Adapter
Network: RealTek Semiconductor RTL8168/8111 PCI-E Gigabit Ethernet NIC
OS: Microsoft Windows 10 Professional Build 10586


Also, "-borderless" is not a valid argument for Source games. The correct syntax is "-noborder".

And finally, running with "-windowed -noborder" did in fact fix the odd issues.

[Turbo Nozomix]

Hey BM team, can an option for borderless widowed be added to the in-game window options?

[Fruity Snacks]

Originally posted by Lupin Saiko:

Also, "-borderless" is not a valid argument for Source games. The correct syntax is "-noborder".

And finally, running with "-windowed -noborder" did in fact fix the odd issues.

Whoops! My bad. You are correct.

Originally posted by Turbo Nozomix:

Hey BM team, can an option for borderless widowed be added to the in-game window options?

I can put in a feature request.

[Turbo Nozomix]

Originally posted by Fr0z3nR:

Originally posted by Turbo Nozomix:

Hey BM team, can an option for borderless widowed be added to the in-game window options?

I can put in a feature request.

Thanks.

Is there a known particular reason why windowed runs so much better than fullscreen on some cards?

I'm using an R9 280x, and the performance gain in windowed is significant.

[thray]

Looks like it only happens on some Windows 10 systems and not all, possibly driver related, devs are looking into it as you're aware.

[Turbo Nozomix]

I've experienced it on my Windows 7 Ultimate 64 system

i5 2500k
16 GB 1866mhz RAM
R9 280x

Using the latest Catalyst non-beta driver, before Crimson. I reverted to Catalyst because Crimson was causing some issues for me.

[Fruity Snacks]

Originally posted by Turbo Nozomix:

Originally posted by Fr0z3nR:

I can put in a feature request.

Thanks.

Is there a known particular reason why windowed runs so much better than fullscreen on some cards?

I'm using an R9 280x, and the performance gain in windowed is significant.

I have absolutely no idea, I'm not a programmer :D

[lozhensel]

-windowed -fullscreen -noborder worked for me too. Thanks.

Manjaro Linux, nVidia 3050. Tearing was annoying but not unplayable with vsync enabled, that set of launch commands fixed the problem entirely