[dmeyer]

How bout a higher res close up?

[eric nixon]

Bump map loses influence at this angle, 30min render sl14. Will run one more test to see if using black rather than grey for the backing plane speeds it up.



There is some backlight getting through, filling in the shadows making it look soft.

[Polyxo]

I agree, this really looks good, thanks for posting!
What makes me wonder is that you use "on the fly". I know, it's advertised as the solution for small detail
but I found its rendertimes absolutely impractical. On the blue carpet I would surely not see a Benchmark
value of more than 50 even with moderate subdivision, while pretesselated can be up to 10 times faster.

[dariolanza]

Hi feynman,

In my opinion, simulating a carpet with displacement could be fine, but it won't look completely convincing. Carpet has fur in different directions that is very difficult to mimic with a displacement map (that uses to look too even).

Instead, I strongly recommend you to set your scene in your 3D platform, export it to MXS and open the scene in Studio to apply MaxwellGrass to it. Just use Studio to create the carpet and launch the render.

Obviously in Maxwell 2.7.10. As far a I know, there shouldn't be any resuming problem in this version, so I strongly recommend you to upgrade to the latest one.

You will save a lot of time, and your carpet will look way better.

Cheers

Dario Lanza

[feynman]

Sure, I had to do it via displacement though, since I had to downgrade all machines to 2.6. Once the cooperative render resumption issue is fixed, then of course I will try the grass modifier.

On a side note: I got practically the same render time with pretessellated and on-the-fly, so I guess in my case (flat round and rectangular tufted wool carpets) it does not matter which one to use.

Hi feynman,

In my opinion, simulating a carpet with displacement could be fine, but it won't look completely convincing. Carpet has fur in different directions that is very difficult to mimic with a displacement map (that uses to look too even).

Instead, I strongly recommend you to set your scene in your 3D platform, export it to MXS and open the scene in Studio to apply MaxwellGrass to it. Just use Studio to create the carpet and launch the render.

Obviously in Maxwell 2.7.10. As far a I know, there shouldn't be any resuming problem in this version, so I strongly recommend you to upgrade to the latest one.

You will save a lot of time, and your carpet will look way better.

Cheers

Dario Lanza

[eric nixon]

Both pretess and grass are impractical for a large expanse of carpet, imagine waiting for 100 m2 of pretess carpet hairs to voxelise !

My render times are good with on the fly as long as the height is low, and also dont use sss with on-the-fly.... thats a big slowdown.

I find that a fine mesh (small polys) with low subdiv (3) renders fast, heres an update with lower disp and a new map;



Halved frequency of texture map and more even disp noise, 15min sl14;

[Polyxo]

Eric, were you willing to share that last map, just for testing?
I hardly ever brought on the fly over a benchmark-value of 50, so thus far I gladly waited for pretesselation.

I also can not imagine hair to be a practical option in such contexts.

[Polyxo]

Ok, here's a little pretess/on the fly comparison on a slightly modified version of the mxm you used earlier on.
5 mins each - pretess is 4 times faster while certainly also capable to capture the small detail.
Model is dense 180k and evenly spaced, I used 3 subdivisions on both. Lowering SubD even more did not make
OnTheFly remarkably faster.

Pretesselated



On the Fly

[eric nixon]

Havent decided if this map is best yet, perhaps not random enough, but its good for testing;



polyxo you need to use a larger piece of carpet to see the benefit, and reduce the bump map a lot. those renders dont mean much at the moment, but I will try pretess to see how long voxelisation takes.

[Bubbaloo]

http://support.nextlimit.com/display/ma ... +component

[Polyxo]

Thanks for the map! I'll check it out

polyxo you need to use a larger piece of carpet to see the benefit, and reduce the bump map a lot.

You mean, it should be smaller in pixel-size?

[Polyxo]

http://support.nextlimit.com/display/ma ... +component

So what do you wish to tell us here?

[Bubbaloo]

There seemed to be some confusion a few posts back about the differences of the two types of displacement. Just a quick link to the section of the help documentation in case anyone who was reading wanted to browse it.

[eric nixon]

When i said try a bigger piece of carpet I wasnt being cryptic... try to count the number of hairs first

So anyway I tried using pretess and it is over twice the speed, but this is still a very small piece of carpet, maybe 1mxm, and it used 5 gigs and took 4 mins to voxelise. So for instant tweaking feedback in mxed go with on the fly and for large carpetted spaces it will be practical to use on-the-fly but for normal rug I would use pretess.



this is pretess after 25mins

[eric nixon]

This render took 20mins sl17 around 2gigs ram, with pretessellated, it looks nicer and very much like carpet, - I used 9 subdivisions and taller displacement because pretess doesnt mind much about the height.



However if this object was in the background of a scene using, on-the-fly would be quicker because it would rarely be sampled, also no ram overhead and voxelisation.