With all the problems being reported about 2015, I thought I'd try and consolidate all that I've seen so far. If anyone has anymore feel free to add.
1. Confirmed - Survey Database edited and/or created with 2015 cannot be opened by a previous version of C3D.
2. Confirmed - Delete a survey figure from the panorama results in a crash and the figure(s) not deleted.
3. Confirmed - Map support path not created on install, resulting in Map commands not working.
4. Confirmed - MAPIINSERT still not reading the GeoTIFF header UNITS at all, resulting in some images in US survey feet being brought in as meters.
5. Unconfirmed - Extracting swept solids from a corridor does not work in 2015.
6. Unconfirmed - Creating a surface from a RCS file is not in C3D 2015
7. Unconfirmed - Geolocation ribbon tab by default getting focus all the time.
8. Unconfirmed - Command line bar width forgetting its width after close.
9. Unconfirmed - Toggling the lineweight button results in the command line reporting strange messages, even though the lineweights are working correctly.
10. Unconfirmed - Audit sometimes reports many hundreds of thousands or even millions of objects in model and paper spaces.
11. Unconfirmed - The bug where MrSid images shift in a viewport that's had a UCS rotated has not been fixed.
...."Involving the basic essence of functionality for GEOMAP...now broken with the new release. The ability to simply place the map over your project coordinates. "
What? they broke it? I thought one of the new 'features' was that images could be grabbed for plotting/offline use? Could you please explain what's not working now?
Seems to me that the new bug list is longer than the new feature list for 2015.
@Anonymous wrote:15. Unconfirmed - Parking Tools dynamic blocks can't be inserted or edited from the tool palettes window as they aren't in the correct folder. The paths are pointing to C:\Program Files\Autodesk\AutoCAD 2015\Sample\Dynamic Blocks\ and they are installed in C:\Program Files\Autodesk\AutoCAD 2015\C3D\Sample\Dynamic Blocks.
This has now been confirmed to me by Autodesk. It seems to affect IDSP and not IDSU. Not sure about other installers, but the IDSP installer installs to the C3D subfolder when it's not supposed to.
Right Click Alignment in Model Space, Civil 3D locks up.
Scratch that. If I right click ANYTHING, C3D is locked. Let me re-install and get back to you.
Mike
...."Involving the basic essence of functionality for GEOMAP...now broken with the new release. The ability to simply place the map over your project coordinates. "
I've not seen any issues with the command not working. To confirm - you're talking about the geolocation tool. There are a bunch of changes with the feature so maybe there's confusion with the new behavior.
In both cases, you now also have the ability to archive a view of the image for plotting and archival. You can also refresh the image and stretch the image boudary to add more/less data.
Thanks
Dave Simeone
Senior Product Manager - AutoCAD Civil 3D
Autodesk, Inc.
If you're not in a coordinate system you can opt to place the map on some location in your drawing (aka, correlate corner of a building in the image with corner of building in your drawing).
Right.
Now Save and Close the drawing and go to lunch. Come back, open the drawing and the drawing doesn't execute the map placement at your geographic location....
Start the geographic location workflow all over again every time you have to close the drawing.
This is the defect I confirmed with Support in Case ID: 09515281
If this is a new feature, please change it back.
16. Confirmed Defect - Median subassembly not crossing baseline
17. Confirmed Defect - GEOMAP manual location not remembering place after save and close
18. Confirmed Defect - Pipe network style through a data shortcut not remembering it's style on sync
19. Confirmed Defect - Intersection object not working with corridor profiles
This list is getting pretty long. It's much longer than any of the new features that have been added. This has been the worst release since I've been using AutoCAD and Softdesk in 1997.
I'm not sure why we need to use torches and pitchforks in our comments. What purpose does it serve other than allowing a moment to vent publicly?
Just curious...
Kevin
People are obviously upset because they are not feeling they are getting value out of their Subscription financial commitment. Autodesk needs to hear this.
I'm sure as a Vendor you're concerned about sales now watching these defects roll in...
You are a Beta tester I believe also from our previous threads. Help me understand what is going wrong in the quality control testing communication loop with the Civil 3D team?
Are you finding and logging these defects and they are simply being ignored?
Hi Fred. I totally understand the frustration of purchasing a toolset and it not functioning as advertised, or even as previously experienced. Yes, i do work for an autodesk reseller.
I can tell you that there is a dedicated sales team that is highly concerned with that aspect. I am not on that team. My charge it to get firms and the software on the same page, regardless of marketing, etc. So, the number of defects aren't a financial concern for me. Our relationship with our clients have always been to help them regardless of the roadblocks they find, even if they relate to the various bugs being discussed.
You are correct, i am also a beta tester. With the given cycles of development, most beta testing is at the Nth hour. So, the opportunity here is to dot all the i's and cross the t's. As much as i can't tell you, the point in using the wider community as beta testers is not to find new issues but to evaluate the new release based on the new improvements AND also to evalute a project you might have in the new release. I know some folks do maintain a rolling list of problems and also evaluate those in the new release. We do have 2 avenues to communcate with the Autodesk team; we can log DEFECTS as well as possible FEATURE REQUESTS. Those go through a similar vetting process as technical support requests you may submit.
Am i personally finding these defects? NO, but when i do, they do get logged as metioned above. It's kind of the chicken or egg scenario. I won't fully test the new release until i put in production. But, i dont want to put it production until i find a majority of the bugs. That is why most firms wait to roll out the new release AFTER the first service pack issued.
I think we need to understand that even a product as evolved a car will have recall notices. When new houses are sold, there are various steps the builder goes through over the course of a year or years AFTER it's sold to make sure the house is in working order. For me, Civil 3D falls somewhere between the simplicity of a stick built house and a complex automobile. Should my expectations for civil 3d exceed those for a house or car? By the way, both of those are more expensive than civil 3d.
I am sure we can continue this conversation without hijacking the thread.... 🙂
Kevin
You're probably right, but why does it matter. Being civil, using torches, using pitchforks, following help ticket protocol...seems none of it works to get resolution and a stable working new release. Trust me, I've been a user and supporter of civil 3d since it came out in 2005-2006. I've sold it to hundreds of users without getting a dime from Autodesk. We just want things that once worked to continue working in new relesases. I spend an enormous amount of time diagnosing problems every release.
point cloud issue case in point (page 2 at end has my reply saying finally fixed) http://forums.autodesk.com/t5/AutoCAD-Civil-3D-General/2011-vs-2013-point-cloud-colors/td-p/3682862 (I never received notice from autodesk on this. I found it myself.)
Here's another gripe that I'm sure is shared. It was from 2010. http://forums.autodesk.com/t5/AutoCAD-Civil-3D-General/question-for-autodesk/td-p/2724605
Why does it matter? Whether justified or not... At some point, all we hear is the boy crying wolf right?
@Kevin.Spear wrote:Why does it matter? Whether justified or not... At some point, all we hear is the boy crying wolf right?
Crying wolf would assume that the complaints aren't valid. These are production and core software issues that came out with a new release. Some were previous problems that still haven't been addressed. We never deployed 2013 because of all the problems that version had and 2015 is much worse. 2014 SP1 broke some of the features that were fine and fixed others, which makes it a wash.
There is a serious problem at Autodesk with regards to how C3D is being developed. It's not that we hate or dislike C3D, quite the opposite. We want it working the way it's marketed and supposed to work.
You obviously didn't read the link to the Point Cloud thread. I had Autodesk on the phone several times, conversed with them over email and discussion group with no luck. Another user (expert elite) had to break it down further for him. I found that it was fixed with service pack 2 or 2.1....follow what I'm saying? Autodesk, Resellers, Gunners etc... don't really test thoroughly or maybe they just don't have enough time because the need to push it out which was the point with my second link.
You as a reseller never have to deal with real world design scenarios, budgets and timelines. I've taken the 3 day essentials class from multiple resellers. It's always 'enlightening' to see them slinging simple datasets around from a marketing standpoint to make a sale. I've thrown some a curve ball by giving them a base map and asking them what their approach would be for a specific design scenario using corridors and other features, something other than a simple square pad with 2:1 slopes.
Dave,
This message received this morning is a good example of the confusion I continue to sense with quality control and product Support.
Extremely frustrating.
..I understood you post as a message to the forum users and not as general support request or status request on the issue.
Therefore I have archived the case in our support system again...
Completely false. I submitted a Support Case first, then posted that this is a Confirmed Defect in the forum.
...The severity gives the product specialist a guideline how quick an answer is needed...
Who is making these judgements and determinations to send certain issues to the backburner? ....First tier Support staff?
The issue of addressing the lost functionality of being able to create Medians that cross centerline for creating Left Turn lanes, should be amongst the highest priority for restoring design capability for our municipal corridor projects!
Sounds like you were taken back also by the Closed case status, I hope you can get this communication debacle with Support, and the front-end quality control issues figured out soon.
This is especially concerning when our Subscription license agreement states that we have only 120 days of grace before we have to remove and destroy all previous software versions. Hence, you can understand our sense of urgency on addressing these defect issues for our economic vitality.
Section 2.4 of the subscription T&C covers allowed use of previous versions, currently including back to v2012 for C3D and/or IDSP.
What am I missing?
Yes you're right. It's people upgrading without subscription that have to destroy within 120 days.
I don't even have 2012 loaded and know if Medians were working in that version? I know it doesn't work as far back as version 2013.
Nonetheless, it is very sad commentary on this product if we have to go back three years and thousands of dollars to a non-compatible version of the software to recapture our design functionality.
Dave,
Never mind. I'm an idiot!
Allen
Allen Jessup
CAD Manager - Designer
Did you find this post helpful? Feel free to Like this post.
Did your question get successfully answered? Then click on the ACCEPT SOLUTION button.
@rkmcswain wrote:
...This is especially concerning when our Subscription license agreement states that we have only 120 days of grace before we have to remove and destroy all previous software versions.Section 2.4 of the subscription T&C covers allowed use of previous versions, currently including back to v2012 for C3D and/or IDSP.
What am I missing?
Well. That will never happen again. You can no longer upgrade if you're not on Subscription. You have to buy new.
Actually on Subscription, you can run any version you've ever owned. Limited to a maximum of the number of licenses you have now or had then. Whichever is smaller. It's just that for anything more than 3 releases back it takes a special request. I just got a license for 2009.
Allen
Allen Jessup
CAD Manager - Designer
Did you find this post helpful? Feel free to Like this post.
Did your question get successfully answered? Then click on the ACCEPT SOLUTION button.
20. Confirmed Defect - Superimposed profiles and multiple profiles in same profile view cause 2015 to crash.
21. Confirmed Defect - Alignment with a profile cannot be grip-edited without crashing. Related to #20.
22. Confirmed Defect - DaylightBasin2: The ditch foreslope does not project to the Elevation Target, as is the case in 2014 (fcernst)
Can't find what you're looking for? Ask the community or share your knowledge.