3ds max bugs - place your bugs here

[Morbid Angel]

Hey everyone, in hopes of improving max I'd like to start this thread and perhaps some one out there (discreet) can read it and take it into account.
So if you have experienced any bugs, problems post them here.
I will, in a bit.

[samuel_bubat]

hehe good topic !

actually I do not expect to much from discreet. Instead of fixing
they seem to make more money by adding funky new features.
However... maybe now that they have a new name.. anything will be good

so I´ll start with the pointcache bug.
Actually I reported this bug I think 3 times since version 4.
So I don´t really believe it will be fixed anymore.. but who knows.
Create an Object, add and animate some modifier, add a pointcache modifier on top, set output file,
Turn off the modifier and record the cache. Turn on the modifier again
and... out of memory.. fast exit to desktop.
I sometimes ran into this when turning the modifier off to adjust
downlying modifiers and I forget to turn it on again before recording.
There are a lot of situations when pointcache runs out of memory
but I cannot name them all.
Anyway I would suggest using the freeware pointcache2 modifier.

Inaccurate Texture coordinates.
Example:
When you render out 6 images for a skybox (Terragen in my case)
And you map those on each site of a cube, place your camera inside
and render you will always get seams on the edges. Those can be corrected by setting the "tiling" values for each pictures to 0,99
(sometimes more sometimes less). Also adding a seperate
uvw modifier in conjunction with the "fit" option doesn´t work.
All other software I have tested (mostly realtime engines.. quake for example) does this accurate by default.

Selection Sets.
When you have a very big selection set (hundreds of objects)
never use the "-" button (substract selected object) to remove
all objects at once from a selection set. (use the remove button instead)
When doing so you can watch in your task manager how max will use more and more memory.. until it crashes.
Actually no big deal... if you know not use the "-" button.

Some other little things that I only experience with max7
(wich is according to discreet of course much more stable than
version 6).

When opening very large scenes, sometimes max just resets
the scenes to the maxstart.max scene. Just annoying
when you have a scene that takes 5 minutes to load and have to open it twice. Wild guess.. could be something with the file units cause so far I only experienced it with scenes that have different unit scales
than the maxstart.max.

When closing large scenes I get a memory allocation failure sometimes
minutes after max seems to be allready closed.

And of course max 7.5. Not much to say.. but so buggy that we deinstalled it from all our machines after 30 minutes of testing.

... to be continued ...

[samuel_bubat]

uhh.. another bad one I nearly forgot.
Actually I don´t know if this is now fixed with the bitmap pager (didn´t test it yet).
If you have a large scene with very large textures... max will from a certain point just randomly skip some textures. (Probabely when it runs out of memory). For example. New scene, add a plane and assign a texture of
10000x10000 (Satellite images in my case) to the plane. Render .. and
it should render fine. Now keep adding high poly objects to your scene,
and do some test rendering. In my case when I had about 1,5mio polys in a scene some textures suddenly disapeared. I can imagine that it sometimes just doesn´t has enough free memory for everything. But just skipping textures
without notifying the user can drive you mad.

[Morbid Angel]

holy samuel!
things i didnt know...
here is my bugs, mainly with mat editor for now and I'd like to stress that this is a must know if you are working with shaders and textures.
When creating a shader and having multiple textures intanced, go into one of the slots of the instanced texture and click make unique button. The shader is erased along with all of your doings, exept the unique texture that replaces it. Same happens with keep old map as submap. But in this case only 50/50 times.

[priad]

hehehe, agree for very old mat editor an other very bad thing:
The selection, when you want to select an object (in complex scene in wire) which is near you, you select always the last one @\{[|@^{[ always always always.....

[cpnichols]

Discreet has their own forum... you should post it there.

[Morbid Angel]

what i want is to gather the bug info then ill post

[jacksc02]

Heres my bug (1 of a few)

In backburner, once a job is submitted you cannot change its dependency, very annoying

[J_man]

Samual,

Wher is your avatar from?

J.

[samuel_bubat]

I put it on a scanner.. before i ate it
no.. seriously.. somewhere from the internet !
don´t know

[Morbid Angel]

Bug - Gradient ramp rapid color changing in flags causes max to give c++ runtime error and crap out.