Correction: Autodesk is going to update Acad 2002

Status
Not open for further replies.

O.H.Ystanes

Usenet Archive
Joined
Jan 19, 2001
Messages
33
Reaction score
0
Sorry but I wrote for some time that Autodesk was not going to update their .DWG format in Autocad any more.

In an well informed E-zine called Upfront Autodesk claims to be develope their own version of ACIS (3D solid modeling core) and update both Inventor and Autocad. It will take about two years before Autocad is updated if I understood it correctly. Such that it may be an Acad 2004 ... perhaps!

BTW: Inventor was going to be updated FIRST!

Hallstein
 
Quote from Ralph's http://www.upfrontezine.com. This is a must newsletter for all CAD users.

upFront.eZine: Is the ShapeManager product finished? Can you explain to me how ShapeManager is being developed?
Mr Kross: We had already been modifying the source code of ACIS. ACIS v7 is the core for ShapeManager. The first release is with the next Inventor early next year, with AutoCAD to follow later in the year. We plan to add enhanced blending and shelling, along with assembly in the kernel. The year 2002 is long way short of 2004! BTW would this by any chance mean that V8 would have to be updated to comply with the new AutoCAD file format. Do I see a follow the leader scenario forming?
 
This still won't likely count as a change in the DWG format. I think there is a basic misunderstanding of what is meant by the file format not changing. The DWG format does not specify exactly what bits and in what order can make up a valid DWG file. Rather, much of the DWG specification defines a type of metadata or container structure. How those containers are constructed may not change, but what goes in them almost certainly will. So, the claim that the DWG file format won't change should be read analogously to the correct claims that the NTFS file system doesn't change even if you store some new kind of data in it, or that a set of kitchen canisters isn't modified if you decide to store a different kind of tea in one of them.

Similarly, Bentley's claim that MicroStation can now natively use the DWG file format should not be read as meaning that they can make complete use of what is stored in all of the containers within a DWG file. For things like solid modeling data, Architectural Desktop objects, and other things that Autodesk (or a third party) adds or wants to hide in these containers, MicroStation may well be limited to using the proxy graphics that should be stored along with the real data (though not the code needed to make use of that data) within the DWG containers. In otherwords, the MicroStation (or vanilla AutoCAD) user would be confronted with static pictures of many of the objects in the DWG file, and would not be able to manipulate and modify those objects in the way that a Mechanical Desktop or Architectural Desktop user could.

In that sense, you are correct, Sam, that the game of follow the leader is all set up for someone who wants to make complete use (via reverse engineering) of the information in current and future DWG files.

Mark
 
Sorry but for us the users, any change that will make the native .DWG format problematic to import in e.g. uStn will be considered as a format change even if it strictly technical isn't.

Mechanical Desktop 5 (which I use for the moment) it is possible to explode parts such they become true ACIS .DWG solids ...

Hallstein

On Sat, 08 Dec 2001 12:15:38 -0800, "Mark Hamstra"
wrote:

This still won't likely count as a change in the DWG format. I think there is a basic misunderstanding of what is meant by the file format not
 
"O.H.Ystanes" wrote:
Sorry but for us the users, any change that will make the native .DWG format problematic to import in e.g. uStn will be considered as a format change even if it strictly technical isn't.

Right. There is no question that changes or additions to the embedded magic nuggets allowable in the DWG file format will affect the users. That's why I thought it was important to clarify that "the DWG format won't change" doesn't really mean what you seemed to think it did.

Mechanical Desktop 5 (which I use for the moment) it is possible to explode parts such they become true ACIS .DWG solids ...

There are (and probably will continue to be) means to "explode", dumb down and make available the various extended application types (e.g., Mechanical Desktop objects, Architectural Desktop objects, etc.) Of course, in doing so they cease to be "intelligent objects," and are more or less old-style DWG elements like lines and arcs. The various OpenDWG-based applications (e.g., IntelliCAD and MicroStation V8) shouldn't have any difficulty with those old-style elements, but editing them will make bringing them back into an application like Mechanical Desktop as anything but dumb, old-style elements problematical if not outright impossible.

It will therefore be interesting to see to what extent users will accept and embrace these extended application objects, to what extent the reverse engineers will attempt to decode and make use of those objects, or whether the users will simply refuse the complications of these types and by their interchanging only vanilla DWG files effectively force DWG to remain a simpler data format and impede the acceptance and use of products like Architectural Desktop.

Mark
 
As I can see from the current NG, bentley.microstation it is absolutely crammed full of messages about items not translating properly from AutoCAD to MicroStation. Is this really what Bentley wants on their NG day in and day out. Isn't here some point when they must say enough, we cannot continue with these problems and concentrate on improving the GUI of MicroStation instead of the problems of translation. Or will they continue with this for ever. I know for sure there are some users not using AutoCAD who are really pissed off with this already and unhappy with the direction Bentley and MicroStation are heading. And as discussed one or two changes to the DWG file format and the whole process starts again. Do they understand that they may be creating a monster out of a so called MicroStation upgrade. On a different track when I bring in a solid model using Parasolid or Step I want to see feature recognition so that the part can be edited and not simply a dumb object.
 
Hi Mark,

One overlooked possibility:

It would be *really* interesting to see if it is possible to implement the run-time environment, say in uStn, so the Object Enablers (or whatever the name for those plugins is) would be fouled to think that they are running in AutoCAD.

This is probably the only way...

Cheers,
/Chris Z.

"Mark Hamstra" wrote:
In article , "O.H.Ystanes"
wrote:

> Sorry but for us the users, any change that will make the native .DWG
> format problematic to import in e.g. uStn will be considered as a
> format change even if it strictly technical isn't.

Right. There is no question that changes or additions to the embedded magic nuggets allowable in the DWG file format will affect the users. That's why I thought it was important to clarify that "the DWG format won't change" doesn't really mean what you seemed to think it did.

...
 
Exchanging drawings is really an artificial intelligence deal, because you have to translate the implied engineering data model (including, e.g. linked database records). So ideally you translate the explicit model and generate drawings in place. The problem is, there's no way to meaningfully exchange explicit engineering data models in a/e/c. There was (quite usable) STEP subset, AP225; then came IAI saying "we'll do the same in 2 years"; then came aecXML saying "we'll really do it in 2 years"... etc. It looks like IAI is finally coming up with something quasi-usable, though.

Cheers,

NS

(just my private opinion in no way representing that of my employer, past, current or future...)

"SamuelG" wrote:

As I can see from the current NG, bentley.microstation it is absolutely
crammed full of
messages about items not translating properly from AutoCAD to
MicroStation. Is this really
what Bentley wants on their NG day in and day out. Isn't here some point
when they must
say enough, we cannot continue with these problems and concentrate on
improving the GUI of
MicroStation instead of the problems of translation. Or will they continue
with this for
ever. I know for sure there are some users not using AutoCAD who are
really pissed off
with this already and unhappy with the direction Bentley and MicroStation
are heading.
And as discussed one or two changes to the DWG file format and the whole
process starts
again. Do they understand that they may be creating a monster out of a so
called
MicroStation upgrade.
On a different track when I bring in a solid model using Parasolid or Step
I want to see
feature recognition so that the part can be edited and not simply a dumb
object.
--
Sam

"Mark Hamstra" wrote:

> In article , "O.H.Ystanes"
> wrote:
>
> > Sorry but for us the users, any change that will make the native .DWG
> > format problematic to import in e.g. uStn will be considered as a
> > format change even if it strictly technical isn't.
>
...
 
<61aR7.797$>, "Chris Zakrewsky" wrote:
Hi Mark,

One overlooked possibility:

Not overlooked, just not explicitly detailed. What you mention is essentially what I was thinking by "reverse engineering."

It would be *really* interesting to see if it is possible to implement the run-time environment, say in uStn, so the Object Enablers (or whatever the name for those plugins is) would be fouled to think that they are running in AutoCAD.

This is probably the only way...

I'll agree that this is most likely way of gaining full access to object data embedded in DWG files; however, several significant issues remain.
Among them: What are the dependencies of various Object Enablers on proprietary and unavailable Autodesk code? Has Autodesk made a sufficient amount of the required runtime available independent of AutoCAD to third parties to make the creation of such an Object Enabler Run-time in MicroStation (or any other application) a tractable engineering task, or would such an effort require a very difficult reverse engineering of the binary interface to much of the AutoCAD runtime environment that is assumed by the Object Enablers? How wise of an idea is it to make archived design data dependent upon the Win32/Intel platform and further upon Autodesk dependencies?

Granted, there has always been a certain amount of dependence on vendor proprietary software even in older, dumber CAD files, but the increased vendor and platform dependence that is going along with more embedded model intelligence should give CAD users great concern. Interchange standards like STEP that seek to retain a model's intelligence independent of a single vendor, and openly available reference software implementations should be receiving a great deal more attention by CAD users than they are at present.

Mark
 
In the words of the late great Alex Januszkiewicz, God rest his soul:

"Even if V8 reads and writes properly DWG (my standalone programs do it too), it's a long way from here to being able to bring to life the growing population of intelligent objects that are the true power of today's AutoCAD. The DWG format is not going to change much in the future. The new objects will be added to it through extensible definition of custom classes, that can be interpreted properly only in the presence of the ARX application that created them. Now, the companies that produce new objects are writing freely distributable object "enablers" - ARX programs stripped of all functionality other then interpretation of the objects (for those who don't need to buy full blown application). "Unless Bentley makes one more (giant, and I think rather impossible) step and makes ObjectARX programs to run inside Microstation (this would actually turn Microstation into AutoCAD ;), the growing number of DWG objects will be represented inside of Microstation as proxies (dependent on application that created them, with no graphics, with some graphics or with totally nonsense graphics). "To have smooth translation (assuming V8 works as promised), somebody will have to stick to lines, circles, 3D solids and other basic objects common to all cadd systems, and stay away from anything that unleashes the real power of today's AutoCAD: ARX applications with their custom objects."

Alex was a valuble resource in this industry as well as an excellent ranter on this NG and CCA. He passed away suddenly a few weeks ago and will be sorely missed. But aren't his words here quite true? For all the reverse engineering Bentley can do, will V8 forever support nothing more than 2D and simple 3D ACAD elements?

DougW
 
"DougW" wrote:
In the words of the late great Alex Januszkiewicz, God rest his soul:

[snip of a pretty good restating of much of what we have been discussing]

"To have smooth translation (assuming V8 works as promised), somebody will have to stick to lines, circles, 3D solids and other basic objects common to all cadd systems, and stay away from anything that unleashes the real power of today's AutoCAD: ARX applications with their custom objects."

Alex was a valuble resource in this industry as well as an excellent ranter on this NG and CCA. He passed away suddenly a few weeks ago and will be sorely missed. But aren't his words here quite true?

For the most part, yes; but I will take issue with one part: the real power of today's AutoCAD is its ubiquity. There is nothing exceptional in ARX applications, or "custom objects." What is exceptional about the base product is the number of people using it. The vast majority of AutoCAD users don't use much if anything more than the basic, common CAD elements, and most don't use anything but 2D.

While the real potential power of AutoCAD-based ARX applications lies in objects embedded within DWG files (or some other datastore -- DWG in and of itself isn't that important technically), this is only inert potential until end users actually deploy and make use of them.

Effectively, Autodesk is trying to coax basic, common DWG users into using other proprietary products whose data is normally embedded in a mostly inaccessible way within DWG files. By blurring the distinction between traditional DWG, DWG as used, and DWG with embedded objects, Autodesk seeks to transition much of their userbase over to using these new proprietary products without those users too critically examining the merits of this transition or of alternative strategies and products.

How effective Autodesk is, or will be, in persuading users into this transition is, therefore, the first question to ask when thinking about whether non-Autodesk products can make effective use of DWG files. At least for now it mostly doesn't matter that V8 or similar products can't make full use of embedded DWG object data: AutoCAD users mostly don't use such objects either.

Mark
 
Mark,

You've hit every nail on it's head. IMO, you should have cross-posted this to the acad groups. I think you would find a lot of agreement in those groups with your opinions. And.... smoke out a few clueless people -- always interesting reading. :-)

WF

On Tue, 11 Dec 2001 12:18:38 -0800, "Mark Hamstra"

In article , "DougW"
wrote:

> In the words of the late great Alex Januszkiewicz, God rest his soul:

[snip of a pretty good restating of much of what we have been discussing]

> "To have smooth translation (assuming V8 works as promised), somebody
> will
> have to stick to lines, circles, 3D solids and other basic objects
> common to
> all cadd systems, and stay away from anything that unleashes the real ...
 
On Mon, 10 Dec 2001 10:21:02 -0800, "Mark Hamstra"
wrote:

There are (and probably will continue to be) means to "explode", dumb down and make available the various extended application types (e.g., . shouldn't have any difficulty with those old-style elements, but editing them will make bringing them back into an application like Mechanical Desktop as anything but dumb, old-style elements problematical if not outright impossible.

In Acad 2000 and above it is possible to edit solids "exploded" from e.g. Mechanical Desktop. The command is SOLIDEDIT. It is not easy to operate or understand but it works some how.

Just for information...

Hallstein
 
Status
Not open for further replies.

Latest threads

Back
Top