Distributed render missing texture

RE: Distributed render missing texture

ChrisRev — Wed, 29 Apr 2015 02:38:07 GMT

Although Jerry's reply have resolved your problem, to me this is just "band-aid approach" ie the questions remain unanswered for the most part. I have similar queries regarding the Managed Workspace vs rendering generally and Distributed Rendering specifically... I do notice that the "data" xml file under the DR job folder refers to the local workspace, not the managed workspace... could be just that it is reading the local config file, but who knows...

RE: Distributed render missing texture

Jerry Flynn — Wed, 12 Nov 2014 11:50:03 GMT

If you add the MicroStation environment variable MS_DEBUG_LXO_ANIMATION and set it to 1, we will write a text file with the information about frame number and the machine that worked on the frame. You will need to set this on all the machines.

My best guess for the logon on issue.....

For the logon I am administrator and have an administrator logon on all the machines and I don't have your issue. Logging on to a machine on the domain does not automatically give you admin on the box you will need to make sure you add your user on all the machines you are using for DR or create a DR user that does and use that user to start the job.

Cheers,

Jerry

RE: Distributed render missing texture

Csaba_Szabo — Wed, 12 Nov 2014 10:06:43 GMT

Hi Jerry!
Thanks for the answer!

Tried your workflow, it works for me as well. Started distributed rendering with only my computer, then after finishing the first few frames, added three more machines.
I also copied the texture jpg to the Design folder - just to be sure.
Now all are running, images have all the textures.

One additional question came up though. When starting the Scheduler, then on Configuration Settings window, is User information my Windows login with our company server domain (which has my win login data)?
With my win login name and password but no domain entered, AECOsim yields the Ignore/Cancel/Continue (?) options window, the one that shows up when the program crashes.
With the domain also entered (I used what Windows displayed on the login screen), then starting MSProcessors nothing happens, AECOsim and modo do not start.
Right now for the distributed process to run I have to log into Windows on my colleagues computer, then start the process, then change back user for her/him to work.

Csaba

RE: Distributed render missing texture

Jerry Flynn — Tue, 11 Nov 2014 13:53:32 GMT

Hi Csaba,

Here is the Distribute Rendering workflow that I use.

For one you should know that when rendering animation frames using DR that we send all the textures to the shared folder so the only way to have missing textures would be to have a machine that cannot find the textures start the process. This can happen easily enough and has happened to me the machine that I am working on has the textures but it does not get the 1st frame so it has textures and the other machines do not.

1. Make sure all the DR process controllers are turned off on all the machines but the one that you are working on (hopefully the fastest computer) when you start the job.
2. Start DR on the fast computer that can for sure render frame with textures.
3. Wait for the DR job to start check the monitor and make sure the machine you intended is working on frame 0 or the start frame. ( wait for preview to appear with textures to be sure)
4. Start the process controller on the other machines and they will pick up the job (and the textures) from the shared location.

Another tip MicroStation always looks in the folder where the design files are located for textures. Putting all the textures in this folder is a good safety valve I usually use Packager to gather up all the textures and dump them to a folder. MicroStation does not need any paths set to look in folder where dgn is, this just always works by default. Usually what happens when you have missing textures is a machines workspace configuration does not have the pattern search folder set correctly or you are pointing to drive that is no longer mapped. Using UNC path in configuration should help I would not recommend using a mapped drive letter.

Cheers,

Jerry