December 04, 2012, 05:39:14 pm
In previous versions in built mode we can manage all this features (sun, camera, exposure, focal lenght,.....) and this parameter are valid for ALL IMAGES you want to create in PhM...
Now it isn't possible, you can save only ten pre-views images no more and have to move from VM to PhM constantly.... this isn't confortable.
Just to clarify what has changed and what hasn't, there were only 10 camera save slots in Lumion 2.5.
It's the same number in Lumion 3.0.
What's new is that you can apply effects to the Photo
section (and you can copy effects from the Photo
section to the Movie
section and vice versa).
In addition, the custom map export options (Depthmap
, Lighting map
etc) as well as the ability to render camera keyframes from clips have been moved to the Movie
If you go to Photo
mode from Movie
mode, the effects are no longer 'inherited' as many people who used Lumion for the first time could not understand this principle.Until the developers of Lumion have a chance to think things through, I would personally recommend that you use the Movie section more as a Photo mode. This will allow you to save more than 10 camera angles (as clips).IMPORTANT: There is a new Shots output mode in the Movie section too:
Movie section -> Save Movie (or Create movie from clip) -> Images -> Frame range -> Custom -> Shots
This lets you quickly render each camera keyframe in a clip or in the entire movie as a still image.
In Lumion 3.0.1 which will be released soon, there is also a new Single
tab in the Save Movie
options window. This allows you to save whatever frame is currently active in the Movie
section. This is basically exactly the same function as when you went from Movie
mode to Photo
mode in Lumion 2.5 to take a photo with all effects. You can save each image including any custom maps such as Depthmaps
, Sky alpha
maps etc in resolutions up to Print
And what is more important the shadows slider, we use very large urgan developments, the new implement for manage shadows aren't confortable and is poor than previous.
As I have mentioned in other posts, this was a bug. The Shadow range
slider was accidentally set to 0-1 instead of 0-2 (as in Lumion 2.5). It will be fixed in Lumion 3.0.1 which will be released soon.