Page 1 of 2
[SOLVED] Displacement - on the fly vs. pretessellated
Posted: Mon Oct 20, 2014 9:45 pm
by 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

Re: Displacement - on the fly vs. pretessellated
Posted: Mon Oct 20, 2014 10:05 pm
by polynurb
what polycount is your basemesh?
watch out with such hight subdiv settings on pre-tess. might be to high.
Re: Displacement - on the fly vs. pretessellated
Posted: Mon Oct 20, 2014 10:20 pm
by seghier
i open the scene and pretesslated worked
Re: Displacement - on the fly vs. pretessellated
Posted: Tue Oct 21, 2014 12:03 am
by feynman
seghier wrote: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 : (
Re: Displacement - on the fly vs. pretessellated
Posted: Tue Oct 21, 2014 12:17 am
by seghier
are you tried to render the scene ?
Re: Displacement - on the fly vs. pretessellated
Posted: Tue Oct 21, 2014 7:51 am
by feynman
Sure did. No displacement rendered. Only when on the fly is chosen : (
Re: Displacement - on the fly vs. pretessellated
Posted: Tue Oct 21, 2014 8:21 am
by 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.
Re: Displacement - on the fly vs. pretessellated
Posted: Tue Oct 21, 2014 9:28 am
by 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.
Re: Displacement - on the fly vs. pretessellated
Posted: Tue Oct 21, 2014 9:58 am
by Mihai
If it says that, then look further in the Console for details....
Re: Displacement - on the fly vs. pretessellated
Posted: Tue Oct 21, 2014 10:11 am
by 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.
Re: Displacement - on the fly vs. pretessellated
Posted: Tue Oct 21, 2014 10:16 am
by JDHill
feynman wrote: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.
Re: Displacement - on the fly vs. pretessellated
Posted: Tue Oct 21, 2014 11:11 am
by seghier
the pretessellated displacement works fine ; nothing modified in the scene

Re: Displacement - on the fly vs. pretessellated
Posted: Tue Oct 21, 2014 1:49 pm
by feynman
Mihai wrote:If it says that, then look further in the Console for details....
No message shows up in the console.
Re: Displacement - on the fly vs. pretessellated
Posted: Tue Oct 21, 2014 2:11 pm
by 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.
Re: Displacement - on the fly vs. pretessellated
Posted: Tue Oct 21, 2014 2:25 pm
by feynman
JDHill wrote:feynman wrote: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!