This forum is now closed.
Please join us at the new Lumion Community forum.
Lumion Community
Use your email address and password from the old forum to log in if your account was created before Feb 20 2020.
Otherwise, you will need to create a new Lumion Account at the new forum.

Author Topic: Collision request  (Read 8587 times)

Re: Collision request
« Reply #15 on: January 31, 2012, 02:02:14 pm »
January 31, 2012, 02:02:14 pm
Concerning collision - for now we have no plans what so ever to include this simply because it does not fit the type of program really well. We want Lumion to be a program for movies and not for walk-troughs. Maybe in some future updates we can add extra camera types such as drive-trough, helicopter or walktrough but for now we have no plans for this. We have many exciting things on the list we want to complete first. Our primairy focus is fast and good looking architecture movies and there are many other areas that come first before we need a collision capable camera.

Nico RVArq.com

    Reputation: 58
Re: Collision request
« Reply #16 on: January 31, 2012, 06:05:16 pm »
January 31, 2012, 06:05:16 pm
But Remko, seems to me that the collision strongly related to the ability to generate an EXE file, isn´t?  :-\ The executable thing, Can you say something about it? Is it in your plans?

Nico RVArq.com

    Reputation: 58
Re: Collision request
« Reply #17 on: February 01, 2012, 02:41:04 pm »
February 01, 2012, 02:41:04 pm
Also I want to know.
When will L2.1 be released ?

Re: Collision request
« Reply #18 on: February 01, 2012, 03:06:00 pm »
February 01, 2012, 03:06:00 pm
I wish I could tell you that, but we keep finding new bugs that Ferry has to fix. Hence the delay.
IMPORTANT: Please do not send private messages and emails to members of staff - unless we specifically ask you to send us sensitive information, for example License Keys.

Nico RVArq.com

    Reputation: 58
Re: Collision request
« Reply #19 on: February 02, 2012, 02:14:29 pm »
February 02, 2012, 02:14:29 pm
Morten, don´t want to sound that I want to make you walk through the fire wondering about the executable thing. (and the planar reflexions, by the way).
But I have also sent an email to ACT3d with the first question and got no response.
I wonder if at least in the plans develop, or if it is something that is discarded for this 2012.

Re: Collision request
« Reply #20 on: February 02, 2012, 02:19:20 pm »
February 02, 2012, 02:19:20 pm
Morten, don´t want to sound that I want to make you walk through the fire wondering about the executable thing.

All I can say is to stay tuned for more information about this.
IMPORTANT: Please do not send private messages and emails to members of staff - unless we specifically ask you to send us sensitive information, for example License Keys.

Re: Collision request
« Reply #21 on: February 02, 2012, 05:52:41 pm »
February 02, 2012, 05:52:41 pm
But Remko, seems to me that the collision strongly related to the ability to generate an EXE file, isn´t?  :-\ The executable thing, Can you say something about it? Is it in your plans?

We abandoned the whole idea of an executable. The reality is it is too cumbersome because people have to have the right hardware. The only thing I can see similar functionality is if Lumion gets an easy way to package scenes so you can send them to someone else. This way someone could just install the free version of lumion and use it as a viewer for your scene.

Maybe at some point we can extend the play mode so you can walk around or something like that.

Nico RVArq.com

    Reputation: 58
Re: Collision request
« Reply #22 on: February 02, 2012, 06:05:59 pm »
February 02, 2012, 06:05:59 pm
Too much sincerity, I preferred the intrigue.
Little less than a disgrace.
I am sorry that things are so.

BMcIsaac

Re: Collision request
« Reply #23 on: February 02, 2012, 06:30:40 pm »
February 02, 2012, 06:30:40 pm
There is a list of rendering apps being used in a survey at Sketchucation...I pointed it out earlier. There are a lot of very useless applications out there. Of the 23 there were only really 5 that where in use at all. The rest got basically no support from a forum that has thousands of viewers in the modeling and rendering business. Those that were on top are no charm either. Thea for example seems to be very popular. It is an amazing indoor rendering machine.  The quality is amazing...but...and a big but...try to build a forested terrain  from an Architects drawing....NOT POSSIBLE! unless you want to work and wait hours...and movies.. forget it you need a rendering farm to get off a 10 second cut.

So that shows that it is hard to compare apples and oranges I guess but the point is, we are just spoiled here. You need to adjust your quality expectation not to your taste but to your customers taste and at the moment my arch customers are switching to Lumion builders because Lumion builders get the job done way faster than anyone else. Please find me something that compares. The small sacrifices in real visual readiness are hardly noticeable.

The big firms in my town are not able to compete with me anymore because they want to charge the old "go slow" rates. I get calls from building owners with drawings in hand who have been quoted 2 to 3 thousand for a half dozen images. They are very good alright but too good!!! We are not trying to create images that get us hits on youtube we are trying to reduce our customer costs and get him a good quality package. That is what makes him happy.  Once they get you under their skin with this Lumion workflow, they will not let you go....believe me.


Aliki_N

    Reputation: 26
Re: Collision request
« Reply #24 on: February 04, 2012, 08:55:51 am »
February 04, 2012, 08:55:51 am
Concerning collision - for now we have no plans what so ever to include this simply because it does not fit the type of program really well. We want Lumion to be a program for movies and not for walk-troughs. Maybe in some future updates we can add extra camera types such as drive-trough, helicopter or walktrough but for now we have no plans for this. We have many exciting things on the list we want to complete first. Our primairy focus is fast and good looking architecture movies and there are many other areas that come first before we need a collision capable camera.

Dead end????

Re: Collision request
« Reply #25 on: February 06, 2012, 10:18:40 am »
February 06, 2012, 10:18:40 am
Dead end????

Not a certain dead end but I just want to make sure you know our position on this now. As we see it there are many more important areas we can improve upon before collision becomes important. Good examples are better reflections, sound, better lighting and things like that. We want Lumion to be a tool primairily for movies so we do not want to confuse things.

We have a lot of experience in the real-time area and we know that as soon as we start implementing real-time walk-trough functionality there's a whole list of extra features you cannot really do without. Think about doors opening, elevators, a top down map, interactive switching of materials and models and many other things. Another point is that the real-time performance of Lumion is not really that good compared to other engines optimized for real-time rendering. This is because we favor the final movie results and only aim to keep the real-time interaction good enough for setting up your scene and rendering a movie.

If we decide to do real-time walktroughs we would probably do it as a seperate product which combines smoothly with Lumion so the interface does not get cluttered and we can optimize for specific purposes.

dgilberto

    Reputation: 1
Re: Collision request
« Reply #26 on: February 07, 2012, 06:44:37 pm »
February 07, 2012, 06:44:37 pm
Not a certain dead end but I just want to make sure you know our position on this now. As we see it there are many more important areas we can improve upon before collision becomes important. Good examples are better reflections, sound, better lighting and things like that. We want Lumion to be a tool primairily for movies so we do not want to confuse things.

We have a lot of experience in the real-time area and we know that as soon as we start implementing real-time walk-trough functionality there's a whole list of extra features you cannot really do without. Think about doors opening, elevators, a top down map, interactive switching of materials and models and many other things. Another point is that the real-time performance of Lumion is not really that good compared to other engines optimized for real-time rendering. This is because we favor the final movie results and only aim to keep the real-time interaction good enough for setting up your scene and rendering a movie.

If we decide to do real-time walktroughs we would probably do it as a seperate product which combines smoothly with Lumion so the interface does not get cluttered and we can optimize for specific purposes.


Ok, it is your opinion and the valid one because you belong to the staff and I respect deeply. But as user, I observe that the Real Time it is so close that it is not an extra more ordinary needed feature, it is a feature that would convert Lumion to use in both ways. Film and RT.
Dgilberto

Aliki_N

    Reputation: 26
Re: Collision request
« Reply #27 on: February 08, 2012, 08:06:49 am »
February 08, 2012, 08:06:49 am
Hi Remko,

Much appreciated of the direction you want to take lumion to. However, you need to take cognisance  of the number of people that are requesting for this feature against say reflections, or improved lighting. Lumion's catch phrase has been "making architectural Visualisation much easier".
Much of architectural visualisation is done at a conceptual stage. One wants to interact with the client at a much earlier stage, walk the client through the project without having to final render 17 hours of high quality video. Changes and improvements are easier to implement in real time walk thrus. Lumion currently has collision detection with the built-in terrain. Why can't the same code be implemented on imported terrains? This way, one could import stair-case elements as objects, inject the collision detection code into them to be treated like terrains, Walk a character up the stair by collision detection or navigate up a stair via collision detection. I think given a chance to vote between this feature and lighting improvement, most users would vote collision detection. Lumion's artificial lighting is currently already within acceptable quality, in my opinion.
So please, put this feature as one of your priorities in this year's feature development. Remko, you are sometimes full of nice surprises, this might already have been included in Lumion 2.1 BUILD 1!!! he, he,he!

Regards,

Alickn

stucki

    Reputation: 32
Re: Collision request
« Reply #28 on: February 08, 2012, 10:11:45 am »
February 08, 2012, 10:11:45 am
i second that !

Re: Collision request
« Reply #29 on: February 08, 2012, 11:59:10 am »
February 08, 2012, 11:59:10 am
i second that !

There are a million different people and there are a million different wishes. We have some ideas lined up on how we can do things like collisions and walk-throughs but for now there's nothing more to do than waiting. Luckily we have 2.1 lined up to keep you busy :D We're now doing the final final tests and packaging the free version and hopefully you will be able to download it later today. The build looks good so far.