PSLTSCALE reverts to 0 at file opening

[Anonymous]

Even though Autodesk AutoCAD Civil 3D help states that the initial value for PSLTSCALE should be 1, with Civil 3D 2018, whenever I open a file, this value reverts to 0.  I've checked the "acad2018doc.lsp" file and there is nothing in there directing PSLTSCALE to set at ANY value.  

This is a super annoying bug (one of the HUNDREDS that seemed to materialize from nowhere with the 2018 version. It makes publishing from sheet set manager impossible, as the linetypes won't display unless you have all of the files open. 

[tcorey · Accepted solution]

Check to see if there is an acaddoc.lsp file. If not, copy acad2018doc.lsp to acaddoc.lsp and put it in:

C:\Users\USERNAME\appdata\roaming\autodesk\c3d 2018\enu\support.

Add this line to the bottom of that file:

(setvar "PSLTSCALE" 1)

Every time a drawing is opened, the value will be set.

[WarrenGeissler]

If you watch your SYSVARMONITOR (little white icon at bottom right) it will show that SOMETHING changed that system variable. There isn't anything in Civil 3D that will automatically do this, so the issue appears to be centered on your system. There is a script, LSP, VLX, SOMETHING that is running on open to change that setting. You might be able to see it by hitting F2 right after opening the file to see what is happening (but maybe not). Is this happening on other computers? If you do not have other computers, can you create a new Windows profile and open the drawing there?

[rkmcswain]

tcorey wrote:

Check to see if there is an acaddoc.lsp file. If not, copy acad2018doc.lsp to acaddoc.lsp and put it in:

C:\Users\USERNAME\appdata\roaming\autodesk\c3d 2018\enu\support.

Wait, there is no reason to copy the acad20xxdoc.lsp file. You can just make a brand new ascii file using notepad for ACADDOC.LSP.

As a bonus -- rather than burying ACADDOC.LSP it that user profile path, just create a new folder (i.e.: C:\CADSTUFF) and drop it in there, and then add that path to the TOP of the support file search path (SFSP). Drop other things in there also, maybe ACAD.PGP, ACAD.LSP, linetype files, shapes, fonts, etc.

Then when it comes time to switch PCs, or move to C3D 2019, all you have to do is scoop up that one folder and add the path to the SFSP again. No hunting down custom files, trying to remember where all your custom things are at.

[Anonymous]

Nice tip for customization file location. Thanks. 

[telze33]

I have had the same problem, and I tried Tim Corey's solution.  It worked on one of the drawings that was doing it, but not the other.  Any other suggestions?

Taylor

[WarrenGeissler]

Make sure the setting ACADLSPASDOC is set = 1

[rl_jackson]

I'm reading this from my phone and wondering why anyone would instill PSLTSCALE variable at 0 in lisp. Just doesn't make good sense.

[WarrenGeissler]

Rick - you're reading it wrong. We're trying to get it set to 1 because it keeps resetting to 0 for some unknown reason.

Don't read posts from your phone at a bar! 

[telze33]

The ACADLSPASDOC set to 1 works once I open the drawing and do saves, but I'm still having the issue when I close and reopen the file.  The drawing goes directly into model space, I have to reset the PSLTSCALE to 1 again, and ACADLSPASDOC to 1 - and then everything works fine (seemingly) from there.  However, it still enters modelspace when I save, although the PSLTSCALE stays at 1.  Still can't delete viewports as well.  I think that is another problem tied together with it.

[WarrenGeissler]

What other add-in programs are you using? (Projectwise or something?) Civil 3D is NOT supposed to be acting this way.

[gramsey]

Same issue here. Almost random when it happens. One of my users just published a 40+ sheet set of plans and two of the sheets had reverted to PSLTSCALE=0.  They were all set to 1 the last time he had saved the file.

Adding (setvar "PSLTSCALE" 1) to startup lisp has not seemed to cure the issue.

And neither of the affected sheets were the current sheet when saved/opened.

Something odd is afoot. This is an IDSP 2018 install. Running Civil 3D with Raster & Vehicle Tracking.

DBMOD verified to be 0 at startup.

[Anonymous]

I'm still having the same problems.  Unfortunately, I can't "un-accept" the answer.  

I still occasionally have PSLTSCALE revert to 0 - and have had the same thing happen with large drawing sets.  I have to diligently review the set after publishing.  

[Anonymous]

It was my 2018 river and flood module causing the problem. I un-installed it and my drawings work fine now.

[telze33]

I also uninstalled Rivers and Flood Analysis module and now the drawings that were having that problem are working properly

[dpresley58]

Yep. Same problem here. In addition to the PSLTSCALE reset, drawings are also opening in model space instead of paper. Has Autodesk been made aware of this, or is there a fix available?

[markedman]

See response 14 above @Anonymous.

This is the only solution we are aware of.

After you open the drawing you are having trouble with, bring up the command list (F2), you will more than likely find that "River and Flood Module" opened with your drawing. 

There is something embedded in these drawings that causes the AutoCAD "River and Flood Module" to open.

This causes the drawing to open in Model Space, changes the PTLTSCALE, and prevents viewports from being deleted. I have no idea why it causes these problems, but it does. 

We have unsuccessfully looked for the embedded item(s) causing "River and Flood Module" to open. If anyone knows what may be causing this, please share. And feel free to make AutoCAD aware of the problem, not sure if they know or not.

Uninstalling the "River and Flood Module"  fixes these problems. You can remove it through your Control Panel on Windows. 

[dpresley58]

Is there a way I can simply toggle it off in the C3d startup? If so, what file contains this info?

[JohnPachol]

I've been using Civil 3D 2020 for at least 12 months with the River and Flood Analysis module installed and did not have any problems until a week ago.  Then I began having the same problems with the PSLTSCALE.  I didn't try any of the above solutions except for uninstalling RFA.  That fixed the problem.

[dpresley58]

Thanks, John.

Yeah, that's what I ultimately ended up doing. I don't need the R&S module, so there was no reason for it to be installed if it wasn't going to sit over in the corner and be quiet.

Thanks for your response, and I'm glad you found a solution as well.

David Presley