[strass]

I have made my Maxwell Scene setup on one machine and moved the mxs file to another machine for rendering. What I didn´t think about was that the image output path is not valid on the second machine. Now the render has been cooking for 24 h and image is ready but no output is produced. The "save image" in meny is disabled. Is there a way to produce an output.tga from the rendered image in the Maxwell display?

[macray]

take a screenshot?

[strass]

It´s a 3600x2700 px image so I have taken out 8 screenshots and assembled it. I just wondered if it was a more elegant way of doing it. Maybe some cryptic MXCL command?

[blueplanetdesign]

Perhaps if you use the resume functions in the renderer after you stop the
rendering you can start back up and the rendering will resume, you can save the image path, and all will be well.

[rivoli]

unfortunately he can't resume the rendering unless he started writing a continuable mxi along with it.

[blueplanetdesign]

Oh yes...I overlooked that. You're right.

[Matthew Schrock]

strass,

If Maxwell is rendering successfully, then I am sure it is writing the file somewhere. Try the default location:

C:\Program Files\Next Limit\Maxwell\output

Matthew

[tom]

Hi strass,

Actually, you can't save it the path is wrong from the beginning.
The viewer command "Save Image" fixed with the release version so it won't be problem.
You can also use -output: switch to define a new location before starting a render.

Best regards,
Tom

[hdesbois]

If Maxwell is rendering successfully, then I am sure it is writing the file somewhere. Try the default location:

C:\Program Files\Next Limit\Maxwell\output

Hmmm, not sure. Something like that happened to me once, while trying to output the image to a network disk that was not online. Luckily, I noticed the error messages in the shell window, because the render was going on even if nothing was writtent anywhere. Yep, we might have an error message in Maxwell viewer for such situations, with an option to specify a new path.
HD

[sidenimjay]

i have noticed in the shell that when this happens there is a default location it writes to . . .


i think it may even be C:


but check the shell that maxwell starts when running , i think it complains there about not being able to write to the expected so it states where the default dir is . . .

i think

[hdesbois]

I just started a render with deliberately wrong output path, and it reads:
"memory error: opening targa file Error: File <pathname/filename> not saved"
No hint of default alternate output for me...
HD

[sidenimjay]

hmm not at home right now so i cant check what i get . . . .

but i am certain that i have had a couple of these situations and was able to retrieve the rendered image from somewhere . . .

perhaps is a function of the particular plugin?

i am using the houdini plugin . . . .


also i have found that relative path locations are the best method . . . . because ./myfile.jpg can allways be written to no matter what . . .unless you dont have permissions that is. . . .

[sidenimjay]

checked things out last night:

1. when the mxs was told to write to z:\image.jpg and no z: exists, i find that it doesnt save
and the only thing maxwell states is that it is not writing the image.


2. when using unc? paths such as //CPUNAME/image.jpg these types of paths are
"unsupported" and maxwell states that in the shell , and proceeds to write to
the main windows partition.


till we can save proper from the viewer i guess the best safeguard is to use relative paths, ./image.jpg vs C:/image.jpg or unc paths //MACHINENAME/image.jpg , as these are the only two that can guarantee the image writes on a network machine

[tom]

I think I already made it clear above.

[sidenimjay]

oh yea tom i see exaclty where you wrote about unc paths




sorry to intrude on your answer all mighty one