Showing posts with label Bugs. Show all posts
Showing posts with label Bugs. Show all posts

Wednesday, 27 March 2019

Civil 3D workaround : Corridor Surface Boundary "Add automatically" option not showing although it should

So you have a corridor made of sub assemblies that should expose one or more codes for adding boundaries automatically but this option is not offered although it should.

Watch for locked layers. Assemblies, alignments, profiles, targets, superelevation views, surfaces whatever may be related to the corridor and its surface.

If all unlocked then check this.
Set boundary to Corridor extends.
Rebuild corridor and watch the Event viewer.
If there is a warning that "could not apply mask (0) to corridor due to crossing polygon" then try this.

Set Corridor frequencies to another much larger value.
Apply.
Now the option for Adding automatically should be available.
Select the desired code.
Apply and rebuild.
Reenter corridor properties and change frequencies back to the previous values. Apply and rebuild.

Add automatically is still available and everything is working fine.

Yet another workaround.
Autodesk is unintentionally training our brains to prevent failure due to aging. Or maybe our brains are about to get burned because of all this over the years searching for workarounds, tricks and things like these trying to make their software to work as expected.
We should also not neglect all those extreme feelings of frustration, surprise, anxiety, desperation and finally...triumph that comes with situations like these.

Thursday, 8 February 2018

AutoCAD/DWG TrueView export DWG, experience, tips, tricks and workarounds

In case of mass export a set of files there are many ways to do it.

1.File/Export
2.File/e-transmit
3.SheetSet manager/e-transmit/archive
4.DWG TrueView

Mass export : 2,3,4
Start on view that DWG was saved last : 1,2,4 (3 always fails. Always starts at Model Space)
Keep XRef insertion point at correct position when insertion is at PaperSpace : 1,4 (2,3 may fail!!!)
Auto find and export all non XRef files DWG is depended from (eg ctb,shx etc) : 1,2,3
Quaranteed export to selected version : NONE
Quaranteed export with AEC objects exploded : NONE

Tip : Before exporting through case 1 to 3 preview Export Report. If it is to fail exporting to selected version it will be mentioned.

Unfortunately, i found no workaround to always create safely an export to the selected version/AEC exploded. I can not understand why autodesk does not fix this problem. It exists through all previous releases.

Friday, 30 June 2017

Generating vb.net classes using XSD schemas !!! A miracle ? No ! Just a bummer !

Two freeware solutions for producing Classes from XSD !!!

Microsoft's XSD.exe
Capable of using multiple schemas at one pass but too many errors and arrays instead of lists !!!

My path for the xsd.exe...
C:\Program Files (x86)\Microsoft SDKs\Windows\v10.0A\bin\NETFX 4.6 Tools\xsd.exe

In case a schema refers to another eg "HeXML-1_5.xsd" refers to "LandXML-1_2.xsd" the syntax should be as following...

xsd.exe LandXML-1_2.xsd HeXML-1_5.xsd /classes /language:vb

https://stackoverflow.com/questions/35285713/vb-net-create-class-from-xsd-and-generate-xml

https://bembengarifin.wordpress.com/2009/07/14/generate-net-class-from-xsd-with-references-to-other-xsd-using-xsd-exe/


XSD2CODE.exe
Not capable of handling multiple schemas at one pass.
Found at https://xsd2code.codeplex.com/

https://stackoverflow.com/questions/9386754/using-xsd2code-with-multiple-schema-files


Finally there is also another guy that ran into the same problems.
https://stackoverflow.com/questions/35658403/error-deserializing-xml-in-c-sharp

Endless corrections leading to...bummer. Hours lost for nothing. Crapware.

Just, do not bother loosing time with them.



Wish i had time to make my own conversion software.

Friday, 2 June 2017

Leica Infrastructure Link - Civil 3D corridor export : failure - Autocad JIT error message "Enumeration has either not started or has already finished"

Searching for a workaround for the previous post i tried exporting the corridor with all baselines checked.
And i got the following message.


More serious bug reports to come...

Leica Infrastructure Link - Civil 3D corridor export : bug - Layer centerline set to wrong baseline alignment

I had a corridor with multiple baselines attached to multiple alignments.
I unchecked all of them except one of them which it was the only one i wanted to export.
I used Leica Infrastructure Link to export it.
Finally i used the MS XML editor to view the exported HeXML file.

The alignment of the checked baseline was not exported.
Instead of it, the alignment of the first (and unchecked) baseline was exported !
The correct feature lines were exported.
Finally the wrong exported alignment was attached to the layer as a centerline.



 

Leica Infrastructure Link - Civil 3D export corridor : failure - Autocad JIT error message "This operation on featureline-based baseline is invalid"

One of the top rated in the wish list about Civil 3D was the option to create a corridor using feature line baseline type. Civil 3D 2017 was the first version to support it.

Leica X-Change no longer exists since this C3D version.
Its successor Leica Infrastructure Link freeware must be used instead.

Running this addon pressing the "Read Civil Objects" button user sees the following message.
The program stucks at this point.



OR

After reading civil objects when trying to save "Export HeXML" user sees the following message

Well at least it is multithreaded. So in either cases user can press Continue and then the OK button and end this addon. But no export takes place.
Same thing happens even if baselines feature line based are unchecked when rebuilding the corridor.
Only solution is to revert to the previous baseline type method of alignment/profile.


Well. It is obvious that Leica developers did not examine the changes between v2016 and v2107.
In v2017 baselines types can differ. Developer should examine if it is "IsFeaturelineBased" or else the above exception is thrown. At least there should exist a user notification.

Leica developers should have seen this link
https://knowledge.autodesk.com/support/autocad-civil-3d/learn-explore/caas/CloudHelp/cloudhelp/2017/ENU/Civil3D-DevGuide/files/GUID-6D41D043-4958-40B7-9C7E-45A6D780955B-htm.html