[Hypsis]

Hi,

sorry I'm in such a hurryand don't have enough tine to investigate on my own properly, but I have to deliver three renderings tomorrow on Friday afternoon.

I have defined three views in Rhino and now I would like to have them all three rendered one after another, they take approx. 7-8 hours to render in 1024x768 resolution. Is there a direct way how to do this?

In xsi I am used to simply set keyframes for the camera switching e.g.
Is there a way to do this in Maxwell/Rhino?

Would it be wise to actually hide all objects that are not seen in a view? If yes, than I would have to save three mxs. How can I easily render them one after another??

(I promise to thoroughly RTM when I am finished with this project, but it came very suprisingly at a time where I have no time, oh well, couldn't say no to the money )

Thanks!

[JDHill]

I don't think there's anything in Rhino that would explicitly allow you to do that, it is primarily designed to be a NURBS modeler and only has very rudimentary animation capabilities. However, I can tell you one way that should work:

1. Begin Animation (main menu > Maxwell > Animation Control)
2. frame your first shot
3. Export MXS File (main menu > Maxwell > Rendering and Export)
4. frame the second shot
5. Export MXS File
6. frame the last shot
7. Export MXS File
8. End Animation

The call to End Animation will start an animation consisting of the three exported frames (or however many were exported between the begin and end calls) rendering in MXCL. Naturally, you should have set up your camera and other scene settings before exporting these files.

Let me know if this is what you're looking for.

JD

[Hypsis]

Hi JDHill,

I tried your solution, and it worked, but it isn't very flexible. If I have to redo the rendering, maybe because I want to resume, I must either redo the animation or load them up into the mxcl.

So I took a small glance at networking, and it is really really easy

I started a manager, a server and a pure mxcl gui, added the three jobs and up it went. I tried to import the three mxs, and it worked, but it didn't change the camera, I will try this again as it must be my fault.

It seems as if there is no way to tell to wait before starting the rendering and I can't seem to edit the jobs afterwards...???

What would be cool, if I could directly generate the emitter layers for the first frame of each created mxi. This is a real nice way to composite everything later in ps.

I hope, by this way, to be able to add my second computer as renderslave. Unfortunately the mainboard has to be changed and I would like to have the rendering on its way.

Btw, if I want to export the mxs from the scene manager it works the first time, but then does an undo evertime I click on the icon, funny ey

[JDHill]

Well, as I indicated, there's not much support for this kind of thing in Rhino. It would be possible to augment that simple example using some Named Views and RhinoScript, if you wanted to go that direction. As for network render questions, I don't have too much experience with that side of Maxwell, so you may want to redirect those types of questions to the main forum or the networking forum.

Regarding your Undo glitch, I don't see it happening here - MXS export seems to be working normally. Can you provide any more details about your particular scenario which may help me to duplicate this?

Thanks,

JD

[Hypsis]

Ok it works quit well, only shock I had with the cameras that they didn't match at allwhat I had in Rhino. I read about this probem here, nothing I can do, I will have to load it in studio and change it there.

IS there a way to export the cameras and settings within studio and then reimport them in a new mxs?

About the bug, yes I could reproduce it with a new scene. Try rhis:

1. create a box
2. create another box.
4. click on the icon write mxs. -> asks for saving, normal procedure
5. Choose anim start -> this will trigger the fault
6. click again on write mxs -> it'll undo the second box.

[JDHill]

Okay, I see something there. It doesn't undo the box here, but when it's in the animation loop I see there is some code printing a single 'r' into the command-line - maybe that is causing an undo under your settings. To avoid that, you can also just use the regular Render command (rather than Export MXS) - it will not start MXCL when you're in the animation loop.

About your cameras, are you sure you had the correct viewport selected when you exported the frames? I am not sure which problem you are referring to (i.e. what it was that you say you read about).

[Hypsis]

To avoid that, you can also just use the regular Render command (rather than Export MXS) - it will not start MXCL when you're in the animation loop.

yes that's what I did then.

About your cameras, are you sure you had the correct viewport selected when you exported the frames?

No, I am not sure, but I didn't have the time to retest it. But probably my fault.

I am not sure which problem you are referring to

http://www.maxwellrender.com/forum/view ... ght=camera

Edit:
http://www.maxwellrender.com/forum/view ... ght=camera


I had to do the camera things within studio, all worked well, had some crashes sometimes though when saving.

Couldn't render out 2048x1536, 2GB seems not enough, have set virtual memory to 2048-4096, but renderer always aborted with microsoft visual c++ error when mem was full. 1536x1280 was ok. But after the first rendering the server was disoconnected (all on one machine).

Phhewww what a nightmare...

[JDHill]

Those topics are quite old, and are not very applicable given the current state of the plugin. I understand you're busy at this time, but when you get the chance, you may want to try some of the functions in the plugin's Camera toolbar:




Camera LCD Readout
- toggle the Camera LCD readout

Camera Heads-Up Display
- toggle the Camera heads-up display

Auto-Focus to Objects
- prompts for a selection of objects, which are then used to set the current Camera's focal distance and fStop.
It is recommended that the current Camera have Auto-Exposure enabled when using this command

Pick Camera Focal Distance
- start the Camera focal-distance-setting routine

Pick Z-Clip Near Plane Distance
- start the Camera Z-Clip near-plane-setting routine

Pick Z-Clip Far Plane Distance
- start the Camera Z-Clip far-plane-setting routine


The heads-up display will show you the camera's film-rectangle as it relates to the Rhino viewport, as shown here:



Using this tool, you can disconnect the viewport size from the rendered image size - changing the size/aspect of the viewport will not affect what is rendered. For example, in the image shown above; what is framed in the heads-up rectangle will still be rendered the same if the viewport is split into 4 views. For example, both of these render the exact same image:





There is more detailed information about how these tools work, located here: http://www.maxwellrender.com/manual/rhi ... atools.htm

[Hypsis]

omg! I feel so sorry and

you are the best, you have a remarkable patience, thank you!