Wishlist SU 8... Let's not !
-
I say fix the core so that it supports higher polys then open source it and let the scripters loose.
-
I think google really needs to take sketchup more seriously and what i mean is:
1- TRY YOUR OWN SOFTWARE!! And preferably in something more advance than cubes or playgrounds... (this way you will know the limitations of your own software so that you can see why users are getting so frustated with the SU bugs and limitis, and you'll stop doing some dumb decisions like the way your new component browser works...who the hell aproved that?!?)
2- Build a robust platform for others to work, compatible with current and future technology (so that plugin makers can also take advantage of this and build better and faster plugins)
3- Have the basic tools work as it should (offsets, shadows, from countors, 3d model formats import, and so on...)
4- Don't be afraid of building tools that there's already a plugin for it (for the love of god we need a plugin to do a basic scale not oriented with the axes or for having a better mesh than "from contours" can give...oh, and keep in mind that any new tool SHOULDN'T be ruby because they run slower than SU native tools)
5- and most important: LISTEN TO USER'S FEEDBACK (and if possible answer them)
-
I hope that this time su developers will listen to real su users and will made some noticable changes. Or this su 8 whislist will be like su 7 whishlist. No more stupid useless dynamic components - real improvements are neded.
-
What makes SU one of the best modeler is not the capacity of making complex forms, but its easy to use, intuitive interface.
1.- I suggest Google should focus in 3 things
Make a excellent platform for 3d Modeling so ruby scripters and coders can make fast and powerful dinamic and specialized tools. Make it Opensource!2.- Integrate real time lights, animations, and reflections, don't need to be perfect but to make it a nice preview (leave perfection for render engines)
But keeping the nice workflow it already has.3.- Concentrate efforts to take the 3D to the web once and for all.
Integrate a powerful 3D viewer native to Goole Chrome and in Goole Gadgets for Firefox and other web browsers. So the web end user can view a webpage and interact as freely as posible (for example make it possible for end users activate Dynamic Components in webpages).
The 3D warehouse and Google earth is just a start. If google can transform web pages into 3D showrooms it would bust online sales as clients can better know the product they are looking at).Make sketchup the new tool to make 3D showrooms 3D Adds and 3D webpages
Google Keep the good work
-
@aidus said:
No more stupid useless dynamic components - real improvements are neded.
Have you got any good suggestions then? Something a little more imaginative than high poly/64 bit etc. ? I'm genuinely interested in these amazing new tools thats everyones requesting, all those ground breaking ideas that no ones thought of before.
-
Remus wrote:
@unknownuser said:
Something a little more imaginative than high poly
Remus I have to disagree there as once we get high poly support then we will be able to imagine, until then we are very limitted.
-
Im not saying high poly would be a bad thing. Im just saying many people seem to be fixated on it to the extent that they dont bother thinking about large scale enhancements that would continue to make SU a ground breaking program.
-
remus:
- add the same line tools from layout
- put "add Detail" tool doing a basic smooth on meshs
- select orientation of the scale tool
- make texture unique working on non complanar meshs (the begining of uv unwarping...)
- make scenes save the positions of points (allowing some basic animation and morphs)
- add a real time graphic engine (like a game engine where we would import our models and play movies and save pictures in real time with soft shadows and reflections and mix it with line styles...let's be honest there's not a single game right now that don't display better pictures in real time than sketchup)
Should i go on remus? Except from the real time graphic engine, i'm not asking too much (it's just ideas for make existing tools better) but i seriously doubt that anyone from google is hearing...
But high poly suport, 64bits suport, multi core suport is (STILL) the most important for me before adding anything new. -
I honestly cannot think of one 'large scale enhancement' that would not require SU to perform better for it to work.
My point here is that Google needs to go back to basics and build a better foundation for SU, we want our favorite app to improve and enable us to do basic things that other apps do but we are restricted to an aged foundation that cannot carry the load of these new tools. So as much as we dream of cool new features we have to be realistic that SU cannot handle them.What bothers me more than the poly problem is Googles non communication policy, they have never discussed this burning issue ever and probably will never as they have no solutions.
-
Give it back to @last and let them run it. Google can lease it or something.
-
DacaD, you are demonstrating my point rather nicely. Aside from the game engine none of those ideas would bring any long term improvement. SU will not last any length of time if all they do is add 'features' like this. These are the sort of features i think should be implemented through ruby.
I am not arguing against better support for large models, it is entirely necessary. I'm just trying to point out that it is not the only thing we should be thinking about. SU needs big new features to keep it going, it needs stuff that is going to differentiate it from the other packages out there after theyve all finished copying the inference system and push/pull. this is the stuff i think the development team should be working on.
-
@solo said:
What bothers me more than the poly problem is Googles non communication policy, they have never discussed this burning issue ever and probably will never as they have no solutions.
Too true, i think improving communication between the developers and the community would ease matters a lot.
shakes fist at google policy
-
I suppose my question is - Why should Google care about Sketchup beyond the basic tie-ins to things like Google Earth. I can't imagine that the revenues from Pro are that substantial and they certainly take a lot of negative flack from the 'pros' who use it.
-
@solo said:
My point here is that Google needs to go back to basics and build a better foundation for SU, we want our favorite app to improve and enable us to do basic things that other apps do but we are restricted to an aged foundation that cannot carry the load of these new tools. So as much as we dream of cool new features we have to be realistic that SU cannot handle them.
What bothers me more than the poly problem is Googles non communication policy, they have never discussed this burning issue ever and probably will never as they have no solutions.
Quoted for agreement. The way development is going now, saying SU is starting to fall behind is something of an understatement.
sighs
@double espresso said:
I suppose my question is - Why should Google care about Sketchup beyond the basic tie-ins to things like Google Earth. I can't imagine that the revenues from Pro are that substantial and they certainly take a lot of negative flack from the 'pros' who use it.
I think you are right. They don't care - SU's just another marketing scheme to them. I mean, they certainly have the resources to be able to compete with the one or two man dev teams out there, now don't they? Anyone remember the vids they used to announce the release of 7? QED.
-
@jmmad said:
3.- Concentrate efforts to take the 3D to the web once and for all.
I absolutely agree; here is my take on that:
Rather than starting with a wishlist, I suggest we try to persuade Google that Sketchup should be a major element in linking human activities via the web; and that both the design and promotion of SU 8 should reflect this.
My summary conclusion is that producers should provide accurate Sketchup models of their products and present them, not in a warehouse, but directly in the user interface. Models are promoted in a file sharing type network, each with its own data formatted for comparative analyses. Users call up previews, download alternative products and assemble selections in their own models.
I believe this plays to three key elements of the web - searching, advertising and, not yet really exploited, data sharing - and, technically and commercially, works as well for water taps as for major developments.
Chris
-
Google can fix that stupid bug when zooming in very close to object.
Better dwg export. Offten lines are missing and some unneeded lines are showing up.And one more thing: when a plane is created and under this plane you place some object (really close but not connected to plane) then when zooming out that object beyond that plane shows up.
Later I will add some screenshot to better understand about what I'm talking.
Thist ugly bug was presented in SU6 and still presenting in SU7 like all other bugs!
Nothing was fixed!PS. Remus I'm not talking about new tools I'm talking about fixing.
-
I hear some of you guys wishing for a good 3D web implementation.
I am not against that, but I am afraid that if it would become the full focus of the SU dev team, we can forget about high poly support and a smoother core all together.
Also, I like Lineas suggestion that Google needs to be more on its tows and watch its own market instead of staring at the belly button and just do what they think would be cool to impress their bosses.
Having a 'market watcher' as that Ubuntu guy would be a great staff member. At least than we can expect things people really care for in upcoming versions.As it is now, no one can really be happy with how things are going.
-
Solo said
@unknownuser said:I say fix the core so that it supports higher polys then open source it and let the scripters loose.
I agree. I think the problem is Google don't seem to understand who uses SU and where to develop. If their only reference point is 3d warehouse then we're all screwed. Open source SU as soon as possible.
This doesn't necessarily mean Google are totally out of the loop. Ubuntu (linux) employ a "community manager" (he's called Jono Bacon http://www.jonobacon.org/) whose sole job is to report back to Ubuntu about scripts and plug-ins and needs in the community and recommend that they are integrated in the core product. Because of this Ubuntu are able to release a new version every 6 months.Chris said
@unknownuser said:My summary conclusion is that producers should provide accurate Sketchup models of their products and present them, not in a warehouse, but directly in the user interface. Models are promoted in a file sharing type network, each with its own data formatted for comparative analyses. Users call up previews, download alternative products and assemble selections in their own models
Maybe I'm shortsighted but is all this virtual product stuff really necessary? SU is going to need very high end rendering capabilities to satisfy the marketing reps. For the architecture industry I think SU have already missed the boat, or probably were never on the same boat as apps like Revit that now have repositries of building products.
But for consumer products I can't see SU being instrumental in this way. If people want something, they buy it. We like everything in 3d, but I just can't see most people orbiting vr models of everything or building a 3d room to place that lamp before buying. When 3d printing really takes off and you can download and print a product at home, then maybe SU has a place, but high poly support will be essential. Google could waste alot of time on this and it could amount to about as much use as Lively.Espresso wrote
@unknownuser said:
I can't imagine that the revenues from Pro are that substantial and they certainly take a lot of negative flack from the 'pros' who use it.
It's worth remembering that SU wasn't always free and would never have got anywhere if people didn't buy it. I don't imagine Google are exempt from the current financial crisis. If it's a question of whether or not Google need the money, then I think they should let us know. I'm still happy to pay for the tool that I use most at work but I won't bother if there is no point.
This comes back to the open source suggestion. Alot of open-source projects give their product away but make money by selling educational materials, providing training and hosting events. So Google could still turn a profit. Donations are also an important revenue for o.s. ventures, if people care enough, maybe this approach is better than Pro licensing. -
@linea said:
Maybe I'm shortsighted but is all this virtual product stuff really necessary?
Well maybe not short sighted but please consider this:
As far as I know designers have always made "virtual products", it is just that they call them drawings, sketches, models and so forth. All I'm suggesting is that instead of the designer making a model of a door, manufacturers' make their own versions and each offers it directly in the designer's interface, most importantly when requested (designer clicks Find). For this to work the versions have to be compatible. Sketchup provides a simple method for them to be so with very few rules.
@unknownuser said:
Advertising and media agencies will be all over this straight away, then SU is going to need very high end rendering capabilities to satisfy the marketing reps selling these products.
No I don't think this is true. More likely rather than use traditional agencies, manufacturers will look directly to expert modellers to provide models suitable for intended purpose. For general design and construction purposes they would likely be raw and light with emphasis on supporting data; for presentations, yes, probably high end rendering.
@unknownuser said:
For the architecture industry I think SU have already missed the boat, probably were never on the same boat as apps like Revit that let you integrate building products.
Absolutely not - there are very few manufacturers doing this; there has never yet been a comprehensive move for manufacturers to be brought in to the design process as early as possible, yet they contribute an ever increasing amount of design input. I think the aim is to persuade building owners to require their designers use accurate models of real products. Then the building industry will then have a chance to act like a proper industry.(Egon-esque!)
@unknownuser said:
But for consumer products I can't see SU being instrumental in this way.
I think, with respect, separating out consumer products is irrelevant, simply because we live, work and shop in buildings, and whatever we consume should be accommodated by their design. (e.g. how many Barbie dolls fit on a supermarket shelf?)
What I think is better than having wishlists for improving SU is to suggest other ways for SU to fit in with what seems to be Google philosophy. (i.e aiming higher than the SU team)
Chris
-
@chrisglasier said:
What I think is better than having wishlists for improving SU is to suggest other ways for SU to fit in with what seems to be Google philosophy. (i.e aiming higher than the SU team)
ChrisI tried to avoid having a 'classic' wishlist here, hence my first post.
Maybe I need to change the thread title.
Advertisement