Well, I doubt this will be any help to you, but in simple batch file I would use the START command along with the parameter /WAIT

start /wait yourprogram.exe <parameters you want to pass along>
next_command (will be executed when yourprogram.exe has terminated)

...but perhaps you can use it somehow.

CadFather, as the name of the function "Divide Rectangles" implies, it only works with rectangles ^^
In your simple case case it would be only one line for each L-shaped polygon to divide them in two rectangles on which Divison can be applied.
As for arcs, domes and spheres - it works fine for me scratches his head
What exactly did you try?

Jim, you already have a reply to your PM; works fine now!
A new bug report/feature request: Right now you can only taper the extrusion up to 99%, if you enter 100 no tapering is done at all. Would it be possible to allow a taper of 100%, resulting in a single endpoint (top of the pyramid) instead of a small face at 99%? Optically this is no big matter, but it would save 3 vertices, 4 lines and one face which could matter in a big model including a few hundred extrusions.

Really a nice bit of ruby to toy around with...!

But there's a little problem using it on a localized (german) OS - as some of you may know we're using a comma to separate the decimal places (and a point for the thousands); but the protrude plugin can't handle that, every floating point value is truncated to the integer value.

@unknownuser said:

{"dmax"=>["65"], "7"=>[nil], "omin"=>["0"], "dmin"=>["35"], "hmax"=>["1"], "1"=>[nil], "tmin"=>["0"], "hmin"=>["1"]}
rcvd callback: "protrude()"
(values were 1,1 for hmin & and 1,7 for hmax)

If I call the 'Set Reasonable Values' function, the calculated values also use the decimal comma format - and protrude won't work, too.

@unknownuser said:

rcvd callback: "setReasonableValues()"
setResonableValues:
{"dmax"=>["65"], "00m"=>[nil], "omin"=>["0"], "dmin"=>["35"], "tmin"=>["0"], "60m"=>[nil], "hmin"=>["6"]}
rcvd callback: "protrude()"
(hmin=6,00m & omin=0,60m)

When trying values with a decimal point an error occurs:

@unknownuser said:

{"dmax"=>["65"], "omin"=>["0"], "dmin"=>["35"], "hmax"=>["1.7"], "tmin"=>["0"], "hmin"=>["1.1"]}
rcvd callback: "protrude()"
Error: #<ArgumentError: (eval):269:in to_l': Cannot convert "1.1" to Length> (eval):66:in initialize'
(eval):63:in eval' (eval):66:in initialize'
(eval):63:in `call'

The only workaround that will work is to adjust the numbers format (decimal point and comma separating the thousands) in windows itself, so SU will use the same number format as the plugin; the disadvantage is, every other program uses it as well.
Is there a (known) way to adjust the script to accept the comma values as well, or do I have to dig into ruby scripting myself...?

Regards,
Stefan

... quite a large number of threads on this topic - and none of them solves my problem (or I simply haven't found it ) so I've chosen this arbitrary thread to avoid opening a 1001st one g

I tried to create a simple model of my village's church, the mortuary and the surrounding cemetery walls for use in GE. Problem is, the terrain is quite sloped; I placed the buildings on the surface (terrain toggled on, added sockets where needed) and modeled the wall according to the ground. So everything looks quite nice in GE when terrain is toggled on; but when viewed without terrain, the model looks awful, everything floating around in different heights over the ground. Making three distinct models looks a bit better, but importing three models in GE isn't the real thing.

So my question to the pros in landscape/city modeling is: How do you deal with this circumstance? Do you completely ignore all users with terrain toggled off, or do you offer an additional 'flat' model for them, or is there some secret trick to make it look good in both views?

Regards, Stefan

Hello!

Recently I toyed around a bit with sketchyphysics (v2b1) and it's simply awesome!
But I've encountered a problem: Joystick control won't work when my SpaceNavigator (see http://www.3dconnexion.de) is connected - input from my gamepad (a Saitek Impact) is ignored completely. Worse than that, using the SpaceNavigator results in awkward behaviour of all joystick controls, eg servos running infinitely in one direction, ignoring their limits etc.
The moment I disconnect the 3D controller, everything works just fine.

• the SpaceNavigator is NOT recognized as a game controller by Windows
• in every other application/game the SpaceNavigator neither interferes with the joypad nor disables it.

So the problem seems to be sketchyphysics-specific... anyone else using a 3Dconnexion device and experiencing this problem?
(SU is version 6.4.112 German for information, SP as mentioned above v2b1; 3DxWare 3.6.10 / driver 6.6.4 / firmware 4.04)

Regards, Stefan