Problem with drawing on UCS in ACAD 2015

[lovecraft]

O.K.  Been running 2015 for a week or so now.  My experience has been mixed.  I like the way Mtext has been improved and I've played around a bit with some of the other selection "enhancements" and some things I like and others will just not use.  Yesterday I ran into a snag that, if not fixed, will cause me some grief and frustration until I find a workaround.  For quite a few years now I've been working with 3D solid modeling and when I create new geometry, be it 2D construction aids or actual solids themselves, my methods involve a lot of moving, rotating and otherwise re-orienting the UCS to facilitate my workflow.  Much to my surprise, yesterday, when starting from the WCS, then moving it to a new location slightly above that plane and rotating the new UCS 90 degrees CCW around the X axis (in effect establishing a work plane parallel to and, in fact co-planar to the WCS Orthographic Front plane), I found that when drawing a new line on this plane, then starting another line originating at one end of that first line, that the start point of the second line was (believe it or not) forced back down onto what seemed to be the WCS and that no matter how I dragged my mouse (more on that in a minute) the second line was constrained to a plane below where I was trying to draw (apparently on the WCS) 90 degrees out of plane with the UCS that I had just established and was trying to draw upon.

Now, I've been racking my admittedly feeble brain trying to explain this shocking and unexpected behavior, since it will, if not overcome, seriously and deleteriously affect my workflow and productivity.

Some of the things I've considered as an explanation and rejected when modifying them had no effect:

Accidentally hitting F7, F9 or F11 keys which would activate snap, grid or tracking modes.

Video card driver.  Autodesk seems to be telling me it's up to date.  By the way, I notice that 3DCONFIG has been retired and has now been replaced with GRAPHICSCONFIG.  I notice that there's no way now in preferences to manually check if this is up-to-snuff, that we just have to rely on the software periodically checking to see that all is well----hope this works as promised.

The next thing I plan on looking into is the mouse, which is an older Microsoft Trackball, something I swore a few years ago I would never use but has actually worked out really well for 3D work, as you can assign orbit commands and the like to one of the additional buttons provided.  However, I guess I need to check to see whether I can update the mouse driver to work better with ACAD 2015----there were NO ISSUES with 2014.

I also tried to audit and recover the file (no help there, and besides, I tried the same frustrating exercise in another known-to-be-uncorrupted file and experienced the same disappointing behavior).

Could the explanation be (just a theory, mind you) that Autodesk is now forcing us to use these Dynamic UCS's that, I guess, were originally created to eliminate the need to move, rotate & otherwise re-orient our co-ordinate systems to facilitate creating geometry in 3D space?  I hope someone out there has an answer for this.  My preference would be to stick with my established and very effective method of controlling my UCS, but if I have to adopt a new methodology I would like to know as soon as possible.

Can anyone in the forum point me in the right direction to take care of this problem? 

[Anonymous]

I would like to confirm that both service packs were installed when this
issue occurred for me. The only thing that worked was resetting the
defaults per the AutoCAD reps' suggestion (Or just using PLINE) which
completely messes up everything you could possibly have customized. This
required half of a day for our IT to re-link all of our standards etc...

Dear AutoCAD rep,

Has the development team come back with anything since you forwarded this
issue to them? The Main issue for me was the affect on the LASSO selection
box.

[jeffFZDLA]

Problem:  Using LINE command while drawing in a UCS that is not coincident with the WCS, the active line segment is not drawn correctly.

Solution:  Set DYNMODE to 2 or 3.  (Setting DYNMODE to 0 or 1 creates the issue.)

Discussion:  I had same issues as the OP.  Using the LINE command while the UCS is set to something other than the WCS had the interesting result of the active line segment being drawn in WCS coordinates (i.e. AutoCAD gets the current UCS X, Y, and Z coordinates, but the displayed active line segment uses the UCS coordinates and displays them in the WCS system.  So the active line segment can be offset and rotated from where the cursor is located.  Sometimes you have to zoom out to see it happening.  This does not affect any actual completed line segments - those are drawn correctly once a line segment has both start and end points defined.  It is just the active portion of the line segment that is affected.

Other commands affected:

PROBLEM:  If you have a rotated/translated UCS active, and you try to select using the Fence, WPolygon or CPolygon options, the active segment of the Fence, WPolygon or CPolygon will not display correctly.  However, as with the LINE function, once a segment is defined with an endpoint (usually via clicking the mouse), all segment except the active segment will be drawn correctly, and the function still works.  It just does not draw the active segment correctly.

SOLUTION:  None known at this time.  Again, I think using 2019 or later will cure the issue.