And that would be a BIG negatory on the solution front.
When a Client asks for data in a specific format it is entirely the responsibility of you to have the capacity to comply with that request. "Having difficulty with", "how about maybe we could" or "is there any chance we might be able to" is simply circumventing the short comings of a process that should be addressed, vis-a-vis your software probably needs to be looked at.
LandXML is merely a work around, not the answer, for the transfer of surface or design models as it does not account for edits you make to the surface. Maybe I'm wrong but you should try exporting a surface that you've edited and look at the debris that comes with it.
Additionally, the problem with points has not been addressed, whereby 3 alpha characters are needed for export, not 2.
As you are using the GENIO extension I'm assuming you are on subscription - have you logged a support request??
I wouldn't hold out much (any?) hope of getting a quick fix if the export routine can't already achieve what you want as I guess the GENIO export/import won't be at the top of anyone's to-do list at AutoDesk.
PS perhaps you should be using Bentley MX if your client base requires deliverables in GENIO??
And therein lies the problem. Half ersed attemps at developing the software we need for a commercial reality we deal with. To be honest I'm surprised this thread was re-animated, however it does go to show that the promise of 2006/2007 when I first got involved here, under a different user name, has never really materialised. I recall too many people tapping away lines like "it's early days, give it a couple of years she'll be a racehorse" etc, etc. For every problem fixed another pops up, just wait until C3D 2016 come out next week, or is that next month, can't remember, some of us lose track after a while.
Sadly, just last week, the edit points panorama crashed, again. Try a search for that one.
Computer more than sufficient
to keep you alive let alone run
a busted a$$ piece of software.
End of rant.
I agree - they should end the annual software breaking release cycle and fix what already exists. My personal favourite is when they broke the DRIVE command in 2012SP1 and it took 6 months to fix it for 2013 - not sure if it was ever fixed in 2012.
To my mind they seem to concentrate too much on the fancy reality stuff (Infrastructure Modeller anyone...!!!) instead of on the tools that actually get the job done
My personal favorite is this one;
Not because it's a thread I started, but because of the reactions, and the breathtaking implications of the programming error. Ask anyone involved with OHSE and they'll tell you that a consistent string of small accidents invariably ends up with a fatality.
P.S. Is there any reason that I can't reply to anyone other than myself when using the reply button. (In answer to your question, yes I'm sure, I've checked.)
Log into access your profile, ask and answer questions, share ideas and more. Haven't signed up yet? Register
Start with some of our most frequented solutions to get help installing your software.