SketchUP 8
-
I'm talking about new features. Why that 3ds Max, Maya , Modo and others allways include something handy and really neede when SU just integrates unneded crap like layout and google earth stuff? Where is normal texturing tools for archs for example? That's why I'm calling this SU 8 - another crap from google. Google thinks that my progress with modeling stay's in one position?
Come on -
I really needed to move on from 32bit memory space. Looks like I will have to buy a render app that has an external 64bit studio. Any recommendations?
-
@aidus said:
Why that 3ds Max, Maya , Modo and others allways include something handy and really neede when SU just integrates unneded crap like layout and google earth stuff?
Because it's fits Google's need?
@Last SketchUp and Google SketchUp clearly has different agendas.I don't think Google SketchUp will be competing about features in the same line as other modeller tools. So comparisons turn into oranges and apples.
Not saying that is good for the users - but just an observation of how I interpret Google SketchUp.
-
@cadmunkey said:
I really needed to move on from 32bit memory space. Looks like I will have to buy a render app that has an external 64bit studio. Any recommendations?
Don't know from the top of my head, but I think that there are several that are considering moving to studio. Think I's seen some chatter about this in the forum. So hopefully the options will expand.
-
@charly2008 said:
i installed Sketchup 8 free. I copied all my plugins and found four Rubies with Syntax errors.
Error Loading File balustrade_components.rb
C:/Program Files (x86)/Google/Google SketchUp 8/Plugins/balustrade_components.rb:228: syntax error, unexpected ',', expecting ')'
if (n1.between? (n2 - interval), (n2 + interval))
^Error Loading File C:/Program Files (x86)/Google/Google SketchUp 8/Plugins/cd_power_m.rb
...snip...Listen peepers.. when you see this error: syntax error, unexpected ',', expecting ')'
It means that Ruby 1.8.6 read a method call and mistook the 1st argument that was wrapped in ( ) as the entire argument list. So Ruby wanted to see the end of the line but of course there is a comma that separates arguments. You need to put a ( at the end of the method name, and a ) after the last argument.
For more info See: http://forums.sketchucation.com/viewtopic.php?f=323&t=14770&p=267503#p267503
. -
@thomthom said:
@aidus said:
Why that 3ds Max, Maya , Modo and others allways include something handy and really neede when SU just integrates unneded crap like layout and google earth stuff?
Because it's fits Google's need?
@Last SketchUp and Google SketchUp clearly has different agendas.I don't think Google SketchUp will be competing about features in the same line as other modeller tools. So comparisons turn into oranges and apples.
Not saying that is good for the users - but just an observation of how I interpret Google SketchUp.
And that's sketchups problem. From now sketchup is not for me. That's really sad.
-
Big time wait,....big time disappointment.
-
@aidus said:
And that's sketchups problem. From now sketchup is not for me. That's really sad.
Sad for who?
-
-
@thomthom said:
It's all about the right tool for the right job. And that is very subjective. It's not about using a hammer OR a screwdriver.
I agree 110%...!!!
Well said, Thomas...
-
whatever will happen, i will still use SketchUp..
-
Another disappointment. Google u r SH*T.
-
every new version we go through the same.. so many disappointed people you feel almost pain.. i will never stop being awed at the wonder of this program which has clearly such an affectionate place in our hearts..
i like and dislike programs, some very much, but sketchup.. it's always been a love thing.. a deep connection worth of depth psychology!
my meta-conclusion is that the program makes us feel co-creators, and google's custodian ears, can feel a little closed to our desires.. but they own it for their reason and so it is..
the blame rather has to be with those pesky ruby masters who shamelessly feed our addiction!!
vive sketchup!
-
@unknownuser said:
Another disappointment. Google u r SH*T.
Seriously?? What an ignorant remark! What are you disappointed about? At least try to explain yourself...you aren't making the situation better by just complaining.
Seems like Google would have saved themselves a huge headache by not making it free for thankless people.
-
@hieru said:
With no X64 or major improvements, shouldn't this be version 7.2?
Ditto! Is this 2010? Don't have many 32 Bit programs left. VUE 64 Bit; most Rendering 64.
Cad 64.....
All this time waiting for a mini Bonzai 3D?? -
@thomthom said:
More expanded changelog for SU8: http://sketchup.google.com/support/bin/answer.py?answer=115424
Thanks Thomthom! That helps.
-
Im really not seeing any point is 'upgrading' as there are no real improvements that i can see upon first glance that actually impact on 3d modelling workflow ... at least for us users who use the various plugins ...
-
@d12dozr said:
@unknownuser said:
Another disappointment. Google u r SH*T.
Seriously?? What an ignorant remark! What are you disappointed about? At least try to explain yourself...you aren't making the situation better by just complaining.
Seems like Google would have saved themselves a huge headache by not making it free for thankless people.
For me:
- Shadow bug not fixed.
- Not 64 bit
- No UI improvements
- No real technical improvements
And that's even before trying it out properly. There'll be more.
No way should this be a x. update. More like .x
With a MASSIVE company like Google behind it, it should be everything we want and more.
And maybe making it paid only would be a better idea, perhaps they would actually focus on Pro users, as we're the ones funding the development. What's the difference between Free & Pro? A few menu options? Not enough IMO.
-
@geomp said:
What's the difference between Free & Pro? A few menu options? Not enough IMO.
Are you serious...??
What about LayOut, a number of really great importers and exporters (i.e. vector, EPS, PDF) and a whole lot more...If you're so ungrateful and don't see the need in using SU, then please move on and find another app that will suit your needs... No-one is forcing you to use SU...
-
I must admit I was really really, really excited when I found out that SU8 was released. Ask yourself what was the first thing you thought when you first heard about the release? That would be the one thing you wanted most from SU8. For me that was "great, no more shadow bug!" I have a few other wishes as well, my top 4 would be: shadow bug fix (top priority), clipping bug, support higher polygon count, and a menu fix.
So I whip out my credit card for the upgrade fee, then I thought: "these are tough times, better check first". I think you know how the rest of that story goes. Truth be told, I'm ready to cut my losses and move on. I've supported SU over a few versions now, I've invested in some ruby scripts to augment the software and overcome shortcomings (this I don't mind as much), I've invested in a few different renderings apps, some of them promising a new release for more than a year and not getting there. However I believe the line in the sand has been drawn for me. I will not upgrade to my pro license to SU8 pro as I have no need for these purported improvements. If the next version of SU have not at least fixed the shadow problem, I have the distinct feeling I will not return to this software. Thus ending my financial support (through the plugins) to the developers of 3rd party plugins as well.
Looks like I got my menu fix, hardly something I would pay $95 for as I have a work-around I use.
Google is turning what was once software with a lot of potential and a keen following into a massive joke. Yes SU is inexpensive, that does not excuse the complacency that has set in with the Google development team and their development architects. Please quit giving us features that we didn't ask for - don't tell/give us what you think we want/need, we know what we want/need and we have not been secretive about it. Rather work on what we did ask for.
Please don't tell me there is no workaround for shadow-bug fix. How many programs are out there that does shadow projection? How many of them suffer the same ailment? How many programming solutions are there to this feature? If the current shadow projection engine only allows that one specific fix, isn't that a sign that the engine is obsolete and should be redeveloped? The owner of the code to the fix may be rich, but I'm sure something could have been hammered out if Google wanted to, but I get the idea they lack the will power to do so.
That's just me. I respect the opinions of my fellow forum members, but please stop protecting a software that is, for all practical reasons, stagnant. Face it, don't be in denial. SU8 is a placebo.
Advertisement