Some accounts on our forum were recently compromised due to password re-use and used to post malware.
Please review this list to see if you may have been affected, as well as our other changes in response to this.
Both can be true. Now more than ever they push features and technologies nobody asked for.
Ultimately, we don't recommend Limit FPS unless the user is hitting a very specific edge case that we feel might be solved by it. Most users definitely don't need it and arguably shouldn't enable it.
I'd also be curious to know if you were seeing that stuttering in the preview, the recording/stream, or both.
Also worth noting the setting was added in 2015 for low-spec PCs. How we run games (& how we encode video) has changed dramatically in that time. Not to mention hardware advances.
I personally agree, you should lower your game FPS when you can (for many reasons). Ideally, to a multiple of OBS FPS.
I'm quite sure the intent of the behaviour (Don't limit) is to allow the game to run at any FPS, and for OBS to be less likely to miss an important frame. It was designed around OBS 30fps, game & monitor at 60fps. OBS FPS runs independently from game FPS, there could be a timing desync on capture.
That forum post is incorrect in its description of the code.
The code grabs the obs_video_info, which is the output FPS (aka your canvas FPS). It does not check the FPS of the game/source. The comment states why, not what it's doing. interval /= 2 is 2x OBS output FPS (when not limiting capture).
As a Stargate enjoyer, absolutely not ;)
Though I do agree season length should better reflect the story being told, rather than arbitrary.
Looking to expand? A show takes 2 years to make, let alone the discussion and negotiations beforehand.
I had a DPS Zenyatta yesterday. In competitive. We won, somehow?
My workaround is via @deck.blue - you can at least mark them as read there.
I love #Overwatch, and I'm super passionate about UI that feels good (see @ow2ui.wizardcm.com)
With Season 1, they overhauled a large chunk of the UI, with the intent of "streamlining". I think they made some positive steps, but overall it introduces more issues than it solves.
So I wrote a list.
Good. We need new maps.
With the influx of players in Season 1, how has the popularity of various game modes changed (namely 6v6 and Stadium)?
Are there plans for more immersive Play Menu backgrounds, rather than the empty blue one?
A couple minor lines and interactions, but also it removes the entirely unnecessarily full frontal. It was required by the network but nobody actually wanted it, and it gives an entirely incorrect impression on the rest of the show.
Absolutely, though it's very unfortunate the first episode is not the director's cut as it will definitely turn off some viewers, understandably.
I could rant for HOURS about what I'm thrilled by in terms of gameplay and the future of the game.
I could probably rant just as long about the things that concern me, such as the new UI (which, based on what I've seen, solves few problems and adds a ton more).
And I will! I'll be LIVE Wednesday!
I'm so damn excited for #Overwatch Season 1.
5 new heroes this week, with 5 more throughout 2026.
Lore & story-based seasons, skins, events, & map changes.
More granular passives via sub-roles.
A (long overdue) lootbox refresh.
And, of course, dropping the 2.
It's a perfect time for new players.
I'm curious if they'll just remove the 2 without changing from the orange branding, as the 1 logo was yellow.
These days most of the functionality of that plugin is built in.
I'm very excited for Forza Horizon 6 after today's news.
I have fewer hours in FH1 & 2 compared to 3 onwards (3 was my first), so I'm going to play more of those before release, but FH5 ruined a number of multiplayer features that made 3 & 4 great.
I'll need to find friends to play with on release
Windows Update Settings page. Restart required (est. 3 min). Notably: "Your device will restart outside of active hours". The update listed is for the Secure Boot Allowed Key Exchange Key Update
The currently set Active Hours setting, configured for 9am to 5pm, with a note "We won't restart your device during these hours"
A dialog that appeared at 1:19pm, stating "We'll restart and install this update at 1:345pm" - which is during active hours.
It's 1:20pm. A story in 3 parts.
This is the second time in two weeks I've seen this happen. The first time (Patch Tuesday, day of), it did restart while I was eating lunch.
#Windows11
I use the "Search Fixer for YouTube" browser extension and it's a game changer. The fact YouTube are willing to have such a broken, unusable search is crazy.
At the same time, I do wish it wasn't such a *fragile* expensive supercomputer. Whole thing is glass, practically requires a case for protection, components almost impossible to replace if something happens. And then newer design trends like a camera bump mean you have to actively think about it.
Badass & of the time, probably.
He does tone down the Jaffa make-up over time, he's certainly less bronze than early episodes.
I'm unsure how far Chulak is from its two suns (junior would heal him anyway), but as O'Neill often wears sunglasses off-world maybe he assumed they'd help him blend in?
I am honestly surprised that VTube Studio doesn't handle transparency in the way macOS capture APIs expect it. I can confirm it doesn't work - their own documentation states to either add a Chroma Key filter or use NDI. github.com/DenchiSoft/V...
I'll continue my digging on both issues.
Based on my questioning internally, transparency should "just work" and there's no toggle in either. It was inconsistent for me on 15.6.1, but apparently works fine in non-legacy in 15.7.1 (Sequoia). I'm installing Tahoe now to see if it changes.
Are you willing to share which game is misbehaving?
Hotfixes have a much smaller scope so significantly less to potentially go wrong. Glad to hear it!
macOS Screen Capture (Window): * Only stores app code (eg `com.apple.Terminal`) and window ID * If matching window ID is gone, it no longer captures anything from the app * **BAD** Opening the properties resets the Window dropdown to the first in the list, resulting in it capturing a *different app* Deprecated Window Capture: * Stores app owner (eg `Terminal`), window name, owner PID and window ID * If matching window ID is gone, falls back to window name, and if that's gone too, no longer captures * **BETTER** Opening the properties leaves the old window in the list and greyed out, and does not blindly reset capture.
Likely. With my quick test as a Windows user, I find the existing behaviour confusing & have asked for clarification.
Long story short below. I'd personally want looser fallbacks, but I know macOS guidelines say to be strict to avoid accidental capture.
App capture more reliably uses app ID only.
Hmm, a quick test with a window capture on Terminal seems to persist fine with an OBS restart (both legacy and modern), but I'd have to check what identifiers it stores.
In terms of transparency, I do see the legacy method does it correctly, I'll ask internally.
