Prelim testing and thoughts

[MarkWalker]

Well done Chaosgroup this is pretty amazing.

I’m just at the start of doing some initial testing of this. Prelim thoughts below.

Scene really needs to be built with Lavina in mind. Though no errors in loading existing scene.
Vrscans support would be great, it is in Cuda now in VR frame buffer, can it be ported over.
Runs fast, about 10x + speed of gpu IPR in Maya. Running RTX 8000.
Colours, lighting not same as Vray gpu IPR in maya.
Can a client version be made that’s secure? Eg, send project baked in to executable to client. Just for preview, model can’t be extracted.
Would like option to run on Cuda CPU. Enables larger scene aka ram.

I will do some further testing in coming weeks.

Thanks.
Mark.

[Phillip Miller]

Hi Mark,

>>send project baked in to executable to client. Just for preview, model can’t be extracted.

Thanks for the vote. It's one of the capabilities being considered.

>>Would like option to run on Cuda CPU. Enables larger scene aka ram.

We can only do what DirectX itself supports, so I wouldn't count on this ever being possible - just like you can't do this for a game either.

- Phil

[vladimir.nedev]

Scene really needs to be built with Lavina in mind. Though no errors in loading existing scene.

We need to improve the reporting of unsupported features. For now, you can check the debug log from Help -> Open Debug Log.

Vrscans support would be great, it is in Cuda now in VR frame buffer, can it be ported over.

We might implement VRscans, but it won't be soon most likely. We need to finish more basic features first.
Also, it might be difficult to keep the same performance with VRscans.

Runs fast, about 10x + speed of gpu IPR in Maya. Running RTX 8000.
Colours, lighting not same as Vray gpu IPR in maya.

It's not fair to compare the performance unless the results are exactly the same or at least very very similar.
For example, Lavina is not computing anything for these magenta materials in your screen-shot.

Would like option to run on Cuda CPU. Enables larger scene aka ram.

Like Phil said, this will most likely never happen.
However, we use DirectX 12 DXR, which is a hardware independent API, so in the future, if AMD/Intel support it, we might be able to have Lavina running on their GPUs.

Greetings,
Vladimir Nedev

[npg]

Apart from the errors in the debug log, you could also check here for what is supported:
https://docs.chaosgroup.com/display/...orted+Features

[Phillip Miller]

>>Scene really needs to be built with Lavina in mind.

Our intent is for everything to eventually convert to a "reasonable" result so you don't need to do that.
Yes, deep shader graphics will be made simpler, but hopefully the "magenta:" result will only be part of the Beta as we increase support.

- Phil

[kosso_olli]

We might implement VRscans, but it won't be soon most likely. We need to finish more basic features first.
Also, it might be difficult to keep the same performance with VRscans.

Support for VrScans would be highly anticipated. With this, we could render our datasets as is, because they mostly consist of VrScans.