SU 9 Wishlist
-
@a_iverson said:
I want to learn can i create like this in sketchup and can i get powerfull renders like this.
If not, i must learn 3ds max
That is more about learning the render engine of choice - the modelling is just one part of it.
-
Trimble wants especially one thing: invest strongly into SketchUp. That's something we haven't heard for years.
There hasn't been any totally new release under Trimble (only a Google-branded bugfix release at the transaction days). And it's still true that they say they don't reveal their future product plans (from which we can't deduce that they don't want these features).
So we shouldn't assume SketchUp 9 won't contain any features. -
I still want a constraint override button or keyboard shortcut and Object Snap Options! (also fix that center snap I'm tired of hovering)
One outrageous wish is NURBS curves for SU
Cheers
-
mi wish: That SU doesn't become bloatware because some people don't get it's lean efficiency. If I wanted it to perform like AutoBad, ArchiCAD, Solidworks or 3D Studio that is what I would have bought not come here b*tchin about it not doing the same job.
-
@arcad-uk said:
mi wish: That SU doesn't become bloatware because some people don't get it's lean efficiency. If I wanted it to perform like AutoBad, ArchiCAD, Solidworks or 3D Studio that is what I would have bought not come here b*tchin about it not doing the same job.
-
@andomar said:
i'm sorry but it is mi wish:
trimble sketchup team should resign. why?, beacuse they don't want SU 64 bits, don`t want improve uv maping, don't want multi threading, they don want do nothing, so only they want the users of sketchup migrate to max,to rhino, sometime i think they only want our beloved SU die.For finish, This is not to offend or annoy to the trimble sketchup team, but it`s that they are communicating.
Where did you hear all this info?
-
-
@andomar said:
Here : http://productforums.google.com/forum/#!category-topic/sketchup/feature-suggestions/cqdbwirP_T8
And you did read the explanation to why they are not focusing on 64bit? As they try to explain, 64bit doesn't magically makes applications go faster. All it means is that it can address more memory. And I have never seen SketchUp ever run out of memory. Only times the SketchUp process has run out of memory has been when using render engines which runs inside SketchUp instead of spawning their own separate one. And that's really a design issue with the render application, not SketchUp.
As Jason explains there, it's better to ask what you really want instead of guessing on technical implementations. Leave the technical implementation to the developers. -
@thomthom said:
@andomar said:
Here : http://productforums.google.com/forum/#!category-topic/sketchup/feature-suggestions/cqdbwirP_T8
And you did read the explanation to why they are not focusing on 64bit? As they try to explain, 64bit doesn't magically makes applications go faster. All it means is that it can address more memory. And I have never seen SketchUp ever run out of memory. Only times the SketchUp process has run out of memory has been when using render engines which runs inside SketchUp instead of spawning their own separate one. And that's really a design issue with the render application, not SketchUp.
As Jason explains there, it's better to ask what you really want instead of guessing on technical implementations. Leave the technical implementation to the developers.Let's take a look at exploding or terrain creation for instance. Now those procedures knock SU out. Wouldn't 64bit architecture solve the bottle neck? (when I make 'mesh attaching' in Max 64bit for example (no mention 'bout heavy vray rendering) it really eats huge amount of RAM)
(me by no means a teck geek so I really wonder) -
@rv1974 said:
@thomthom said:
@andomar said:
Here : http://productforums.google.com/forum/#!category-topic/sketchup/feature-suggestions/cqdbwirP_T8
And you did read the explanation to why they are not focusing on 64bit? As they try to explain, 64bit doesn't magically makes applications go faster. All it means is that it can address more memory. And I have never seen SketchUp ever run out of memory. Only times the SketchUp process has run out of memory has been when using render engines which runs inside SketchUp instead of spawning their own separate one. And that's really a design issue with the render application, not SketchUp.
As Jason explains there, it's better to ask what you really want instead of guessing on technical implementations. Leave the technical implementation to the developers.Let's take a look at exploding or terrain creation for instance. Now those procedures knock SU out. Wouldn't 64bit architecture solve the bottle neck?
Explode is terrible slow - agree. But I've never seen it crash due to that. 64bit really means nothing more than being able to address more memory. Being able to address more memory doesn't mean more speed. In fact, you double the size of the data and switching to 63bit over 32bit might make things slower.
I don't know why people keep thinking 64bit as a magic bullet for anything - but unless the application is running out of memory it's no point asking for it.Instead it's best to leave it to the developers of the application. Your example of Explode is a good one: Ask for better performance when exploding geometry - leave the technical implementation to the developers who knows the complexity of the SketchUp source code and platform. If you just ask for 64bit when you really mean faster explode performance they'll never guess where to improve it. If there where to implement 64bit explode would still be as disappointed.
The slowness of explode I think has something to do with how SketchUp merges geometry. Whenever you explode it needs to compare every entity with every other in the context and compare for intersection and merge etc. Whatever they can do to improve that is something only they know as it involves the inner working of the SketchUp engine.
-
@rv1974 said:
(when I make 'mesh attaching' in Max 64bit for example
mesh attachment in Max is fast in 32bit as well. But remember that Max doesn't merge and intersect mesh automatically like SketchUp does. In Max you need to weld the mesh together manually. It's a very different animal in terms of how it manages and deals with geometry. Also remember that SketchUp also has it inference engine and always tries to render the viewport in it's sketchy style - while Max quickly degrades the viewport and it's not as much as a WYSIWYG viewport as SU is. SketchUp is doing a whole lot of work automatically which many other modelling applications doesn't.
@rv1974 said:
(no mention 'bout heavy vray rendering) it really eats huge amount of RAM)
Render engines of course benefits from 64bit - but not in speed. Just being able to address that much data so it doesn't crash. But SketchUp render engines can make use of 64bit - as long as they create their own process outside the SketchUp process. That's a technical implementation and design that only they are responsible for - not SketchUp.
-
Interesting that you have to drag up a two year old thread from when SU was under Google to prejudge Trimble's development plans which are as yet unknown! If SU is holding you back go buy something else that does the job.
-
Want Split Screen Operations, such as in blender? I guess with Split Screen Trimble could invest some huge $$$$.
-
Not that again. Sheesh! There's absolutely no need for multiple screens as in Blender. This as been discussed multiple times over the years.
-
@dave r said:
Not that again. Sheesh! There's absolutely no need for multiple screens as in Blender. This as been discussed multiple times over the years.
My bad, I thought it comming...
I actally wan't another window: ["window/another view" menu item], which will open and let you place it, move-it, size it, such as standard tool window. In another window I want to be able to orbit, move and zoom camera, but without being let to make modifications, nor select anything. Just, a window where you could see from another viewpoint. Plus, an API to that where you can set camera pos, direction, fov... I don't think that this will require modifying the standard SU class. Its not a pain of work
-
You could just set a scene on the view you're working on then spin the model as you wish and when done you can go back to exactly where you were with one click?
-
You can turn off the "animation" transition between scenes so you get an almost instant jump between views if that helps?
-
@arcad-uk said:
You can turn off the "animation" transition between scenes so you get an almost instant jump between views if that helps?
THks, but I'm not a noob with that
I jst planned to create a multiplayer game at Sketchy Physics, with two viewpoints. -
@desertraven said:
I still want a constraint override button or keyboard shortcut and Object Snap Options! (also fix that center snap I'm tired of hovering)
came in here to post exactly this.
-
@thomthom said:
Explode is terrible slow - agree. But I've never seen it crash due to that.
I have, on numerous occasions, had crashes when exploding heavy geometry like imported high quality furniture.
For the VR apartment I posted a while ago I had to separate the apartment into ten different SU models with up the four models/ scenes per room.
Another strangeness often seem to appear when having heavy models in SU is that upon save or sometimes just by closing a group it often unsmoothes random parts of the model.
Memory issues?I'm not wishing for a 64 bit version to gain speed. I just want SU to be able to handle bigger/heavier scenes.
Advertisement