[req]Model Scrambler
-
your too kind
-
@tig said:
You coul;d always delete the file ?
or, talk to h4zel:
http://www.sketchucation.com/forums/scf/viewtopic.php?f=15&t=18218
-
You could always delete the file ?
-
why??
-
If your forced to hand over a model that you dont want really want them to have.
-
@remus said:
If your forced to hand over a model that you dont want really want them to have.
how about if you could password protect a model? you could only use the camera on it.
-
@remus said:
I was wondering if it would be possible to make a script that:
- Exploded all groups/components in the model
- Purged the model
- Exploded all curves
- Unhid/unsmooth all geometry
- Hid a random selections of lines
- Rotated the whole model very slightly off axis in every direction
- Created lots of new layers and moved random pieces of geometry to the new layers
- Made components of random selections of geometry
And anything else that you can think of that would make it very hard/impossible to work on the file.
thats an awesome idea for a plugin! I really dont know how it could be useful, but still, I LOVE IT! How about also adding a feature, that when someone else, not allowed, tries to edit the model, all the electric appliances in a 10 meters radius will burn?
-
While we are at it, why not embed a virus with the model so if the user decides to alter the mesh in any way it drops a virus and removes the .ini files from his operating system and reboots to nothing?
Seriously I do not see any point to the above scrambler, if you do not want anyone to mess with your model then just do not send it to them.
-
@solo said:
Seriously I do not see any point to the above scrambler, if you do not want anyone to mess with your model then just do not send it to them.
ultimately, that's the best way to go about it..
that aside, maybe you could twist it ever so slightly with freescale2.. or export it as a dwg or something and re-import it -- do that a few times and i'm sure you'll be able to screw it up that way.
-
Don't forget to lock the compnents, and to have a component in a component in a component, etc.
And best of all, make a hidden line 1000 to 10000km away. No one will notice it, and guess what'll happen
-
Ideally all the changes would leave the model visually unchanged, though.
scrap the unsmoothing thing in the original post.
-
@remus said:
Ideally all the changes would leave the model visually unchanged, though.
AAaahhhh, that makes so much more sense now! You could write something like that.
model = Sketchup.active_model ents = model.entities group_found = true to_explode = [] curve = [] while group_found group_found = false ents = model.entities ents.each do |e| if e.typename == "Group" or e.typename == "ComponentInstance" to_explode.push e group_found = true end end to_explode.each { |e| e.explode } to_explode = [] end ents = model.entities ents.each do |e| if e.typename == "Edge" curve.push e if e.curve end end curve.each { |e| e.explode_curve }That is the explode all group/comps and then explode all curves part of the script. Just add something to randomly move geometry onto layers and hide things, delete all scenes, purge all, etc. Your good to go!
Chris
-
How difficult would it be to make a script that renders the model uneditable?, making it a locked component that cannot be unlocked without a password?
-
Cheers chris
I should have said that te model should appear unchanged in the original post, would have saved a lot of confusion i think. -
Also add some tiny faces with lots of random materials so that it would actually be a PITA to purge it. Ideally biiig tiff files or something.
-
Question: How do 'they' know what the model should be like ?
If they haven't seen it then you could send them any old model containing assorted rubbish...
If they've seen some images of it then send them any old model containing assorted old rubbish but with the same images inserted into it...
If they've received a draft of the model re-send that (perhaps with the later version images inserted).
Who are 'they' that 'they' can demand this model from ? If they 'own it', or have a claim on it in some way, you must give it to them - otherwise they can sue you... You should only ever agree to provide images unless they specifically are paying for the 3D model...
A contract in law is 'an offer' and 'an acceptance' - however, it usually consists of three basic bits 'a time/cost', 'a date' and 'a handshake': i.e. how long it'll take or how much it'll cost [the "lead-in time" and/or "the total cost" of the service/goods - often the same because "time is money"] + when it'll be ready [the "programme to delivery"] + what it is that's to be done [the "specification"]... Anything else is extra window dressing - what happens if xyz etc...
Who offered what to whom. Technically no 'consideration' is necessary (payment), but it does strengthen the case if something is paid for something that's not been received...
I say - don't give'em "it" unless they have a serious threat... By the way - the questions around scrambling / password-protecting models has been around since almost the start of Sketchup BUT it has never been sorted...
-
To be honest i havent thought a lot about the applications/implications of such a script.
The only real use i had in mind was if you wanted to send someone a file for visual inspection but didnt want them to be able to modify it.
I think it could be pretty useful in this context, as it makes it feasible to provide models for inspection by a client without risking them being able to use it. I imagine youd have to be quite careful using it in this context, though, as the potential for pissing of your client is pretty big.
-
I'd say password protection would be best. I know that there are ways to fix "messed up" models, but a password would be foolproof.
-
Ahh nice, that saves about 20 lines of code
I find I'm not very concise in my coding. I use a lot of lines to get stuff done. But its easier for me to read later when I'm checking over my code. -
Ok!
I test our codes, and yours is really, really faster than mine!!
100 times faster than mine...
IMO yours is faster because you don't enter into components to find sub components. You stay in model.
Great test! Thank you Chris!
Advertisement