#Background Rendering
2 messages in this thread
My previous question on the above subject may not have been sufficiently
specific.
What I need to know is the exact procedure to follow to RENDER in the
background, from say WINDOWS, using the NULL driver as stated in the 3d Studio
manual. I am among many 3D studio users who are experiencing this same
problem.
It may be a VIBRANT issue, I do not know but it would be of great benefit if
someone could come up with a solution.
Thanks
Cyrus,
>> What I need to know is the exact procedure to follow to RENDER in the
background, from say WINDOWS, using the NULL driver as stated in the 3d Studio
manual. <<
Looking at the readme files for some versions of the updated drivers, I think
there is some confusion about rendering in the background versus running 3DS as
a rendering slave in the background, as expressed in the quote below, (from the
driver file):
o NULL
At the end of the card list a 'NULL' card. This has been
provided to allow Windows users to run 3D Studio as a
rendering slave in the background. Nothing is displayed
on the 'NULL' device. If 'NULL' is the display mode,
typing 'Q' followed by a 'Y' will still exit.
It *sounds* like you must have a slave session running to utilize this feature.
I, too, hope that someone from Autodesk or Vibrant can clarify this.
John