VTENABLE resets at startup & drawing open

[randyc]

Judging by the number of strings asking how to turn this option off, apparently I am one of the few who actually like this feature (I know, :screwy: ). Unfortunately, the View Transitions Options (VTENABLE sys var) keeps resetting every time I restart AutoCAD or open a drawing from within AutoCAD:banghead: . The default setting for VTENABLE is supposed to be 3 but mine reverts to 0 (I prefer 7 but I'll take anything above 0 :neutral: ). Is there some way to make the VTENABLE sys var setting permanent? When I took an AutoCAD 2007 class this seemed to be the default setting, how or why would this get changed :confused: ? Any help would be very much appreciated.

[Tom Beauford]

Mine does the same. Do you have Eagle Point software as well?

[rkmcswain]

The default setting for VTENABLE is supposed to be 3 but mine reverts to 0

VTENABLE is saved in the registry, so once it's set it's stays set -- until something changes it. You have a startup routine that is changing it.

I would say just add a call to (setvar "vtenable" 3) in your "acaddoc.lsp" -- but this is not necessary. Just find where this occurs in your startup routine(s) and fix the problem rather than trying a band-aid solution.

[randyc]

Tom, sorry to hear you're having the same issue. No we do not use any Eagle Point Software. Hopefully you will be able to find a solution to this through me 8-) .

rkmcswain, thanks for the info. I have tried unsuccessfully to find which startup routine is setting the vtenable variable. I looked through every .lsp and .dcl routine in the Autodesk root, support, usercache, and land directories but found no reference to vtenable in any of them :confused: . Now, I am extremely new to 2007 (we just upgraded from 2004 3 weeks ago), so I am not as familiar with the new Autodesk structure as I was in 2004 (and with 2004 I only kinda knew my way around). Maybe I am just looking in the wrong places, and if I am then I plead ignorance :Oops: . Could you lead me in the correct direction and give me a hint as to where I should be looking? I would very much appreciate any assistance you could lend. Thanks.

[Tom Beauford]

VTENABLE is saved in the registry, so once it's set it's stays set -- until something changes it. You have a startup routine that is changing it.Thanks, that got me pointed in the right direction. It's going to keep resetting to the registry value each time. I added this item to my CUI:
Name: $(if,$(or,$(and,1,$(getvar,vtenable)),$(and,3,$(getvar,vtenable))),!.)View Transitions
Macro: ^C^C^P(if(= 0 (getvar "vtenable"))(setvar "vtenable" 3)(setvar "vtenable" 0))(vl-registry-write (strcat "HKEY_CURRENT_USER" (chr 92) (vlax-product-key) (chr 92) "Profiles" (chr 92) (getvar "cprofile") (chr 92) "General" (chr 92)) "vtenable" (getvar "vtenable"))
Works like a charm for me, but it may need modification for your setup.

[rkmcswain]

Could you lead me in the correct direction and give me a hint as to where I should be looking? I would very much appreciate any assistance you could lend. Thanks.

I would try setting up a reactor as shown in this post, to track changes to VTENABLE.

[rkmcswain]

Thanks, that got me pointed in the right direction. It's going to keep resetting to the registry value each time. I added this item to my CUI:
Name: $(if,$(or,$(and,1,$(getvar,vtenable)),$(and,3,$(getvar,vtenable))),!.)View Transitions
Macro: ^C^C^P(if(= 0 (getvar "vtenable"))(setvar "vtenable" 3)(setvar "vtenable" 0))(vl-registry-write (strcat "HKEY_CURRENT_USER" (chr 92) (vlax-product-key) (chr 92) "Profiles" (chr 92) (getvar "cprofile") (chr 92) "General" (chr 92)) "vtenable" (getvar "vtenable"))
Works like a charm for me, but it may need modification for your setup.

Tom,

Why write to the registry when AutoCAD makes this change for you? Setting the VTENABLE sysvar is all that's necessary.

[randyc]

I just found out that our Autodesk2007 directory and all sub directories have read only limits set on them. I have no clue why our IS dept. would do this, it certainly was not like this before our upgrade :banghead: . Correct me if I am wrong, but wont this affect the way Autodesk saves changes to the program if it cannot write to these directories? I certainly is keeping me from modifying my acad2007doc.lsp.

[rkmcswain]

I certainly is keeping me from modifying my acad2007doc.lsp.

You don't want to edit that file anyway. That file comes with the program and is "owned" by AutoCAD - meaning that during a reinstall, repair, or upgrade it is subject to being overwritten.

Create your own directory and your own "acaddoc.lsp" in it. No upgrade or reinstall headaches. More details here:

http://rkmcswain.blogspot.com/2006/07/autocad-customization-setup-and.html

See also:
http://support.autodesk.com/Getdoc.asp?ID=TS21336
http://support.autodesk.com/getdoc.asp?ID=TS28079
http://support.autodesk.com/getdoc.asp?ID=TS43235

[randyc]

Oh, ok! Great! Thanks for the link, I'll give it try :wink: .

Now back to my other question: Does Autodesk still need read/write access to the parent Autodesk 2007 directory? I know from experience in 2004 we had to have access to that directory or changes we made to tool bars, menus, etc. would be overwritten every day (our setup had Autodesk reinstalling at our workstations every login, so our roaming profile data would be overwritten). Now I understand the whole CUI thing has changed the .mnu/.mns thing totally, so maybe it is not as critical to have access to these directories (especially since all of our CUI info is saved into our roaming profiles, which is no longer being overwritten :mrgreen: ). This is just for curiosities sake, if we don't need the access, then so be it :roll: .

Thanks again for the info.

[rkmcswain]

Now back to my other question: Does Autodesk still need read/write access to the parent Autodesk 2007 directory?

I can't see why WRITE access would be needed. That directory only contains program files.

Files such as the PGP, CUI, MNL, etc are in your local windows profile:

C:\Documents and Settings\username\Application Data\Autodesk\product\version\language\Support

(where the blue items vary...)

However, on the other hand - I can't see why directory permissions would be used to restrict access to that directory either.

[randyc]

Hmmmm :| . Well as long it is working then I'll leave it as is and wont rock the boat with our IS dept. (for now :twisted: ).

Again, thanks for the info, I really appreciate it :beer: .

[BrenBren]

I can't see why WRITE access would be needed. That directory only contains program files.

Files such as the PGP, CUI, MNL, etc are in your local windows profile:

C:\Documents and Settings\username\Application Data\Autodesk\product\version\language\Support

(where the blue items vary...)

However, on the other hand - I can't see why directory permissions would be used to restrict access to that directory either.
Our IT policy is to restrict anything from being written to your hard drive :screwy: I know.. I've been able to work around it so far, but if they start looking, I have no idea what we are going to do...

[randyc]

I always go by the old saying "It is better to ask for forgiveness than to ask for permission" when dealing with our IS department, it also gives me plausible denialbility... "I didn't know I wasn't supposed to do that and no one told me not too...

:veryevil:

[sinc]

Are you using Vanilla Autocad, or are you using any sort of vertical app?

I notice the same behavior on Land Desktop 2007. VTENABLE constantly gets reset to 0. Nothing we have done changes this value. This seems to be the default behavior of Land Desktop, contrary to what the Help says.

In Civil-3D 2007, VTENABLE behaves as stated in the Help, with a default of 3.

[randyc]

We are using the whole Autodesk 2007 Civil package (LDT 2007, Land Enabled Map 2007, Civil 3D 2007, Civil 3D as AutoCAD 2007, and ADT 2007) and in every application our VTENABLE is set to 0 on startup. I halfway suspect it was set during the install (our PC's are imaged during upgrades/installations so everyone has the exact same install) and may have been set due to configuration issues with our graphics card and Autodesk 2007 (our IS dept. felt that upgrading the drivers for our graphics cards to meet Autodesk 2007 specs would have been to time extensive so was not done :banghead: ). But this is just my unconfirmed (and most likely wrong :Oops: ) opinion. What I do know is that during our training the laptops we were using had the whole Civil 2007 package as well (we used Land Enabled Map 2007 only during the training) and the VTENABLE setting was 3 by default then so I have no idea what the difference really is.

[randyc]

BTW, rkmcswain, the acaddoc.lsp w/ the setvar script is working great 8) , thanks a million for the tip :mrgreen: .