|
The problem that I’m having is the “No network job assignment dialogue” (F10 + check net render + render = 3ds max flash and nothing) problem coupled with the backburner “unexpected exception in network renderer” when net rendering. Deleting/renaming the AutoCamMax.gup plugin or using Backburner 2007 to net render 3ds Max 2009 do not fix the problem.
My entire render farm (all various forms of dual Athlon MP 2000+ processors) will not net render. The only machines that net render don’t have Athlon MP processors (they have significantly newer Athlon processors).
I have tried everything down to a fresh hard drive with a new image of windows with a fresh installation of 2009 + sp1 + the 2008.06.10 hotfix (although the hotfix is smaller in size and claims to incorporate sp1). Process Explorer/Monitor does not give any reason why this would be failing.
I have tried to debug this using the “Debugging Tools for Windows “ which gives me the only useful piece of data yet.
So the reproduction steps are as follows:
1) Launch 3ds max 2009
2) Launch WinDbg (from the latest “Debugging Tools for Windows” package)
3) In WinDbg, File->Attach to Process and select the 3dsmax.exe process that is running, select “Go” so that you have control over Max again
4) Drop in a simple geometry type and bring up the render setup, select Net Render and hit the render button
5) The problem in this case is that the 3dsmax gui dissapears to make room for the Network Job assignment dialog, but then the 3dsmax gui just reappears, giving the sensation that the window just “flashed” in and out of existence.
6) The code left behind in WinDbg is:
“Illegal instruction - code c000001d (first chance)”
Also, if I attach the WinDbg tool to the 3dsmax.exe launched by Backburner when I attempt to do a net render, the same basic error messages come out, except they seem to be coming from the libDLnrapi40.dll
Anybody else having either of these problems, I’m not sure if they are related. It sure seems like they are, though.
| 
