[MetinSeven_com]

Hi,

I'm coping with an odd problem in 3ds Max which might have been caused by installing Maxwell. Whenever I create a chamferbox, I cannot set the Length and Width spinner values lower than 0.1 centimeter. All preferences are set to their defaults in a fresh Vista 64-bit Max 9 installation with the Productivity Booster. Units are centimeters, decimals indicated by points, not commas. I've never before encountered this problem and used the 64-bit Max 9 with Maxwell before on a Windows XP x64 system.

I'd appreciate your help, thanks in advance.

Cheers,

Metin

[j_man]

Hello Metin,

sounds a little unusual, but it is also the same for me using both max8 and max9. I'm not using the productivity booster BTW.

If you want to have finer detail then model in mm. If you need your fine detail mesh in a larger model then collapse it to a mesh and then import it into your CM scene.

Cheers mate,

Josh.

[MetinSeven_com]

Thanks for your feedback Josh! Do I understand it right that you're somehow coping with the same problem in Max 8 and 9? I've never encountered it before, and it should work correctly.

In the mean time I noticed two more odd things:

1: The chamferbox fillet stops at a certain size, regardless of further increasing the fillet value (while the lowest side value should allow a larger fillet).

2: Somehow a certain chamferbox in the scene was smaller than 0.1 cm, while the spinner was still indicating 0.1 cm. So I touched the spinner and it suddenly popped bigger, and from then on I couldn't get it smaller than 0.1 cm again.

[j_man]

Metin,

I must admit i'm not a big user of chamferbox but I've tested your issue on two different systems, one a fresh install of Max9_32 and this is the case here as well (This machine does have MW installed prior to the fresh install of max), and I've found it to be consistent

1 - I'm not sure I understand! The fillet size stops at the maximum allowable fillet on the smallest side, the spinner will happily keep going though!

2 - I can imagine this happenning if an object is merged from a file with a different scale, it keeps it's size until you click on a spinner which then jumps to the smallest allowable size.

I would imagine this small scale was built into the code to stop errors at very small object sizes.

I hope this is useful!

Josh.

[j_man]

I would imagine this small scale was built into the code to stop errors at very small object sizes.

although the problem doesn't occur with cgamferCyl

hmmm

J.

[MetinSeven_com]

Thanks again for your valuable feedback Josh. I guess I'll start switching to millimeters and check what'll happen.

Cheerio,

Metin