SketchUp 2016 Wishlist
-
128bit?
-
Sketchup with the mind, telepathically.
-
Faster imports
Better mapping
Quads
Proper animation
Keyframing
-
@rich o brien said:
Faster imports
Better mapping
Quads
Proper animation
Keyframing
yes, yes, yes, yes and yes.
-
Better mapping heck yeah, we need UV controls next
-
I bought AC3D just so I could have proper mapping tools.
-
maybe mess around with newer openGL stuffs* and change the look of, or allow additional controls over, the visual aspects of our models/workspace.
nothing too crazy yet (real time photorealistic rendering).. just a little more modern(?) looking
*.. that mention of newer openGL stuffs.. well, that's one of those mistakes of requesting a feature by offering the solution when in reality, i'm not sure if this is even an openGL thing
but i'll say it like that anyway
-
or at least offload that presentational aspect to StyleBuilder.
Which is still the same since its inception.
-
@numerobis said:
Compairing my wishlist for 2013, 2014, 2015...
- importing improvements (maybe this is improved with new face finder)
- Quads
- sub-D modeling
- better texturing tools
64bit
- multicore support (yes, this is the way processors evolve now - since a few years)
- high poly support
- faster ruby script execution (it's just a joke, that you have to watch a counter when you round some edges, where another app can do this instantly...)
- faster saving/auto-saving (!)
- faster explode or copy/paste (i have to test 2015...)
- disable/configure snapping
Can you elaborate on the "Multicore support"...?
I understand what multicore is, but unless you're talking about SU native render, what purpose would/should it serve...?As for the high poly support...
Please take one of your heavy models and give it a test with SU2015 64-bit, I'm sure you'll notice that it's behaving much better now...
I'm quite sure you can agree that the model no longer change to wireframe when orbiting or panning...I'll also claim that there is a much faster execution of ruby scripts...
-
@numerobis said:
...
- faster saving/auto-saving (!)
Have you tried disabling 'redefine thumbnail on save' in Model Info - File? Should make it save instantly (on an SSD).
-
@frederik said:
As for the high poly support...
Please take one of your heavy models and give it a test with SU2015 64-bit, I'm sure you'll notice that it's behaving much better now...
I'm quite sure you can agree that the model no longer change to wireframe when orbiting or panning...You need to be a bit careful saying that, Kim.
Many people assume that 64 will fix all their graphic issues, but if your card isn't up to it it won't totally solve the problem.
As you can see below , this is 64bit 2015, but on a steam driven laptop, and all the little columns in the balustrade and light fittings switch to wireframe when moving.
-
@box said:
You need to be a bit careful saying that, Kim.
Many people assume that 64 will fix all their graphic issues, but if your card isn't up to it it won't totally solve the problem.
As you can see below , this is 64bit 2015, but on a steam driven laptop, and all the little columns in the balustrade and light fittings switch to wireframe when moving.I see, Box...
It's just that IMPO it's now much more rare that I see these wireframes, when moving, so I believe that there's been a great improvement in this area already... -
True Kim and I'm sure there is a huge improvement. I don't expect this laptop to manage much better as I know it's graphics card is pretty basic. But thought it worth noting because people will complain when 64bit doesn't seem to make that much difference on their system.
-
So since layout got a little discreet love with 2015, in the form of dynamic reporting, I'm getting quite interested in the ultimate possibilities it holds. So Imma put down my wish for layout plugin support, plus an API.
-
I wish there was a date stamp that updates automatically. So many things missing in LO that make drawing production easier in CAD. This is only a small one, but saves headaches.
-
@frederik said:
Can you elaborate on the "Multicore support"...?
I understand what multicore is, but unless you're talking about SU native render, what purpose would/should it serve...?To improve the overall sketchup performance? If you compare the single thread performance of the processors of the last years, there has been not much improvement. The last bigger jump in IPC was from Nehalem/Westmere to Sandy Bridge with maybe 15-20%. Incl. the higher possible frequency a bit more - if you overclock. But the real progress is done on the core count - we are now at 14 cores @3,5GHz and up to 18 with slower clocks.
I'm aware that it is not an easy task to make a modeling program multithreaded and maybe there are many operations where it is impossible today. But when i look at the current and coming processors i think it is how it has to work now and that it is the only way to get more performance in the future if you look at the IPC improvements of the last two generations.
And i think there are things that could be "easily" done using multiple cores, like exporting images (as you mentioned), background saving or if it is only opening the components window with a few thousand entries. But i think also exploding should be possible, maybe more complex ruby scripts, maybe shadow calculation, everything that can be split up in several parts for processing...@frederik said:
As for the high poly support...
Please take one of your heavy models and give it a test with SU2015 64-bit, I'm sure you'll notice that it's behaving much better now...
I'm quite sure you can agree that the model no longer change to wireframe when orbiting or panning...I'll also claim that there is a much faster execution of ruby scripts...
I'm curious about it - i will try it.
@kaas said:
Have you tried disabling 'redefine thumbnail on save' in Model Info - File? Should make it save instantly (on an SSD).
i think i tried that already but i'll test it again. Thanks!
-
@pbacot said:
I wish there was a date stamp that updates automatically. So many things missing in LO that make drawing production easier in CAD. This is only a small one, but saves headaches.
Hi Peter, Layout does have Auto-Text tags that have a current date stamp, which always shows the current date. Is that not quite the feature you need?
Just insert this <CurrentDate> tag into any text.
-
Yes... I would love Layout to have Ruby. Never understood why Layout was such a separate program and had no developer support. We had all the drawing and text tools in SU. I always wondered why Layout wasn't actual inside of or part of SU.
-
@chris fullmer said:
@pbacot said:
I wish there was a date stamp that updates automatically. So many things missing in LO that make drawing production easier in CAD. This is only a small one, but saves headaches.
Hi Peter, Layout does have Auto-Text tags that have a current date stamp, which always shows the current date. Is that not quite the feature you need?
Just insert this <CurrentDate> tag into any text.
Nice. I looked around for command. Where are these tags?
-
Comparing my wishlist for 2013, 2014, 2015...
- importing improvements (maybe this is improved with new face finder)
- Quads
- sub-D modeling
- better texturing tools
64bit- multicore support (yes, this is the way processors evolve now - since a few years)
- high poly support
- faster ruby script execution (it's just a joke, that you have to watch a counter when you round some edges, where another app can do this instantly...)
- faster saving/auto-saving (!)
- faster explode or copy/paste (i have to test 2015...)
- disable/configure snapping
I add to my list:
- less wasted space around the icons, like it was up to v8. I can't find it to be better readable, it just looks worse and i have less space.
- a PhotoMatch window that has the same width as the other windows (layers/info etc.) so that they don't get wider when you dock it ...like it was in v8. I don't see any reason why this window has to be bigger now, same content. Just wasted space, again.
and... since this is a wish list (i don't really think this will ever happen): non destructive and parametrical modeling using a modifier stack or node graphs. But maybe we'll see a ruby
Advertisement