Summary

Title:Distribuition Map problem
Category:Crash/Critical
Status:Closed
Posted By:MiguelAngeloCBT ( MiguelAngelo )
Date Created:10 March 2013

Problem

Description:

Hello!

 

Looks like I have a issue using distribution map in the lastests versions of Ornatrix. If you see in the picture, no matter if I use a normal texture or procedural map (any map on the slot), the fur go crasy in some areas (please see picture).

I used an old version of ornatrix on this project (1.8 i guess) and all was perfectly fine. After some time, did the upgrade (I'm now with the latest version 2.2.30), and when I opened the project again, all the fur of this dude went crasy, with this bloop hairs keeping together.

 

Don't know If is an error of Ornatrix or if I did something wrong, but I start the hair solution from scratch, and all goes always wrong...

 

Any help? :)Crasy hair with distribution map

Steps to Reproduce:

-Hair go crasy after applying a texture mask on the distributed map slot in the "hair from guides" modifier

Hello again!

Did some downgrades, and looks like this issue starts on verion  2.2.0.0! In version 2.1.7.0 all goes fine, and there are no weird fur distribution. Please see picture above. I'm using 3DsMax 2012 64bits, just for the record.

Don't know if this happens with other people, but if so, at least you (coders of Ornatrix), can see that this issues starts on version 2.2.0.0

 

Distribution Map OK - version 2.1.70

Thank you for the report Miguel, I will investigate this.

Marsel Khadiyev (Software Developer, EPHERE Inc.)

Just wanted to point out that I was having the same issues from version 2.2.6.0 -  2.2.8.0. I downgraded to version 2.2.3.0 and so far it seems that the distribution maps are working.

 

cheers

This is strange, I reverted the "force exact root count" functionality in 2.2.7 I believe so it should not be a problem anymore. Can you reproduce it in a basic scene? Perhaps, if you have hair cached, you need to uncheck the "Remember" button so that it re-caches the hair. Though I don't see how going back to 2.2.6 would fix it then.

Marsel Khadiyev (Software Developer, EPHERE Inc.)

I am closing this issue for now. Please let me know if you are still able to reproduce.

Marsel Khadiyev (Software Developer, EPHERE Inc.)