GameNetworkingSockets VS wine

Steam does have a NAT traversal/punchthrough service too. It's apparently usable without Steam according to their README on https://github.com/ValveSoftware/GameNetworkingSockets but honestly the only easy to use implementation I know is in Facepunch.Steamworks which requires a SteamID to initialize

Halo was mostly all about single player and early multiplayer/local multiplayer but their online netcode has sucked since Blood Gulch. Lots of games do networking horribly, I have been in gamedev making networking and I hate most of what people do. The ones that have a clean natting, based on enet style reliable UDP channels, RakNet style punch are better (RakNet was good until Facebook bought it). It has come a long way but also fallen back. Valve source netcode (on github) is probably the best and you can check it out here. They started with the best in Quake networking, then to Source.

There are some general APIs that are tied to Steam, like some networking stuff (even then there's an open source library), but the devs are not required to use any of those. If the devs chose to develop exclusively for steam and use their libraries, then that's their own decision.

Keep in mind that if you do go the GodotSteam route, there's GameNetworkingSockets from valve that doesn't have the requirement of needing Steam that you can use for releasing on other platforms. It has the same interface as the Steamworks SDK without requiring the Steamworks SDK.

Their UDP-but-connection-based game networking protocol can be used completely separetely from Steam (it also supports encryption). I think that does not include their relay networking solution, but still.. maybe it's helpful. They also have a TCP-like interface to make it easy to plug into an existing solution.

You can also use the non-Steam parts of that library in any game in case you don't just release on Steam (have a look at https://github.com/ValveSoftware/GameNetworkingSockets )

If you want to go the route of using a raw protocol and packing your messages yourself, I suggest to at least have a look at Valve's GameNetworkingSockets either for inspiration of what you might need or even to just use the library: https://github.com/ValveSoftware/GameNetworkingSockets

There is early NAT piercing support in Valve's GameNetworkingSockets. Check out:

You can also try Valve's GameNetworkingSockets with a serialization of your choice.

Sometimes when a detail of Windows isn't documented, the Wine source code can be useful. Have you tried looking at it for details of win64 SEH? For example:

https://github.com/wine-mirror/wine/blob/master/dlls/ntdll/e...

https://github.com/wine-mirror/wine/blob/master/dlls/msvcrt/...

Source code: https://github.com/wine-mirror/wine/tree/master/programs/wor...

It's Wine with some special sauce (Apple couldn't reuse VKD3D because they chose to invent Metal rather than stick with OpenGL/Vulkan so they had to build their graphics translation themselves). Crossover is built on the same technology. In fact, Apple's brew script literally links to Crossover's sources: https://raw.githubusercontent.com/apple/homebrew-apple/main/...

Things like the crypto API should be implemented if you can find the reference for your specific API calls here: https://github.com/wine-mirror/wine/tree/master/dlls/crypt32

Apple's version of Wine is aimed at developers, though. It shouldn't take too long for someone to make an app or script to easily set up environments with the developer runtime, but I doubt they'll support it as well as Valve supports Proton. If your application of choice doesn't need any fancy graphics, there's a decent chance Wine/Crossover can already run it anyway, no need to mess with Apple's SDK.

With the M2 Max outputting 28fps at 1080p (screenshot linked), I wouldn't expect too much from the gaming performance of this thing, though.

Not the OP, but Github's stats on https://github.com/wine-mirror/wine say the current Wine codebase is 95.1% C, 0.3% C++

Take a look at Wine's commit log. It's really well curated. https://github.com/wine-mirror/wine/commits/master

Fixes Overwatch 2 game freeze after a few seconds in game. After a long bisect it was found that wine-mirror/wine@4bf9d24 from upstream wine wine 7.13 and higher needed to be backported.

git clone https://github.com/wine-mirror/wine \ cd wine \ ./configure \ make \ make install \ wine ./Anomaly.exe

Well, I personally can't confirm nor deny that (the only "old" game I play is Plants vs Zombies (2009), and surprisingly it still works great with latest Proton). But the reality is that Wine/Proton are very large and complex projects, developed by pretty much just reverse engineering Windows; Couple this with the fact that a lot of changes happen in-between versions (especially in Wine), and even though an one-line change fixes an issue, it might end up breaking something, elsewhere. My point is, it's almost inevitable not to break stuff eventually. This is why Valve gives us older Proton versions to choose from.