Greeble Beta (Updated Feb-06-2009)
-
, yeah I know this version right now has bugs. I made the mistake of updating it thinking I had all the bugs worked out. Then I found some problems and realized I did not have a backup copy of the older version - oops! So give me some time and I'lkl get a more stable version up, but I might have to revert a few features.@Todd the progressbar.rb is a great idea. I was a little overwhelmed thinking about making an hourglass cursor and stuff, but progressbar sounds like a great option!
Chris
-
Interesting. It should not happen. Would you mind trying again with this new version I just finished? It now supports (requires) progressbar.rb from smustard and it also supports a min/max offset value. I think its kind of confusing, but I'll leave it in because it is sort of cool what it allows you to do. But to get decent results, the first offset # should be closer to zero than the second offset number. Or set them both to zero for no offset or both to -10 for an even -10 offset on all faces. And remember, that negative numbers will make an inset face, while positive numbers will offset a larger face. It might be time to update my beginning video now. Thanks for testing everyone!
Chris
-
Another thing
Is that normal on a Tin surface all facets are selected but all facets don't be greebled
-
Thank you sir Malaise!
I will take care next time
-
Sorry but nothing works with this last version
( maybe because i am in cm and your written in inch ?)
Have you somewhere an old version because I have yet a version that not working now
(I have not made a saving one of the previus
I must go back to Protrude
-
Partly due to the outrage expressed in this thread, I've decided to dis-allow posting of other people's scripts. A script author needs to be able to control which version of the script is available, and where it is posted.
-
Hi Pilou
here is the first version
MALAISE
[removed attachment] -- Jim
-
@jim said:
Partly due to the outrage expressed in this thread, I've decided to dis-allow posting of other people's scripts. A script author needs to be able to control which version of the script is available, and where it is posted.
There's a huge difference between someone helping another member out by posting an earlier version that worked for them and someone who's collecting other people's rubies and charging money for them.
Chris said, on this page: yeah I know this version right now has bugs. I made the mistake of updating it thinking I had all the bugs worked out. Then I found some problems and realized I did not have a backup copy of the older version - oops!
-
Okay John, I guess Jim would like members to follow these guidelines applying common sense of course.
-
No problems Folks.... I understand.
MALAISE -
Oh dear, go to bed and all heck breaks loose
I'll look at the script right now and see if its better. It sure run smoothly on my computer I was testing it on, so it definitely could be the metric problem. Thanks for the patience,
Chris
-
Well this is driving me nuts. I can see already that the version I uploaded is not the most recent version based on a few tweaks that are wrong. SO I'll go to the computer I was working on this on and see if it has the most recent. I did find a the spot that the script is breaking, and its in a spot that looks stable. Soooo, hopefully I'll find the working copy again and be able to upload that later today.
Chris
EDIT: for now, if someone wants to post an older working version, I wouldn't mind having a copy either
But once I get the script working, I wouldn't mind it being removed. -
Take your time!
And a little trick ; when you develop : make some copy any time on any version on any supports!
DD,DVD, Usb,Net etc...
That can seems obvious but now your prog is only maybe less than 10 Kb so some easy to recover
That will be not the case when you will have some megas of code!
-
@chris fullmer said:
Well this is driving me nuts. I can see already that the version I uploaded is not the most recent version based on a few tweaks that are wrong. SO I'll go to the computer I was working on this on and see if it has the most recent. I did find a the spot that the script is breaking, and its in a spot that looks stable. Soooo, hopefully I'll find the working copy again and be able to upload that later today.
Chris
EDIT: for now, if someone wants to post an older working version, I wouldn't mind having a copy either
But once I get the script working, I wouldn't mind it being removed.Nice addition Chris!
FYI: I just d/led this file. it works with SU 7 but SU6
It might be better to simply post updated scripts in a zip or rar file that way the rar or zip will have a revision number you can always keep track of. Instead of simply changing the original post. Its just an idea I had. -
@tomot said:
FYI: I just d/led this file. it works with SU 7 but SU6
It might be better to simply post updated scripts in a zip or rar file that way the rar or zip will have a revision number you can always keep track of. Instead of simply changing the original post. Its just an idea I had.that should have read " FYI: I just d/led this file. it works with SU 7 butnotSU6"
-
@unknownuser said:
that should have read " FYI: I just d/led this file. it works with SU 7 but not SU6"
aaaaaaaaaaaaaaaaahhhhhhhhhhhhhhhhh !
-
@chris fullmer said:
EDIT: If any Ruby coders are still following this thread, I am having problems that some greebles end up overlapping other faces and then delete faces that are queued to be greebled, then my script stops because it runs across a face that has been deleted. At least that is what I think is happening. So to solve that do I need to test each face to make sure it is not delete before I run the offset and push/pull?
If you are trying to modify deleted objects then you should get an error in the console about that. If that's your problem then do a .valid? test on the entity you try to work with.
I'm currently working on a script where I clean up the model, deleting lots of stuff and I've run into all sorts of problems as things shifts around when you delete entities. It seems the best is to loop over an array copy of entities which you've collected in before hand.
-
OK, so I'm getting some conflicting reports here (between my home and work computer). I've uploaded the most recent version. It works perfectly on my office XP, SU7 computer. I found a bug that caused SU6 to not work. It should now be working perfectly in 6. But it is not working on my home Vista SU7 machine. So if anyone has troubles with it now, let me know the SU version number and the platform. Thanks!
Chris
EDIT: If any Ruby coders are still following this thread, I am having problems that some greebles end up overlapping other faces and then delete faces that are queued to be greebled, then my script stops because it runs across a face that has been deleted. At least that is what I think is happening. So to solve that do I need to test each face to make sure it is not delete before I run the offset and push/pull?
-
Thanks Thom, I think that is what the problem is. I am getting this error
Error: #<TypeError: reference to deleted Face>
and it happens when I am repeatedly apply greeble to very messy geometry - like faces that have been greebled many times already and are overlapping all over the place. Eventually it just breaks with that error. I'll add a validity check, and hopefully that will clear it up. I don't think I can keep rechecking the model entities though because the script creates so much geometry that I don't want touched. I only want it to work on the faces that exist before I begin the script. But the more intertwined those faces are, the more likely I am te have one of them overlap and delete a face that has not been greebled, thereby breaking the script. So, I'll try the a.valid and see if that does the trick. Thanks Thom!
Chris
-
Definitely test with face.valid?
if face.valid? #do code here endAs for SU6/7 issues, it could be an issue of the model.start_operation(name,true) breaking SU6, since SU6 only takes one argument. I use this:
(Sketchup.version[0,1].to_i<7) ? (view.model.start_operation "name here") ; (view.model.start_operation "name here", true)obviously changing "name here" to something a bit more descriptive
Advertisement