Author Topic: Collision request  (Read 5737 times)

dgilberto

    Reputation: 1
Collision request
« on: January 25, 2012, 07:50:02 pm »
January 25, 2012, 07:50:02 pm
It will be absolutely necessary to include collisions in Lumion. I found that Lumion is extraordinary to make movies but it is very difficult to navigate as a man in a virtual world. For this feature I prefer any VRML. Unfortunately  It is not possible to obtain the same quality of the environment in VRML,  but we can walk !!!. Once Lumion will have collisions I think we’ll  forget about burning textures and navigate in VRML.
Some news about that????
Dgilberto

Aliki_N

    Reputation: 26
Re: Collision request
« Reply #1 on: January 25, 2012, 08:34:48 pm »
January 25, 2012, 08:34:48 pm
Collison detection is a must have feature, at least with any object that is assigned a landscape material. It is not a nice feeling to constantly find yourself under the artificial landscape material while navigating. I therefore totally agree with you.

Ming Architect

    Reputation: 3
Re: Collision request
« Reply #2 on: January 25, 2012, 09:08:36 pm »
January 25, 2012, 09:08:36 pm
i think ...............Thats Impossible




Oops ... are you sure?
Even SketchUp have it long time ago.
I think it should be in Lumion oneday, for those do real-time navigation in front of clients.
Not just those w/a/s/d style, but maybe with kinect:
Kinect Effect

Oneday...

Thanks,
Ming

Aliki_N

    Reputation: 26
Re: Collision request
« Reply #3 on: January 25, 2012, 10:22:35 pm »
January 25, 2012, 10:22:35 pm
Ming, I love your line of thought. Impossible ........................................  I think not, too.

RAD

    Reputation: 32
Re: Collision request
« Reply #4 on: January 25, 2012, 11:52:47 pm »
January 25, 2012, 11:52:47 pm

5 additional layers is almost impossible for them to add.


Ming Architect

    Reputation: 3
Re: Collision request
« Reply #5 on: January 26, 2012, 07:51:39 am »
January 26, 2012, 07:51:39 am
I'm confusing now ??? ??? ???.

Dazomatic, please show me the light why that's impossible. What I am missing ?
CRhoades, I don't know about layers need to be add. Could I have more infos ?

Is it technically or commercially impossible ?
e.g. We can't have it because it hard to implement or that must be reserved for quest3d?

Thanks,
Ming

RAD

    Reputation: 32
Re: Collision request
« Reply #6 on: January 26, 2012, 07:56:53 am »
January 26, 2012, 07:56:53 am
Sorry Ming,  I don't have the link.

Stucci started the post where Morten discuss the improbability of just adding additional layers.
In that it is hard to implement.
Sounds like adding layers is hard to implement because they will need to rebuild Lumion from the ground up to implement such things. 


Re: Collision request
« Reply #7 on: January 26, 2012, 12:51:36 pm »
January 26, 2012, 12:51:36 pm
5 additional layers is almost impossible for them to add.

Sounds like adding layers is hard to implement because they will need to rebuild Lumion from the ground up to implement such things.

Just to avoid misunderstandings, here's what I replied when Stucki wanted someone to comment on his requests in the Wish List section:

"I don't have much authority on this matter. I'm basically making a guess based on my limited knowledge about the inner workings of Lumion, and it could well be that it's easier or harder than I think. Only Remko/Ferry/Arthur/Artur know how difficult and time-consuming it is to actually implement these features."

...

I'm not a developer but here's what I know:

Seemingly simple changes are rarely as simple as they might seem.


...

"Adding unlimited layers with naming capability would require that the Layer system would have to be completely overhauled and redesigned from the ground up. And that could take some time..."

"Even "just" adding say, 5 more layers would require user interface changes, changes to the Show/Hide Layer effects, changes to the Move selection to Layer command, changes to the Save scene function and the Scene file format, and lastly implementing backwards compatibility so that Lumion 1 projects with just 5 Layers would still load."

In this example, I'm basically just describing some of the pitfalls that would make a seemingly simple feature request trickier to implement than you might think at first glance.

Something similar could probably be said about implementing collisions.

RAD

    Reputation: 32
Re: Collision request
« Reply #8 on: January 26, 2012, 02:20:32 pm »
January 26, 2012, 02:20:32 pm
right right. 

Essential Layers might be....
Layer for lights
Layer for trees
Layer for imported trees
Layer for people
Layer for animals
Layer(s) for cars
Layer for boats
Layer for furniture
Layer for main model
Layer for Aerial
Layer for layout material
Layer for Special Effects
Layer for Animated objects
Layer for Non-Animated objects
Layer for Sky-dome
Layer for Alternate Terrain
Layer(s) for Alternate main model
Layer for Billboards
Layer for Place Holders
Layer for ........


Vas

    Reputation: 5
Re: Collision request
« Reply #9 on: January 26, 2012, 03:12:59 pm »
January 26, 2012, 03:12:59 pm
Anyway... we definitly need more layers  :-D... I hope more layers will be added soon..

Ming Architect

    Reputation: 3
Re: Collision request
« Reply #10 on: January 26, 2012, 06:20:47 pm »
January 26, 2012, 06:20:47 pm
Thanks everyone,

I see now, it happened to all software that have long history. I guess the layers coding are quite low level which was set up very early of quest3d and at that moment it robust enough.

I'm not qualify to say this. IMO upgrade path need to be break in some version, not necessary every version, to keep Lumion robust, e.g. the model will be kept but textures, effects and some functions are lost when open in newer version. But instruction for remedy should be provided. It is about clear message to customers since Lumion is quite new and can set up some new tradition.

Too many criteria will eventually slow development down. Don't know if it could be change if Lumion become big and have resources for rewrite, but I hope so! I see no reason why  should something hold Lumion back for being the most robust in the field, it's about planning and decisions !

Regards,
Ming

Aliki_N

    Reputation: 26
Re: Collision request
« Reply #11 on: January 27, 2012, 09:18:05 pm »
January 27, 2012, 09:18:05 pm
Hi Morten,

Your response to these requests paints a very grey picture about lumion's ability to incorporate what appears to be standard and basic functions. It almost sounds like lumion started on a difficult to expand software platform. Layers, landscape modelling tools, collision detection at least with any object assigned to a landscape layer, sound, animation paths and speed control, seated animated people, business people, casual people, people from different races, different light objects with illumination properties, high quality material shaders, tendered lawns, ability to turn any surface into a paintable surface, high quality plants for close camera animation are some of the basic functions which lumion users have been asking for a long time. I feel we have been given lots of plants and less of animated people, less of high quality metal materials, less of landscape painting options. I don't mean to sound ungrateful - lumion has given us the rendering speed we want, and the team interacts on a daily basis with their users which we greatly appreciate, but we need an assurance that the requests that have constantly recurred are being addressed..We need a definitive list of items that are being addressed. If it means lumion developing high quality bundles of library objects for extra cost in order to support future development, let it be so.

Impossible?................................I still think not.

dgilberto

    Reputation: 1
Re: Collision request
« Reply #12 on: January 30, 2012, 10:38:56 am »
January 30, 2012, 10:38:56 am
I think it is the most reasonable think I have read about that. Or they are waiting for more advanced release (this is a very common strategy in soft and hard), or as you said, they are reserved it for Quest3D. But Quest3D is very difficult for architects, they have enough looking for assignments, designing and supervision the buildings. At the end, although Q3D is thought and structured by parquets, it is kind of programming and need a lot of time to learn it.
Lumion is not like this, once solved the way to import textured pieces is very easy. So architects, could use it, but only for one goal: To make animations.
We have to forget about making presentations emulating real walking people. This is, for the moment, in my opinion, reserved for VRML burning textures to obtain some quality.     



I'm confusing now ??? ??? ???.

Dazomatic, please show me the light why that's impossible. What I am missing ?
CRhoades, I don't know about layers need to be add. Could I have more infos ?

Is it technically or commercially impossible ?
e.g. We can't have it because it hard to implement or that must be reserved for quest3d?

Thanks,
Ming

Re: Collision request
« Reply #13 on: January 30, 2012, 10:53:51 am »
January 30, 2012, 10:53:51 am
Your response to these requests paints a very grey picture about lumion's ability to incorporate what appears to be standard and basic functions.

As I already said, "only Remko/Ferry/Arthur/Artur know how difficult and time-consuming it is to actually implement these features... it could well be that it's easier or harder than I think".

We need an assurance that the requests that have constantly recurred are being addressed... We need a definitive list of items that are being addressed.

As I mentioned in several other threads, I doubt you will get a definitive list of *all* items that are being addressed. Until after the features have already been implemented, that is...

The developers can't promise that something will be implemented until they're certain that it can be done. Programming is a bit like running through an obstacle course in thick fog. The obstacles sometimes don't show up until you're pretty close to them, and you don't always know in advance if a given obstacle is a showstopper or not.

While I understand your request for a roadmap, the problem is that if a potential customer purchases Lumion on the basis of us promising that feature X will be developed in 2012, and this promise fails to materialise due to insurmountable technical problems, it could be interpreted as false marketing.

The last thing the developers want is for you to promise a future client that something will be possible - before it has been implemented.

Regarding your list of shortcomings, here's what I know at this moment in time:

People: More animated people (including seated people and different races) will be included in future updates.

Plants: High quality indoor plants for close-ups will be included in future updates.

Sound: They are actively looking at the possibility of adding 2D/3D sounds to Lumion, but bear in mind that this is no guarantee that it will materialise in a future update.

Aliki_N

    Reputation: 26
Re: Collision request
« Reply #14 on: January 30, 2012, 01:10:46 pm »
January 30, 2012, 01:10:46 pm
Thanks Morten for your response. I really appreciate.