Bug - OSNAP and ORTHO

[dbinkney]

F3 and F8 shortcuts start interacting weirdly with the OSNAP and ORTHO commands.  F3 will turn ORTHO off, but not OSNAP on, and vice versa depending on how CAD is feeling.  Sometimes F8 will toggle ORTHO, sometimes not.

Please resolve, it is causing me a lot of frustration.

[Patchy]

How many PC doing this?

[dbinkney]

Just mine so far. Running Civil 3D 2014 on Windows 7.

[Patchy]

Ask C3D group and see if anyone got the same bug, until more than one user got it I doubt autodesk will resolve your problem.

[GrantsPirate]

Is this on a laptop or PC?

If laptop what brand, model.

If PC, is the keyboard attached with USB or wirelessly. 

If wirelessly check batteries and replace.

If USB, try another keyboard or try one that plugs in to the keyboard connection (PS/2).

[dbinkney]

Laptop:  Lenovo T420s, almost exactly 3 years old.

Docked, with a wireless mouse.

I will ask around about other people with the same issue at my firm.

THANKS TO ALL FOR THE RESPONSES.

[jmontie]

Add another one to your list.

Running AutoCAD Mechanical 2014. F3 and F8 toggles are screwed. Sometimes have to switch back and forth 3 or four times to get the desired result. I have pushed F8 without taking a finger off the key and after continually pushing the key it will work correct. Hve only noticed this with F3, F6, and F8.

[Cadguru42]

---

@jmontie wrote:

Add another one to your list.

Running AutoCAD Mechanical 2014. F3 and F8 toggles are screwed. Sometimes have to switch back and forth 3 or four times to get the desired result. I have pushed F8 without taking a finger off the key and after continually pushing the key it will work correct. Hve only noticed this with F3, F6, and F8.

---

This is now happening to me on C3D 2015 with SP1. Very, very annoying!

[ttcfcl]

This is happening to me and all my users with Autocad 2015. We have 2014 as well and it functions properly. 

[Cadguru42]

My SR about this took two responses over 12 days for Autodesk to say they won't send this to development since he couldn't replicate this issue. I sent Autodesk links to many posts on these forums as well as outside forums where people are running into this issue and they were all ignored. This is just another reason why bugs don't get fixed or even looked at by development since they're not even getting notice that this is happening. Autodesk really needs to fix the way they handle these kinds of issues.

[dgorsman]

How do you propose they diagnose a problem they cannot replicate?  What would they fix?

[Cadguru42]

---

@dgorsman wrote:

How do you propose they diagnose a problem they cannot replicate?  What would they fix?

---

Well, considering how many people have had this issue they should know something is in need of fixing. Since it wasn't reproducible on my end, do you think they should just ignore it and not even let development know that there is something wrong?