I have had a support request going for this for a while, but it seems like the installation of C3D 2014 from IDSP causes this issue. There is something about the installer that causes this to happen, but not on an install from the stand-alone installation for C3D.
I've now spent 3.5 hours today trying to narrow this down. Turns out if you do a Workspace>Save Current As..>(insert any name), close C3D, then reopen it, do another Workspace>Save Current As..>(same name as before) and replace it the profile view lineweights stop working. This did not affect any installs from the stand-alone C3D installer, only the IDSP installs.
Finally think we figured it out. When saving a workspace in an installation of C3D 2014 from IDSP, if the Navigation Toolbar (below the ViewCube) is turned off when the workspace is saved, it corrupts the workspace. This is a confirmed defect that has been sent to development. When I thought it was DynamicInput it was because I saved the workspace after turning it and the navigation toolbar off.
There is apparently another known issue with the Navigation Toolbar that will show it on a printout. Support has linked this case to that one. There is definately something wrong with the Navigation Toolbar.
A temporary workaround is to either leave the Navigation Toolbar on or when you open a drawing make sure you're in a workspace with the Navigation Toolbar turned on at first. You can change workspaces and keep working without the profile view lineweights messing up, but if you close a drawing and have a workspace with the toolbar on, the next drawing you open will not have the profile view lineweights work correctly.
had this bug for a long time, just realized it after my major & minor grids were the same lineweight and you couldn't tell which grid was the major. turning the nav bar on fixed it, if you find it annoying just turn off all the buttons and it really doesn't get in the way...
The sad part is Service Pack 1 didn't fix it and there's not been a hot fix for it. We're only a month away from 2015 and I doubt this will ever be fixed for 2014.
Log into access your profile, ask and answer questions, share ideas and more. Haven't signed up yet? Register