Wondered if anyone else had come across this problem.some machines on our farm are crashing when net rendering, with the error
assertion error: line 1178 ‘units.cpp’
the worst thing about this is it brings up the massive error window, that gives you the option to continue or quit. Not seen that for a while. This means I have to restart the servers everytime, quite time consuming.
any body have any ideas, we are running the latest build with 7.5. This problem only seems to have started since we updated these.
any one? been on the discreet board, and others are suffering the same fate.
can i ask another quick question, whats the vraydummy60.max in the root max folder do? Could this be linked if the units are different in the this dummy scene, to the system units?
I’ve never seen this error; do you get it during DR rendering, or normal network rendering?
The vraydummy60.max is just an empty file that vrayspawner loads up into 3dsmax when it is started in server mode for DR. You can try to re-save that file with the latest 3dsmax version that you have and see if it helps.
ok, found the problem. when upgrading to max7.5 the max.ini has changed slightly. Not all my render nodes have been updated properly, causing the error. So if anyone else finds this problem, copy an .ini that works to the effected machines.
computers suck sometimes! :lol:
Well, I hadn’t touched the config/UI files, so that’s not it. I did check recycle bin just to be sure though. Even copied UI files from backups to make sure they were ok. Opened the INI file too, but the lines mentioned already read correctly.
this error only flags up on the renderfarm. all local workstations seem fine. scanline and mental ray work fine. Its only Vray that causes this problem. Oh, and the one red herring is that only one renderfarm machine is working.
I have copied the 3dsmax.ini accross the network, and the plugin.ini. all machines are identical bought at same time, same model same procs. All max installs are the same, done at the same time off the same disk etc.
So i’m really stumped. This happened with max 7.0 upgrading to max 7.5. so somehting aint right.
any help would be muchly appreciated! :?
I had a smiliar problem a few months back, but it seems to have cleared up now. I wish I knew why so I could help.
Have you done a fresh install?
When you do the fresh install make sure you delete the registry files that max leaves behind and all the files in the max root directory.
unknown perhaps sharing the death.max file would be helpful to try out.
I also have never seen this, however knowing how terrible max 7.5 was we didnt upgrade.
cheers guys.
cant really up a file, but im trying to narrow it down this end.
we had a massive problem with 7.5 too, but i was foolsih to think that 8 might be resolved.
the next interesting thing is that a new fresh scene of max 8 with vray works fine over back burner 3. but old max 7 with the vray before max 8 upgrade is have unit.ccp troubles. gonna keep testing to narrow it down further. what a pain.
ok, now i reckon I have cracked it, but this happened last time and it didnt work. so…
narrowing it down it seems to be related to vray units and 3dsmax. The main culprit being the vray edges texture. So any max 7 scene files with a max 7 vray edges needed to be removed. and voila problem solved…for now.
this also links in with opening up old max 6 scenes into max 7, somehting that also caused a problem coz of the vray edges texture.
hope this helps anyone else with the same problem.
finally found it. seems like procedural speckle and dent and cellular from max 7 scenes do not like rendering in backburner on max 8. somehting to do with real world scale. so you need to remove them from your materials and rebuild max 8 versions.
weird how i seem to be the only one suffering from this.
ho hum.
