Annoying max 2009

[kwok3d]

I do a lot of test render... and these are the top annoying changes in max 2009 to me.

1) Auto file saving before EVERY rendering! (we work with large files!!)
2) Troublesome Crop/Region Render, not friendly with vray FB (I don't have to say...)
3) Crop/Region Render cannot be zoom large than 100% (View Render ok tho.)
4) Slow/Fancy selection menu (fixed)
5) Default MR material (I remember there is a way to change default to vray mat but forgot how exactly. Anyone?)

what is wrong with Autodesk?! I wouldn't have stepped up if my 2008 is still working.

[vlado]

For the default materials, if you go to Customize > Custom UI and Defaults switcher, you should be able to find a MAX.vray preset, which will set V-Ray as the current renderer, and will populate the material editor with V-Ray materials.

In SP3, there will be an option to region-render inside the V-Ray frame buffer also.

Best regards,
Vlado

[vlado]

For the default materials, if you go to Customize > Custom UI and Defaults switcher, you should be able to find a MAX.vray preset, which will set V-Ray as the current renderer, and will populate the material editor with V-Ray materials.

In SP3, there will be an option to region-render inside the V-Ray frame buffer also.

Best regards,
Vlado

[judderman]

Autosave when network rendering - YES! How annoying is that! Especially annoying when you hit Ctrl+S then wait 5 minutes and then network render and the bloody thing saves again.

Is it possible to turn that off?

[Kyle_Grace]

This is more of a work around for the Autosave, but have you tried working with xref scenes?

We work on extremely large projects, often consisting of many tall buildings. We xref all the model files into a Master file (which only contains, lights, cameras, and minor animated objects). This gives many advantages... one of which is a small file size. So each time autosave kicks in, it only takes a second, compared to a few minutes with heavy files.

[andrewjohn81]

We've been using pretty much the same Xref process for a while now. Autosave can really save my life, but on huge files is really a killer. We work off a shared network drive (and it's not the quickest thing in the world) as well which makes saving all that much more dreadful.

I've found strange things happen all the time though, like parts suddenly not being where they use to be, suddenly go missing, stuff like that.

We've started getting down a process that Helps some of that, but our problems aren't eliminated. For instance, We add a prefix and number before saving the Xref file. This way it ensures to two objects are named the same, even in different files. In order to make it so we can swap parts later I create a dummy somewhere and link all the parts to that. Then when I Xref that file we Move the Dummy to the initial position. That way, if we need to replace any part from another software we just import it, link it do the dummy, and it'll be in the right place when we add that object into the new file even if we've moved it.

Anyone know a good place to get some "best practices" when working with Xrefs? They seem really picky and I think it's just because I don't have a really good understanding of what the software is doing in all aspects. I'm not sure anyone really knows for sure at Autodesk either, but I thought you guys might know.

[stevesideas]

Using Xrefs sounds like a really good idea to keep file size down, but if they keep moving around that just sounds like a complete pain in the arse !

[mmikee]

To avoid some of the "moving" problems, I always merge the xrefed files into the scene one at a time, position them correctly, then save selected the xrefed elements, and xref them back in. This way I dont have to rely on the linked dummies.


Regards,
Mike

[judderman]

I'm convinced xrefs caused my problem with huge files. I started using them and my files mysteriously started growing. If I take a brand new file, and merge even a camera from the file I'm working on at the moment, the camera saves at 500mb. Wtf is that about?!

I've been literally tearing my hair out the past few days working on a max file that started life at 100mb and now somehow has bloated to 750mb. Have you any idea how impossible that is to work with? I'm sure you do

Then the client wants more stuff added...gah!!!

[Kyle_Grace]

Judderman - I've been working with x-ref scenes for years and never heard of this. Are you sure the file isn't corrupt?

I try to avoid linking the x-refs to dummies for all the reasons that people have been talking about. I always build the model and move it to the correct location (preferably from a drawing) and save the file. I also never increment files. If I want to keep a history I generally save a copy of the file into a different folder (i.e - a "WIP" folder) at key points, meaning that I always have a current file that can be auto-updated into the master file.

I've not encountered objects disappearing or moving around?

[stevesideas]

Not sure about the file size issue apart from possible hidden geometry that you are not accounting for.

Seems to me, the xref objects need to have their positions saved correctly from within the xref file..

[maguai]

I have that problem with render region/ crop like every 30 minutes, Its killing me!I cant get any work done!!