2005 is looking worse by the week...

Discussion in 'AutoCAD' started by James Maeding, Mar 9, 2005.

  1. The problem isn't that it is a bug.

    The problem is that it is a severe bug that Autodesk is well
    aware of, but has voluntarily chosen to do nothing about.

    Their reluctance to fix problems that affect end-user or third
    party customization, coincidentally serves a conflicting interest
    (selling vertical crossgrades and/or consulting services).

    The game plan seems clear to me.



     
    Tony Tanzillo, Mar 10, 2005
    #21
  2. I am wondering if just adding a (command "undo" "end") will close out any possibly unclosed undos.
    It seems to be pretty harmless. Its two (command "undo" "begin")'s in a row that error out.

    glad you agree this is severe, I'll keep on this.

    "Tony Tanzillo" <tony.tanzillo@U_KNOW_WHERE.com>
    |>The problem isn't that it is a bug.
    |>
    |>The problem is that it is a severe bug that Autodesk is well
    |>aware of, but has voluntarily chosen to do nothing about.
    |>
    |>Their reluctance to fix problems that affect end-user or third
    |>party customization, coincidentally serves a conflicting interest
    |>(selling vertical crossgrades and/or consulting services).
    |>
    |>The game plan seems clear to me.

    James Maeding
    jmaeding at hunsaker dot com
    Civil Engineer/Programmer
     
    James Maeding, Mar 10, 2005
    #22
  3. Its easy to be pessimistic in light of the fact that these bugs drag on, but we don't know enough to make statements
    like that. Every person I have worked with at AutoDesk has been professional and fairly upfront.
    They just have a lot to deal with and sometimes a fix to one thing messes up another.
    So I prefer to just keep talking to my sales rep and reseller, they are both excellent and have hooked me up with the
    right people in the past. It does take persistance though which can be frustrating.

    "Tony Tanzillo" <tony.tanzillo@U_KNOW_WHERE.com>
    |>The problem isn't that it is a bug.
    |>
    |>The problem is that it is a severe bug that Autodesk is well
    |>aware of, but has voluntarily chosen to do nothing about.
    |>
    |>Their reluctance to fix problems that affect end-user or third
    |>party customization, coincidentally serves a conflicting interest
    |>(selling vertical crossgrades and/or consulting services).
    |>
    |>The game plan seems clear to me.

    James Maeding
    jmaeding at hunsaker dot com
    Civil Engineer/Programmer
     
    James Maeding, Mar 10, 2005
    #23
  4. I have heard Adesk plans to fix this for 2006, lets cross our fingers.

    James Maeding <jmaeding at hunsaker dot com>
    |>Its easy to be pessimistic in light of the fact that these bugs drag on, but we don't know enough to make statements
    |>like that. Every person I have worked with at AutoDesk has been professional and fairly upfront.
    |>They just have a lot to deal with and sometimes a fix to one thing messes up another.
    |>So I prefer to just keep talking to my sales rep and reseller, they are both excellent and have hooked me up with the
    |>right people in the past. It does take persistance though which can be frustrating.
    |>
    |>"Tony Tanzillo" <tony.tanzillo@U_KNOW_WHERE.com>
    |>|>The problem isn't that it is a bug.
    |>|>
    |>|>The problem is that it is a severe bug that Autodesk is well
    |>|>aware of, but has voluntarily chosen to do nothing about.
    |>|>
    |>|>Their reluctance to fix problems that affect end-user or third
    |>|>party customization, coincidentally serves a conflicting interest
    |>|>(selling vertical crossgrades and/or consulting services).
    |>|>
    |>|>The game plan seems clear to me.
    |>
    |>James Maeding
    |>jmaeding at hunsaker dot com
    |>Civil Engineer/Programmer

    James Maeding
    jmaeding at hunsaker dot com
    Civil Engineer/Programmer
     
    James Maeding, Mar 10, 2005
    #24
  5. I had seen that before and tried it just now. It had no effect on the speed of the first acad start.
    thanks for the reminder though, I had not done it for some reason.

    Jürg Menzi <>
    |>Hi James
    |>
    |>(...)
    |>> 1) It takes forever to start up in the morning, like a minute or so, without
    |>> any customization. Longer with.
    |>(...)
    |>Work wonders:
    |>http://usa.autodesk.com/adsk/servlet/ps/item?siteID=123112&id=4366058&linkID=2475323
    |>
    |>Cheers

    James Maeding
    jmaeding at hunsaker dot com
    Civil Engineer/Programmer
     
    James Maeding, Mar 10, 2005
    #25
  6. James Maeding

    Doug Broad Guest

    James,
    I think you're going to be very pleased if you upgrade to 2006. The new features should
    not
    require much if any retraining and customization is going to be a breeze, if radically
    different
    from it ever has been. Gone for example are mnu and mns files AFAIK. There is now a new
    CUI command that integrates many of the menu customization tasks and adds a new workspace
    feature which is very nice.

    This release will require very little re-training IMO but with dynamic blocks and many
    granted
    wishes of AUGI members, its likely to be as beloved as R14.

    Regards,
    Doug

    stuff in it, but it seems to take about a year to discover the bad stuff in AutoCad. It
    used to be that there were large time gaps between releases, so bugs worked themselves
    out. Now we are beeing overrun by new ultra-fancy cool features that cause instability.
     
    Doug Broad, Mar 11, 2005
    #26
  7. James Maeding

    Matt W Guest

    Doug: Are you talking about Vanilla ACAD? What're they recommending for a
    minimum for RAM??
    ABS6 recommends 2GB of RAM with a MINIMUM of 1GB.
     
    Matt W, Mar 11, 2005
    #27
  8. James Maeding

    Doug Broad Guest

    Matt,
    Am talking about ACAD 2006, not ADT or ABS 2006.
    I don't know what the recommendations are but I have run ACAD 2006 on
    a laptop with 512 MB RAM with no problems. Of course, more RAM is
    always a good idea and makes everything respond faster.
     
    Doug Broad, Mar 11, 2005
    #28
  9. James Maeding

    Matt W Guest

    True, but 2GB is a little excessive. That far surpasses any RAM
    requirements for any other program we use.
     
    Matt W, Mar 11, 2005
    #29
  10. James Maeding

    Doug Broad Guest

    Matt,
    I can also tell you that I only have 1GB on my main computer. Both
    vanilla ACAD and ADT seemed to work fine on both. Do want to
    get another GiG this year. I think it will help with rendering.
     
    Doug Broad, Mar 11, 2005
    #30
  11. According to 2006 help, 512 MB is recommended.
     
    Daniel J. Altamura, R.A., Mar 11, 2005
    #31
  12. James Maeding

    ECCAD Guest

    Luis,
    give me an E-Mail.

    (remove the nospam & ".")

    Bob
     
    ECCAD, Mar 11, 2005
    #32
  13. Well, I have heard that the regen bug is dealt with in 2006, so thats the main thing.
    To me, the big thing with 2006 is the dynamic blocks.
    That is absolutlely huge. It will change the way many of my progs do things because now blocks can act like stretchable
    leader callouts. I need to play with it more but I could not believe it when I saw it in the beta.
    The heads up is cool too.

    The workspace will be interesting. I have a prog now that saves menus loaded, pulldowns, and toolbar positions into
    states. It is the only tool I have ever seen that does it right. Hopefully Adesk copied the idea, it didnt take a
    genious to know it was needed.
    I think it will be one of the best releases ever, lets hope its stable and faster than 2005 at starting up....


    "Doug Broad" <>
    |>James,
    |>I think you're going to be very pleased if you upgrade to 2006. The new features should
    |>not
    |>require much if any retraining and customization is going to be a breeze, if radically
    |>different
    |>from it ever has been. Gone for example are mnu and mns files AFAIK. There is now a new
    |>CUI command that integrates many of the menu customization tasks and adds a new workspace
    |>feature which is very nice.
    |>
    |>This release will require very little re-training IMO but with dynamic blocks and many
    |>granted
    |>wishes of AUGI members, its likely to be as beloved as R14.
    |>
    |>Regards,
    |>Doug
    |>
    |>"James Maeding" <jmaeding at hunsaker dot com> wrote in message
    |>|>
    |>> Now the scary part is they are releasing 2006 in a few weeks. There is so much good new
    |>stuff in it, but it seems to take about a year to discover the bad stuff in AutoCad. It
    |>used to be that there were large time gaps between releases, so bugs worked themselves
    |>out. Now we are beeing overrun by new ultra-fancy cool features that cause instability.
    |>

    James Maeding
    jmaeding at hunsaker dot com
    Civil Engineer/Programmer
     
    James Maeding, Mar 12, 2005
    #33
  14. James Maeding

    Doug Broad Guest

    Don't expect it to be faster starting up. The second startup however seems quick.
    Its the time between the startup and shutdown that should be the real consideration.

    I will tell you this. ADT as ACAD works perfectly.

    There are many other little enhancements that won't get a lot of press
    dimarc
    dimjogged
    flipping dimension arrows
    extension line linetypes
    new grips on arcs
    improved grips on other things
    more stable interface
    drawing recovery managers

    ...literally hundreds of wishes answered.

    Regards,
    Doug
     
    Doug Broad, Mar 12, 2005
    #34
Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.