Windowizer
-
I can make glass thickness an option
(naturally, it's easier coding to have a single face, but since the coding is done for double face, adding a check for glass thickness is no problem).EDIT: Easier than I thought - just specify a glass thickness of 0
-
Fantastic news Rick...
-
Wonderful news!
Anssi
-
-
Seems like I'd be handing over some more cash to Smustard quite soon...
-
@rickw said:
I'll throw some items out there for a consensus "vote":
1a. V4 will cut an opening in a "wall", and a "wall" is determined by the distance between two faces. I can hard-code a reasonable distance value (currently 16"/~40cm), or I can make it user-defined.
1b. If user-defined, do you want to see it in the main dialog every time you use Windowizer, or would you prefer it to be located in a separate configuration dialog?
-
V4 groups the resulting window assembly. I can add an option to group or not group this, if desired (the group would be exploded if non-grouping was selected).
-
When multiple faces are selected for a Windowizer operation, should "undo" work on just the last window assembly created, or on all of them? For clarification: currently in v4, 10 faces selected to be Windowized would result in 10 separate actions, thus 10 separate "undo" actions. This could be an option as well, subjecting it to question 1b. (main dialog or separate configuration dialog?)
1a. user defined
1b. separate window
2. group it by default
3. undo should work on all of them. option on main dialog. -
-
@rickw said:
I'll throw some items out there for a consensus "vote":
1a. V4 will cut an opening in a "wall", and a "wall" is determined by the distance between two faces. I can hard-code a reasonable distance value (currently 16"/~40cm), or I can make it user-defined.
1b. If user-defined, do you want to see it in the main dialog every time you use Windowizer, or would you prefer it to be located in a separate configuration dialog?
-
V4 groups the resulting window assembly. I can add an option to group or not group this, if desired (the group would be exploded if non-grouping was selected).
-
When multiple faces are selected for a Windowizer operation, should "undo" work on just the last window assembly created, or on all of them? For clarification: currently in v4, 10 faces selected to be Windowized would result in 10 separate actions, thus 10 separate "undo" actions. This could be an option as well, subjecting it to question 1b. (main dialog or separate configuration dialog?)
1a) User defined, but with the option to set parameters within which script should search for the other face of the wall.
1b) Main dialogue box.
2) Add option to have the output either grouped or ungrouped.
3) Last window created. I think one should check the window before going on to create the next. -
-
Okay, here's a simple form for answering the questions (which will help me tabulate responses).
(Edson & Juju, thanks for your feedback - I've logged your responses already)
-
@rickw said:
I'll throw some items out there for a consensus "vote":
1a. [EDITED] V4 will cut an opening in a "wall", and a "wall" is determined by the maximum distance between two faces. I can hard-code a reasonable distance value (currently 16"/~40cm maximum), or I can make it user-defined.
1b. If user-defined, do you want to see it in the main dialog every time you use Windowizer, or would you prefer it to be located in a separate configuration dialog?
-
V4 groups the resulting window assembly. I can add an option to group or not group this, if desired (the group would be exploded if non-grouping was selected).
-
When multiple faces are selected for a Windowizer operation, should "undo" work on just the last window assembly created, or on all of them? For clarification: currently in v4, 10 faces selected to be Windowized would result in 10 separate actions, thus 10 separate "undo" actions. This could be an option as well, subjecting it to question 1b. (main dialog or separate configuration dialog?)
1a User-defined
1b Main dialog is OK - at least in the version I have it is still uncluttered enough
2 Grouping is OK, adding the option is OK too, but not absolutely necessary
3 Undo all in one go is IMO the way to goCheers
Anssi
-
-
I'll throw some items out there for a consensus "vote":
1a. [EDITED] V4 will cut an opening in a "wall", and a "wall" is determined by the maximum distance between two faces. I can hard-code a reasonable distance value (currently 16"/~40cm maximum), or I can make it user-defined.
1b. If user-defined, do you want to see it in the main dialog every time you use Windowizer, or would you prefer it to be located in a separate configuration dialog?
-
V4 groups the resulting window assembly. I can add an option to group or not group this, if desired (the group would be exploded if non-grouping was selected).
-
When multiple faces are selected for a Windowizer operation, should "undo" work on just the last window assembly created, or on all of them? For clarification: currently in v4, 10 faces selected to be Windowized would result in 10 separate actions, thus 10 separate "undo" actions. This could be an option as well, subjecting it to question 1b. (main dialog or separate configuration dialog?)
EDIT: If you answer using this survey form, I can better track the responses.
Thanks!
-
-
Okay, based on responses so far, I've made some determinations:
-
This will be user-configurable in a separate dialog, as I expect it won't change very often - if you never have a wall thicker than 16"/40cm, it will never change!
-
I will add the grouping option to the main dialog
-
"Undo" will undo all windows created in that instance.
Thanks for the input,
-
-
Hi Rick, this looks great! congrats!
can a value of "0" be specified for the frame and have it therefore only build divider mullions/muntins? this way we would be able to use it to subdivide panels in a previously built curtainwall system?
Will it have the option to be only one sided curtainwall? the additional polys will be very heavy in the scene if they are not needed. I would then have to keep the old windowizer as I prefer the lowest polys possible... for quicker SU response and quicker render times.
Is there a way to make the grouping a component instead? one that cuts the opening? Say I picked 3 identical faces, and told it to make the window, and it were to make it, make it a component, and place the component in all three places for me... that would be powerful.
-
@fletch said:
Hi Rick, this looks great! congrats!
Thanks!
@fletch said:
can a value of "0" be specified for the frame and have it therefore only build divider mullions/muntins? this way we would be able to use it to subdivide panels in a previously built curtainwall system?
Yes
@fletch said:
Will it have the option to be only one sided curtainwall? the additional polys will be very heavy in the scene if they are not needed. I would then have to keep the old windowizer as I prefer the lowest polys possible... for quicker SU response and quicker render times.
Yes, there will be a "front-only" option.
@fletch said:
Is there a way to make the grouping a component instead? one that cuts the opening? Say I picked 3 identical faces, and told it to make the window, and it were to make it, make it a component, and place the component in all three places for me... that would be powerful.
I think I could modify it to make a component - I'd have to do some research on instance placement (haven't used it for a while, so it's a bit rusty). The more difficult part is verifying that the faces are the same size/shape.
-
Hi Rick,
Now here is a ruby I use so often !! Even with its current limitations !
The update looks veryyy promising ! The answers you gave to Fletch are also just the things I need. Sometimes low poly, sometimes high. I usually make a group of the face prior to the windowizer command makes it more easy to change.
Anyway looking forward to the update of your script.
greetings,
erikB -
For me, this script is essential. I use this thing more than any other script out there, by FAR. I'd be lost without it. In order: water, food, shelter, windowizer.
-
Thanks for the comments and encouragement. I've got some other eyes looking over the current iteration. After that, a couple of UI tweaks, and it should be ready.
-
really looking forward to this one...
-
-
+2
-
+3
Advertisement