VaM 1.x DLSS 5 in VAM2 + DLSS 5 Experiments in VAM1

[Curves3E]

Ideas that could improve this are:

• Atom-specific rendering: A plugin that applies only to individual atoms, rendering the character model without processing the entire viewport or even the foveated viewport.
• Multi-GPU support: A driver or architecture that makes SLI relevant again, allowing DLSS 5 to run on one NVIDIA GPU while the game world is rendered on a second GPU or even an APU.

 

[UncleBurrito]

More work with dlss upscaling + nr in vr

 

[VaMStaff]

Links to unauthorized "patches" to Paid plugins will be removed, and may result in restrictions to your account up to and including a ban.

 

[hazmhox]

Atom-specific rendering: A plugin that applies only to individual atoms, rendering the character model without processing the entire viewport or even the foveated viewport.

From what I saw and tested on the masks systems. Masking or not, this is an "image wide" treatment. Masks are just a way to adjust the final input but it won't cut your computation cost. For now at least.

Multi-GPU support: A driver or architecture that makes SLI relevant again, allowing DLSS 5 to run on one NVIDIA GPU while the game world is rendered on a second GPU or even an APU.

LOL. For fappin' 3mins and a half? Masturbation cost can't get higher than that haha

 

[EvilBox]

From what I saw and tested on the masks systems.

Were you testing this in VaM 2?
And if so are you planning to make any kind of announcement about whether this technology will actually be supported in VaM2? It would be really interesting to hear how you’re thinking about implementing it from the technical side, and what kind of problems or limitations it might introduce in game

 

[krizzy]

Ideas that could improve this are:

• Atom-specific rendering: A plugin that applies only to individual atoms, rendering the character model without processing the entire viewport or even the foveated viewport.
• Multi-GPU support: A driver or architecture that makes SLI relevant again, allowing DLSS 5 to run on one NVIDIA GPU while the game world is rendered on a second GPU or even an APU.

Yeaaa to be able to choose would be very nice, especially with passthrough. I'm no techie, but that does sound difficult.

I loaded a scene on desktop that I had edited for passthrough use, NR took my chroma green and obviously altered it, as well as making my model looking sickly green lol.

 

[Curves3E]

Yeaaa to be able to choose would be very nice, especially with passthrough. I'm no techie, but that does sound difficult.

I loaded a scene on desktop that I had edited for passthrough use, NR took my chroma green and obviously altered it, as well as making my model looking sickly green lol.

Passthrough color manipulation is more art than science where you need to match colors using Sally's background plugin and all the lights in your scene need to have corresponding color that makes sense with the actual room you are in. If it looks sickly green it's the wrong color to use, i think the ALVR guide mentions "Blue (0, 71, 187) Similarity 20%, Smoothness 3% - Works on most, easy to use" . VAM 1 doesn't support invisible pixels because the engine is too old so other methods cannot work with VaM 1.0 . Everything is better from a developer standpoint with VaM 2.X because it's got more support for all the new technical features.

 

[Curves3E]

From what I saw and tested on the masks systems. Masking or not, this is an "image wide" treatment. Masks are just a way to adjust the final input but it won't cut your computation cost. For now at least.

Fingers crossed that Nvidia decides not to be evil and makes the tools available to indie developers.