[Plugin] S4u Make Face
-
Yep, I can confirm what Ken says, it is a repeatable bugsplat.
-
Hi all!
I have post the version 1.0.0 while i find this error. -
First, Thanks so much for you job on plugins HDVP, really all the plugins that you did so amazing and very useful
.
Second, I wanted to ask you about a problem in S4U MakeFace 2.00 because really i can't resolve it, I don't why it don't make all the edges and just some edges like its appear in the attachment ?
-
At a guess it looks like you are trying to work at too small a scale.
If the piece is very small the faces can't form.
Try scaling up by 10 and trying again. -
@mokhtar : Can you post your sketchup file?
-
Update s4u MakeFace v3.0.0
FixBug crash Sketchup! -
-
-
Thanks! I will add soon!
-
I get an error on loading with the newest version on SU2016, both when installed via Extension Store and manually:
Error Loading File s4u_makeface/s4u_makeface_loader.rb
Could not find included file 's4u_makeface/s4u_makeface_loader.rb' -
The author needs to change his files and remake the RBZ [v3.0.1] and get it re-signed/republished...
The base-level 's4u_makeface.rb' which sets up the extension has a path set for the extension's loader to be:
's4u_makeface/s4u_makeface_loader.rb'
BUT that file does NOT exist !
There are two files added by the signing process:
's4u_makeface/s4u_makeface_loader.rbe'
's4u_makeface/s4u_makeface_loader.rbs'
If the base-level 's4u_makeface.rb' were to say:
's4u_makeface/s4u_makeface_loader'
it will work - however, editing this file manually breaks the signing hash!
So v2016 won't like it unless it's running in 'Unrestricted' mode.
So it must be done by the author and re-signed.This is a typical error caused by the new and unfortunately half-baked v2016 signing process which has been introduced.
An author testing his code with all .RB files in the subfolder will find it works, but making the RBZ with them included and then signing it, will then fail unless the specified loader path is left 'open ended' - i.e. it does not include a file-type suffix, and IF the author chooses any encryption at all - i.e. RBS or RBE - because only unencrypted RB files will work.
The new signer does not allow a mixture of RB and encrypted files [that used to be possible].
Also [at least at the moment] the signer perversely allows the author to add both types of encrypted files [RBS and RBE] into the same signed RBZ - although RBS works in ALL SketchUp versions anyway and publishing in RBE only protects the author's IP when there is no RBS version out there... ill-advisedly shipping them together means any 'hacker' can easily see inside the RBS anyway, and compromise the RBE's encryption.
Of course, publishing only RBE means the extension won't work in anything other than >=v2016 !
Also, if the signed RBZ includes encrypted files, then it may currently not be exempt from malicious tampering !
If someone were to [ill-adisedly] add their own 's4u_makeface/s4u_makeface_loader.rb' file that would NOT break the signing hash check in v2016, AND if the loader looks for an open-ended path [with no file-type specified], then the RB will load instead of the encrypted versions and this could do something wicked [it's RB/RBE/RBS load-order, with mo check on the signed/hashed files - at the moment ! ] - but of course unless you stupidly got the RBZ from an iffy site it should all be OK - but that's more to do with the source being trustworthy - like EWH or the SketchUcation PluginStore - rather than the RBZ being signed, which unfortunately on its own could offer only illusory assurance... -
In fact I had loaded the V 1 and not the V3 from the first post!
Else I have the same error message when I load the V3!
-
Works with any problem! Loaded by the first post file on the 2016!
S4u Make Face v1.0.0 + Free Visualizer + SU IVY
-
Thanks ALL,
I fixed it.
Please try again! -
Thank you!
-
Now works fine! V 3.02
-
BUT now the RBZ is no longer signed, and the two files inside it are no longer encrypted.
That RBZ will only work under v2016's 'Unrestricted' policy.
If you are happy to leave the files as RB, it still needs signing.
But if you have published in error then you need to tidy up your subfolder, in code inside the loader RB ? to delete those now rogue RB files in the subfolder, because otherwise these will remain in the subfolder after the new version is installed AND the older RB files will load in preference to any RBS in there !
That's also because you now have an open-ended file-path [no file-type suffix] in the loader RB... -
@tig said:
BUT now the RBZ is no longer signed, and the two files inside it are no longer encrypted.
That RBZ will only work under v2016's 'Unrestricted' policy.Sorry! I don't understand this.
-
Do you mean you don't understand me, or just what has happened ?
Here are screen-shots of the RBZs for the two versions', showing the subfolder's contents.
Clearly the 2nd one is not 'signed' [it has no hash file] and the files are RB, i.e. NOT encrypted at all...
-
Thank TIG!
I understand.I fix now.
Advertisement