topic Re: C3D 2018, Win10E, command line won't stay docked, LOCKUI doesn't fix it. in Civil 3D Forum

C3D 2018, Win10E, command line won't stay docked, LOCKUI doesn't fix it.

jeff_rivers — Fri, 11 Oct 2019 20:28:25 GMT

I've been upgraded to a new workstation with Win10E, more ram, and a better video card. AutoCad C3D 2018 with update 2018.2.

My command line won't stay docked on the bottom of the drawing area, and I've saved my workspace and set LOCKUI to 15, per the solution in this thread. When I close then reopen C3D the command line is floating up in the drawing area again. What next?

Re: C3D 2018, Win10E, command line won't stay docked, LOCKUI doesn't fix it.

Jeff_M — Sat, 12 Oct 2019 17:00:21 GMT

@jeff_rivers , have you seen what I posted HERE? This seems to have worked for quite a few others.

Re: C3D 2018, Win10E, command line won't stay docked, LOCKUI doesn't fix it.

jeff_rivers — Mon, 14 Oct 2019 22:27:46 GMT

Hi Jeff, today was spent mostly behind the power curve, so I didn't have time to look into it until just now. My Win10E path is different from yours, so I need to do a bit of exploring. I'll dig into it Tuesday morning...

Re: C3D 2018, Win10E, command line won't stay docked, LOCKUI doesn't fix it.

jeff_rivers — Tue, 22 Oct 2019 15:16:05 GMT

I finally had time to try this today. Here's the line in my profile, showing a negative number for one of the coordinates for the command line (sorry that I have to use Notepad, I don't have access to an XML editor):

I futzed and futzed with it, and nothing was working. I tried several edits to this line, copying the values from the screenshots you posted in the other thread, but nothing changed.

I was about to give up when I noticed that the Workspace="Civil3D" is incorrect: I'm using a customized workspace. Changing that value to reflect my custom workspace finally solved this.

Strangely enough, that Workspace= entry appears in several places in my profile, and all of them except this one were pointing to the correct workspace.