[zak]

hey everyone,

is there a possibility to change the idcpu of an excisting mxi-file?

we did a render on 3 machines in order to merge them later, unfortunately we didn't check on the idcpu, which was set to 0 in all three files.
is there another way of getting the 3 files merged?

[Mihai]

Strange because the IDCPU should be initialized to a random value when you load an mxs for rendering. Did you manually set the IDCPU to 0 when rendering? I don't believe there is a way to change this seed value after the rendering is done.

[pipcleo]

I have had the same problem.
Rendering the same mxs on multiple machines , then unable to merge as the idcpu is also set all to 0.
on mac by the way.
Presumed the IDCPU should be initialized to a random value when you load an mxs for rendering as Mihai says

[zak]

I did not set ID CPU manually. but it was set to zero by Studio. We used the same MXS file to start the renders. Anybody knows if there is a way after the renders are done to merge them manually ?

zak

[QuakeMarine1]

there is no way
the noise seed in the image is the same if all ID is set to 0
the ID define the "Noise seed starting parameter" wich can not be changed afterwards

[pipcleo]

how do you change the seed value before starting the render in studio ?

[Bubbaloo]

You don't need to anymore. It is random. But if you want to you can add "-idcpu 7658" for example to the additional flag input area.