Anuncios

The Autodesk Community Forums has a new look. Read more about what's changed on the Community Announcements board.

JamesMaeding
1531 Vistas, 29 Respuestas

2016 breaks 2009

I have a set of programs I maintain for acad 2009 to current version.

When I installed acad 2016, it broke several things in acad 2009 (actually map 3d and civil3d).

The easiest one to test is open a blank drawing and click a layout tab to switch, it locks.

I also get a "close or debug" error when closing the 2009 session.

 

Curious if others are seeing this.

Not that I expect adesk to care about 2009, but it may indicate they broke something common to all acad versions.

 


internal protected virtual unsafe Human() : mostlyHarmless
I'm just here for the Shelties

pendean
en respuesta a: JamesMaeding

I support all the way back to 2011 and nothing broke with the 2016 installation: But I have no map3d or c3d products installed.
JamesMaeding
en respuesta a: JamesMaeding

ok, so out of desperation, I uninstalled 2016.

It did not help 2009 c3d.

A reinstall of 2009 c3d did not help.

 

So I switched to 2015 to do something, and it is broke in areas too.

Try this lisp code:

(vla-GetInterfaceObject (vlax-get-acad-object) "AutoCAD.AcCmColor.19")

and

(vla-GetInterfaceObject (vlax-get-acad-object) "AutoCAD.AcCmColor.20")

 

both are broke now. Those are for 2011 and 2015. I am not happy.

 


internal protected virtual unsafe Human() : mostlyHarmless
I'm just here for the Shelties

pendean
en respuesta a: JamesMaeding

You'll need to post in your subscription page for help with all of that stuff, you know the painful fix that I would recommend.
dgorsman
en respuesta a: JamesMaeding

Did you install any of the BETA releases?

----------------------------------
If you are going to fly by the seat of your pants, expect friction burns.
"I don't know" is the beginning of knowledge, not the end.


JamesMaeding
en respuesta a: dgorsman

good thought, but I did not.

I'm scared to try on another machine now as indications are it did mess up versions besides 2009.

 

BTW, 2016 itself ran fine, no issues with it.


internal protected virtual unsafe Human() : mostlyHarmless
I'm just here for the Shelties

Jason.Ferrelli
en respuesta a: JamesMaeding

I just installed the 2016 version of AutoCAD and at this point I have not seen any issues with any of my Civil 3D versions. I currently have Civil 3D 2011-2015 installed. I unfortunately do not have 2009 to compare however.

 

As I have just installed this, I did only test switching tab and created some basic Civil objects. If you provide me with something specific I can test, I will be happy to do so and relay my findings.

 

 



Jason Ferrelli
JamesMaeding
en respuesta a: Jason.Ferrelli

hmm, in C3D 2015, what does this code give you at command line:

(vla-GetInterfaceObject (vlax-get-acad-object) "AutoCAD.AcCmColor.20")

 

I get a "problem in loading application".

 

I have only tried 2016 on one machine, so no data to say its consistent. Glad it sounds like its not...


internal protected virtual unsafe Human() : mostlyHarmless
I'm just here for the Shelties

JamesMaeding
en respuesta a: pendean

not necessarily, as unanswered posts become sub support requests. I already got an email on it.

 

However, in this case your "advice" would be good, as messed up API things point to registry or common file issues which a reinstall should help with.

I'm just amazed my 2015 is messed up too, at least for the color object thing. Its been a while since several versions have been affected by an install.


internal protected virtual unsafe Human() : mostlyHarmless
I'm just here for the Shelties

hmsilva
en respuesta a: JamesMaeding


@Anonymous wrote:

...

So I switched to 2015 to do something, and it is broke in areas too.

Try this lisp code:

(vla-GetInterfaceObject (vlax-get-acad-object) "AutoCAD.AcCmColor.19")

and

(vla-GetInterfaceObject (vlax-get-acad-object) "AutoCAD.AcCmColor.20")

 

both are broke now. Those are for 2011 and 2015. I am not happy.

 


If I recall correctly, for 2011

(vla-GetInterfaceObject (vlax-get-acad-object) "AutoCAD.AcCmColor.18")

 

Henrique

EESignature

JamesMaeding
en respuesta a: hmsilva

oh, I meant 2014 and 2015, typo, thx

 

my full routine is: (for acad and bricscad)

;(MAKE-AX-COLOR (cons acColorMethodByaci 2))
(DEFUN MAKE-AX-COLOR (color-list / color-object color-method)
  (cond
    ;BRICSCAD
    ((WCMATCH (VLAX-PRODUCT-KEY) "*\\V12*")
      (setq color-object (vla-GetInterfaceObject (vlax-get-acad-object) "BricscadDb.AcadAcCmColor.12.0")
            color-method (car color-list)
      )
    )
    ((WCMATCH (VLAX-PRODUCT-KEY) "*\\V13*")
      (setq color-object (vla-GetInterfaceObject (vlax-get-acad-object) "BricscadDb.AcadAcCmColor.13.0")
            color-method (car color-list)
      )
    )
    ((WCMATCH (VLAX-PRODUCT-KEY) "*\\V14*")
      (setq color-object (vla-GetInterfaceObject (vlax-get-acad-object) "BricscadDb.AcadAcCmColor.14.0")
            color-method (car color-list)
      )
    )
    ((WCMATCH (VLAX-PRODUCT-KEY) "*\\V15*")
      (setq color-object (vla-GetInterfaceObject (vlax-get-acad-object) "BricscadDb.AcadAcCmColor.15.0")
            color-method (car color-list)
      )
    )
    
    ((WCMATCH (VLAX-PRODUCT-KEY) "*\\R16*")
      (setq color-object (vla-GetInterfaceObject (vlax-get-acad-object) "AutoCAD.AcCmColor.16")
            color-method (car color-list)
      )
    )
    ((WCMATCH (VLAX-PRODUCT-KEY) "*\\R17*") ;(vlax-dump-Object (vlax-get-acad-object))
      (setq color-object (vla-GetInterfaceObject (vlax-get-acad-object) "AutoCAD.AcCmColor.17")
            color-method (car color-list)
      )
    )
    ((WCMATCH (VLAX-PRODUCT-KEY) "*\\R18*")
      (setq color-object (vla-GetInterfaceObject (vlax-get-acad-object) "AutoCAD.AcCmColor.18")
            color-method (car color-list)
      )
    )
    ((WCMATCH (VLAX-PRODUCT-KEY) "*\\R19*")
      (setq color-object (vla-GetInterfaceObject (vlax-get-acad-object) "AutoCAD.AcCmColor.19")
            color-method (car color-list)
      )
    )
    ((WCMATCH (VLAX-PRODUCT-KEY) "*\\R20*")
      (setq color-object (vla-GetInterfaceObject (vlax-get-acad-object) "AutoCAD.AcCmColor.20")
            color-method (car color-list)
      )
    )
  )
  (vla-put-ColorMethod color-object color-method)
  (if (= color-method acColorMethodByRGB)
    (vla-SetRGB  color-object  (NTH 1 color-list) (NTH 2 color-list) (NTH 3 color-list))
   )
   (if (= color-method acColorMethodByACI)
    (vla-put-ColorIndex color-object (cdr color-list))
   )
   (if (= color-method acColorMethodByLayer)
    (vla-put-ColorIndex color-object 256)
   )
  color-object
)

 


internal protected virtual unsafe Human() : mostlyHarmless
I'm just here for the Shelties

hmsilva
en respuesta a: JamesMaeding

This box don't have 2016, I can't test it...

 

Henrique

EESignature

JamesMaeding
en respuesta a: JamesMaeding

so started looking at reg entries for "AutoCAD.AcCmColor.20"

found its typelib and hunted that down.

It has many entries pointing to things like:

C:\Program Files\Common Files\Autodesk Shared\axdb20enu.tlb

 

I believe those ar the com libraries for 2015.

That rings a bell....I just remembered that I applied a hotfix for c3d 2015 a couple days ago from:

http://knowledge.autodesk.com/support/autocad-civil-3d/downloads/caas/downloads/content/autodesk-C2-...

 

I better double check 2014....awesome, it does not have the color problem.

I might have mixed issues here.  I was thinking 2014 was affected as I thought yopu could make the 2014 interface object even while in 2015.

Botched that apparently. The hotfix must have messed up 2015.

 

Lets hold off on concluding anything but 2009 is affected. Thanks for those who have replied on those versions.


internal protected virtual unsafe Human() : mostlyHarmless
I'm just here for the Shelties

JamesMaeding
en respuesta a: JamesMaeding

further testing has revealed the 2015 hotfix did not cause the color issue, it had to be the 2016 install.

So now I have screwed up 2009 and 2015.

Others may be affected but I have not noticed yet.

 

 

 


internal protected virtual unsafe Human() : mostlyHarmless
I'm just here for the Shelties

Jason.Ferrelli
en respuesta a: JamesMaeding

When I put that code into both of my machines (One with 2016 and the other without) I get this:

 

#<VLA-OBJECT IAcadAcCmColor 0000000037478610>



Jason Ferrelli
JamesMaeding
en respuesta a: JamesMaeding

So I did a reinstall on 2015, it fixed the color issue, so the com stuff seems to be working again.

My 2009 is still screwed up, even after reinstalls.


internal protected virtual unsafe Human() : mostlyHarmless
I'm just here for the Shelties

Jason.Ferrelli
en respuesta a: JamesMaeding

one thing you coudl try is to reset your 2009 user profile to see if that resolves the issue.

 

  1. Navigate to: “C:\Users\\AppData\Local\Autodesk”
  2. For the Autodesk product with which you are having a problem, append the word “OLD” to that folder (For Land Desktop, I dont called how that folder was named. I assume it is something like LDC2009, LDT2009, or it might be Land Desktop 2009)
  3. Navigate to “C:\Users\\AppData\Roaming\Autodesk”
  4. For the Autodesk product with which you are having a problem, append the word “OLD” to that folder.
  5. Open Regedit and then navigate to HKEY_CURRENT_USER\Software\Autodesk\AutoCAD\
  6. If you have more than one AutoCAD product, you’ll see a variety of Rxx.x numbers. These correspond to different AutoCAD releases, with the major number incrementing when a new DWG format is released. For 2009 Versions the number should beR17.2. For a specific list, see here: http://en.wikipedia.org/wiki/AutoCAD
  7. Now delete the R17.2 folder.
  8. Now launch Land Desktop 2009 and it will rebuild the Autodesk Windows Profile from default.

I have seen this resolve many issues, so it could be worth a try.



Jason Ferrelli
JamesMaeding
en respuesta a: Jason.Ferrelli

I did, no effect.
Its odd because Map 2009 seems ok. For c3d 2009, clicking the layout tab crashes it every time.
I can most other things in c3d 2009 no problem, even make c3d surfaces and so on.

James Maeding
Hunsaker & Associates
direct voice (949) 458-5448
fax (949) 583-0759

internal protected virtual unsafe Human() : mostlyHarmless
I'm just here for the Shelties

Jason.Ferrelli
en respuesta a: JamesMaeding

Has this happened to anyone else in your office with their Civil 3D 2009?



Jason Ferrelli
lhampton
en respuesta a: Jason.Ferrelli

Bump for visiblity. We are having this same issue with LDT after C3d 2016 install. Was there ever a solution found for this?

Intel i7 2600 /z68 Gigabyte
8gigs DDR3 1800
Intel 320 Series SSD
Quadro 600 (1gig)
C3D 2016 / LDT 2009 / Win7 x64