Isotropix Forums

Hey there,

So, I'm having a little problem. Not sure if it's my stupidity or what, but here goes - I'm building one uber scene with all of my assets inside. I'm at a point where I create materials and here's where it gets interesting. I wanted to have one uber material for all the assets that share the same texture set, and control the maps via shading variables on object level. So I went ahead and created the mastah material with empty texture map files and used shading variables to specify the location on the drive. And shieeeeeeeeeet - viewport performance went south. Like, 100 to 0 real quick. It's not smooth even though there are only 2 spheres and a plane! I created a video to demonstrate the issue:

https://vimeo.com/270202092

As you can see, rotating and panning is not interactive at all. I've had scenes with a LOT more geo in it and it was working without any problems. The issue (or not?) happens whether I use .jpg or .tx files. I have 12 GB of cache set for streamed files, everything is located on an NVMe SSD with over 3GB/s read speed so I do not think that hardware is the botleneck.

Just to clarify - when I import the textures inside Clarisse, create new material for each object, it's all working fine. It's only like that when I import the textures via shading variables. Is it normal? Or am I just missing something? I guess I could just import all the maps and create one shader per object but it's not fun (and we want fun, right Sam? ). The whole reason not to do it and why shading variables were introduced is to reduce rendering times by cutting down the number of shading nodes to compute.

Can you elaborate?


Also - I think I may have found a bug. Let's say we have context A locked to the viewport. All good. Now, create context B outside of context A, instantiate context B into context A so that the content of context B is also displayed (love that sentence). And here's the bug - if you import some geo into oryginal context B - Clarisse will crash. Upon restarting the imported stuff will be there - but still, shouldn't have crashed.

Cheers to y'all

Hi,

Do you use map file or streamed map file? We found bugs when using map file nodes. Clarisse reloads the textures in an infinite loop, and it's worst when a texture is missing. (warning logs)

Sometimes, for some obscure reasons, the encoding of a .jpg file is bad. It slows down the viewport as well. If you open the file in nuke and re-save the map it fixes the bug. Jpgs saved in photoshop make the 3D view slow, it comes perhaps from the sub-sampling...

And no, using shading variables doesn't speed up the render. In fact, it slows it slightly as the maps have to be loaded dynamically. But it speeds up the material setup as you need just one uber shader.

For the instantiated context bug, could you please use the bug tracker ?

Thanks for reporting those issues

Cheers !

During troubleshooting I was testing both streamed map file and map file, jpg and tx formats, the outcome was the same in all cases.

Let me ask this then - what's the difference between importing texture via import menu vs importing it via shading variable? As far as my (limited) knowledge goes - Clarisse does not import the texture iteself but only references it, so it is dynamically loaded anyway?

The slow down comes from a bug. I added an entry in our database.

The difference is that Clarisse has to resolve the variables in the rendering process.

Cheers

Awesome. Will do some workarounds untill it gets fixed.
Merci

dboude wrote:The slow down comes from a bug. I added an entry in our database.

The difference is that Clarisse has to resolve the variables in the rendering process.

Cheers

Hello Démian,

Has this bug been solved in Clarisse 4.0?

If not, which is the optimal procedure to prepare map files for clarisse?

Many Thanks
F.

Hi,

The 3d view is slown down when a texture is missing. In other case it works.

Cheers