Lumion Support Center

Support for unlicensed users => Post here if you can't find your License Key => Topic started by: gabrielefx on February 01, 2011, 12:42:54 pm

Title: no snap
Post by: gabrielefx on February 01, 2011, 12:42:54 pm
How can I move an object without snapping on my imported model?

For example I have a low wall and I want to add an intersecting hedge. If I add the hedge from the library it will snap on the top face of the wall. I want that the hedge must be stay aligned with the garden and I want to move it manually so it will be positioned crossing the wall.

If I move the hedge aligned with the garden plane it will automatically snaps on the low wall top face.

Any help?

Lumion can do constrained movements? Why don't you add a funcion that constrain xy axes or an angle constrain at 90°?


Best regards.
Title: no snap
Post by: Remko on February 01, 2011, 12:58:35 pm
In RC4: If you press G to move objects only on the landscape and imported objects. If you want your object to intersect you can just move it up or down. You can also place your object in another layer and hide that layer temporarily while you move the hedge.
Title: no snap
Post by: Morten on February 01, 2011, 01:09:08 pm
(Type-in positioning/constraints/locking optional axes while moving are already on the wish list)

Your example clearly demonstrates that it's difficult to place imported objects with 'overlapping volumes' correctly with the current transformation system – unless the hedge object you're trying to place is exported with an offset pivot but that's a seriously daft workaround Smile

I guess you could switch to Advanced Move (Move object button -> Escape key) which will make your hedge object snap to the Lumion terrain instead of snapping to the wall, and then move the hedge object up until it occupies the same space as the wall. However, this solution is far from ideal as you might not even be using the Lumion terrain in your scene…

Btw, I better clarify what Remko says about snapping as this was changed recently (the following applies to Lumion 1.0 Update 1 Release Candidate 4 which many of our paying customers are using):