Medeek Wall Plugin

medeek

The latest release has not yet addressed the stud spacing algorithm issue. The reason being is that I have to test it in numerous states to verify all possible situations are calculating correctly, and even though I have made some critical changes to the algorithm I am not yet ready to push it out. I am looking at this right now and hopefully should have the fix out later this afternoon.

alpro

Charlie pointed me in the right direction, end corner was set to inside corner though I was sure I had set it to outside corner, once I did that and updated all was good.

medeek

Version 0.7.7d - 06.10.2018

Added 2D (construction or solid) line options for sheathing, cladding and gypsum within the global settings.
Fixed a bug within the corner trim module (trim width).
Added additional standard metric stud sizes: 36x68, 36x98, 36x148, 36x198, 48x72, 48x98, 48x148, 48x198

medeek

This is the direction I am going with the Wall Edit Menu UI and Draw wall Tool:

Notice the wall presets section at the top of the UI, here you can delete, load or save a preset wall template.

The actual templates will be stored in a simple text file within a sub-folder called "presets", that way the user can also manually edit the wall preset file and even cut and paste presets from other users into their preset file. This solution offers the most flexibility and user control in my opinion.

Loading a preset will re-populate all of the parameters in the form below except for the excluded items.

The save function will create a new preset (with user entered name/description) based on the currently listed parameters in the form.

Does this make sense? and the better question, am I missing anything here?

Hopefully this new addition of presets will speed up the wall creation process and spare the user from having to recreate a specific wall type from scratch each time they start a new model or session.

I still have not fully arrived at what the excluded parameters should be in the wall preset functions so please provide any feedback in this regard.

Charlie__V

1.) Since we can enter wall lengths as feet and inches while drawing can we please have the wall length editable in same format? TIA
Wall length request in ft. & inch

2.)Are there any unforeseen/adverse effects of moving a wall using the native SU move tool?
(Realizing using the Medeek wall move tool will auto-heal/move existing walls if attached in a way they will follow/heal.)
But for other circumstances where this is not the case.

Charlie

medeek

@charlie__v said:

1.) Since we can enter wall lengths as feet and inches while drawing can we please have the wall length editable in same format? TIA

2.)Are there any unforeseen/adverse effects of moving a wall using the native SU move tool?
(Realizing using the Medeek wall move tool will auto-heal/move existing walls if attached in a way they will follow/heal.)
But for other circumstances where this is not the case.

Charlie

Funny as I have not really noticed that with the wall length until you pointed it out. Yes, we can switch it to feet-inches for imperial units.

Yes, you can move the walls with the SU move tool without any adverse issues (at least none to my knowledge currently). But as you have already stated manually moving a wall will disconnect it from any previously attached walls.

Charlie__V

@medeek said:

This is the direction I am going with the Wall Edit Menu UI and Draw wall Tool:

Notice the wall presets section at the top of the UI, here you can delete, load or save a preset wall template.

The actual templates will be stored in a simple text file within a sub-folder called "presets", that way the user can also manually edit the wall preset file and even cut and paste presets from other users into their preset file. This solution offers the most flexibility and user control in my opinion.

Loading a preset will re-populate all of the parameters in the form below except for the excluded items.

The save function will create a new preset (with user entered name/description) based on the currently listed parameters in the form.

Does this make sense? and the better question, am I missing anything here?

I think the more information you can pre-set and leave out of initial "draw wall" window the better.

IE:
A 2x6 Ext.Wall_Horiz.Side_16_O.C. removes the need to specify stud width/depth/O.C./plates/etc. if wall name/definition states it.

Or a 2x6 Ext.Wall_Horiz.Side_16_O.C.Trtd.plate has treated bottom plate only.

An edit button for the active wall definition would be great to have too.(within initial "draw wall" window)

Charlie__V

PS
When using polyline it seems the draw wall tool is self aware enough it doesn't require the need to pre-select "start" and "end" type........so maybe that is not necessary on initial "draw window" either

medeek

@charlie__v said:

PS
When using polyline it seems the draw wall tool is self aware enough it doesn't require the need to pre-select "start" and "end" type........so maybe that is not necessary on initial "draw window" either

You are correct. When the auto-corner configuration global setting is enabled the plugin will correctly sense the corner angles and configurations and take care of that automatically. If this global setting is enabled I should probably just gray out the appropriate parameters (at least in the draw tool GUI). One can always edit a wall and manually change these value which will override the auto behaviour.

I like how you term it "self aware", I'm a huge fan of AI and a bit of an AI programmer myself but I wouldn't go quite so far as to call this AI or even self aware. Just a fairly complicated algorithm that tries to check for specific wall corner and tee intersections. As time goes on the algorithm will probably be revisited a few more times making it more robust and flexible, but it has no capacity to learn (ie. memory). Just a static set of instructions which it follows without variation.

However, with that being said I have considered using some sort of adaptive behavior for the plugin that would slowly adapt to the users most commonly used values for certain parameters and try to predict what those values should be in the future. A good example of this would be header selection for interior walls. Over time it would begin to rank which header sizes/types are used the most and then within the drop down menus it could sort them so that the most commonly used sizes appear at the top of the list with the most commonly used one being selected as default.

Again I don't know if I would call this AI but it would certainly be adaptive software and would tailor itself to the users habits.

Bob James

Where are the updated versions located for downloading?

Do just go to http://design.medeek.com/resources/medeekwallplugin.html and download the Trial?

medeek

Login to the Account Manager and the download link will appear under the license listing.

Medeek Design Inc. - Login

(design.medeek.com)

Bob James

Toolbar icons do not scale for 4K monitor.

Bob James

@medeek said:

Login to the Account Manager and the download link will appear under the license listing.

Medeek Design Inc. - Login

(design.medeek.com)

Thank you!

medeek

@bob james said:

Toolbar icons do not scale for 4K monitor.

[attachment=0:2u1yiq42]MedeekIcons-1.png[/attachment:2u1yiq42]

Does anyone know how to address that?

Here is my typical toolbar/icon ruby:


cmd7.small_icon = "images/mdkplg_tool_icon16_8.png"
cmd7.large_icon = "images/mdkplg_tool_icon24_8.png"
cmd7.tooltip = "Medeek Wall"
cmd7.status_bar_text = @Trs['Change Global Settings']
cmd7.menu_text = @Trs['Global Settings']
toolbar = toolbar.add_item cmd7
toolbar.show

Do I need an extra large icon?

Bob James

The icons have to be .svg format. This is a scalable vector format that is the new SU standard.

medeek

There are really three functions in one here: Loading, Saving and Deleting.

Quite a bit of new code to implement the new presets system. I'm still testing it out to make sure it is solid, but so far it is looking pretty good.

Note, that it is possible to give a preset the exact same name as another preset, this is by design and they will both appear in the drop down list. What you are not seeing in the drop down is the hidden number assigned to each preset which is stored in the presets file. This number is really the identifier of the preset and allows one to correctly specify which preset you are wanting to load or delete.

Once this system is in place for the walls and fully tested and verified I will implement a similar system for windows and doors.

I have a number of minor fixes and bugs that are quite hot items right now that have been delayed due to my attention to this latest upgrade, I apologize for the delay in getting the fixes out, but I really feel that this UI upgrade is top priority right now.

medeek

@bob james said:

The icons have to be .svg format. This is a scalable vector format that is the new SU standard.

I've messed around with a few PNG to SVG converters and the result are not spectacular. I've actually used SVG quite extensively in some of the menus for the Truss Plugin so I have a pretty good understanding of how SVG works. Unfortunately, SVG does not lend itself well to shaded or rendered images or to gradients. Line drawings is where it excels, I'll have to give this some more thought.

If I can somehow detect that the user is running a 4K monitor or some other high resolution monitor that the current icons are not well suited to then I could substitute the regular icon set with a lesser quality SVG set.

medeek

I released the LT version of the plugin a couple days ago and I am surprised that no one has shown any interest in this lesser version of the plugin.

Just to clarify, it is a full featured version of the plugin without the internal wall framing, estimating and engineering components. The ability to creating openings, windows, doors, exterior and interior cladding etc... is all there.

The intended audience of the LT version is architects and designers who do not need all of the nut and bolts of the design (how it goes together) and are concentrating more on the big picture.

Please let me know what would make the LT version more attractive to you the designer or architect.

Charlie__V

@medeek said:

@charlie__v said:

PS
When using polyline it seems the draw wall tool is self aware enough it doesn't require the need to pre-select "start" and "end" type........so maybe that is not necessary on initial "draw window" either

You are correct. When the auto-corner configuration global setting is enabled the plugin will correctly sense the corner angles and configurations and take care of that automatically. If this global setting is enabled I should probably just gray out the appropriate parameters (at least in the draw tool GUI). One can always edit a wall and manually change these value which will override the auto behaviour.

I like how you term it "self aware", I'm a huge fan of AI and a bit of an AI programmer myself but I wouldn't go quite so far as to call this AI or even self aware. Just a fairly complicated algorithm that tries to check for specific wall corner and tee intersections. As time goes on the algorithm will probably be revisited a few more times making it more robust and flexible, but it has no capacity to learn (ie. memory). Just a static set of instructions which it follows without variation.
.

To sort of state the obvious, the “smarter” the draw wall feature gets, the better the plug-in will be. (little to no post draw edits req’d)

In version (0.7.7d) I notice the draw wall ....Justification: Front seems to be the most mature/predictable and less so for Center and Back.......I assume the Center and Back will catch up at some point?

Thanks,
Charlie

medeek

@charlie__v said:

In version (0.7.7d) I notice the draw wall ....Justification: Front seems to be the most mature/predictable and less so for Center and Back.......I assume the Center and Back will catch up at some point?

Thanks,
Charlie

Correct, the FRONT justification is really the only option that is working as it should right now, do not use the other two options. I am still sorting out the details on those other two, and yes, they will work in future releases.