Some of you may remember a bug in 2013 where AutoCAD is constantly querying a reg key named XREFSTATE
Ref:
http://forums.autodesk.com/t5/AutoCAD-2013-2014-DWG-Format/XREFSTATE/td-p/3467052
http://forums.augi.com/showthread.php?139634-XREFSTATE&p=1200789
So I decided to check up on C3D 2014 SP1, and it appears to be even worse, at least for me.
Here is a capture of ±1 second of registry activity while C3D is "idle"
It's looking for XREFSTATE again, along with two other non-existent keys, at the same rate of once every 0.26 seconds.
So while AutoCAD is busy querying the registry 12 times a second for data that doesn't exist, I can't help but wonder what else the processor could be doing that would actually be productive?
If anyone else is familiar with Process Monitor and would like to test their 2014, please check this out..
In 2013 and 2014 I have the xrefstate not found. I do not have the two other unfound keys in 2014.
John Mayo
@rkmcswain wrote:Some of you may remember a bug in 2013 where AutoCAD is constantly querying a reg key named XREFSTATE
Ref:
http://forums.autodesk.com/t5/AutoCAD-2013-2014-DWG-Format/XREFSTATE/td-p/3467052
http://forums.augi.com/showthread.php?139634-XREFSTATE&p=1200789
So I decided to check up on C3D 2014 SP1, and it appears to be even worse, at least for me.
Here is a capture of ±1 second of registry activity while C3D is "idle"
It's looking for XREFSTATE again, along with two other non-existent keys, at the same rate of once every 0.26 seconds.
So while AutoCAD is busy querying the registry 12 times a second for data that doesn't exist, I can't help but wonder what else the processor could be doing that would actually be productive?
If anyone else is familiar with Process Monitor and would like to test their 2014, please check this out..
Have you submitted this as a SR?
Yes.
Date Created: 1/10/2014 4:41 AM Defect ID: DE8639 Status: Closed
Results: "I just wanted to follow up and let you know that I did log this defect with development" "....I will now be closing this case with technical support. This does not mean your case is forgotten, but it is in a pending status while the development team works to investigate this instance."
@rkmcswain wrote:@engrtech wrote:
Have you submitted this as a SR?Yes.
Date Created: 1/10/2014 4:41 AM Defect ID: DE8639 Status: Closed
Results: "I just wanted to follow up and let you know that I did log this defect with development" "....I will now be closing this case with technical support. This does not mean your case is forgotten, but it is in a pending status while the development team works to investigate this instance."
This does not mean your case is forgotten
Except it does
AutoCad 2016, currently querying XREFSTATE every 0.8 of a second.
Could it be slowing down?
Or maybe just because it is also searching for these missing entries in every single 0.8second cycle:
09:53:14.3799471 acad.exe 1816 RegOpenKey HKLM\Software\Autodesk\AutoCAD\R20.1\ACAD-F001:409\Variables\CONTENTTYPEORDER NAME NOT FOUND Desired Access: Read 09:53:14.3800196 acad.exe 1816 RegOpenKey HKLM\Software\Autodesk\AutoCAD\R20.1\ACAD-F001\Variables\CONTENTTYPEORDER NAME NOT FOUND Desired Access: Read 09:53:14.3800768 acad.exe 1816 RegOpenKey HKLM\SOFTWARE\Autodesk\ObjectDBX\R20.1\Variables\CONTENTTYPEORDER NAME NOT FOUND Desired Access: Read 09:53:14.3801298 acad.exe 1816 RegOpenKey HKCU\Software\Autodesk\AutoCAD\R20.1\ACAD-F001:409\Variables\CONTENTTYPEORDER NAME NOT FOUND Desired Access: Read 09:53:14.3802036 acad.exe 1816 RegOpenKey HKCU\SOFTWARE\Autodesk\ObjectDBX\R20.1\Variables\CONTENTTYPEORDER NAME NOT FOUND Desired Access: Read 09:53:14.3803010 acad.exe 1816 RegOpenKey HKLM\Software\Autodesk\AutoCAD\R20.1\ACAD-F001:409\Variables\INPUTSEARCHOPTIONFLAGS NAME NOT FOUND Desired Access: Read 09:53:14.3803500 acad.exe 1816 RegOpenKey HKLM\Software\Autodesk\AutoCAD\R20.1\ACAD-F001\Variables\INPUTSEARCHOPTIONFLAGS NAME NOT FOUND Desired Access: Read 09:53:14.3803913 acad.exe 1816 RegOpenKey HKLM\SOFTWARE\Autodesk\ObjectDBX\R20.1\Variables\INPUTSEARCHOPTIONFLAGS NAME NOT FOUND Desired Access: Read 09:53:14.3804337 acad.exe 1816 RegOpenKey HKCU\Software\Autodesk\AutoCAD\R20.1\ACAD-F001:409\Variables\INPUTSEARCHOPTIONFLAGS NAME NOT FOUND Desired Access: Read 09:53:14.3804748 acad.exe 1816 RegOpenKey HKCU\SOFTWARE\Autodesk\ObjectDBX\R20.1\Variables\INPUTSEARCHOPTIONFLAGS NAME NOT FOUND Desired Access: Read 09:53:14.3806880 acad.exe 1816 RegOpenKey HKLM\Software\Autodesk\AutoCAD\R20.1\ACAD-F001:409\Variables\XREFSTATE NAME NOT FOUND Desired Access: Read 09:53:14.3807426 acad.exe 1816 RegOpenKey HKLM\Software\Autodesk\AutoCAD\R20.1\ACAD-F001\Variables\XREFSTATE NAME NOT FOUND Desired Access: Read
these
Darawork
AutoDesk User
Windows 10/11, 3DS Max 2022/24, Revit 2022, AutoCad 2024, Dell Precision 5810/20, ASUS DIY, nVidia Quadro P5000/RTX 5000/GTX760
If you haven't seen Randy's post here check it out.
http://forums.augi.com/showthread.php?139634-XREFSTATE&p=1200789&viewfull=1#post1200789
John Mayo
@jmayo wrote:If you haven't seen Randy's post here check it out.
http://forums.augi.com/showthread.php?139634-XREFSTATE&p=1200789&viewfull=1#post1200789
I don't have a login for there, what's the image for the registry value look like that's in his post?
Hi, I've uploaded Rkmcswains picture with this post.
I was able to create the Reg key sequence ( HKEY_LOCAL_MACHINE\SOFTWARE\Autodesk\AutoCAD\R20.1\ACAD-F001\Variables\XREFSTATE ),
...but I'm not sure if I should be using the same 64bit D-word sub-entries? I wonder what the process involved was to come up with the values?
I presume they are different on a per application basis?
Before seeing the picture, I thought it would be something as simple as creating the key and then a value of either 0 or 1;
Darawork
AutoDesk User
Windows 10/11, 3DS Max 2022/24, Revit 2022, AutoCad 2024, Dell Precision 5810/20, ASUS DIY, nVidia Quadro P5000/RTX 5000/GTX760
Yes, just tried it and made two basic keys, and set their default data values to 0:
HKEY_LOCAL_MACHINE\SOFTWARE\Autodesk\AutoCAD\R20.1\ACAD-F001\Variables\XREFSTATE (Default) REG_SZ 0
HKEY_LOCAL_MACHINE\SOFTWARE\Autodesk\AutoCAD\R20.1\ACAD-F001:409\Variables\XREFSTATE (Default) REG_SZ 0
It worked, not more checking for XREFSTATE.
Now on to the other two; CONTENTTYPEORDER, INPUTSEARCHOPTIONFLAGS.
I'll let you know in a few days if my installation explodes.
Darawork
AutoDesk User
Windows 10/11, 3DS Max 2022/24, Revit 2022, AutoCad 2024, Dell Precision 5810/20, ASUS DIY, nVidia Quadro P5000/RTX 5000/GTX760
If you type contenttypeorder into the command line, what value do you get?
I get B1L1H1T1D1V1
I have no idea what contenttypeorder controls, according to http://www.jtbworld.com/autocad2014.htm it's:
CONTENTTYPEORDER | Sets content type order. |
Hrmm, ingenious.
If the value is static on every installation, I suppose I'll use that value.
I'll check the other workstations in the office.
INPUTSEARCHOPTIONFLAGS: https://plus.google.com/111635815263403722886/posts/Vx8pucZ1cJp
I've got 20. The other workstations are 29 and 31. This apparently governs the amount of processes active in that command line AutoComplete muck.
Darawork
AutoDesk User
Windows 10/11, 3DS Max 2022/24, Revit 2022, AutoCad 2024, Dell Precision 5810/20, ASUS DIY, nVidia Quadro P5000/RTX 5000/GTX760
Darawork
AutoDesk User
Windows 10/11, 3DS Max 2022/24, Revit 2022, AutoCad 2024, Dell Precision 5810/20, ASUS DIY, nVidia Quadro P5000/RTX 5000/GTX760
For some reason, I decided to check on this again today (Civil 3D 2015 SP3) and of course the massive registry poking is still going on.
Then I got to looking at the value that I had set for HKEY_CURRENT_USER\Software\Autodesk\AutoCAD\R20.0\ACAD-E000:409\Variables\XREFSTATE\PrimaryType (138b, in Hex) - because it was not querying the registry for this key.
I decided to try setting this value to the other two poked items:
HKEY_CURRENT_USER\Software\Autodesk\AutoCAD\R20.0\ACAD-E000:409\Variables\INPUTSEARCHOPTIONFLAGS\PrimaryType
and
HKEY_CURRENT_USER\Software\Autodesk\AutoCAD\R20.0\ACAD-E000:409\Variables\CONTENTTYPEORDER\PrimaryType
voila... it worked... no more constant querying of the registry for these keys.
The image below was the BEFORE image.
And here is a screenshot of the registry editor after making the "fix".
I created the registry entry for XREFSTATE, set the value to 0. and now it's showing SUCCESS instead of NAME NOT FOUND, but still checking.
Shouldn't it have just went away, or do I need to set the value to something else?
I also now see a Storage Type entry under XREFSTATE.
Ok.
Got those three figured out and stopped. That slowed the process monitor down a lot.
Now to see if there is any performance increase.
How about this one? GEOMAPMODE
Any ideas what's going on there?
I had completely forgotten about this, but sure enough, C3D 2019, process monitor running like a wild fire.