Google Sketchup Pro 7 is out
-
@mike lucey said:
Paul, I agree with what you say about the need for better 2D
drafting capability in SU and LO2 and I believe you are right
in saying that such features would be welcomed by many. It
would in deed be a big seller for Google but I doubt SU will
go this route as it is my understanding that SU policy is to
'shake hands' rather than compete with 2D applications.Still, as you say one never knows
Mike
Mike, I don't mean all singing and dancing 2D cad tools, just the sort you can get with the free CD on computer magazines, just integrated into Layout thats all. That wouldn't be so hard or cause 2D CAD wars would it?
anyway enough moaning now. I'm off to play with Sketchup 7
-
I'd say that if only one thing comes from all the posting and commenting here it is that GSU needs to develop a dialog between themselves and the pro users. Really that seems to be the heart of problem here.
-
Rick, although i agree with most of what youve said, i think SU has moved on form its sketched based origins. It is so easy to create hugely detailed models, if only SU was faster!
Larry, i have to agree. I cant help but think a huge amount of hassle could have been prevented if there was a good dialogue between developers and users.
-
They clearly need to issue a formal plan stating the direction they are headed with the software. If they would have discussed it, this entire thread wouldn't exist.
-
ignoring multicore these days is a complete joke to me. it's totally clear for everyone that there will be no substantial improvements in processor speed in the near future - the future is multicore! ok, implementing multicore usage for modeling seems to be not that easy but i think i has to be done because it's seems to be the only way to speed things up. And why not using multicore for the rendering part? seeing 3 cores sleeping while exporting a picture takes half an hour is really annoying...
definition of "semi high poly":
this skp file has 140mb on the hdd and needs ~1gb ram! and i would call it only "semi high poly". in max i can handle 7 mio polys or more without such big problems...and it's not only about display and modeling speed... saving such big files is veeery slow in skp and importing objects with some 100k polys is taking ages. when i have to copy/paste only a few polys from this skp file to another sometimes i wait for 15-30 min before skp is responding again...
and 64bit support becomes quite useful if you try to export a model like this for rendering (or as dwg/3ds) and skp likes to crash at ~1.6gb ram usage...
-
it is a shame so many of you feel very disappointed about this release, maybe it was always impossible for Google to meet up such great expectations and waiting so long to release V7 only increased it by 10 fold. Now don't forget that when you pay peanuts you get monkeys... i am sorry to say some of you expected a version capable to deliver what a five times more expensive application still does not! I still think that pound for pound this application remains one of the easiest to learn and use and fills a niche of the market that few others can compete with and if you are after something more sophisticated then there's dozens of other programs out there that you should try, but don't expect it to meet all your expectations. I have used a few and despite the incredible progress most developers can still learn one thing or two from this humble application....
-
@rickw said:
A big one is that ruby scripts can now bypass a lot of UI calls and boost performance (by around 2x) when creating/querying geometry. This has been a bottleneck for 3 versions, and is now fixed!
That is very good to hear. Ruby speed was another of my wishes. Would you happen to know; is the SU UI more responsive when a ruby is working now? In SU6 when a ruby did some working and displayed a progressbar, the instant you switched focus away from SU the SU UI would flicker madly for a couple of seconds before it didn't update until the ruby was finished, making it impossible to know if the ruby had stalled or not, or get any more info to when it'd complete.
-
Brad Schell once commented that the intent of @Last was to develop the core product and let third-party ruby authors create peripheral capabilities. That intent is apparently still the driving force with Google now, since SU7 has improved the core significantly. No, it's not all bells and whistles (that's what ruby is for, in part), it's a more stable, more versatile platform. It's also still called SketchUp.
It seems we have all just gotten so used to pushing it so far beyond its intended capabilities that we want/expect the combined capability of Rhino/Modo/Maya/Max/fill-in-the-blank wrapped in the familiar SU interface, and we want it last year.I understand/sympathize/agree with the multicore, high-poly, shadow-bug-fix disappointments. I've also been alternately thrilled (new/requested capabilities and fixes to reported bugs) and disappointed (a few unfixed anomalies) with ruby issues as well. But considering what I can accomplish in 7 versus 6, I'm moving forward.
Similar complaints surrounded the release of 6, since few realized the huge potential that was added through ruby enhancements (observers and webDialogs). We still have yet to really hit the broader potential of those new features. There are similar enhancements to 7 that are either unnoticed/unknown or as-yet-underappreciated. A big one is that ruby scripts can now bypass a lot of UI calls and boost performance (by up to 2x) when creating/querying geometry. This has been a bottleneck for 3 versions, and is now fixed! I also think the power of DCs is unappreciated. There is HUGE potential waiting for 3rd party developers here, FAR BEYOND just prebuilt manufacturers' components (he said, with a knowing smile).
As for some of the rancor in this thread, my goodness - it sounds worse than tomsdesk, solo, bellwells, and me in a political discussion!
(I am glad we can all still be friends, even after that)Bottom line:
Was it everything that everyone wanted? No. Clearly no.
Is it an improvement over 6? Yes. Tremendous. And (as yet) unappreciated. -
@rickw said:
Brad Schell once commented that the intent of @Last was to develop the core product and let third-party ruby authors create peripheral capabilities. That intent is apparently still the driving force with Google now, since SU7 has improved the core significantly.
Agreed Rick.
I refer to a session at 3DBC 2008 - "Maxing Out Your Productivity with Ruby Scripts" where Tyler Miller spoke of Google's slant on Ruby....
http://sites.google.com/site/3dbasecamp2008/all-sessions-2008/maxing-out-your-productivity-with-ruby-scripts
Scroll through to 41 minutes, 20 seconds...Quote:"A word about how these API’s kinda come out…you would think the main desire here is for us to provide the ability to create a bunch of new tools for SketchUp…the reality is it come about ‘cause we’re kind of lazy as developers……. And ah, we get overwhelmed with all these requests and, ah we think “how can we sucker other peopleinto doing this for us….” unquote
I'm sure you remember Rick, you had just left the lectern!!!
-
I was using the trial version of SketchUp Pro 7 and I must say that in my humble opinion, I feel desepcionado Aldo, I thought that going to be faced with a version passed completely, with a lot more modeling tools taking as examples the number of plugins that are on everything in this forum, but only parts of the expanded program, it appears that users, advanced by calling them in some way are not the priority for developers, there was not even a change of interface as to say, it will change the face Not because it is necessary, if not compensate for waiting so long, I hope that any updates are remedied this, greetings to all and anyway thanks for a new version that makes this remains so alive.
-
@utiler said:
I refer to a session at 3DBC 2008 - "Maxing Out Your Productivity with Ruby Scripts" where Tyler Miller spoke of Google's slant on Ruby....
http://sites.google.com/site/3dbasecamp2008/all-sessions-2008/maxing-out-your-productivity-with-ruby-scripts
Scroll through to 41 minutes, 20 seconds...Quote:"A word about how these API’s kinda come out…you would think the main desire here is for us to provide the ability to create a bunch of new tools for SketchUp…the reality is it come about ‘cause we’re kind of lazy as developers……. And ah, we get overwhelmed with all these requests and, ah we think “how can we sucker other peopleinto doing this for us….” unquote
I'm sure you remember Rick, you had just left the lectern!!!
Ah, good times! Yep, I remember (and am looking forward to the next 3DBC) - I also remember laughing about it - both the truth and the humor of the situation
-
A quick maybe stupid question, I want to upgrade to SU7 to check it out for myself, will this overwrite my SU6? Will I have to buy a full license to SU7 if I want to keep SU6 and SU7? Thanks.
Mike
-
@alpro said:
A quick maybe stupid question, I want to upgrade to SU7 to check it out for myself, will this overwrite my SU6? Will I have to buy a full license to SU7 if I want to keep SU6 and SU7? Thanks.
No, the two versions will peacefully coexist - better than some forum members, even!
-
@unknownuser said:
Rick wrote:
No, the two versions will peacefully coexist - better than some forum members, even!
At least we get threads going, agreeing is overated afterall.
-
One important issue that nobody mentioned is.... drum roll. Does the Drape tool work without bugsplates in SU7?
-
I agree Solo....
-
Thanks for the info, now to get that upgrade.
Mike
-
@unknownuser said:
A quick maybe stupid question, I want to upgrade to SU7 to check it out for myself, will this overwrite my SU6?
That was not so evident because
here or there was not the same !
Second was seem overpass the previus version yesterday
First is cool today! -
I'm a bit surprised that the Leopard hang is still present. Good thing ThawUp didn't assume SU7 would fix it.
-
@remus said:
i think SU has moved on form its sketched based origins.
hehe - yeah, we kidnapped it and took it with us
But seriously, that is, I think, the root of the whole problem here - the difference between @Last/Google's intent and the users' collective intent. They still see it as SketchUp, while we tend to see it as IWantItToDoEverythingThatTheSoftwareIDoNotWantToSpendTheTimeOrMoneyOnCanDoUp. The turmoil comes from the different expectations...
@thomthom said:
@rickw said:
A big one is that ruby scripts can now bypass a lot of UI calls and boost performance (by up to 2x) when creating/querying geometry. This has been a bottleneck for 3 versions, and is now fixed!
That is very good to hear. Ruby speed was another of my wishes. Would you happen to know; is the SU UI more responsive when a ruby is working now? In SU6 when a ruby did some working and displayed a progressbar, the instant you switched focus away from SU the SU UI would flicker madly for a couple of seconds before it didn't update until the ruby was finished, making it impossible to know if the ruby had stalled or not, or get any more info to when it'd complete.
I haven't checked that particular issue yet. It's been on my pester-my-Google-friends list for some time
EDIT: Just tried the lose-focus issue with ImageProfile in SU7. Mixed reviews: if the window is not covered up by another app, losing focus doesn't lose status bar updates (I started the IP process, then clicked on my browser in another monitor, still got feedback). However, when I restored Excel over SU then tried to refocus on SU, got a blank screen until it was done processing (less than a minute).
Advertisement