I've noticed some issues with Osnap tracking not working consistantly with a floating commandline. It seems to happen especially when trying to track back along an object.
No problems whatsoever when commanline is docked.
Can anyone else confirm?
>> I've noticed some issues with Osnap tracking not working consistantly with a floating commandline.
>> It seems to happen especially when trying to track back along an object.
Can you describe what is this issue looking like? The words "some issues" and "It seems" is not enough (at least for me) to know what you get in another way as you think it should work .... and so what we should look for.
- alfred -
I have also noticed that when the command line is floating it causes problems. If the command line is floating and you try to do anything without first moving your cursor it will not work on the first try. Example: start the line command and without moving your cursor pick a point on your screen, it will not start the line. After the first pick or moving the cursor a little everything works fine. Also on osnaps: If you are hovering over a line and then control right click + e to do an end point selection it will not work on the first click unless you move the cursor a little. Very annoying when doing rotate or scale and using reference with same end point location without moving cursor. Everything works perfectly fine when the command line is docked. Also if you start the line command and do not move crosshair and click a point in screen your crosshair will disappear until you move the cursor and the line will be wanting a start location.
start the line command and without moving your cursor pick a point on your screen, it will not start the line.
Confirmed, and not acceptable.
>> If the command line is floating and you try to do anything without first moving your cursor
>> it will not work on the first try
>> Very annoying when doing rotate or scale and using reference with same end point location without moving cursor
Same as in 2012, so nothing new.
Not that I see that now as acceptable, but my question is more: have you ever put this info to the Autodesk-support?
For me it's not important as I have my commandline docked.
- alfred -
I didn't notice it in 2012 either because I had my comman line docked also. Only noticed the problem when trying out the "new and improved" command line in 2013. I now have the command line docked for a work around. I will submit a support request with autodesk so that maybe it will be corrected with the first service pack.
I have also noticed that it works fine when a command is entered and DYNMODE is = 1 or 3,
but if you want to continue the same command and just hit enter (without typing the same command) the problem still occurs.
This also is the case in any command you continue by hitting enter that ask for a selection, it will not select the item you are hovering over on the first click unless you first move your cursor a little.
OSNAPS: If you are already hovering near the end point of a line and the endpoint osnap is turned on it will snap to the endpoint with no problem when the line command is typed in. But if you hit enter to go back into line command again, the endpoint osnap will briefly show and disappear until you move the cursor.
All works properly if the command line is docked.
This is the lastest email from Autodesk Support Team.
Thank you for choosing Autodesk Support. Your case has been documented and sent to our development team for investigation. The development team will try to reproduce your case and make an initial assessment. We appreciate your patience as we work to resolve your inquiry.
Yes Indeed , and very thank"s for your message because I'se seeking the cause of this very disturbing bug !!Maybe the upcoming SP will Fix it