sketchucation logo sketchucation
    • Login
    ℹ️ Licensed Extensions | FredoBatch, ElevationProfile, FredoSketch, LayOps, MatSim and Pic2Shape will require license from Sept 1st More Info

    Plugins 2016

    Scheduled Pinned Locked Moved Plugins
    5 Posts 3 Posters 721 Views 3 Watching
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • leedeeteeL Offline
      leedeetee
      last edited by

      Hi all,

      I was merrily using SUMake 2015 until I inadvertently updated it to 2016. I re-installed all the plug ins to 2016 but for some reason, many aren't showing up. Is it something I am doing or are they not compatible with 2016 yet? Chris Fullmer's extended view is a prime example, as is 1001bit pro.

      I was happy on 2015 - can this be ran alongside '16? Can't find anywhere to download if so.

      Many thanks.

      x

      1 Reply Last reply Reply Quote 0
      • D Offline
        driven
        last edited by

        go to Preferences >> Extensions and make sure they are 'checked' then restart SU...

        the auto 'on' for some plugins no longer works, but they run once this has been done manually...

        john

        learn from the mistakes of others, you may not live long enough to make them all yourself...

        1 Reply Last reply Reply Quote 0
        • leedeeteeL Offline
          leedeetee
          last edited by

          Hi,

          Many thanks for this - such an easy solution.

          I'm still having trouble with the Extended Views. Just not showing up anywhere. Is this a compatibility issue do you think?

          Thanks again.

          1 Reply Last reply Reply Quote 0
          • TIGT Offline
            TIG Moderator
            last edited by

            If something worked in v2014/2015, then it should work in v2016.

            There's this newfangled 'Extension Loading Policy' pseudo-security feature in v2016, accessed under Preferences, which means that extensions/plugins that are not 'signed' by Trimble, will have their auto-loading restricted or stopped, unless the Policy is set to be 'Unrestricted' [currently the shipped default, but not guaranteed as even being available to users in future versions].

            The unintended consequence of this draconian regime was that it broke the auto-activation of Extensions.
            It will need to get fixed in an upcoming maintenance release for v2016.
            Most authors write their Extensions to be set active when they first load [which is also remembered across sessions], the user can of course choose to deactivate them sometime later, and this is also remembered thereafter too.
            Unfortunately even when the Extension is coded this way the bugged v2016 perversely deactivates it when it first loads.
            But if you then activate the Extension manually it is remembered and works thereafter as you might hope...

            Do not be fooled by the EW saying that a particular Extension is not compatible with v2016 - this is misinformation.
            If it works with say v2015 it will almost certainly work with v2016, although, as I said earlier, if it's not signed by Trimble it will not auto-load in all security 'Policies'.
            Trimble misjudged the extent of the work required by their [unasked for] introduction of this spurious security system. All authors must now re-code parts of their extensions/plugins and then submit them as an un-encrypted RBZ to Trimble for the signing process [or resigning later on], to make them fully compliant with all of v2016's loading-policies - of course nearly all users will continue using 'unrestricted' mode anyway, making this whole process somewhat academic!
            All of these changes take time and effort, and most authors have little compunction to do this - after all, no one pays anything for most of this anyway ! ...
            Trimble say it gives comfort to users that the extension/plugin is genuine - because once signed with a hash, then any changes to it make it un-loadable in v2016.
            Of course the fact that the RBZ was downloaded from kosher sources like the EW, SketchUcation PluginStore or Smustard etc should have given the users that confidence anyway.
            It is quite possible to introduce additional files into a hashed RBZ that can do malicious [silent] things to the user's computer, without it being picked up in the hash-checking. Of course these doctored RBZs will be got from unofficial sites, so the user only has himself to blame...
            I have already shown Trimble [privately] how easy it is to do this sidestepping, and I expect an upcoming maintenance release will probably address at least some of these loopholes - however, hard working hackers will be looking at ways of circumventing the hash-checker even now... The only effective way is to include all files in the RBZ in the checking, which slows SketchUp v2016 startup even more than it is extended now by these additional processes...
            So there's a lot to resolve yet...

            TIG

            1 Reply Last reply Reply Quote 0
            • leedeeteeL Offline
              leedeetee
              last edited by

              Thanks for the thorough response, TIG, much appreciated and really interesting.

              1 Reply Last reply Reply Quote 0
              • 1 / 1
              • First post
                Last post
              Buy SketchPlus
              Buy SUbD
              Buy WrapR
              Buy eBook
              Buy Modelur
              Buy Vertex Tools
              Buy SketchCuisine
              Buy FormFonts

              Advertisement