SUPro 7.1 cannot export to dwg

tim

Have you purged the model?

Have you tried copying the content into another model?

Yes and yes. And I tried deleting any textures and then purging, just in case it was something to do with large texture bitmaps. No luck.

boofredlay

Tim, I had no problem exporting your model, that is the basement plan and the main floor plan. I did not try any other views. I am running 7.1.481, not the newest release I know. I just have not gotten around to upgrading. Maybe this is a glitch in the newest release.

Gaieus

Hi Tim,

I have also tried (the very first scene) as dwg and went without any glitch. I do have the latest version (BTW Eric - do you use your phone number as your SU version? )

boofredlay

@gaieus said:

(BTW Eric - do you use your phone number as your SU version? )

Watch this Gai...
http://www.youtube.com/watch?v=axLRUszuu9I&feature=related
and the original..
http://www.youtube.com/watch?v=tBHJqtgo8RA&feature=related

Sorry for being Off Topic Tim.

tim

Thanks for testing it guys. The really annoying thing is that many other models export perfectly well, including a 3 month old version of the house. So somewhere in there is a change that has triggered a bug in the exporter code. Sigh. It exports to collada ok, to Layout.... bummer.

Anssi

The 2D views exported OK, but exporting the 3D model led to bugsplat. Same result when renaming the file with a short name without spaces (non-ascii characters caused trouble in a previous release).

Has anyone else tried to export the model?

Anssi

honoluludesktop

I used some of my own code to export Tim's components to dxf, but my application's getdxf failed to convert it. Haven't had problems with my own models, (yet

charly2008

I tried it too and got also a Bugsplat.

Then i took a copy of the Footings plan and pasted it into a second Sketchup instance and here the export worked fine both for DWG and DXF. I suspect that the problem is connected with the other scenes.

I made the same test too with the Elevation Scene and here i got the Bugsplat. This confirms my suspicion that the problem is caused by some scenes.

Another test with the export of the Floor framing scene for example worked also fine. A further test with
the Basement details scene was also Ok.

Karlheinz

Ashling Rd Main 12 NovXX.skp

DWG-DXF.zip

tim

Hmm, interesting results folks. Of course the irony is that the 'elevations' scene is really the one most needed since it is the entire model of the house!

I wonder what has changed in the last three months that could be causing such a problem. Not that there is any meaningful way to automatically compare two versions of a model.... most of the recent changes that I recall were minor alterations in the details of dimensions (changing size of ICF blocks, moving the odd rafter, stuff like that) rather than major additions.

tim

Progress report for anyone interested - it's the roof component. With that layer removed and the model purged, I can export to dwg. Delete every other layer, purge, save to a new file and try to export - boom!!!

So I wonder what is wrong with the roof that upsets export but not LO or any of the other tools I normally use? More on this channel as the news breaks, later.

tim

Well, well.

One of the components had managed to get a definition (the component name) of '' ie blank. This makes sense of the crashlog appearing to have a problem in some code relating to adding a symbol.

So the immediate solution is to provide a proper name for the component, which is easy enough. But the more serious problem is that the exporter shouldn't crash that badly, the integrity checker that checks the model ought to have picked it up sooner and warned me and perhaps even more importantly there should be no way you can delete the name of a component. You can't have duplicate names and you should be able to enter any other sort of invalid name.

I've noticed that the keyboard focus occasionally seems to move to the component name field of the entity window or the outliner window and then using a hotkey (like 'm' for example) results in you having a component called m. Easy to miss when working away. Shouldn't happen.

If Barry or any other googleSU person is reading and interested I can supply models with and without the error.

bjanzen

Sure. Send it and we'll see the extent of this and file a bug. Thanks.

b

lusodxb

Hi im new to this forum and am having problem exporting my model form skp 8 pro to dwg! can anyone help?
Thanks

thomthom

@lusodxb said:

Hi im new to this forum and am having problem exporting my model form skp 8 pro to dwg! can anyone help?
Thanks

If you describe the problem we might.