I m using box edit a lot, both for quick edits and verification.
In V6, I often find that I select an object and the values in box edit are wrong, I escape and re-select until I get the correct readings, but it defeats the purpose.
Also, on another occasion, I modify the X value and other values change as well.
I know you will request of example or photo or video but its a little hard to reproduce.
Has anybody else noticed this behavior? I have tested in different workstations.
I have had the issue where selecting an object with box edit isn’t giving me the correct dimensions. It happens to me in both Rhino 5 and 6.
In this simple case it happened when I had multiple objects selected then went to just having 1 single object selected. But as you can see from the image the bounding box shows my previous selection. This happens sometimes even when I hit escape in between to deselect everything. Both on my work computer (R5) and home computer (R6).
I said it before and I’ll say it again: BoxEdit performance, reliability, behavior and experience is an absolute shitshow and I find it really depressing that no one at McNeel gives a damn about it.
This is extremely easy to fix if you just would have a basic level of care for a tool that’s extremely important for many of us, and a tool that if it does not do its ONE JOB the consequences can be extremely costly (metal CNC is expensive, especially tooling releases, like many multiplies of the cost of a seat of rhino or an operators month salary, this is serious stuff). We can’t have a model edited numerically end up with wrong dimensions. This is the whole point of CAD guys. This HAS to work. Every god damn single time.
What you all have shown at McNeel with the continued tragedy of what a shitty job this basic tools does is one thing: You don’t care enough about your own work, or ours. That needs to change.
It only takes probably a few hours, or a day or two tops, of a single developer + designer with basic level of craftsmanship and care to fix this simple tool completely.
What are you going to do to fix this shitshow of a tool?
Who is going to do it?
When will it get done?
As you can imagine seeing developers working on new stuff when some of the most fundamental and basic tools of a shipping product are getting zero proper attention is really frustrating. Maybe this tool got lots of distracted, careless, bug-fix pothole-patching attention, but this has gotten so far zero proper attention IMO, and the results are undeniable about it.
I think it’s cool to play with new nerd tools, etc. But come on McNeel team, check all the basic boxes first. Including Boxedit. Stop shipping crap. This tools (and a few others, but I’ll stop here for today) is total crap. This is not you. You can do better. You must do better.
I’d like to hear an answer about this, and why do you have a working culture that even lets you get to this.
Seriously, I could not use rhino without BoxEdit, I would be an angry homer. Back when I first started with rhino 2009? I was struggling to use till I installed BoxEdit.
BE is a significantly important tool, especially for highly technical designs where absolute accuracy & ease of placement/moving/resizing is required.
When boxedit is getting some maintenance attention a wish-list item I would like is an additional button “Apply to duplicate” I think this is more ergonomic than the checkbox “copy objects” because don’t have to scroll down to check it then scroll back up & often I forget it is checked which is a bugger with a group of items. or maybe move the “copy objects” CheckBox close to the apply button.
Still a problem. I’ve got a box shape that’s 1’x1’x0.5". It’s showing that it’s 1.5’x1.5’x0.5’. Meanwhile, it’s not letting me adjust the size or scale by any increments lower than 1/4" (I want to change it by 1/8", nothing crazy.) Anyone else still having these issues?
Thanks Jeremy. That seems to have solved both issues. I set it to 1’1-1/16". I guess I hadn’t had to change the setting since installing Rhino 6. Most of what I’ve been doing is modeling in feet and half feet, at most.
I have a similar Box Edit Issue. If I’m not going crazy, I think I was able to do dynamic calculations with the Box Edit tool, and I can, yet more specifically it won’t compute the calculation and implement the change if I mix imperial and metric units, say for e.g. I want to shrink the objects length in the y-axis by 1/2" and I punch in the following calculation it won’t compute; XX'-XX"-.5
my units being in the feet-inch format. Is something awry with Box Edit?
I don’t see anything in the documentation (caveat: I haven’t read it all!) to suggest that calculation is a feature of the Boxedit entry boxes in R6 or R7. The calculator function that is documented is explicitly linked to the command line.
That said, it looks like you can do calculations in Boxedit if you have your units set to metric, or inches, but not feet-and-inches. And you can’t mix units. Until someone can point to something in the documentation that I’ve missed, I’m going to treat this as an undocumented effect and not trust it to calculate correctly…
But it would certainly be a great feature to have, @pascal
The native BoxEdit of Rhino was one of my requests, since we used a lot the script that did this before. I don’t recall who had written that one. Probably Thomas A, Ryan Perry or David Rutten?
As a typical McNeel development I had to outline all the things it should have, this happened probably 15 years ago, if not earlier. The original spec included being able to input dimensions in any unit system as long as you identify any values that are not in the file units. Also calculations would be supported. Of course those two things did kind of happen, but not together. Then years later I think @dale included the option of combining calculations AND multi-units, still it was partially executed, never tested, never documented, which makes it very very confusing and something I still today cannot trust.
I had also asked originally for an option of displaying BoxEdit values in a user selected unit, independently fo the file units. This never seemed important enough for McNeel to prioritize.
I stop asking for useful features, all of the going back to the original spec because after almost 2 decades this team can really exhaust you, and I think that exhaustion might be mutual, so I gave up.
In the last few year the only thing I’ve been asking is that the tool is not broken, that it does not show wrong values and that if updates quickly. This also seems too much work apparently.
It’s not necessarily the accuracy I’m worried about (working in AEC ±1/16" is good enough for me but I can see how it is different for others and yea, I have non-overlapping line/point OCD as well) but more so the finnicky nature of it all. I can almost swear that I can shorten/lengthen objects by just punching XX'-XX"±1 with the keypad. Now it doesn’t seem to be working, is it the latest rhino 6 update?