Tim S wrote:
> Jason,
>
> I know you and I have gone 'round about' on issues before, but I don't think
> you understand the frustration of trying to get this stuff to work in a
> production environment. I would say most users install their software
> themselves, and don't have a lot of time away from chargeability to make it
> work. This software was introduced as Civil3D 2004 for cryin' out loud. And
> has been touted as workable in every version so far until we actually try
> it, and then it gets renamed "A Work in Progress". We don't have the time
> that dealers and trainers have to play and find workarounds. It should work.
> Period.
You don't think I understand the frustration? How about leaving a job
as a CAD manager for a 200+ person firm? How's that for frustration?
If you are smart enough to install your own software, then you should be
smart enough to read the readme file that came along with it. Those
nicely typed words aren't there just for show, they actually convey
information. If people can follow instructions, then their headaches
will be much fewer and farther in between.
> Now that being said, maybe we can go at it from a different direction. What
> still doesn't work even with SP2? What commands destroy whole projects and
> cause us to abandon the effort for LDT? I'm really the through with the
> "This SP really works" claim. None so far have.
Have you installed it? Are you using it? If not, stop complaining.
If so, then let us know what areas you're having issues with, and
you'll either get help or a confirmation that you can't do what you're
wanting to do. It's as simple as that.
> Many people would be happy with the Beta state of this software if they just
> knew up fornt that comand A,B or C will cause total corruption of the
> database so stay away until it is fixed. We aren't Beta testers. We are
> trying to make money in a mine field.
Then stick with what you know. Is Autodesk actually at your office
right now forcing you to use Civil 3D?
> You have to admit that many times you have claimed that it works fine for
> you. Why do we need SP's if all the versions so far work fine?
The issues that I state that work for me simply DO. If something doesn't
work, then I'm very quick to discuss it True, there are unstable areas
of the program (grading sound familiar?), and I don't work much with
that. The areas that I've had success, though, simply work. I look at
overall project enhancement, not just one or two little areas that annoy me.
Here's a question - are you really using Civil 3D in production, or have
you just installed it and played with it for a while? As I said, if
you've got it in production and are having problems, document them.
Let people know. The good thing about this newsgroup is those people
who "Just have time to sit and play with the software" are finding
workarounds and fixes free of charge to users. Amazingly enough,
people like you still don't appreciate what's being done. If you don't
like it, don't use it. Simple. But don't stand in the way of those
of us who CAN make it work.
--
Jason Hickey
Civil 3D 2007, SP2
Dell Precision M70
2 GIG RAM, 256 MB nVidia Quadro FX Go1400
Intel Centrino 2 gHz Processor
www.civil3d.com
![Autodesk Design & Make Report](https://forums.autodesk.com/t5/image/serverpage/image-id/1350519iCB55845EBFC43016/image-size/large?v=v2&px=999" "Autodesk Design & Make Report")