Author Topic: My wishlist - conclusions regarding Lumion  (Read 19306 times)

My wishlist - conclusions regarding Lumion
« Reply #15 on: January 05, 2011, 01:08:18 pm »
January 05, 2011, 01:08:18 pm
I understand what you mean, Gabriel.

The reason I asked is that there's already quite a few specialised road construction applications out there and we need to know what it is that you (and other architects/urban planners/engineers) feel is lacking in the existing applications.

In your case, you're using Allplan for modelling (but no designated road construction software), so you would be interested in a tool in Lumion which would speed up your workflow when constructing "basic" roads, for example by letting you import 2D CAD drawings from AutoCAD as an overlay combined with spline-based extrusions of customizable 2D road profiles. And I gather from your posts that it's tedious to get terrains and roads to match up in Allplan, so this would have to be addressed as well in Lumion.

In order for us to determine if there is a niche in the market, it would be great if other users could chime in with their workflows, so that we can build a better picture of what the majority of our users need. Do you agree with Gabriel's ideas?

Do any of you use designated road construction applications in your CAD workflow?
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.

mischa

    Reputation: 24
My wishlist - conclusions regarding Lumion
« Reply #16 on: January 05, 2011, 01:31:49 pm »
January 05, 2011, 01:31:49 pm
I don t use other applications for generating roads. I mainly model them in 3ds Max. The preconstruction is done in Autocad.

Aaron

    Reputation: 80
My wishlist - conclusions regarding Lumion
« Reply #17 on: January 05, 2011, 01:43:00 pm »
January 05, 2011, 01:43:00 pm
Same here as Mischa. 3dsMax for modeling and mapping of roads. There are lots of plugins but I dont use them much. Somehow they always fall short of what I need for a specific task.  This could be a hint to your question if there is a niche in the market. I think there most definitely is. Keep it simple and allow for importing of the most common formats concerning roaddesign. Make mapping and conforming to terrain a breeze and my guess would be the gods will reward you all with lots of camel and women.

My wishlist - conclusions regarding Lumion
« Reply #18 on: January 05, 2011, 01:46:55 pm »
January 05, 2011, 01:46:55 pm
LOL you can never have enough of those, Aaron…

Thanks for sharing your workflows, guys.
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.

Frank

    Reputation: 29
My wishlist - conclusions regarding Lumion
« Reply #19 on: January 05, 2011, 01:48:00 pm »
January 05, 2011, 01:48:00 pm
I model roads in Autocad. I think lumion is for visualisation, not a modeling tool.

But i agree with Aaron (including camels / women / residences and rollsroyce). Making roads in CAD is not one of my favourite things. 

Ferry

    Reputation: 0
My wishlist - conclusions regarding Lumion
« Reply #20 on: January 05, 2011, 02:00:35 pm »
January 05, 2011, 02:00:35 pm
My main problem is that Lumion is not a modeling tool.

 

Since if you suddenly make a big road building tool you might need to export that again and that is a road we don't want to go on.

Aaron

    Reputation: 80
My wishlist - conclusions regarding Lumion
« Reply #21 on: January 05, 2011, 02:16:25 pm »
January 05, 2011, 02:16:25 pm
I fully understand the pros and cons regarding possible integration of this feature. Like Frank commented, I'd be expressing myself gently when stating road modeling is not one of my favorite activities. Often I find myself finishing up a design and cutting corners where it concerns roads to make it come across at least somewhat integrated into its surroundings. As such I think, regarding a roadtool in Lumion, it would have to be looked at as a additional element inside the landscape editor. Not just pure fluff though but basic yet flexible enough to handle certain types of imports.

Gabriel

    Reputation: 0
My wishlist - conclusions regarding Lumion
« Reply #22 on: January 05, 2011, 06:44:13 pm »
January 05, 2011, 06:44:13 pm
Lumion is not a modeling tool, but yet it is. How come it is not a modelling tool if you get to make ALL landscape in it with sea, mountains etc. If this is not modelling than what is? The design of buildings only? Dunno.. maybe i am missing something here. For me it seems a very good terrain modelling tool (best until now in the easy-fun-results factor), and as far as i am concerned roads are an important part of terrain and always around buildings and make a lot of the human made landscape. 

If by modeling you understand the tedious thing that i do now with roads then yes, lumion should never ever go that way. It must be as fun and easy as the rest of the tools. The power of lumion so far as i;ve seen is that it keeps hard things simple. It'll fool you with it' s simplicity, yet there's a tiger under the hood.


Pete Stoppel

    Reputation: 33
My wishlist - conclusions regarding Lumion
« Reply #23 on: January 05, 2011, 06:58:59 pm »
January 05, 2011, 06:58:59 pm
If there was a way to export the Lumion terrain mesh and open up in your choice of modeling app, one would be able to create the roads as needed that follow the terrain, maybe this could be a future option?

Gabriel

    Reputation: 0
My wishlist - conclusions regarding Lumion
« Reply #24 on: January 05, 2011, 07:08:41 pm »
January 05, 2011, 07:08:41 pm
I gave an example of how hard it is to make a curved road on a real non flat terrain. For example I use stairs to fool the software when I make ramps for basement parkings.

For me it is damn hard and a killer to make. I guess there are other softwares out there that make this quick and easy, but as far as I am concerned I am an architect not a engineer. I do not need very exact roads, they just need to be there for a integration with the building and landscape. There is no need for advanced sections through the road, building details of the infrastructure or such. Just a basic thing.  

This is a typical ramp for cars, took just 10 secs to build, but just try and make some border on that curved thing, and time increases to 5-10 mins because you have to make a plan out of it and stick a "wall" to that plan.

 


Gabriel

    Reputation: 0
My wishlist - conclusions regarding Lumion
« Reply #25 on: January 05, 2011, 07:12:17 pm »
January 05, 2011, 07:12:17 pm
Solo said:

If there was a way to export the Lumion terrain mesh and open up in your choice of modeling app, one would be able to create the roads as needed that follow the terrain, maybe this could be a future option?






Yes, i agree, but problem is you export the terrain to that software, make a road on the terrain with that software, than import it back, add people, cars and trees (and the building) and then render. This seems like a inapropriate way to work, bound to import/export errors especially for large areas.

Gabriel

    Reputation: 0
My wishlist - conclusions regarding Lumion
« Reply #26 on: January 05, 2011, 07:19:34 pm »
January 05, 2011, 07:19:34 pm
Also, i would like to point out that underpasses, overpasses, bridges, multi-lane roundabouts, working traffic lights from multiple regions etc, that somebody told about in a previous post ARE incidental objects, not used all the time, and they may be integrated seamlessly by the user with a little extra work and taken easily from google warehouse. There is no need to actualy have all that in lumion.

Aaron

    Reputation: 80
My wishlist - conclusions regarding Lumion
« Reply #27 on: January 05, 2011, 08:25:14 pm »
January 05, 2011, 08:25:14 pm
Indeed imho it's kinda logical to have a great terrain editor, that even comes equipped with a material to seamlessly integrate terrain sections from imported models, seen extended with the same functionality where it concerns a important item in (urban)terrain design: roads. This however is not where the focus for ease of setting up your scene should stop. Again I point to Trainz sim 2010. With the same editor a fence is layed out around a house in seconds. Now try this in Lumion. The fences are there but I doubt you'll find many people enjoying fiddling with single units of fence or hedges to properly allign them around a sizeable campus, yard or officebuilding with many corners and elevations to tackle. The same doctrine applies for bassically every asset that you come across in most urban envorinments requiring array-style allignment and layout. Perhaps it would free the mind of some design burdens if the tool to be would therefore be conceived as a more generic layout assistant to give your scene a larger visual appeal then a merely exclusive road-editor would bring to the table. 

mischa

    Reputation: 24
My wishlist - conclusions regarding Lumion
« Reply #28 on: January 05, 2011, 09:05:35 pm »
January 05, 2011, 09:05:35 pm
If you add a road editor that would be great great thing, but then, after my opinion, an export function would be necessary.... (to import the model with the landscape and the roads into max for example).

Aaron

    Reputation: 80
My wishlist - conclusions regarding Lumion
« Reply #29 on: January 06, 2011, 12:55:24 am »
January 06, 2011, 12:55:24 am
Yes but surely the same could (and already has been) argued about the product without a roadeditor right? As Lumions features will expand in the near future there will also probably be a higher demand for cross-application export abilities yet it has been clearly stated, at several occassions, the developers dont want to go there so perhaps its best to focus on where they do want to go and the possibilities for everyone within that framework ;-)