| Post |
|
|
Amis - Guest
12:02 pm - Sep 19, 2008
|
| |
|
Hello all,
I'm making following test:
2 sculpted cubes - cube1 and cube2
cube2 is an instance clone of cube1
i'm rotating , scaling and moving both cubes
after export i open project XML file and find that the size values are same in both sculpted prims (rotation and position are fine) , but in 3ds max they are right. Why this is happening ?
note: i've changed my max to 9 instead of 2009 to use prim composer 
note2: i've found this nice little script here “http://www.scriptspot.com/3ds-max/instance-replace” which helps you to make instances from your prims after you finished building( because u forgot to do it in the beggining  ). It will be great to have this implanted in future versions of Prim Composer.
|
|
|
| |
|
I'm embarassed to say it, but it looks like I never tested instanced prims with different scales. I tested them with different rotations, but not with different scales.
This is a bug and a nasty one, too. There's a good chance that I won't be able to fix it in the release that's coming later today. If not, I'll try to fix it next week.
I'll take a look at the instance-replace script next week.
|
|
|
|
Amis - Guest
2:43 pm - Sep 19, 2008
|
| |
|
I can only wish u luck , and thank you.
Other nice trick with this instance-replace script is that u can change big number of sculpted prims with new ones ( ex. changed , improved versions ), with few clicks, instantly. Just rez new version of the sculpt , select old ones and make them instances to the new one. Mesh ( sculpt ) will change and they will preserve size , position and rotation. I found it very useful.
|
|
|
| |
|
Okay, I've managed to work around the problem, so that instances will export properly in 1.0f (releasing today).
However, I didn't fix the source of the problem. Exporting multiple instances will work fine, but scaling will cause problems if you attempt to scale the prims larger than 10m or less than 0.01m.
Here's way to reproduce the bug. Create a box 10×10x10. Create an instance of it. Move them apart and scale one of them smaller. Now, select both of them and try to scale them both larger. One of the boxes will revert to both the scale and position of the other one. This bug only occurs when scaling and only when you try to scale one of the objects greater than 10m or less than 0.01m. So, scaling is fine if you aren't near the upper or lower limit of prim size.
I'll try to fix this in the next version, although it is a tough one. But exporting of instances will be fixed in 1.0f.
|
|
|
| |
|
Shack Dougall said:
However, I didn't fix the source of the problem. Exporting multiple instances will work fine, but scaling will cause problems if you attempt to scale the prims larger than 10m or less than 0.01m.
Fixed in 1.1.4 which will be released Fri Dec 12th.
At this point, I believe that I have fixed all bugs related to instances/references. If anyone sees a problem in 1.1.4 or later, please let me know.
|
|
Forums
