Bassquake wrote on Oct 9
th, 2026 at 5:46pm:
Ok cool, I can see the list now but cant connect. Basically Im rendering the game in stereo through OpenXR and to do that it replaces cshell.dll with a build from Monolith's 1.0.9.6 source release. It also replaces a few first-person weapon models (*_pv.ABC) so they look right in VR. It runs alongside your patch: AVP2P5.REZ stays loaded for its maps and art. The VR client now gets its server list from master.avp2msp.com:28900 (the 001 request) and queries the servers itself.
But joining a 2.4 server from VR doesn't work: it stays on "Connecting". As far as I can tell there are two reasons:
1. Client verification. The 2.4 server mod expects the verification that your patched cshell.dll does (machine GUID, patch version and so on). A client built from the 1.0.9.6 source doesn't do it.
2. File checksums. The server's checksum list covers CShell.DLL and the *_pv.ABC weapon models, which the VR mod replaces.
I don't want to get around either check in order to keep cheaters out.
Would any of the following be possible?
- Sharing the client verification protocol, so the VR cshell.dll can do it properly, or
- A way for server operators to allow a known VR client (for example its checksums, or a server option), or
- whatever approach you'd prefer.
Let me know. Appreciate you taking the time to respond. Many thanks.
Hi there,
Great job getting that list together! It's good to see the progress you're making.
Regarding the master server, we unfortunately cannot share anything related to its code or internal systems. This is not something we would normally consider due to security concerns. However, I'll discuss it with the team and see what might be possible further down the line.
In the meantime, keep up the good work! The VR edition is looking great so far, and it's certainly an interesting project.
I'd recommend focusing on version 1.0.9.6 as your starting point. Get the single player experience working properly first, test the campaigns thoroughly, and see how things like night vision behave in VR. There's still plenty to work through, but you're making good progress!
As for your suggestions regarding the client verification protocol or allowing server operators to approve known VR clients, both sound like reasonable approaches worth exploring. As mentioned, I'll need to discuss this with the team before we can make any decisions or commitments. We'll get back to you once we've had a chance to look into it.
For now, I'd encourage you to keep developing the project and refining the VR experience.
You're already in our Discord too, so please keep sharing your progress over there. It's always great to see what the community is working on.
These forums are mostly kept around for historical and archival purposes these days, but it's still nice to see you joining in and sharing your work here!
Keep it up, and best of luck with the development!
Cheers,
x-M-x
Pages: 1
Aliens Versus Predator 2: VR Multiplayer Internet (Read 262 times)