This is a random problem, but documented it this time. When I add an interior shed wall (image 1), it does not appear in the selected location. What does appear are random entities near the origin of the model (image 2). No ruby errors noted. Did a “Purge unused” and “Fix Problems”, no help. The GIF shows the sequence of events (used hide on some walls to clearly show the results). Thanks for any suggestions.
Model emailed as requested …
Turn on the ruby console and duplicate the error. I guarantee there will be an error code posted if this wall is being drawn at the origin like that.
Send me that error code.
Here is the ruby error code:
Error: #<NoMethodError: undefined method +' for nil:NilClass> /users/na/library/application support/sketchup 2021/sketchup/plugins/medeek_wall_ext/medeek_shed_wall.rbe:5803:in block in draw_shed_wall’
/users/na/library/application support/sketchup 2021/sketchup/plugins/medeek_wall_ext/medeek_shed_wall.rbe:5800:in each' /users/na/library/application support/sketchup 2021/sketchup/plugins/medeek_wall_ext/medeek_shed_wall.rbe:5800:in draw_shed_wall’
/users/na/library/application support/sketchup 2021/sketchup/plugins/medeek_wall_ext/medeek_shed_wall.rbe:2120:in draw_selector_shed' /users/na/library/application support/sketchup 2021/sketchup/plugins/medeek_wall_ext/medeek_shed_wall.rbe:1708:in main_menu_html_shed’
/users/na/library/application support/sketchup 2021/sketchup/plugins/medeek_wall_ext/medeek_draw_shed_wall_tools.rbe:1770:in calculate_obj' /users/na/library/application support/sketchup 2021/sketchup/plugins/medeek_wall_ext/medeek_draw_shed_wall_tools.rbe:1790:in update_state’
/users/na/library/application support/sketchup 2021/sketchup/plugins/medeek_wall_ext/medeek_draw_shed_wall_tools.rbe:1812:in `onLButtonDown’
There was no error code when it first happened (image 1). I had to repeat the shed wall creation, multiple times, in order to generate the Ruby error code. At my experience level this is all magic! This has happened repeatedly, but completely randomly in multiple models. The only common factor is the shed walls. Most times at the 60-90% project completion point. Generally to complete the project I am forced to explode the affected wall or the entire project, in order to finish. Very frustrating.
This is an interesting bug. It only happens in a very specific situation.
It is not just with shed walls it is also with rectangular walls.
I can see why I never caught this before, I will rectify it and release and update shortly.
Thanks. Does this bug have anything to do with the “corner” problem in an earlier post?
I don’t know, we will just have to test it and notate any ruby console errors and then address them. It’s always an iterative process.
Updated the Wall extension to 2.2.6. When I regen the wall that has a corner problem, the Ruby console looks like:
1 max_z: 79.98985206816894
1 max_z: 77.32318540150229
1 max_z: 74.6565187348356
1 max_z: 71.98985206816894
1 max_z: 69.32318540150229
1 max_z: 66.6565187348356
1 max_z: 63.98985206816895
1 max_z: 61.32318540150228
1 max_z: 58.65651873483561
1 max_z: 55.98985206816895
1 max_z: 53.32318540150228
1 max_z: 50.65651873483561
1 max_z: 47.98985206816895
And the shed wall has these problems:
On another shed wall the end Tee connection is not shown (after another regen). Any suggestions?
When I added rafters, I get this Ruby error:
Error: #<ArgumentError: Cannot convert argument to Geom::Point3d>
/users/na/library/application support/sketchup 2021/sketchup/plugins/medeek_truss_ext/medeek_roof_rafters.rbe:11488:in add' /users/na/library/application support/sketchup 2021/sketchup/plugins/medeek_truss_ext/medeek_roof_rafters.rbe:11488:in getExtents’
Error: #<ArgumentError: Cannot convert argument to Geom::Point3d>
/users/na/library/application support/sketchup 2021/sketchup/plugins/medeek_truss_ext/medeek_roof_rafters.rbe:11488:in add' /users/na/library/application support/sketchup 2021/sketchup/plugins/medeek_truss_ext/medeek_roof_rafters.rbe:11488:in getExtents’
Error: #<NoMethodError: undefined method -' for nil:NilClass> /users/na/library/application support/sketchup 2021/sketchup/plugins/medeek_truss_ext/medeek_roof_rafters.rbe:11908:in draw’
More strange behavior on adding rafters.
Ruby console:
Error: #<ArgumentError: wrong number of arguments (given 0, expected 1)>
/users/na/library/application support/sketchup 2021/sketchup/plugins/medeek_truss_ext/medeek_roof_rafters.rbe:10830:in create_cj_array' /users/na/library/application support/sketchup 2021/sketchup/plugins/medeek_truss_ext/medeek_shed_roof.rbe:718:in draw_shed_cj2’
/users/na/library/application support/sketchup 2021/sketchup/plugins/medeek_truss_ext/medeek_roof_rafters.rbe:1582:in draw_rafter_selector' /users/na/library/application support/sketchup 2021/sketchup/plugins/medeek_truss_ext/medeek_roof_rafters.rbe:1347:in main_menu2’
/users/na/library/application support/sketchup 2021/sketchup/plugins/medeek_truss_ext/medeek_roof_rafters.rbe:323:in main_menu' /users/na/library/application support/sketchup 2021/sketchup/plugins/medeek_truss_ext/medeek_edit_roof_rafters.rbe:1300:in block in show_edit_menu’
Update Truss Extension to 3.0.0. Still getting this error with a shed roof (rafters). Any suggestions? Thanks.
I will be looking at that in just a couple hours.
The issue with the blocking and tee intersections within shed walls should be resolved with the latest update (Version 2.2.9).
I occasionally create walls in 2D mode with camera parallel projection, top view. I type specific values in the VCB (eg. 10’). I click on or reference, start/end markers for proper alignment. This produces mis-aligned walls, start/end markers not aligned (see GIF#2). If I do not type in specific values, but click on approximate lengths, then I get properly aligned start/end markers and walls (see GIF#3). If the start/end markers are not aligned, the auto corner feature does not correctly configure the corners.
Another interesting behavior is once I change the wall framing setting to “2D”, and then change back to “Yes”, the setting will revert to “2D”. And yes, in global settings the setting is “Yes”.
Am I expecting results not possible with the wall extension? Or maybe the procedure (workflow) I am using is wrong? I posted a similar issue on Jun 5. As always, thanks for your help.
This is SU2021 on MacOS (Mojave), Wall Extension Version 2.3.2, Ruby console, no errors.
I often download a Medeek sample file from 3DW to experiment with. Some of the model assemblies have been exploded and therefore are not editable through the extensions. However others are editable with the extensions as evidenced by right clicking on an assembly and finding the “edit wall assembly” menu selection. In this sample file (Framing Test 12), the walls display this menu option, but when changes are made they do not update as expected. What am I missing? Are models made with earlier extension versions compatible with latest versions? Thanks for your help.
FramingTestr12.skp (1.8 MB)
I depends which version of the extension you are running and which version of the extension was used to create the walls.
If you open it up in the latest version and then edit the wall, be sure to check that there are valid arguments for each drop down and parameter shown. This should allow you to then update the wall and it will then automatically be upgraded to the latest version.
The requirement that each variable have a value is extremely tedious ( GIF represents just one wall, blanks galore, 37 for one wall ! ). Each wall, truss, foundation element has to be checked and blank fields populated. Why can’t the default value be inserted automatically?
This model was probably created a couple years ago. The plugin development as been major in the last two years. Moving forward backward compatibility is a serious concern however anything that is older than four months is just not worth the effort trying to maintain backward compatibility right now.
As the development matures and slows, which it will, in fact it already has, then backward compatibility will become less and less of an issue.
There are two reasons why backward compatibility is too hard to maintain for releases older than last year:
1.) It bloats the code to add in extra logic and what percentage of the users will actually use it.
2.) It requires more effort to create that logic and I don’t have a team of coders to do this sort of thing, it is just me.
19 days is a lot of hours! Maybe I am the only one affected by this issue (a Mac user), but when it happens, considerable reworking is required and is quite disruptive to the workflow. I would gladly change my workflow if I could determine what I am doing to cause the issue, but it seems very random in nature. I know you have many priorities, but would appreciate any related status updates. Thanks.
