REFramework VS nomicon

Yeah the VR mode is unfortunately exclusive to PlayStation. There is a VR mod for older RE games, but it doesn’t support RE4.

Good catch! Praydog has a released mod for this https://github.com/praydog/REFramework

Resident Evil

Here is more info about the mod and how to install it, though the mod version linked there is outdated. Here you can find the most recent version that supports upscaling.

Who ever is interested: Releases · praydog/REFramework (github.com) And here is how to install it (works the same way with both games) How to install Resident Evil 2 and 3 VR mods in 2 minutes [TUTORIAL] - YouTube

This is the github for his currently released mods https://github.com/praydog/REFramework, which is the resident evil games, dmc5, street fighter 6 and monster hunter, which is what you probably already found. The mods are in the releases section.

Creator Praydog has just released a new version (1.5.1) that adds official support for Street Fighter 6 and Resident Evil 4. To install the Street Fighter 6 VR mod, just download the RE Framework for the game, extract the downloaded file into the game folder, and make sure to have SteamVR (or OpenXR on a supported headset) installed.game master

it’s even written by the same person that wrote the Nomicon (the guide to the dark arts of unsafe)

If you want to dive deeper you can always have other options but now there are concrete cases, if you want to do low level thing https://doc.rust-lang.org/nomicon/ while if you want multi thread/concurrency stuff https://marabos.nl/atomics/ . There are many many books so you will have to point yourself to what you want

Nonononono. SeqCst is the most error prone memory order: https://github.com/rust-lang/nomicon/issues/166

Hope this helps. For more details, see the Rustonomicon. I referenced the subtyping chapter here extensively.

Nice video! Glad I could help out. This stuff is hard, and I'm still learning a lot about it myself even years later. The Rustonomicon is a great read if you haven't already.

Have you got a moment to read through the good book , after reading through this perhaps try the Rustonomicon.

That is not what UB means. Undefined Behaviour is behaviour that the compiler is allowed to assume will never happen, and which can consequently cause miscompilations due to optimisation passes gone wrong if it does in fact occur in the source code.

It's true that Rust does not have a written specification that clearly delineates what is and isn't UB in a single place. But:

1. UB is impossible in safe code (modulo bugs in unsafe code)

2. There are resources such as the Rustinomicon (https://doc.rust-lang.org/nomicon/) that provide a detailed guide on what is and isn't allowed in unsafe code.

In practice, it's much easier to avoid UB in Rust than it is in C++.

However, this is a wide topic out of scope for a Reddit comment, so maybe just read the Rustonomicon. It explains everything about data handling in Rust.

The ownership model & borrow checker makes rust a bit of an awkward language in which to write complex data structures like trees and graphs. It can be done - since you can always use raw pointers & unsafe code when you absolutely need to to treat rust like C. But the language fights you, and the community can get a bit moralistic about this sort of thing. The rust nomicon is a fantastic resource for learning the limits of the borrow checker, and where and how to use unsafe code correctly. You will need unsafe less than you think you will, but sometimes you will have no choice.