SketchUp 2016 is here....
-
Oh, thanks! It is not so visible, as if there is nothing to see there
-
Hey guys,
As always, we do a bunch of testing on our website when we launch a new version. You should see more info on our blog and website pretty soon. But yes, it's real!
Mark, on behalf of the SketchUp team
-
-
Some nice improvements, though not the overwhelming feature additions some might look for.
this footnote will make my life easier: "*Bonus: we upgraded LayOut’s PDF exporter. Now, LayOut’s PDF exports are about 10-15x smaller. High five!"
And this is definitely an answer to Wishlist requests: "We’re proud to announce our first step towards an extension ecosystem for LayOut. Using this new API developers can now create and customize .layout files from SketchUp models."
-
An embarrassingly small new feature set, not sure how they'll justify the upgrade price this time...
-
'An embarrassingly small new feature set, not sure how they'll justify the upgrade price this time'
Well maybe it's just me.....but I'm not even mildly tempted
-
Version Make seems work also!
A new builder building maker!
-
PDF exporter is a good one!!
-
Oh, and the re-work of how layers can be manipulated in LO, much needed!!!!
-
Yeah, exporter upgrade is great work. I think that the updated inferencing engine will come in super handy on some of my engineering projects where I'm trying to align multiple items that are a long way apart:
Also, the reporter was sorely in need of update. If its as good as the cut list plugin then I'll be happy. Unfortunately I just finished writing about the built-in reporter's deficiencies so may have to redact my words.
-
I like:
- the speed increase in some of my ruby scripts
- you can leave the Outliner open when running ruby scripts. Up to v2015 that could make your ruby go very slow.
I have to get used to:
- the tray - Must read the manual. I don't want my materials docked. I want them where I want.
I had hoped:
- saving a file with 'redefine thumbnail on save' still takes a lot of time. Have to keep that one disabled.
-
@kaas said:
- you can leave the Outliner open when running ruby scripts. Up to v2015 that could make your ruby go very slow.
It still runs much slower... Where did you find differences? If it's in autohide the problem disappears as outliner... autohides
-
@jql said:
It still runs much slower... Where did you find differences? If it's in autohide the problem disappears as outliner... autohides
I tested it with a custom stencil plugin. Lots of calculations. It had just 1% difference in time with the outliner open or closed. (406 vs 390 seconds). In v2015, the same took 800 seconds so thats quite a speed increase. Have to do more investigations to see what/where/why
-
-
amongst other things, the talk of LO's C API has me excited to see what enhancements can be made to LO...
-
@ashscott said:
Banksy, is that you?
I wish
-
As Fredo said a few posts earlier - all current v2015-compatible Extensions/Plugins RBZs should, install, load and run OK in v2016 - BUT you must have the Preferences > Extensions Policy set to 'Unrestricted' [the shipped default].
If you change to another restricted policy, then only 'signed' extensions/plugins will load...
So it's highly recommended that you do not copy files from earlier Plugins folders [as it always was!], and that you get the latest versions of ALL of your extensions/plugins' RBZs, either from the EWH, or the SketchUcation PluginStore, or another trusted developer's site - NEVER use hooky-copies from dubious sites - they will either fail or contain malware, and harm the authors IP and maybe income etc...Currently all of the authors are getting their RBZ files signed by Trimble.
Fredo has already had all of his 'signed' - they are now all available from the PluginStore.
I have also had several of mine 'signed' - these are also in the PluginStore - others will follow soon.
Those RBZs I have also adjusted for other authors in the PluginStore [like Didier] will also get 'signed' versions available in due course.The test-version of the SketchUcation Toolset - aka 'ExtensionStore3' - was released a few days ago and this is already 'signed', in anticipation of the v2016 release.
The 'Unrestricted' policy will almost certainly not be around forever, so you need signed RBZs installing wherever they are available.
So probably one day 'unsigned' [or mis-signed] versions will become un-loadable - although there will be a [yet to be explained] 'developer-mode' to allow authors to test their new or modified code before hey have it 'signed' and published... -
@unknownuser said:
The 'Unrestricted' policy will almost certainly not be around forever, so you need signed RBZs installing wherever they are available
In that case how will authors be able to test scripts without signing them?
-
@pixero said:
@unknownuser said:
The 'Unrestricted' policy will almost certainly not be around forever, so you need signed RBZs installing wherever they are available
In that case how will authors be able to test scripts without signing them?
@tig said:
...although there will be a [yet to be explained] 'developer-mode' to allow authors to test their new or modified code before hey have it 'signed' and published...
-
Can someone explain to me the need to lock down the plugins / extensions? If you're not sure about the plugins / extensions and where you downloaded them from, surely you have prior knowledge that something could go wrong/break?
By locking down the plugins / extensions, are there any guarantees that there won't be any of these that clash with another? If that is the case, great, if not then I don't quite understand the need for the lock-down.
Advertisement