SU is great, but cannot handle complex models with trees etc
-
@unknownuser said:
That's Pete's (Solo) handiwork
Oops, missed the logo.
So....
Pete, every time I see something like that it tempts me try my hand at architecture. Amazing work
-
Yeah, that's a great piece of work from Pete. I thought it needed no intro with his logo in the corner.
Vue is an excellent bit of software. I don't have it installed at the moment, but I was playing with it When SU was still a twinkle in Brad Schell's eye...and when it was still playing second fiddle to Bryce.
Now, of course, it's being used for cgi enhancements to Pirates of the Carribean, Avatar and such, but is still reasonably priced ($199) and still as much fun to simply play with. It has a large amateur userbase, like Bryce or Poser, which gives some indication of its ease of use. -
@beschleunigt said:
Hello,
I like Sketchup very much but it is not suited for complex models with lots of trees or grass.
What do you recommend for that? I am using Macs so I cannot use 3D Studio Max.
The ideal program should have an GUI and modeling concept like Sketchup and some kind of workflow with sketchup would be great. I had Bonzai3D in mind and tried it, but it doesn't seem to be very fast with complex models.Do you have any ideas or experiences?
Kind regards
sketchup can go a lot farther when models are well organized with layers and scenes. you could also use a plugin like fredo's ghostcomp to hide the trees until they are needed for rendering or exporting images. to have a complex model and to keep all the elements on all the time is not the best practice, at least with sketchup.
-
Beschleunigt, Jason is right MOI is an excellent tool. Go get it while it's free and in beta. I am using it for converting rhino format files into sketch up models.I have started using the ghost comp ruby it makes a simple block object of your high poly component. It looks handy but takes a while to create the ghost component.I have created objects in sketch up that are so big 9/10 times sketch up crashes opening them ! I am wondering is it the viewport that makes sketch up slow or the application itself ?
a bit more background on MOI can be found here:
http://blog.novedge.com/2008/07/an-interview-wi.html
for other mac users Architosh is a good source.
-
@unknownuser said:
I like Sketchup very much but it is not suited for complex models with lots of trees or grass.
This is exactly the reason we developed Shaderlight's Replace Me feature. Being able to replace a complex model with a simple 2D proxy in your SketchUp scene that renders in glorious 3D with Shaderlight has been a real hit amongst landscape designers using complex tree and plant models.
-
@chedda said:
Beschleunigt, Jason is right MOI is an excellent tool. Go get it while it's free and in beta.
Free?
-
Mac version is free until the summer
Windows has either 30 day trial or save disabled
-
@unknownuser said:
Mac version is free until the summer
Windows has either 30 day trial or save disabled
Right after I posted that I was thinking they might have been talking about the MAC version. Sorry.
-
@chedda said:
I am wondering is it the viewport that makes sketch up slow or the application itself ?
I live near the edge of SketchUp's limits as a habit -- there are many ways to manage the issue once things are actually in SketchUp (via layers and such), however the hard part is actually importing outside assets in the first place (most of the time). I've seen SketchUp successfully import a high-poly model (after a few hours) only to have it crash once the viewport tries to draw it. This is the reason I shared the above style -- it will minimize the chances of that happening, and allow you to at least get the stuff into Sketchup long enough to save (which is its own ordeal).
Best,
Jason. -
I couldn't open the styles file. I think i know whats best from research already, no shadows, no profiles basically nothing. Your right imports take forever, then another eon if you need to explode or group. It's these extended periods when i feel sketch up could use all my cores. Even saving files takes forever, pfft. 3ds is definitely faster than .obj and you get groups. Your right i think the importers could be a lot more robust, is it just that the .skp format is so different from anything else mainstream ?
-
It's odd that you couldn't use the style -- it should be as simple as dropping it into one of your styles folders...
I'm not sure what the holdup is on importing -- I know some of the issues that effect Sketchup while you are working, but import/export innards are greek to me... probably TIG and some of the other plugin gurus could fill those gaps for you.
Who knows on the cores thing -- it makes sense to me, but the base core of SketchUp must be completely incompatible with modern hardware architecture somehow... I know pure Ruby creates limits on multi-core for the free version... but if you are using SketchUp Pro that should not be an issue at import/export.
At one point in time they tried to do multi-core in Layout and it got messed up -- so they dropped it in the next update and I'm not sure if it ever got put back in.
Best,
Jason. -
In addition to the mentioned ways of handling complex scenes:
use a low poly component as placeholder, eg. a cylinder for a tree, one for each component you will use later. You can scale and rotate and this information will be kept.
Use random selection of a set of components to generate eg. a forest.After you set up a certain scene you can go to component library, select the placeholder, select component instances and then select "replace selected". (right click on high poly component)
That way you can make a big scene and handle it in viewport and replace it with high poly objects later. Keep im mind to set the pivot correctly within the components as these will be inserted there.
Definitely for handling bigger scenes in SU a good computer is a must.
Importing big files can be tricky, import files in parts, if possible.
The same for big automatised functions, using plugins.
Sometimes it's just better to use it on parts, not all at once.And never forget to save before you do a critical action
-
@jason_maranto said:
At one point in time they tried to do multi-core in Layout and it got messed up -- so they dropped it in the next update and I'm not sure if it ever got put back in.
multi threading for modeling operations (i.e. geometric calculations) is a pretty non-trivial thing, this shouldn't be underestimated... I'm not aware of any recent modeler being capable to do this, besides simple raster operations during rendering/raytracing of course.
Even file I/O operations putting to another thread seems to be difficult, at least according to the reply of John Bacus in the Google Help Group concerning my corresponding proposal. A further posting concerning multi-threading can be found here.
The sophisticated inference engine and geometry merging etc. that we all do like su much do obviously have a negative effect on application responsiveness which increases (maybe exponentially) with high poly count models of course.
Norbert
-
Thanks for the links sketch.de, they make interesting reading. I think the high poly, import and exploding problems have all been accelerated as sketch up has evolved. The render engines have opened up sketch up and have produced some spectacular results, people enjoy using sketch up and want to add all that detail that makes a good image. Also i think because of the huge user base a lot of people have grown inside sketch up, because it's so fast to model surely it was inevitable they need higher poly support. Perhaps 64 bit or multiple processor support is not easy or ideal, but at some point the application needs to respond to modern hardware. Other apps manage fine, so i believe it must be possible. perhaps inference and the other cpu hungry processes can be toggled off. I am becoming increasingly frustrated in the amount of crashes and lost modeling time, the worst thing is even with a lot of research sketch up is pretty much irreplaceable.
It seems that google are being tight lipped understandably but that could be a good thing, at least it seems like a sign that something is coming. Because of the huge range of users and the large free user base i think the answer lies in making the pro & free version more different. I expect most pro users would pay more for extra features i know i would. I have been with sketch up since v4.0.chedda
-
Google for sure have a different ethos to @last, the free version will fill all their GE needs, they can then open another avenue to add to their empire. I suppose to the google overlords sketch up is almost irrelevant it's a shame really because i'd like to see the roots driven love in the app.
-
@chedda said:
It seems that google are being tight lipped understandably but that could be a good thing, at least it seems like a sign that something is coming. Because of the huge range of users and the large free user base i think the answer lies in making the pro & free version more different. I expect most pro users would pay more for extra features i know i would. I have been with sketch up since v4.0.
I also agree and think it would be a good incentive to get free users to make the leap to Pro -- It may be my native paranoid thought processes at work, but part of me believes the reason SketchUp is not developed in that direction is because it has no application for Google Earth, and therefor to Google. They want low poly, and SketchUp (as it is now) already suits their purposes -- adding real high-poly support seems counterproductive to their goals.
Don't get me wrong, I like talking to the SketchUp devs -- and I'm not pinning this on them, I think it comes from above them... maybe from much higher.
I mean lets break it down, free version users are not the real customers of SketchUp (from Google POV) -- the real customers would the pro users of Google Earth, and the advertisers on Google Earth -- SketchUp free version users are meant to be a free labor workforce to populate Google Earth, making it a more compelling environment -- which would in turn draw more users, which would in turn generate more ad revenue for Google.
Best,
Jason. -
I've proposed a "work for SketchUp Pro" scheme that I thought would benefit everybody -- but it didn't seem to resonate with them (SketchUp) for some reason.
My idea was to give 3D warehouse users credits toward a SketchUp Pro license for each model they have accepted into Google Earth (maybe 1-5$ per model).
I thought this would rapidly increase the amount of models on Google Earth (making Google happy) and also allow people who could not afford a license to get a legitimate copy of SketchUp Pro.
I'm not sure why they didn't go for this idea...
Best,
Jason. -
some users might still know the times of @Last and the type of models SU was meant to be used for... today users are trying to replace expensive AEC/BIM apps like Allplan or ArchiCAD or Revit etc. and claiming that their 150mb model does lag during push'pulling and screen transformations etc. sometimes using a weak system additionally.
I very doubt that demanding development tasks as e.g. multi-threading for modeling operations which are still not solved by the 'big boys' can be done by the probably small SU dev team and from the revenues of the SUP version.
in short, evolution yes, revolution nope
jm2cts,
Norbert -
I don't think this thread has anything to do with Modeling operations at all -- this is about importing large assets from other packages... I think most users know that you can manipulate SketchUp to work well (or passably) with very large files once you actually successfully get them into SketchUp in the first place.
I have 6 3D packages and none of them have the problems of SketchUp (on open/import/save) and all of them can handle far more polys in camera movements and editing with no issues -- and several of them are cheaper than SketchUp Pro... and many of them are older too.
It doesn't add up... and SketchUp does not play well with others.
On top of all that there is the UV layout mess that is SketchUp -- it's almost comical to see the UV's SketchUp makes sometimes.
Best,
Jason. -
@jason_maranto said:
I don't think this thread has anything to do with Modeling operations at all -- this is about importing large assets from other packages...
I don't think this thread has anything to do with Data Exchange operations at all -- this is about using high poly count models in SU.
@jason_maranto said:
I think most users know that you can manipulate SketchUp to work well (or passably) with very large files once you actually successfully get them into SketchUp in the first place.
not the initial poster, data exchange was mentioned by you first.
@jason_maranto said:
I have 6 3D packages and none of them have the problems of SketchUp (on open/import/save) and all of them can handle far more polys in camera movements and editing with no issues -- and several of them are cheaper than SketchUp Pro... and many of them are older too.
and none of them is comparable with SU in the sense of user interface interactivity.
I do not deny that improvements concerning speed are possible and required and btw done already for all of the latest releases. I doubt that with the current implementation and internal data structures the speed improvements in quantum leap size many users are expecting for future releases are in general possible.
anywayz, future will show and we and our customers would be more than happy to have a lightnin' fast SU in the hopefully very near future.
cross fingers,
Norbert
Advertisement