TheSwamp
CAD Forums => Vertically Challenged => Land Lubber / Geographically Positioned => Topic started by: MSTG007 on April 27, 2016, 12:51:30 PM
-
Sorry having one of those moments again. Who do we contact if we have a Civil3D Bug? or how does that work. Apparently, I forgot again.
thanks
-
Sorry having one of those moments again. Who do we contact if we have a Civil3D Bug? or how does that work. Apparently, I forgot again.
thanks
I don't think it really matters....not much seems to get fixed or added...C3D Autodesk's unwanted step child.
-
Bug reporting: http://usa.autodesk.com/adsk/servlet/item?id=1073063&siteID=123112
You can also post it on the Autodesk C3D forum. After a post goes unresolved a certain period of time it is supposed to be escalated to the Support team. I have had a number of items fixed via this route....mostly API related.
-
Jeff,
Thanks that's what I forgot!
-
Bug reporting: http://usa.autodesk.com/adsk/servlet/item?id=1073063&siteID=123112
You can also post it on the Autodesk C3D forum. After a post goes unresolved a certain period of time it is supposed to be escalated to the Support team. I have had a number of items fixed via this route....mostly API related.
Then why doesn't more stuff in the core application get fixed?
-
I have no idea, Michael, other than not enough people complain about what isn't being fixed. When I submit a defect in the API I must provide them with a business case as to WHY I need it., which includes:
Impact on your application and/or your development.
The number of users affected.
The potential revenue impact to you.
The potential revenue impact to Autodesk.
Realistic timescale over which a fix would help you.
In the case of a request for a new feature or a feature enhancement, please also provide detailed Use Cases for the workflows that this change would address.
So perhaps if more people were very specific about what needs to be fixed, why it needs to be, and the $$ it's costing them by not being fixed, then more might get accomplished? But I see more "It's broke, fix it, its still broke, why haven't you fixed it" comments over yonder than anything else.
-
Great way to explain that. That shines a whole new light on why some of the comments I see are like that. But if that is what we need to do for them to help us, then there we go.
-
So we must make the business case for them to fix their own product?
Where, or when do we get our pay check from them for doing their job(s)?
-
So we must make the business case for them to fix their own product?
Where, or when do we get our pay check from them for doing their job(s)?
That's been the norm in the software industry for decades -- going back to punch cards at least. See "The Software Conspiracy" by Mark Mimasi. Probably 20 years old now, and still 100% on track. Also -- "Silicon Snake Oil" can't recall the author's name at the moment, but he achieved a measure of fame back when tracking down a 75 cent accounting error to East German intelligence.