WPONG

1) Got it -- so there is no way to orbit about cursor, when in section view? --Will

I have assigned a shortcut to "show selected" (J) and it works fine with most elements in the scene. I click a part in the browser, press "J" and the part appears. Good so far. However, I just split a structure part into 2 bodies ("split"). And now something is wonky... 1. When I right-click on a body, I see the popup in the attached image. "show body J". I didn't assign this shortcut (to my recollection, anyway). Was this a default, or is Ironcad automatically applying my "show selected" shortcut also to "show body" ? 2. Regardless of the answer to #1, (however "J" came to be displayed as a shortcut for "show body"), "J" doesn't work as a shortcut for "show body". That is, when I click "J" the body doesn't appear. I need to select "show body" in the popup, and then it shows. Bug? --Will

Update 1. (still having trouble here, comments welcome) 2. Ahh... "precise mode" -- now I can measure --Will

It appears that after sectioning parts within a scene 1. It appears that the spin center for scene rotation is computed as if the parts weren't sectioned. That is, the scene doesn't spin about the sectioned face of the part where I middle-mouse-click, but about the area of the part that *would be visible* if I hadn't sectioned at all. Frustrating when I'm sectioning precisely so I can spin and inspect some buried feature. I suspect this is a bug. 2. I can not click any of the lines or edges generated in sectioning the part(s) for measurement purposes. Is this a bug as well? This is a structured part, so perhaps it's peculiar to structured parts? (haven't tried this with innovative parts yet) --Will

Thanks Kevin. Downloaded and had a look. Great! Almost down to nm. (the nm place occasionally rounds to the next higher/lower value, but this will work). And thanks to you and the team for the impressively quick turn! --Will

Thanks Cary. Sp1 would be great if possible. For what it's worth, I'm working on optics related machinery projects, so 10e-9 sounds silly-tight but it isn't. Nanometers or better would be a very good thing... Thanks again!

Thanks Cary. Will adjust the setting, and use your suggested workaround . Here's hoping it gets resolved soon. It's strikes hard at one of the strengths of IC -- rapid design conceptualizing, which obviously presumes reliable precise dimension adjustments for part interfaces and fit-up. --Will

Cary -- Thanks. I look forward to a fix. Do you have recommendations / best practices in the meantime to mitigate this issue? Its a big problem wondering if incremental changes "stick," and having to go back and check, then drag and enter if it they don't... Perhaps a temporary mitigation would be to revert to the 2018 dimension display -- where the current dimension is displayed after enter is pressed, (rather than auto-advance-to-next-dimension) so that a user can at least verify that their change "stuck"? Is there a setting for this (looked but might have missed) or perhaps a patch could be created? Malcom -- Thanks for the tip. I'll gI've it a try! --Will

Jolizon -- Thanks for the video. I am aware of this workaround (and have used it), but for the reasons I mentioned it's not ideal. Needing to keep track of dimensions, drag, and then retype them makes the design evolution painful and cumbersome, at least for me. Most importantly, I don't know when my changes will "stick" and when they won't. This is game changing. Malcom -- Thanks for your video. Whew! Your video typifies my experience as well. I was beginning to wonder if it was just me! Cary -- I've attached an avi of the file -- let me know if this works. Really grainy, sorry -- it's a re-captured playback of the video. Malcom's video is representative of my situation as well. (Incidentally, what screen-recorder do you and Kevin use? I believe you or Kevin sent a video a bit ago, and it was nice and clean, and worked well.) --Will precision2.avi

Thanks Jolizon (I can't seem to view your video successfully...) Thanks Cary -- I've attempted to screenrecord my session. (not the best quality but should be legible). You'll see that I make a few attempts at changing the height of the Hblock. 1. The first few times, I try to change the 4th digit of the dimension to a few different values. I highlight, overtype, and then press enter. Each time, when I look at the height value again, it has reverted to the original value. 2. Finally, I highlight and delete the digits to leave a round 9.5 as the dimension value, then press enter. This time when I look @ the height value again, it has retained the 9.5000. Let me know if this is legible enough... Thanks again for all. --Will precision1.swf

Thanks Cary -- I've already done this, but unfortunately the issue remains -- just more zeros are displayed. Perhchance, have you worked w/ my file and found that it behaves differently (ie correctly) for you? --Will

Thanks. I understand that the dimension shows the last (current) value. But entering a new value should update the intellishape to the new value, yes? I see an inconsistency here. 1. I select the intellishape, 2. I graphically click the height dimension, and it displays 9.5035. 3. I edit the dimension to 9.5000 and press return. 4. Then all is well, the intellishape updates, and the dimension updates. This is expected behavior. If instead: 3. I edit the dimension to .95034 and press return. 4. Then the intellishape does not update, and the dimension does not update. This is unexpected behavior, and the only difference is the amount of change in the entered value. It's also an unpredictable result. One doesn't know whether a normal graphical dimension change has "taken" or not. Yes, I can drag the intellishape first, and then enter the desired dimension, but this is disruptive, particularly when just slightly adjusting a dimension (one must memorize a a dimension to many decimal places, manually drag, then re-enter the desired dimension; or enter a different temporary value, then re-enter the desired dimension...yikes). Most disconcerting is that I'm not sure when the "drag-then-change" method, is needed, and when it's not... Were you able to recreate this? I played with it some more and it's repeatable on my setup. But if it's only on my machine, then maybe there is something wrong with my setup, settings, or...? Thanks again, --Will

Greetings. I have a cylinder, into which I want to make a flat of a known width (like a flat on a shaft) I figured I'd just try to model this in innovate part mode. The parts are metric. 1. I modeled a cylinder. 2. Then I dragged an H block onto the cylinder, and my plan was to tweak the height of the hblock (and thus the "interference" between the Hblock and the cylinder), iteratively to get the desired flat-width (28.4mm). 3. What I found was that I am unable to adjust the height of the hblock at the 4th decimal point in the graphical window. "9.5035" is the present figure. When I type "9.5034" and return, then edit the hblock again, the height dimension is "9.5035" once again. 4. When I do "intellishape properties" and "edit sizebox" I *am* able to adjust the 4th decimal place and make it stick. So it seems I am not able to adjust the hblock dimensions with the same fine-ness in the graphical window that I am within the "edit sizebox." (I've tried tweaking general settings to increase decimal display, etc). Is this a bug or a setting I'm missing? Some thoughts: 1. Acknowledged that this is not the most efficient way to make such a flat. It probably makes more sense to do this with an appropriate sketch in structured part mode, I get it, so please don't beat me up there. My question here pertains to precision of IC dimension input, which I stumbled upon as I'm experimenting with the tool. 2. Yes, this is physically very small in metric dimensions. In this case, I was intending to tweak the height of the hblock so that I could achieve the flat-width that the vendor expects. Yes, this could be handled with rounding, drawing digits-displayed, etc, etc, etc. Again, I'm trying to understand and gain confidence and fluency in the tool. This affects my understanding of how dimensions are handled, and what I can do with the tool. Thanks again all. I'll now try to attach a pic, and also the scene. --Will precision_test.ics

Thanks much Kevin. --Will

Okay, I believe I've isolated the problem. When I type an expression into the size field, things work fine if I use the *number pad* on my machine to type the operator symbol. If instead I use the regular keyboard to type the operator (for instance SHIFT+8 for "*"), I get kicked out of the size field with that keystroke. Bug? --Will

Thanks Jonas -- changing the driver to DirectX11 did the trick! The centerpoints appear to consistently highlight now! For what it's worth, I was running OpenGL. The problem was frequent but not predictable. In my brief experimentation, it seemed worse with cylinders, and was (perhaps) dependent on the orientation of the cylinder. Fixed now, however. Thanks again! --Will

Thanks Jonas -- I guess you had v2018 on the same computer? Which graphics card do you have? 48579[/snapback] (First to confirm what you correctly surmised -- I speak of v2018 and v2019, not "v18" and "v19" as I incorrectly mentioned) Yes, I'm running v2018 and v2019 on the same machine. My graphics card is an Nvidia Quadro 1000M. This evening (away from machine at the moment), I'll tweak the settings you mention and report back. --Will

Thanks Jonas -- Hmm. Thinking this was the case, I tried to enter an expression "35.5*2" for a cylinder diameter, the dimension kicked me out of edit mode, and retained the previous value of 40.0. As I recall, it kicked me out at the "*" keystroke. (I can confirm this evening when I'm back on my machine if such confirmation is helpful). --Will

In v19, I no longer see the region to the right of an intellishape dimension which allows to toggle to "formula" mode. Is there a setting for this? --Will

Greetings -- First post here, and I'm relatively new to IC so feel free to redirect me if I've missed posts addressing my questions (perhaps due to incorrect search terminology). I've tried to maintain a steady intake of help-topics and some videos, but alas, so much to learn. First question: I was running v18 for a time, and now I'm trying to migrate to v19. In v18, when dropping a new shape onto an existing (say dragging a cylinder onto a previously dropped cylinder), the centerpoint of the existing shape face would highlight green when I hovered in the vicinity, and I could release the new shape there, knowing it would snap to that location. In v19, when I hover and drop over the center of the end of a cylinder (for instance), the snapping appears to still work, but the centerpoint *disappears* rather than turning bold-green. A bit disconcerting. Perhaps there is a setting I'm missing? --Will