Fox2Code

@JG-Adams a branch would be enough, but it requires active interactions from the maintainer, this is why it is not feasible to just use a branch.

Just saw stuff being done again! See: https://github.com/glfw/glfw/pull/2732 @dougbinks Is the project alive again? What are your plans for the future? What kind of support for the community would you...

The `glfw-staging` idea is to help with testing PRs like `wine-staging` do, the idea and commands would be: - `glfw-staging.py help` show a nice help message to explain how the...

@dougbinks thanks for answering about the project future, knowing you still there sometimes on the weekend is cool. I opened https://github.com/glfw/glfw/issues/2761 which is about the project focus, I'll be happy...

This PR fixes Not-Enough-Crashes compatibility issues.

@xCollateral can you review this please.

v2: - Rebased to `dev` branch - Removed `null` check for `GlTexture.texParameteri`, this will be moved into another PR

Null check has been replaced by proper implementation: - https://github.com/xCollateral/VulkanMod/pull/526

Note: @xCollateral want to do the commit himself, I keep this PR as a reminder for him.

The proprietary driver doesn't support implicit sync, `linux-drm-syncobj-v1` is the protocol for explicit sync. SRM/Louvre somehow worked around issues with the proprietary Nvidia driver in other ways.