[Plugin] Honeycomber

juanjo

Hello TIG
Thanks again for another amazing plugin. Seems I haven't been able to get this one working.
I followed the install instructions. Activated the extension. I can see "TIG::Honeycomber" on the tools menu, but can't see nothing on the toolbar.
Issues: When I run the tool, (select a group or component) it just prompts the main parameters dialog. It does not prompt what you say on the tool description
(structure, foam, comb menus). I kinda runs (turns to xray mode and the shell parameter does works) but it doesn't do anything else... no geometry population, nothing.

also i noticed that i don't have any file called "honeyFOAMER" as you describe... all the files in the installer folder refer to "honeyCOMBER" not FOAMER

(i am using skp8 on bootcamp but i've never had any trouble with your plugins before)

i'd really appreciate your help because i'd rally like to play with this jewell
and THANKS AGAIN for such great work

best regards

TIG

@oxer said:

Hi TIG,
I'm testing the plugin on Mac OSX 10.6.8 & SU 8 and the plugin doesn't work, it appears this error in Ruby Console window
[attachment=0:h2gpf8qe]Error.jpg[/attachment:h2gpf8qe]
Oxer !
The correct path for MAC Plugins is in the Root Library tree, NOT the User one...

Something is seriously adrift here.
Line #599 reads
rayt=@model.raytest([zcent, Z_AXIS], true)
where
zcent is a point3d
Z_AXIS is a vector
true says to ignore hidden objects.
Where's the 'float' issue arising...
Try reinstalling it properly.
Do not edit it etc before installing in case it's been corrupted in some way...
I suspect that something is up with your SUp installation otherwise.

TIG

@juanjo said:

Hello TIG
Thanks again for another amazing plugin. Seems I haven't been able to get this one working.
I followed the install instructions. Activated the extension. I can see "TIG::Honeycomber" on the tools menu, but can't see nothing on the toolbar.
Issues: When I run the tool, (select a group or component) it just prompts the main parameters dialog. It does not prompt what you say on the tool description
(structure, foam, comb menus). I kinda runs (turns to xray mode and the shell parameter does works) but it doesn't do anything else... no geometry population, nothing.

also i noticed that i don't have any file called "honeyFOAMER" as you describe... all the files in the installer folder refer to "honeyCOMBER" not FOAMER

(i am using skp8 on bootcamp but i've never had any trouble with your plugins before)

i'd really appreciate your help because i'd rally like to play with this jewell
and THANKS AGAIN for such great work

best regards
Sorry about my typo - of course I meant " Honeycomber" [I've corrected the original post!] - during development this tool has been called 'Fret', 'Honeyfoamer' and eventually 'Honeycomber' - so I'm easily confused... the 'fret' name remains for the subfolder's skp/png files...
The TIG::Honeycomber toolbar is in the View > Toolbars menu...
Make sure you only have the 'loader' file in Plugins and everything else inside the subfolder...
Do you have a TIG-Honeycomber folder in the Plugins folder containing two png files - these are needed for the toolbar creation, and the four skp files loaded as objects to be subtracted from the selected thing...
IF you make the size of the 'perforators' bigger than the original object then, as explained in the notes, the object is NOT honeycombed as there is nothing to 'boolean', if you included a 'shell' dimension then that is done [provided that is not dimensioned so large that nothing can be 'booleaned' either].
How large is the xyz of the object to be honeycombed?
What are the xyz sizes/walls specified?
To test it, make a 4" cube, with a thin shell, and 1" perforator cubes [with thin walls in xyz]...
You should get this Do you get any messages in the Ruby Console etc... ?

Oxer

Hi again,
I have downloaded the plugin again and i reinstalled it in the Root Library, the same ruby console error. I probed to uninstall the rest of the plugins, perhaps it had some conflict and the same error.

TIG

Oxer

There's a list of files in a post a few back, remove all and ensure you only have the required ones in the correct folder/subfolder...

Oxer

Yes, i have all files and folder in his correct situation.
Perhaps another Mac user can tell us if the plugin works.

TIG

There's nothing that I can think of that's PC specific... so it should work fine on MACs too...
Any MAC users want to chip in...

SUFractal

@oxer said:

Yes, i have all files and folder in his correct situation.
Perhaps another Mac user can tell us if the plugin works.

TIG:

I have it installed exactly as you described (see attachment).

I had it installed that way before several times, but the plugin wasn't loading the either. The only way to have anything close to operational was the clumsy way I did try (which I realize isn't the way it is intended)... but it crashed SU every time.

Thanks.

Ben Ritter

TIG, thank you so much.

TIG

SUFractal

I can't tell from your screenshot if the Plugins folder is in the the 'root' [Macintosh HD] library path, where it should be; or say an incorrect User path...
Assuming it's in the right place... can you be more specific about about what's 'crashing' and how this manifests itself...
Does Sketchup star without errors?
Does the Extension appear in the Preferences dialog?
If you deactivate it and restart does the Tools menu item vanish, and does the toolbar vanish?
If you activate it do you get a Tools menu item and a toolbar?
If you activate the toolbar does it appear as expected?
Open the Ruby Console.
If you make a simple 4" cube [e.g. make a square and PushPull it up 4"] and make it into a group [Entity Info will show it as 'solid' when it's selected] and run the tool from the toolbar what happens?
Does a dialog appear?
If you accept the default values and press OK, what happens?
Are there any error messages? [either in the Console or in a message-box]
If errors what do they say - exactly - ?
What happens to the cube-group?
etc...
With a little more logic applied to the testing/reporting we can track the issue and fix it...

[Oxer - are you listening too?]

PS: On a completely separate side note... I see you have 'toggleWindows.rb' installed in your Plugins folder - that's a PC only script; since MACs don't have Outliner crash issues, and that script uses .so files incompatible with a MAC anyway ?

SUFractal

@tig said:

SUFractal

I can't tell from your screenshot if the Plugins folder is in the the 'root' [Macintosh HD] library path, where it should be; or say an incorrect User path...
Assuming it's in the right place... can you be more specific about about what's 'crashing' and how this manifests itself...
Does Sketchup star without errors?
Does the Extension appear in the Preferences dialog?
If you deactivate it and restart does the Tools menu item vanish, and does the toolbar vanish?
If you activate it do you get a Tools menu item and a toolbar?
If you activate the toolbar does it appear as expected?
Open the Ruby Console.
If you make a simple 4" cube [e.g. make a square and PushPull it up 4"] and make it into a group [Entity Info will show it as 'solid' when it's selected] and run the tool from the toolbar what happens?
Does a dialog appear?
If you accept the default values and press OK, what happens?
Are there any error messages? [either in the Console or in a message-box]
If errors what do they say - exactly - ?
What happens to the cube-group?
etc...
With a little more logic applied to the testing/reporting we can track the issue and fix it...

[Oxer - are you listening too?]

PS: On a completely separate side note... I see you have 'toggleWindows.rb' installed in your Plugins folder - that's a PC only script; since MACs don't have Outliner crash issues, and that script uses .so files incompatible with a MAC anyway ?

TIG:

I have the plugin installed in the correct location ... as I have all of my countless other plugins. I am in full understanding of where plugins are req'd to be located on Macs. I've gotten rid of the 'toggleWindows.rb' script (didn't realize that was PC only at the time I suppose).

When I attempt to operate the plugin with even a simple cube:

A dialogue box appears asking for parameters.
The cube switches to X-ray mode immediately.
Using the default settings, the console window says" TIG::Honeycomber: Perforating.
After waiting as long as 15 minutes, nothing "happens" to the simple cube.
If at any time during the console message (or even after 15 minutes) I even slightly move the mouse/cursor, the message in the status window disappears.

The 'symptoms' I am describing sound very similar to juanjo's.

TIG

SUFractal

You'd only need to wait 15 minutes if doing an incredibly complex object with thousands of perforations...

So, it seems that it runs, but produces no result?
Does it 'crash' ?
Does it 'hang' ?
What 'Console message[s]' ?
There should be none, only Status-bar messages saying what's being done and some incrementing '...' or ',,,' etc.
You should actually see the perforators being added, then subtracted in turn as the view refreshes as it goes...

Can you post your cube size, and a screenshot of the dialog settings you used...
It it completes with no changes, then it suggests that the perforations were bigger than the object so it remains unchanged.
If you use 'Shell' > 0 [at a fraction of the cube's dims] do you at least get a simple shell added ?
This is a mystery

SUFractal

@tig said:

SUFractal

You'd only need to wait 15 minutes if doing an incredibly complex object with thousands of perforations...

So, it seems that it runs, but produces no result?
Does it 'crash' ?
Does it 'hang' ?
What 'Console message[s]' ?
There should be none, only Status-bar messages saying what's being done and some incrementing '...' or ',,,' etc.
You should actually see the perforators being added, then subtracted in turn as the view refreshes as it goes...

Can you post your cube size, and a screenshot of the dialog settings you used...
It it completes with no changes, then it suggests that the perforations were bigger than the object so it remains unchanged.
If you use 'Shell' > 0 [at a fraction of the cube's dims] do you at least get a simple shell added ?
This is a mystery

I meant status window, not console, sorry.

Using a 12' x 12' x 12' cube and the default parameters (see screenshot), I click 'OK', the status window changes to "Tig::Honeycomber:Perforating", and then it "hangs/doesn't do anything else/whatever" ... nothing 'happens' to the cube.

I then tried a shell setting in the Parameters window of 12" (and all other settings at 12") and it generated a shell and 'cube within a cube'.

I get no prompts for structure, comb, or foam (or anything) beyond that.

Oxer

Hi again, again... TIG
See images below

I select the Cubo (Solid Group) push the plugin icon and it appears the Setting Window.
I press Aceptar (OK) and nothing happens, see the Error Ruby Console.

TIG

Oxer[and probably SUFractal in the absence of a Console error report from him...]

The reason the 'Shell' part works is that the basic shell is added before any raytesting starts [it still fails BUT then the shell is there], but with no shell specified the raytesting starts early-on - before any new geometry is added at all.

From the error messages I can see the error is that your setup seems to think that the model.raytest is expecting a Float [number] not a Point3d as it is getting.
In fact it has to be that
model.raytest([**point**, vector], true)
which is of course exactly what the code in line #599 does.
rayt=@model.raytest([zcent, Z_AXIS], true)
where 'zcent' is clearly defined as a point [as it ought to be],
the Z_AXIS is clearly a vector, and 'true' is simply saying 'ignore hidden objects'.

So... I can but deduce that another third-party script is ill-advisedly redefining the model.raytest() method
Though God knows why...

To see if the error occurs outside of my tool's code, please do the following and report back...
Use an empty SKP.
Switch Axes 'on'.
Make ~1m radius circle, based flat on the ground [Z/Blue=0], centered on the origin [crossing of XYZ/RGB axes].
Now open the Ruby Console.
Then copy/paste +<enter> this line of code

Sketchup.active_model.raytest([Geom;;Point3d.new(0,0,-1),Z_AXIS],true)

You should get a result something like this [although the face's 'reference' will vary].
[Point3d(0, 0, 0), [#<Sketchup::Face:0x11aba8e0>]]
If it succeeds then I can't immediately see why it'd work in the Ruby Console and not my code...
If you get an error similar to the one you've posted we know the built-in model.raytest() method has been broken.
If there is an error could you try to 'grep' [i.e. 'search' through files for certain text inside them] through the files in the 'Plugins' folder, and its subfolders [and also in the 'Tools' folder], for the text ' def raytest'.
If you find a file please report back.
If you disable that file does the model.raytest() 'test' work now ???

Oxer

I have done it that you have said, this is the result TIG.

TIG

Oxer

Thanks!
Now we know that it's has nothing to do with my tool.
Rather, the built-in model.raytest() method is broken.

Can you try to find the ' def raytest' text in Plugins etc as I explained...
There has to be something redefining it.
If its inside a compiled .rbs we won't find it, BUT it might be a .rb and we get lucky...
We can do mass disablement testing, BUT that's a last resort...

When we find out what's messing with your system we can 'fix' it...

TIG

SUFractal

Your issue is just the same as Oxer's !
It is not my tool... but something broken in the core methods: almost certainly by a 'rogue' script...
Can you try the steps I set out for Oxer over the last few posts...
Hopefully we can resolve this...

SUFractal

@tig said:

Oxer[and probably SUFractal in the absence of a Console error report from him...]

The reason the 'Shell' part works is that the basic shell is added before any raytesting starts [it still fails BUT then the shell is there], but with no shell specified the raytesting starts early-on - before any new geometry is added at all.

From the error messages I can see the error is that your setup seems to think that the model.raytest is expecting a Float [number] not a Point3d as it is getting.
In fact it has to be that
model.raytest([**point**, vector], true)
which is of course exactly what the code in line #599 does.
rayt=@model.raytest([zcent, Z_AXIS], true)
where 'zcent' is clearly defined as a point [as it ought to be],
the Z_AXIS is clearly a vector, and 'true' is simply saying 'ignore hidden objects'.

So... I can but deduce that another third-party script is ill-advisedly redefining the model.raytest() method
Though God knows why...

To see if the error occurs outside of my tool's code, please do the following and report back...
Use an empty SKP.
Switch Axes 'on'.
Make ~1m radius circle, based flat on the ground [Z/Blue=0], centered on the origin [crossing of XYZ/RGB axes].
Now open the Ruby Console.
Then copy/paste +<enter> this line of code

Sketchup.active_model.raytest([Geom;;Point3d.new(0,0,-1),Z_AXIS],true)

You should get a result something like this [although the face's 'reference' will vary].

[Point3d(0, 0, 0), [#<Sketchup::Face:0x11aba8e0>]]
If it succeeds then I can't immediately see why it'd work in the Ruby Console and not my code...
If you get an error similar to the one you've posted we know the built-in model.raytest() method has been broken.
If there is an error could you try to 'grep' [i.e. 'search' through files for certain text inside them] through the files in the 'Plugins' folder, and its subfolders [and also in the 'Tools' folder], for the text ' def raytest'.
If you find a file please report back.
If you disable that file does the model.raytest() 'test' work now ???

I get this ruby console 'result' when trying your suggestion to Oxer.

Sketchup.active_model.raytest([Geom::Point3d.new(0,0,-1),Z_AXIS],true)
Error: #<TypeError: (eval):61:in `raytest': can't convert Geom::Point3d into Float>
(eval):61
(eval):61

By the way ... I do not see 'def raytest' in my plugins folder anywhere. Using the "Find" function, I do not 'def raytest' anywhere on my computer.

SUFractal

@tig said:

SUFractal

Your issue is just the same as Oxer's !
It is not my tool... but something broken in the core methods: almost certainly by a 'rogue' script...
Can you try the steps I set out for Oxer over the last few posts...
Hopefully we can resolve this...

I did just try that ... no luck.