So, you're an avid part-time MODO user, but you'd still like to be able to keep up-to-date with all the neat tricks and cool ways you can optimize your MODO workflow.
Being a hobbyist sometimes it can be weeks or months before I manage to find some spare time to mess around with MODO, by which time, I've almost forgotten everything. :-/
This site is just as much for me as it is for you. It's a place where all can keep all the tips and tricks I come across, and it's fully indexed, so you should be able to find whatever you're looking for very easily :)
I'm no MODO expert - far from it, but every other month I'd like to be able to present you with a new article that'll become a new string to add to your modo bow.
If you're a longterm 3D artist or professional, then I can't guarantee there'll be much here you don't already know. You can always have a poke around though., or if you are looking for something specific, use the Search menu up the top (and the links with topics, categories and tags underneath) to find exactly what you're after. If you don't have any luck, let me know if there is anything in particular that you're looking for.
- Debi (alphageekgirl)
| Description | When setting up a scene you may need to move the camera and lights around quite a bit until you get it just right, but you don't want to have to continually re-focus them. So by creating a locator that is parented to the subject object, you can keep manually adjusting the camera and it will always stay in focus. | ||
|---|---|---|---|
| Step-by-Step | Create Cameras
Create Locator
 |
||
| Problem | When applying images to a surface, they may appear in the rendered frame as being a bit too light or washed out. This is because modo always renders internally at gamma 1.0 (linearly), and then applies the user's specified output gamma when displaying or saving the rendered result. Bitmapped images typically have automatic gamma applied to them in an image editor or digital camera (otherwise, they would look too dark to most users); and because of this, rendering with modo’s default gamma value (2.2) will make your images appear light or washed out as they have received double gamma. Therefore, it is important to de-gamma your images. |
||
|---|---|---|---|
 |
|||
| Solution |
This can be done by inverting the gamma amount, simply by dividing the Render Output gamma amount, whatever it may be (but 2.2 is the default), by the image map's item 1.0 value. This can be done directly in the value input field using mathematical shorthand. For instance users can simply type “1.0/2.2” into the dialog box and press enter, and it will return the value “0.4546” (modo does the math for you!). Now the rendered image will produce the correct result. And if you are interested in a general understanding of gamma and how it works on your computer, Richard Yot has made this video that might fill in some of the gaps. |
||
| Source | modo 601 User Guide | ||
| Author | James Darknell (MutantPixel) | ||
| Photoshop > File > Open |  |
||
|---|---|---|---|
| Description | Okay, so this is not actually MODO-specific, but the other day I rendered out a sequence of images in MODO. .You're right, I could have rendered them out as a movie. But if for some reason you have to shut down your machine, or it crashes - you lose EVERYTHING! - so individual images, though slower, is often a more reliable way.. Later I needed to quickly render them out as a .mov file. Of course I could have used After Effects, but I found it much quicker to do it in Photoshop.[/dcs_p] |
||
| Step-by-Step |
|
||
| Description | I was just reminded of something that I discovered last year whilst rendering out my final animation assignment. I had around 1500 frames to render out, and I was fortunate to have two machines to work on. It was late, and I wanted to set them up and go home. But if I started one machine at frame #1, how could I guess whereabouts to start the second machine from to ensure all frames were covered? Simple. Start from the last frame and render out the image sequence in reverse order |
||
|---|---|---|---|
| Step-by-Step |
|
||
| Forum Link | (Old Luxology Forums - no longer exists) | ||
| Source | James Darknell (Mutant Pixel) | ||
 |
|||
|---|---|---|---|
| Description | The Preview Renderer now lets you specify a total Render Time, giving you a predictable way to meet deadlines as you render out to an image sequence or a movie file. Although modo tries to fit within the constraints you've imposed, you'll still need to be reasonable. For instance, with movies, say you want one second of video - don't expect modo to render out 24 nicely rendered frames in half an hour. What I do, is start to render out one frame just to get an idea of how long it will take, and then halve that time and multiply it by the number of frames you have. Yes, it can still end up taking a long time, but it's so worth it especially when you know you're going to have to make some adjustments anyway. Note: As the time of writing, if you try to place modo in the background while you get on with other work, you will get an error message saying that modo 'lost focus' and aborted. This error message is not evident until you maximize modo again and can be very disappointing if you have been waiting hours already. I suggest like a regular render, that you set it up on a dedicated machine and walk away. As an alternative, if you just want to check your composition, blocking and timing and you're not fussed about colours, textures, lighting or render quality, you could always do a playblast through your viewport window. |
||
| Step-by-Step |
From the Render Preview, click on Options, and then right at the bottom you will find Render Animation . Eneter the maximum time you would like your render to take, the frames you want rendered (from > to) and whether you want a single still frame, or an animation. |
||
| Source | http://www.youtube.com/watch?v=ZVOYCZCsGIo | ||
| Author | Brad Peebler | ||
0%