Stuck in Network Rendering

[Syclone1]

So I opened an older scene in 3dsmax 2016 yesterday and made some edits and then tried to render a test and no matter what I did it kept trying to use network rendering, I switched engines, even sent a test to the network renderer and then tried to go back to production but no luck, changed every option I could find but it still kept wanting to use network rendering. Anyway I finally found this little line of code below to put in to the listener and it worked awesome and just thought I would share it for anyone else that might run into this annoying problem:

rendUseNet = false

Cheers,
Dave

[kosso_olli]

Oh, we had this a number of times. Thanks for the tip!

[flipbook]

You can just switch to 'Iterative Rendering Mode' from the Target drop down and back to Production also. That's what I do anyway :P

[Syclone1]

You can just switch to 'Iterative Rendering Mode' from the Target drop down and back to Production also. That's what I do anyway :P

I did try that but for some reason it wasnt working this time... prob a new 'AD unintended feature' lol

[padre.ayuso]

So I opened an older scene in 3dsmax 2016 yesterday and made some edits and then tried to render a test and no matter what I did it kept trying to use network rendering, I switched engines, even sent a test to the network renderer and then tried to go back to production but no luck, changed every option I could find but it still kept wanting to use network rendering. Anyway I finally found this little line of code below to put in to the listener and it worked awesome and just thought I would share it for anyone else that might run into this annoying problem:

rendUseNet = false

Cheers,
Dave

And I thought I was the only one in the universe that had that happened to. Thanks mate!

PS: As a note, I open the VFB and click the little teapot and that renders on your computer, not on the network.

[Dave_Wortley]

In the maxscript listener enter this...

rendusenet = false

[krassi]

Dave.. You are my hero!! )
i also had this strange bug with my 2016 and thanks to that litle line its gone!

best regards, Daniel