[feynman]

A wall, the bricks rendered with a stucco frame... bump looks unreal, hence the displacement. Same file; on the fly displacement renders, pretessellated does not render. Is it a bug or a feature? A nasty MXED creature? Sample here https://www.dropbox.com/sh/mrm7h5eggfop ... 6X6Aa?dl=0 Cheers for taking a peek!

On the fly setting


Pretessellated

[polynurb]

what polycount is your basemesh?

watch out with such hight subdiv settings on pre-tess. might be to high.

[seghier]

i open the scene and pretesslated worked

[feynman]

i open the scene and pretesslated worked

The exact same scene works on your PC? That's very odd! Pretessellated works on none of mine : (

[seghier]

are you tried to render the scene ?

[feynman]

Sure did. No displacement rendered. Only when on the fly is chosen : (

[JDHill]

Not sure which version you're using, but have you checked whether it makes a difference to use an embedded, rather than referenced, material? I think there may have been a problem related to this in the past. Barring that possibility, but still using a simplified embedded test material, I'd try to confirm the issue using a known texture (not having yours, nobody in this thread is actually rendering the same thing as you); for displacement tests I commonly use the veins.png map, from the standard Maxwell materials database.

[feynman]

I used the "veins.png" and get no pretessellated displacement in viewport render and render render as before. When I embed the material, I get "Data preprocess failed. Render cannot continue." which is even stranger... I updated the Dropbox content accordingly.

[Mihai]

If it says that, then look further in the Console for details....

[choo-chee]

I can tell you that I never use pre-tes. as it simply does not work with meshes that I create in maya and then had to make holes etc. in them.
On the fly always works, as long as you have enough sub-divisions in your mesh.

[JDHill]

I used the "veins.png" and get no pretessellated displacement in viewport render and render render as before. When I embed the material, I get "Data preprocess failed. Render cannot continue." which is even stranger... I updated the Dropbox content accordingly.

The problem in this case is very likely the Subdivision value of 2048. Please try opening your file, changing Subdivision to 48, Height to 10 cm, and starting FIRE.

[seghier]

the pretessellated displacement works fine ; nothing modified in the scene

[feynman]

If it says that, then look further in the Console for details....

No message shows up in the console.

[Mihai]

When I embed the material, I get "Data preprocess failed. Render cannot continue."

You looked in the Console in Maxwell? Not the Studio console.

[feynman]

I used the "veins.png" and get no pretessellated displacement in viewport render and render render as before. When I embed the material, I get "Data preprocess failed. Render cannot continue." which is even stranger... I updated the Dropbox content accordingly.

The problem in this case is very likely the Subdivision value of 2048. Please try opening your file, changing Subdivision to 48, Height to 10 cm, and starting FIRE.

Thanks, JD. I did that. The result (using the Pretessellated setting) is:

• - A 8x8 plane (Studio primitive) renders in the viewport and FIRE, when the Subdivision is 256 or lower and the material is embedded
  - A 8x8 plane (Studio primitive) does not render in the viewport and FIRE, when the Subdivision is 256 or lower and the material is referenced
  - A 1x1 plane (from my Alias/Rhino/NX models) renders in the viewport and FIRE, when the Subdivision is 512 and the material is embedded

So, in a nutshell, when referenced materials are used, Pretessellated does not work, no matter the plane's polygon count before Pretessellation.

Thanks for your help!