AutoCAD Plant 3D
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic to the Top
- Bookmark
- Subscribe
- Printer Friendly Page
strange hot key behavior since SP1 install
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Report Inappropriate Content
When I use my Osnaps, I use shift+right click, then use a single hot key (as underlined when the menu opens).
Since installing SP1 for 2013, I can only use the hot key once (after a short while I can use a hot key once again), next time I try to use a hot key, it just closes the menu and redirects the key entry into the command prompt.
Any thoughts on what is going on here? BTW, this does seem to be just in Autocad/ plant as excel still "hot keys" normally.
Thanks, Rob
Solved! Go to Solution.
Re: strange hot key behavior since SP1 install
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Report Inappropriate Content
there is no SP1 for Plant 3d 2013
Re: strange hot key behavior since SP1 install
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Report Inappropriate Content
Hi Rob,
Could you provide the details of the hot key issue you experieced with AutoCAD 2013 SP1? You can contact me via my email - kb.lee@autodesk.com directly.
Thanks,
KB Lee
AutoCAD Test Development
Re: strange hot key behavior since AutoCAD 2013 SP1 install
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Report Inappropriate Content
You are correct, this issue also effects using Osnaps in Plant3d (and apparently all other verticals based upon AutoCAD 2013 for which SP1 was installed upon). I posted it here since my Suite of products are under the Plant design ultimate suite.
I have found others with this problem:
http://forums.autodesk.com/t5/AutoCAD-2013/SP-1-Is
http://forums.autodesk.com/t5/AutoCAD-2013/Mouse-w
Re: strange hot key behavior since SP1 install
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Report Inappropriate Content
Looks like the latest SP1.1 for x64 win7 has fixed this issue; although, I did not notice it mentioned within the readme.
Rob.
