Manually Remastering Assets

[fair helm]

If you skin the replacement character model to the skeleton that is captured by USD capture, then it should work like a normal mesh replacement.

The captured skeletons are kinda miserable to skin to though. You can use the original asset's skeleton if you have access to it, bu tyou need to make sure that the bones are in the same order as the captured bones (and when you go from fbx -> usd you need to make sure the exporter doesn't try to add a bunch of new bones to it)

[stray ether]

yea I have access to the model

[stray ether]

whats the best way to check if the bones are in the correct order?

[fair helm]

so the biggest failure point is in making sure that the captured skeleton has the same number of bones, in the same order, as the skeleton you're skinning to.

you should be able to grab each bone and move it around in USD composer, which will let you see which vertices it modifies.

If the skeletons don't match up it is actually possible to fix them with some USD properties, by messing with the joint lists that USD uses... but it'd be a lot easier to just skin it to a matching skeleton

[flat ginkgo]

Sadly though, the captured mesh has no bone data in the usd, which I think might be due to cpu skinning
Might be worth enabling the debug view to show geometry hashes, see it the character is stable or if it changes color crazy every frame
@stray ether

[stray ether]

you cannot see the character in most levels unfortunately. I need to try another level that is entirely interior.

[stray ether]

this just a case of exporting as usb in blender and then trying to open it in create?

or are create and composer two different apps?

[flat ginkgo]

Create has been renamed as USD Composer

[stray ether]

all I am trying to do really, is get the character to render at all. This person has somehow managed to do it but I have no idea how. Even reached out.
https://www.youtube.com/watch?v=cQ1GujNEHYQ

[stray ether]

ok, that is where I am getting confused

[flat ginkgo]

Maybe if you play with the game's graphical settings, you might trigger an special rendering mode that makes it work. It is usually recommended to play with the minimum settings to avoid more complex stuff like custom shaders and such

[stray ether]

Yea, that's what I have been doing. there are so many variables when it comes to textures but I might just try the absolute minimum

[spark dome]

Someone know why when im applying POM in Omniverse i just see PBR without POM?

[fair helm]

Omniverse renderer doesn't have any support for displacement or POM, and I didn't bother to spend a bunch of time implementing our own version in our MDL files

[spark dome]

Sorry i mean i dont see any POM in game

i remember that in Omniverse its non visible

but in game its depence

[fair helm]

post a snip of your material?

[spark dome]

Like what do you mean exactly?

[fair helm]

(open the usda in a text editor and search for your material, then copy/paste that text into here)

[spark dome]

Sure

[spark dome]

over "mat_BE95E973251EBBAB"
{
over "Shader"
{
asset inputs:diffuse_texture = @./SubUSDs/textures/diffuse/BE95E973251EBBAB.dds@ (
customData = {
asset default = @@
}
displayGroup = "Diffuse"
displayName = "Albedo Map"
doc = "The texture specifying the albedo value and the optional opacity value to use in the alpha channel"
hidden = false
)
asset inputs:height_texture = @./SubUSDs/textures/displacements/BE95E973251EBBAB_H.dds@ (
colorSpace = "auto"
customData = {
asset default = @@
}
displayGroup = "Displacement"
displayName = "Height Map"
doc = "A pixel value of 0 is the lowest point. A pixel value of 1 will be the highest point."
hidden = false
)
asset inputs:normalmap_texture = @./SubUSDs/textures/normals/BE95E973251EBBAB_N.dds@ (
colorSpace = "auto"
customData = {
asset default = @@
}
displayGroup = "Normal"
displayName = "Normal Map"
hidden = false
)
asset inputs:reflectionroughness_texture = @./SubUSDs/textures/roughness/BE95E973251EBBAB_R.dds@ (
colorSpace = "auto"
customData = {
asset default = @@
}
displayGroup = "Specular"
displayName = "Roughness Map"
hidden = false
)
}
}

It could appear if i reopen omniverse and save usda

but this time it doesnt happen

[fair helm]

It could appear if i reopen omniverse and save usda
erm, what do you mean? It doesn't work in game, but then you open the usda, save it, and then it does work in game?

[spark dome]

Yep

Its pretty weird tho

[fair helm]

so is the snip you posted from after opening / closing it? or before?

I don't see anything wrong with the stuff you posted

[spark dome]

After

But still no changes in game

[fair helm]

I'm very confused right now, so please say very clearly what is happening. You implied earlier that it could appear by opening and saving the file in USD Composer, but now you're saying no changes in game?

[spark dome]

No changes in game if doing same thing as before

opening

saving

Actually i apply Heightmap once again

even so it already was

[fair helm]

... you've just made me even more confused

Assume I know nothing about what you're doing, and list out exactly what you're doing, what you expect to happen, and what is actually happening

[spark dome]

Im confused also because i dont understand why its happening

[spark dome]

In general: I applying PBR with POM in Omniverse as always. Saving USDA, opening game - see that PBR is here but without POM. Before i just tweak a bit some materials so i can save USDA once again and after that POM was in game

but now if im doing almost same thing, nothing happen

Before POM was applying fine i suppose

[fair helm]

Here's a material from one of my test files. You might need to set the displace_in property

        def Material "Mat_01"
        {
            token outputs:mdl:surface.connect = </World/Looks/Mat_01/Shader.outputs:out>

            def Shader "Shader" (
                kind = "Material"
            )
            {
                uniform token info:implementationSource = "sourceAsset"
                uniform asset info:mdl:sourceAsset = @./AperturePBR_Opacity.mdl@
                uniform token info:mdl:sourceAsset:subIdentifier = "AperturePBR_Opacity"
                asset inputs:diffuse_texture = @./textures/basecolor.dds@ (
                    colorSpace = "sRGB"
                )
                float inputs:displace_in = 0.05
                asset inputs:height_texture = @./textures/height.dds@ (
                    colorSpace = "raw"
                )
                token outputs:out
                asset inputs:normalmap_texture = @./textures/normal_OTH.dds@ (
                    colorSpace = "raw"
                )
                asset inputs:reflectionroughness_texture = @./textures/roughness.dds@ (
                    colorSpace = "raw"
                )
            }
        }

Also be aware - older versions of the AperturePBR_Opacity.mdl files didn't have a height_texture, so if you open the usda in USD Composer and it's pointing to one of those older mdl files, USD composer will strip out the height_texture property. You should make sure you're using the latest runtime, take a USD capture, and use the MDL file generated from that new capture.

[spark dome]

in first try

[fair helm]

do the height_texture and displace_in properties show up in USD Composer?

[spark dome]

Idk actually

i did nothing

and suddenly Displacement asignment appeared

in USD Composer

[fair helm]

Okay, that means you're using the updated MDL files, so that should be fine.

[fair helm]

try setting inwards displacement to something other than the default value

[spark dome]

0.05 is actually not default

material that on screen is one of textures where POM is working

default is 1.0

So yeah

i think i need to put 0.05 to other textures and see

what will change

[spark dome]

Yep now its working

[soft zenith]

Okay, we know that to add light, the light source needs to be made a child of mesh_hash. But what do you need to do to remove a captured light source from the scene? Yes, I know that you can set the intensity and exposure to 0, but are there any more effective options?

[soft zenith]

And another question is that the usd opens differently every time - is this a bug?

[fair helm]

setting the lights to 0 is the way. Although you can also just move / tweak the lights instead of disabling them - or add more lights as children of lights.

[fair helm]

That does look strange... I'm guess some sort of texture or material initialization bug? The resolution is too low for me to read the text, but it looks like you're getting some warnings. you should open up the console tab and see if you can find any errors or warnings that look related (be warned, the console in OV is spammy)

[soft zenith]

Okay, I fixed it by just setting the game's graphics settings to minimum.

[soft zenith]

What is a reasonable number of light sources to add to a scene that the path tracing didn't make so much noise?

[flat ginkgo]

Well, this seems very glitchy. You probably disabled temporal denoising, or is just using way too low number of RIS lights

[soft zenith]

I put 1-2 ray bounce and a high denoiser preset through the simplified settings. Everything else is completely stock

Dlls ultra performance for 1440p output

But it's the same without dlss ±

[flat ginkgo]

I'm not home rn to point you to the settings, but there is a slider right on top of the rendering tab, something about RIS lights which you can crank it up of it is too low. Something around 15 should be great iirc.
Also, I think there is a chance your motion vectors are screwed up. Try enabling the debug view to visualize them, see if the roof has some weird behaviour different than the walls and floors

[soft zenith]

I'll take a look a little later, thanks for the tip

[deep ice]

That shouldn't ever happen anyway

Enable the debug mode

I wanna see if there is anything unstable there

[soft zenith]

@deep ice @flat ginkgo

In general, it seems like the motion vectors are generated correctly. It seems that the problem is in the denoiser, I guess I will have to select parameters by trial and error method

[soft zenith]

Or if anyone has documentation on denoisers in rtx remix, I'd love to read it

[keen canopy]

Your denoiser settings don't save, I wouldn't bother messing with them. Maybe choosing the method in the drop down but you'll have to do it every time you start the game

[soft zenith]

Hashes are stable

[keen canopy]

Your motion vectors are crazy

[soft zenith]

But then dlss wouldn't work, would it?

[keen canopy]

It works just not awesome

[pulsar hound]

your game is is like what are you doing

[kindred bronze]

forgot to send this. this morning because i fell asleep.

i'd assume this may be caused by the games use of vertex shaders.
or maybe i messed up something, somehow.

p.s this is a mesh replacement, with the same mesh.

[fair helm]

The lightsaber is getting left behind? It might be bound to a skeleton, and your replacement doesn't have matching joint binding information

[kindred bronze]

are skeletons supposed to be captured? there is nothing in the folder

guess ill have to extract the game

[fair helm]

If the mesh is skinned using GPU skinning, there should be bones in the captured USD. If it was skinned on the CPU, the hash wouldn't be stable enough to replace

[upper dock]

Why light don't change?

It should be yellow

[upper dock]

Or distant lights don't change?

[kindred bronze]

will remix ever support meshes with vertex shaders?

[upper dock]

It can now, with very limited support

[kindred bronze]

mesh replacements with vertex shader transformation support when?

[upper dock]

replacements no, view yes

[tight oriole]

this is a recent state of the game

[snow lagoon]

No that's a screenshot of the capture from Omniverse

[tight oriole]

ah

also i didnt realise this was a different channel so it got sent in the wrong channel lmao

[night pond]

That's not an issue with the denoiser. It's is caused by 3 potential things:

1. Don't use DLSS Ultra, use Quality and lower base resolution instead. I recommend 720p or 900p followed by DLSS Quality. Also make sure to set RTX settings to Ultra, anything lower is not worth it unless you really struggle for framerates.
2. Your light output is too low, and the Auto exposure kicks up too high. Turn off Auto exposure feature then raise the output of light sources and lower exposure/brightness in the post process section.
3. Something weird is going on with your lights. Did you disable the vanilla lights or remove them completely? It may also be the case with double, triple "layers" of multiple light sources added in the same place, this can happen if you add light sources to one area multiple times in different sublayers. Always make sure to only add light sources to an area once.

And next time, please feel free to DM me and discuss questions like this when it comes to Max Payne, because I spent many hours tweaking and trying different settings and I have a pretty good understanding on how Remix works in this game as well as most of the different settings in the Remix menu. Cheers!

[soft zenith]

The problem there was the lack of pbr, as soon as I plugged in your textures everything was fine.

[dusky solar]

Yep, thats what we do with underground 2

[kindred bronze]

last message here was 02/18/2024

[clear tree]

last message here was "last message here was 02/18/2024"