John Bacus interview about Sketchup 7
-
If you look at the current results of this survey, it says that performance is only the fourth most important issue. According to this, a new survey has been released where the "feature requests" possible to select are mostly things that could be done via plugins.
-
Slap a skirt on me and call me Shirley, but I think your interpretation of the results is off. Better yet: the results show that the likes of Bigstick, Kwistenbiebel and myself are not quite as marginal, with regards to our wishes for SU, as some make us out to be.
-
I never meant "marginal" but not a first priority (the "powerful" thing there refers to modeling tools while the "run faster" is about performance).
Look guys, I am not against high poly support at all - what's more, I have also voted for that when I filled in the survey. It's just other people who would like other things prior to this.
-
Not knowing the description given when asking the question: I'd say "powerful" refers to the amount of stuff (complexity) the program can push around without straining...ie. "high poly"?
-
Well, if you have a look at the original survey, it says it a bit more detailed: "More powerful (e.g., add new features and support different kinds of modeling)"
So this is the result the new survey is based on. "What tools"
-
Gotcha...still?
-
Yeah, the "wording...", I know. And the "Run faster" option is not very clear either...
-
@gaieus said:
I never meant "marginal" but not a first priority (the "powerful" thing there refers to modeling tools while the "run faster" is about performance).
Look guys, I am not against high poly support at all - what's more, I have also voted for that when I filled in the survey. It's just other people who would like other things prior to this.
lol. I wasn't referring to you.
-
I'm all for better high poly support as well (
), although i think there are other important things to look at as well. -
I read JB's interview with Architosh quite carefully before responding. I have to say that I agree with his whole multithreading argument. With something like rendering for example, it lends itself very well to multithreading. You start a process and then when the CPU has a big chunk of work to do, it can be divided up into separate chunks for parallel processing. It is probably only Ruby and a few other operations that would benefit from multi-threading. For example file import/export, sandbox activities and that sort of thing where a specific task can be 'farmed out' to the various cores. This is his linear workflow argument and it seems to be convincing to me.
As has been discussed previously, one of the drawbacks with the later releases of SU is slow orbiting. I did think that some kind of keyboard override to disable inferencing while orbiting might improve things a lot here. This seemed to me to be completely logical and perhaps an easy temporary fix. However, the point about the viewer seeming no faster without (apparently) having inferencing was interesting and would tend to indicate that this might not be the case. Can anyone shed any more light on this? We know the SU team checks out the forum threads.
But - I have to come back to the point about orbiting (and high poly support because the 2 issues are linked), SU is not fast enough when manipulating large or complex models. I think the survey is misleading because the questions are too vague. If you want a survey to be of any value at all, you have to be very specific about the questions asked, otherwise you can't really draw any meaningful conclusions. In my opinion, the question about making SU more powerful should have explicitly mentioned adding new features, and the issue regarding improving speed ought to have been clarified in terms of improving shadows, and performance with more detailed models. I mean, in what other ways is the performance unsatisfactory?
I am an unashamed SU fan, I really love using the application, except when the limitations become an obstacle to the design process. It's useful and fun to be able to model a whole building, including some of the detailed construction elements, and to see how these things affect the whole building before you actually start construction.
I'm sure I can't be alone in going to site and finding that the clumsy and ugly way some of the services have been integrated lets a building down. SU has the facility to include as much detail as possible to effectively simulate construction before you get on site. The more detail you add, the more problems you can anticipate and solve. I think it's practical, efficient and (still) fun!
With the cool plugins that are available, you can try out different design options, including light fittings, furniture and render them to show clients and inform the design.I'm not sure the SU team really appreciate exactly how obsessive architects in particular can be in terms of design. With components (and more so with DCs) we can be so much more fanatical about this stuff. For some of us it's like 3d OCD! As a result it is absolutely imperative that we get nice, smooth navigation of detailed models. Other apps can do it, and I don't think it's an unfair request. It might be a massive job to improve the geometry manipulation, but I'm sure it's going to be necessary some time or other, so why not now? You really need to get the foundation of anything right, and a fast, smooth and reliable geometry engine which supports tens or even hundreds of thousands of polygons is essential.
No-one is expecting the core application to be a cheap or free alternative to 3ds max, Lightwave or Maya with NURBS and bones and fabric and in-built photorealistic rendering, but we do want to be able to add lots of detailed basic geometry and be able to smoothly and freely navigate some complex models with textures and shadows.
To be honest, I don't really think there is much point in adding many new features if we can't use the existing ones with a satisfactory degree of complexity. If SU does become 'more powerful', it's unlikely that this is going reduce model complexity is it?
So if I'm speaking from a position of unparalleled ignorance, sorry - but quite a few of us really do think that we need a more capable 3d core.
-
@bigstick said:
To be honest, I don't really think there is much point in adding many new features if we can't use the existing ones with a satisfactory degree of complexity. If SU does become 'more powerful', it's unlikely that this is going reduce model complexity is it?
Sorry to pick just one phrase out of your well formulated discours, Jim, (I really dig the whole post), but I can't help reacting on this line.
You hit the sweet spot with it.
Without optimisation of the Sketchup core code, new functionality will indeed make no sense.
The new in(ter)ference engine makes SU a tad slower than before. Also the DC (which is a nice feature by the way)pushes the limit.
I think it all proves that the SU engine is running at its limit.....
In the survey, if 'more power ' means having more functions than 'more speed ' needs to be solved first.As some of the other members here, I support the idea to further 'OpenUp' the Sketchup 'Platform' and make a strong playground for the plugin developers. But they will need a stronger base to work on to get serious things going.
It is good that SU still is a lightweight app (as Kmead pointed out) and it should stay that way. A strong but small Sketchup can be the foundation and open platform for lots and lots of plugins for different kinds of purposes.I see parallels with how Microsoft is now trying to strip the current Vista and make a smaller but more stable core and release it as 'Windows 7' (next year). Sketchup should be going that route as well imho.
Make it small but powerfull and make it as open as possible for 3td party devs.Asking for 64 bit and multicore (those words are starting to sound nasty) is not just about high poly modeling, it is also about stretching the live span of Sketchup and strengthening it for more years to come.
64 bit is not marginal anymore. If you are about to buy a PC soon, really consider a 64 bit OS, as 32 bit will be dead in a year (or two) for newly purchased computers.
64 bit has much more to offer now and it IS very stable, especially in Vista. -
@unknownuser said:
Make it small but powerfull and make it as open as possible for 3rd party devs.
My thoughts exactly.
-
Great post bigstick. I agree and i also don't think were asking for too much. In the post i made for the "sketchup 8 wishlist" thread (http://www.sketchucation.com/forums/scf/viewtopic.php?f=10&t=14234&st=0&sk=t&sd=a&hilit=wishlist#p111818) most things asked were just solving bugs and optimization.
@unknownuser said:
Your first mistake was to buy the model....build your own!! SU is just not built for importing complex x-format models...it is built for modeling!!
When i say that i had to fix a big (as you think) imported model knowing that i had to redo some of the modeling and texturing (with some using uv unwarping) should tell you that i'm should be able of doing most of the model in sketchup, but even so, the main reason people sometimes have to use other models (skp or any other format) to do a work it's probably the most (if not always) requested thing in this works: SPEED (very short deadlines to answer). And if sketchup it's not built for import then they shouldn't put that option in there. And you still didn't answer my question in that post..
-
@unknownuser said:
SU is just not built for importing complex x-format models...it is built for modeling!!
Correction, for modeling simple things only.
SU is probably suited for woodworkers, as the geometry will be simple enough.
For architects, SU is only suited for pre-design.
Don't try to use it as a visualisation tool for architecture, as Sketchup will choke on anything more than a beautiful 3D tree you want to import. -
@kwistenbiebel said:
Don't try to use it as a visualisation tool for architecture, as Sketchup will choke on anything more than a beautiful 3D tree you want to import.
And where would architects be without trees?
-
Quite interesting read. We all love SU and that is a reason why we are all so frustrated. I must say that SU (pro) still feels like inherited burden for Google.
Looking to improve existing SU without looking at the heart of problem will not bring solution. Reality is that core is very old and without complete rewrite things will not improve. Now question is does Google want to do that or not. My gutt feeling is that the answere is no simply because the current version serves perfectly the purpose for which Google bought it. I would love to be proven wrong though.
What we need is strong , stable and fast modeling core which can handle a lot of geometry and with import and export facility which works.
As it stand SU is slipping(big time)from ArchViz tool to PreViz tool. -
Wasnt it always meant to be a previz tool form the start?
-
No I do not think so Remus. It was originally made as ArchViz tool.
-
@kwistenbiebel said:
Correction, for modeling simple things only.
SU is probably suited for woodworkers, as the geometry will be simple enough.
For architects, SU is only suited for pre-designActually I disagree, and I'm sure this was really meant tongue-in-cheek.
I have attached some links to images of why I disagree. These are images of a model which is for design development.
We have all seen some of your fabulous work, you can't tell me that you don't use SU as a tool for evaluating design options. This is why I got involved with rendering
For me it makes SU a proper design development (and communication) tool. These images are just based on showing the client design proposals, no creating great images. In fact I only really use rendering for this purpose. It is true that free-form organic modelling with any degree of precision is almost impossible, but my buildings don't have the budget for this degree of complexity anyway. I add door handles and even signs to my models, so I can get a more accurate idea of how things will look in real life. All architects must have experienced the awful reality that occurs when what you have designed in the office, just doesn't look right at all when finished. I try to use SU (and renderers) to avoid/minimise this. -
It was indeed a tongue in cheek remark I was making.
Off course Sketchup is a very good visualisation tool.
I am just experiencing the damn limits of the software concerning the polycount handicap, and especially when using render software.If you really want to take visualization (rendering) to the next level, Sketchup fails.
It will work for simple buildings , adding some props and 3D trees around it , but once you go for streetscapes or bigger projects part of a masterplan, Sketchup becomes a real pain. Modeling wise, no problem, but it will become too slow to handle, despite of the tricks we all know by now.It is a pitty, because Sketchup could have that potential.
If only Google saw this too.....(yawn).....
Advertisement