an unexpected exception has occured

[bernhard]

Hello friends,

for some reason I get all the time the same error on our farm: an unexpected exception has occured

I already checked the path with the asset tracking, no texture maps are missing, nothing strange in the scene file at all.
Even if I clean everything, and I leave a teapot only I get the same error on all machines.

Does someone know what this could be ?

thank you so much for every little help,
bernhard

[vlado]

Remove or rename the files related to the viewcube (AutoCamMax.gup or something) from the render slaves, it might help.

Best regards,
Vlado

[OZRAY]

Same here...

All the machine in the farm are identical and configured the same way with all the same path.
I tried to rename the AutoCamMax.gup but the same.
I have 16 machines that are rendering no probleme and 5 that are constantly doing this but not on all scenes.

Found somthing?

[pixelstudio]

you did rename it to a other extension or deleted the file

[OZRAY]

Renamed is to AutoCamMax.gupOLD

You think that it will still load it if it's juste renamed?

[OZRAY]

Bernhard, of you been able to fix it ????

Deleted the file or renamed it?

Regards,

[3Seventh]

Any news on this? I have the same problem here

[3Seventh]

Nerver mind. Renamed stdplugs files and it's working like a charm....

EDIT: .....mmmmm....... ironically crashed while wirting this.

[Morne]

in 2010 renaming the viewcube files did not work for me. I had to remove them from the stdplugs folder completely.

[bernhard]

serious problem

Hello friends,

it's a serious problem.. I can't get rid of this weired and strange error.
I am working right now on a really important project, and this thing needs to get rendered.

what I did and didn't fix that error:
- I merged all objects into a new scene file
- I changed from Vray to scanline render and back to Vray
- I three times checked the RAM
- I optimized all geometry, all is clean and perfect
- I checked all every single path to every single texture map
- same thing with all proxies
- same thing with all xrefs
- I unplugged all plugins
- .gup files were changed

and now... I have no more ideas...

If I render on my local machine, it works perfect, without any problem.
If I send it to the whole farm or only one machine on the farm, I get the unexpected error.

It doesn't make any sense...

I tried to do so, with max2008 64bit and max200964bit - both failed.
I need to stay in max2008 because I am using some plugins I don't want to install on max2009 or 2010, but I thought just to check it.

Additional to that, I really want to say that I was already running several tests.
That means, once I deleted all, and just put a Teapot inside and the error was gone.

So I thought, it must have anything to do with any specific geometry. So I deleted, piece by piece and was running a chekclist and tested around 30-40 options to find out what could cause that issue.

After several tests, I could see, that if I delete my proxie trees, the error was gone.
So I was convinced.. ok, now I found the source of that. So I double checked again the mesh from my trees, before converting into proxies.

Trees alone rendered fine. So I merged the new trees into my master scene file, and tried again...

but still the same error on the farm, so I thought still the trees, something must be wrong with that part. So I deleted the trees again and the same scene file, that worked on the farm when I deleted the trees 10 minutes before, came up again with the error. But now, even if I deleted the trees.... what the heck ?

after more tests, it didn't matter anymore what I was deleting, or what I kept.. the error appeared constantly.

so what is it ?

and of course this is what I have to mention... this error started suddenly.. before that error I was rendering from the same scene file many many frames.

So I tried to load a previous version where I knew it worked, before this error happened, but then even when I loaded those previous scene files, the error came up.

holy holy... so what else to say to this strange thing... I have put a lot of work into that animation, and I am not capable of to render now with Vray...

any little suggestion is more than welcome,
thank you,
bernhard

ps: what actually happens, if you remove all .gup files from your max folder ?

[RE:FORM_STUDIOS]

(repost from another thread as I think it's the same problem brought up here)

I had the same problem and it appears to boil down to a problem in the MaxManaged.Cui file in your ENU folder.

This crashes max in backburner (with or without vray) :

[Graphite Modeling Tools]
Rank=1
SubRank=0
Hidden=1
FRect=232 321 1604 475
DRect=0 88 2214 129
DRectPref=2147483647 2147483647 -2147483648 -2147483648
DPanel=1
Tabbed=0
TabCt=0
CurTab=-1
CurPos=1 0 88 2214 129
CType=4
[Graphite Modeling Tools (Vertical)]
Rank=0
SubRank=0
Hidden=0
FRect=150 100 400 959
DRect=1779 127 1823 1394
DRectPref=2147483647 2147483647 -2147483648 -2147483648
DPanel=8
Tabbed=0
TabCt=0
CurTab=-1
CurPos=8 1779 127 1823 1394
CType=4

but this works :

[Graphite Modeling Tools]
Rank=1
SubRank=0
Hidden=0
FRect=232 321 1604 475
DRect=0 277 152 318
DRectPref=2147483647 2147483647 -2147483648 -2147483648
DPanel=1
Tabbed=0
TabCt=0
CurTab=-1
CurPos=1 0 277 152 318
CType=4
[Graphite Modeling Tools (Vertical)]
Rank=0
SubRank=0
Hidden=1
FRect=150 100 400 959
DRect=0 92 203 1098
DRectPref=2147483647 2147483647 -2147483648 -2147483648
DPanel=4
Tabbed=0
TabCt=0
CurTab=-1
CurPos=4 0 92 203 1098
CType=4

The only differences being the following entries :

[Graphite Modeling Tools]
Hidden=0
DRect=0 277 152 318
CurPos=1 0 277 152 318
[Graphite Modeling Tools (Vertical)]
Hidden=1
DRect=0 92 203 1098
DPanel=4
CurPos=4 0 92 203 1098

Way to go autodesk! Couple of hours wasted troubleshooting a problem with graphite modelling tools positioning that somehow causes backburner to become crashburner!

[vlado]

That's odd, but thanks for the info

Best regards,
Vlado

[mcnamex]

(repost from another thread as I think it's the same problem brought up here)

Way to go autodesk! Couple of hours wasted troubleshooting a problem with graphite modelling tools positioning that somehow causes backburner to become crashburner!

LOL, joke of the day

[digitalx3d]

OMG.... I can't believe this works!! Of all things!!!!!!

I'm rendering out an animation well ahead of time to work out any kinks and issues. It's been a couple years since I've done any animation so I've forgotten things, and new systems and all. I don't want to wait till the last minute to discover problems. So while I'm working on my scene my workstation renders just fine. I set up backburner and my slaves (I normally use DR between my workstation and 2 dedicated slaves) and the slaves render just fine, but my workstation was giving the good ol' "Unhandled Exception" error. Anyway... I stumbled onto this thread after trying the "viewcube" fix (which didn't work), and by golly, it boils down to the damn GRAPHITE TOOLS!!! Geeeeezzzzzz..... I just renamed the CUI files in my ENU folder and now it's rendering fine. How silly. Guess I will put this in a pre-render script perhaps.

Thanks guys!!!