2015-10-29 02:25 AM - last edited on 2023-05-23 04:20 PM by Rubia Torres
2015-11-06 04:09 PM
DGSketcher wrote:Yes, there can be many Snap Guides. The solution is to control the number of marked Snap Reference. I would say it is best to never have more than 2 or 3 Snap Guides displayed at the same time, that probably offers good usability.
I think this perhaps offers the best indication of a problem...
https://www.youtube.com/watch?v=knMw7CLh7a4&index=16&list=PLnXY6vLUwlWXj_1QX5iXbZ0cfscL-VNEX
What I don't think is considered by GS in the real world is that where you have a complex drawing then the resulting intersections aren't always what is anticipated. Where previously I might have expected a simple perpendicular connection the snap guides are offering numerous intersections some of which can be misinterpreted.
I guess I can turn the guides off unless really needed. However I am still getting odd results for the dimensioning mentioned previously. If I dimension by clicking the edge or centreline of the beams I get the right result, however, if I click on the intersection points of two beams the resulting dimension can be random. It is also necessary for a beam to be highlighted before a dimension becomes associated which slows things down.Can you post a screenshot of this one?
2015-11-06 04:21 PM
2015-11-06 07:06 PM
2015-11-06 11:35 PM
Erwin wrote:This is the issue I have been having described in this thread
Below is a screenshot I sent to the local reseller.
2015-11-09 09:44 AM
2015-11-09 12:02 PM
KeesW wrote:For this I would check your View > Grid & Editing Plane Options > Grids & Background settings. Even if the Rotation Angle says 0.00º (or any custom angle you have entered), highlight the value and type 0 (or the angle you desire) to insure there is not a rounding error happening. Also using the buttons in this dialog set the grid to Orthogonal. It might be easier to see this under the View > Grid & Editing Plane Options menu. Make sure the checkmark is next to Orthogonal Grid.
I have and issue with using the 'SHIFT' constraint to place elements vertically or horizontally. Sometimes, the constraint puts the object just off vert. or hor..The off angle is around 1 degree or even less and it is often too close to notice. It is only when one aligns it with something that is correctly hor. or vert. that it is noticed. Then, it seems to fix itself, until it re-occurs - usually unwittingly. I've had this happen in many recent versions including AC19.
Erwin wrote:I believe I have been able to reproduce this as you describe it and I have forwarded my findings to HQ with a video and test file. So they should be able to get a handle on the matter.
I'm also having issues with edge offset of fills, slabs, roofs etc picking a random point away from the edge (which shouldn't even be possible). I've reported these to the dutch reseller (Kubus). It's hard to reproduce, but it happens multiple times a day.
DGSketcher wrote:I am testing this out now. I believe there is an accuracy issue when zoomed out beyond a certain point, which may or may not be reasonable. But I am still pinning down the details and I do tend to lean in favor of your findings at this point. As soon as I have the finer details of the matter sorted out I will post it to HQ.
Laszlo, I'm not sure if this was worth a new thread for the linear dimensioning issue.
If as previous I anchor the end points for my dimension line and cmd-clk to add in-between dimension points I am prone to get random static dimensions. If however I highlight the dimension line and then click again to bring up the pet pallet and select insert/merge dimension point then the cursor momentarily changes to a hammer before converting to a tick when the dimension point is reached. The resulting dimension is consistently accurate and normally as expected associative.
Both processes have been tested at the same zoom e.g. my normal working zoom.
To me this is starting to look like a bug in the dimensioning process.
Obviously the latter workflow is also a lot slower than just cmd-clk on a string of points...
Erwin wrote:I can reproduce the feedback you are getting if I have an extremely thin skin, like 1mm thick or thereabouts, and if I click on the wall corner while zoomed out to a point where I cannot clearly see the skin. So I do not think it is directly related to the other issues. Maybe it is just a matter that under these tight conditions there is not a different feedback from the cursor if it is the end of a reference line or a wall skin you are about to select or have selected. I'll bring it up with someone on the product team. Please let me know if I am mistaken or if there is more to it than what I describe.
Possible related issue: if I click on the end point of a wall reference line I get the pet palette for moving the wall (as if you would click on another point of the wall), clicking again (or sometimes more than a few tries) gets the right pet palette so I can stretch the reference line.
2015-11-09 12:50 PM
2015-11-09 10:55 PM
2015-11-10 12:11 AM
2015-11-10 12:58 AM
lasse wrote:It does seem very similar to the feedback of the error with the Offset. However I cannot reproduce this particular set of circumstances. I will send you a Private Message with an upload link. If you would, please send us an example file so that our developers may have an sample to investigate.
This may be related: I'm getting similar frustrations even with guidelines OFF as well as input constraints and guidelines off (except Hor & Perp)....and even with grids and snap grids off. In my case the Horiz/Perp constraint is fixed with shift key and I'm dragging out to the next input point (perpendicular in my case), but the cursor snap (rubber band line from pointer - whatever it is really called) doesn't constrain anymore, instead offering many bizarre snap points and origins, which leads me to get erroneous input by a matter of degrees. (see attachment). Thx - L