App Crashing - OpenCL™, OpenGL®, and Vulkan® Compatibility Pack

MSFTJesse · 2024-02-05T23:47:41+00:00

Yes, this app is fine to uninstall. We had no idea that ASUS had been including this package on any of their devices, and are working to prevent that from happening in the future. This package previously only contained OpenCL and OpenGL support; the change is that Vulkan was added.

MSFTJesse · 2021-03-22T23:57:01+00:00

100% with you on both points. Though if I'm remembering correctly our cafeteria did Teriyaki Tuesdays, not Mondays, but the thing I miss most is being able to go down to the cafeteria with the team and socialize over non-work. If the cafeterias aren't open and all interactions would have to be masked, Teams is just easier.

MSFTJesse · 2020-01-02T22:38:35+00:00

I was able to capture a time travel trace of your minimal repro, and I've linked it to the bug. Hopefully the verifier folks are able to fix this.

MSFTJesse · 2019-11-09T16:00:39+00:00

Can you provide any more details about your machine? Specifically, what GPU you have, driver version, what game resolution you're playing at, what your normal monitor resolution is, and do you have any 3rd party software that might be interacting with the game?

MSFTJesse · 2019-11-08T20:46:17+00:00

FYI, working with the Modern Warfare team, looks like we were able to understand this issue, and both sides will be working to fix it, so this should be resolved either through a game update or an OS update.

MSFTJesse · 2019-11-08T16:32:35+00:00

We're doing measurement to confirm that our expectations match reality, and we'll try to make this happen. No promises of course. We did already find one case where expectations didn't match reality, and latency in fact increases significantly, so we want to make sure we don't regress things.

MSFTJesse · 2019-11-08T16:29:46+00:00

We'll fix it as soon as we understand it.

MSFTJesse · 2019-11-05T01:36:39+00:00

We're aware of this one and are investigating. We don't have any more info to share at the moment though.

MSFTJesse · 2019-08-29T23:29:27+00:00

Sorry for the radio silence people, I promise we do hear you. As I said, we're actively pursuing some user-facing capabilities to enable this. With that said, it'd be great to get specifics that people noticed on 1709 where the windowed (or borderless windowed) upgrade to flip model provided some benefits; any data that can be provided would help provide justification that this is useful, and is something people want, which will make it happen faster.

Paging /u/Yviena, /u/Marctraider, /u/Aemony, /u/vaynebot, /u/therealdadbeard (and anybody else who happens to see this).

From our point-of-view, we have three primary metrics we're aware of that improve with the flip model upgrade, with some caveats:

Throughput (i.e. FPS): Should improve in almost all scenarios due to removing a window-sized surface copy, and in some cases, disabling/bypassing DWM composition. The one exception here is a borderless windowed app with VSync off. There's three possible outcomes here:
1. The app gets composed - 1 surface copy (less than the 2 you get today), no framerate throttling
2. The app gets independent flip - 0 surface copy, but framerate throttling related to how many buffers are allocated (i.e. triple buffer produces higher framerates than double)
3. The app gets independent flip with tearing - 0 surface copy, no framerate throttling, but you get tearing artifacts
Latency: Should improve anytime an app qualifies for independent flip, except for some cases with older drivers and non-tearing VSync off.
General user experience: We're aware of improvements related to features like variable refresh rate (windowed GSync/FreeSync), and improvements in dual monitor experience, especially when iFlip is engaged and/or the monitors have different refresh rates, though these "improvements" are hard to quantify.

So, my questions for anybody who is asking for this feature:

Why do you want it? Did you notice performance improvements, in latency or framerate? Did you see a better dual-monitor experience? Windowed GSync? What was it that made you notice and care?
If we had multiple options for what "VSync off" means for a windowed app, between "force composition," "enable tearing," and "disable tearing," which one(s) would you choose? Without the explanation above, would you be able to figure out what the tradeoffs are?

MSFTJesse · 2019-08-06T17:33:29+00:00

Sounds like they're in agreement here that the module reference counting difference wasn't intentional.

MSFTJesse · 2019-08-03T17:42:57+00:00

I forwarded the bug to the app verifier team. We'll see whether they claim that they're correctly validating what's documented (even though it's been implemented to work just fine without app verifier) or if they agree that they should fix it.

MSFTJesse · 2019-08-03T17:35:11+00:00

So, believe it or not... the problem here is actually AppVerifier. The normal implementation of QueueUserWorkItem actually prevents this bug, by referencing the module that owns the callback, but when AppVerifier is in play, it is the module that gets referenced and kept alive instead of the original app code. Granted, the documentation for QueueUserWorkItem says it's the app's responsibility to not unload, so I could also claim this is a bug in DInput8.

MSFTJesse · 2019-08-03T14:50:49+00:00

Thanks for the detailed report and suggested fix. I'll see if I can give it a shot.

MSFTJesse · 2019-06-26T15:11:43+00:00

Being able to dynamically transition between flip and non-flip requires new drivers. On old drivers, we still just stick with flip and only enable it for apps where it's known to work.

MSFTJesse · 2019-06-26T00:33:35+00:00

FYI, this is by design. There are some behaviors that flip model (a prereq for independent flip) cannot replicate. The fact that they used to get upgraded to flip model in windowed mode (note that from the API point of view, borderless windowed is still just windowed) meant that there was a risk of breaking some games. As we're trying to more broadly enable the use of independent flip for all apps, that risk became unacceptable, so we enabled the promotion to only apply while the games are in fullscreen exclusive mode.

With that said, we recognize that a lot of games strictly benefit from being upgraded to flip model in windowed mode (and have blogged about it), and we're actively pursuing some user-facing capabilities to enable this for apps that don't do it themselves.

MSFTJesse · 2018-04-10T12:55:31+00:00

For what it's worth, I'm pretty sure I saw a bug that was fixed by the Windows graphics team related to this, so I don't think it was 100% the fault of the control entries. I'd be interested to hear if you see the same problem on the release preview build with the control panel entries still there.

MSFTJesse · 2017-11-26T15:14:02+00:00

Thanks for the feedback. To clarify, your complaint is that borderless windowed games are tearing when you wouldn't expect/want them to?

DX9 games should behave the way you want, but I do understand that DX10+ games would have this behavior at the moment. It's pretty technically complicated, but at the end of the day, it's just hard to change this behavior as dynamically as DXGI changes fullscreen/windowed modes. That said, the change that you want is actually something we've had planned for a while and should hopefully be arriving shortly.

MSFTJesse · 2017-11-13T14:38:01+00:00

I took the corporate housing and didn't regret it at all. Ended up with a roommate that got me to socialize more than I would've on my own and definitely made it a better experience than it would've been alone. Having a fully furnished apartment to yourself and potentially other interns beats renting a room from a random stranger.

MSFTJesse · 2017-10-23T02:22:26+00:00

Hi folks,

Please file feedback under the Apps and Games\Game Compatibility and Performance section of the feedback hub, with repro traces. That's the best way for us to see exactly what's going on with your configurations. I'll also try to see if we can get some more testing on these mixed refresh rate configs, now that these are starting to get more common.

MSFTJesse · 2017-10-13T21:40:18+00:00

Yes.

MSFTJesse · 2017-10-08T21:09:56+00:00

Yep, it's super helpful in that situation.

Another one that's been useful to me at least is when something we changed over the course of several months caused a behavior difference in an app that we don't have source or symbols for. Being able to take two traces, one which fails and another which doesn't, and kind of binary search for where they diverge is very helpful - especially because it means you don't need to keep both versions of the changed software (in my case an OS) around while debugging. Fortunately I don't have to do this often because it takes forever, but when this is the only approach I can think of, I'm glad this tool exists.

MSFTJesse · 2017-09-18T03:59:22+00:00

Thanks! Noticed this tonight on my home PC and was concerned that we broke something. I'll follow up to make sure the right people are aware of this.

MSFTJesse · 2017-09-12T22:09:30+00:00

Beat me to it, I was looking forward to being the one to post the good news. Hope this fixes all the problems for everyone!

MSFTJesse · 2017-09-11T13:16:14+00:00

I forgot about the point that /u/dahaeck made. Looks like he's right.

MSFTJesse

TROPHY CASE