#ACAD13 to 3DS4
11 messages in this thread
I'm having big troubles with exporting to 3DS4 from ACAD13
I did some test 3 weeks ago by reading in small files from 3DS in ACAD like
x29.3ds no problem edited in ACAD and saved to 3DS again with no problem.
Even some simple ACIS entities exported flawlessly.
So I started a 3D of a building 3days ago.
Mainly using Regions, no exporting locks up, and doing DXF, via ACAD13 or 12
looses all regions created in ACAD.
Anyone has suggestions. I'm working against a next week deadline for this
model.
Christophe Van Oyen
Sorry for double mailing but I think I mailed the first one in the wrong
section
Hi,
>>Mainly using Regions, no exporting locks up, and doing DXF, via ACAD13 or 12
looses all regions created in ACAD.<<
I exported a bunch of regions from r13Win yesterday via 3DSOUT. Worked OK. I
don't think it will work anymore using DXF. Is 3DSOUT not working for regions?
3DSOUT is _far_ from correct at this point but I think it is generally useable.
I always save before I run it and never save after I run it …
Mark
(BTW, have you seen the patch for 3ds to read in ASCII r13 DXF files?).
<<I'm having big troubles with exporting to 3DS4 from ACAD13>>
Christophe,
Are you using 3DS R4c1? Or have you downloaded the patch DXFPCH.ZIP from this
forum? If you haven't done one or the other, your problems are to be expected.
Download the patch or get the C1 version, if you haven't already.
-Brian
I haven't got the C1 Patch yet, however problem seems to be with ACAD.
I can export 3DS files from ACAD with regions and with ACIS entities without a
problem. But as soon as I do it with files that where originally started with
R12 and converted to R13 it seems ACAD 13 crashes during the process of writing
a 3DS file. DXF is no good to get ACIS + REGIONS out of ACAD.
BTW I did the DXFPATCH on R4, also have ACAD 13c1
Just not 3DS4.
Crashes do occur in ACAD, any tips on this???
I get the following in ACAD13 WIN
3DS file starts making:
then:
Unifying Normals
Assigning Smoothing
And Nothing happens anymore, mouse is still usable
Then I do CTRL .ALT DEL
And get following message:
No Free File Handles
Cannot Load Command, System Halted
Then I crash to DOS.
I tried on A tip to increase Files= to 100 in CONFIG.SYS
It only worsened that the mouse was also gone?????
It Is a big problem, and BTW I'm very displeased with ACAD R13 Performance at
this time.
I used it for 3 weeks, and changed back to R12, WOW and what a difference in
performance.
Christophe
So it sounds like your problem is in exporting R13 ACIS entities. You are
correct in that the only method for getting these into 3DS is via R13's 3DSOUT
command. The important thing to realize is that ACIS entities are meshed "on
the fly" by the Renderer and 3DSOUT. This intermediate mesh creation can
overload your system if it's too big. R13's FACETRES variable governs the
density of the ACIS mesh conversion. It's range is 0.01 to 10.0 and is somewhat
view dependent (coming from the Renderer).
As a test, try lowering your FACETRES to 0.01 (which should give you one
segment per 90 degrees) and try exporting If this works, try increasing the
value and continue to export. At the very least you will understand the
influence of this variable <g>. At the best, you'll solve your export problems.
Either way, I would be intereIsted
To aid in this you might try the following LISP routine to automate the
FACETRES assignment when you do a 3DSOUT:
(defun c:3dso (/ orig new ask)
(setq orig (getvar "FACETRES")
ask (strcat "\nNew FacetRes Value <" (rtos orig 2 2) ">: "))
(while (/= orig "end")
(setq new (getreal ask))
(if (not new) (setq new orig))
(if (or(> new 10.0)(< new 0.01))
(prompt "\nFacetRes range is 0.01 – 10.0")
(setq orig "end")))
(setvar "FACETRES" new)
(princ"\nBegining 3DSOUT") (c:3DSOUT)
(prin1)
)
You are now prompted for the FACETRES setting at the time of export.
I'll give the setting a try.
Christophe
This setting is not causing the problem.
However I will upload all my setting files, anyone that looks at them and has a
clue, please let me know???
My Windows ini files might need some cleaning?????
Christophe
How much virtual memory do you have set asside for Windows?
How large (MB) is the file in question?
You got the same error when usind DXFOUT with a FACETRES setting of 0.01?
Have you tried the same operation in R13 DOS?
The reason I'm asking is that it's quite possible you're simply running out of
memory. When meshed, the ACIS files can become HUGE. I've seen a 200k DWG turn
into a 30Mb DXF file with high FACETRES setttings.
– Phil
>>How much virtual memory do you have set asside for Windows?
32MB RAM + 45MB Windows Swapfile
>>How large (MB) is the file in question?
36.000k (very small), larger drawing gives same problem, however new drawing of
106.000k works just fine and exports perfectly?????
>>You got the same error when usind DXFOUT with a FACETRES setting of 0.01?
Exactly the same error, so it seems not to be related to the FACETRES setting
at least for what windows is concerned.
>>Have you tried the same operation in R13 DOS?
I did that yesterday, after installing 13 for DOS, and here the file exports
perfectly, however the 106.000 file crashes (gave it only one try, probably
because I have only 39MB free on th swapdrive, Windows Swapfile is on another
drive 2.1GB).Problem is I can not free any diskspace at this time to do further
test, due to lack of backup system at this time, my MO died on me 14 days ago.
Seems to point to a Windows specific problem, Win specific drivers etc…
I'm really puzzled by this one, and I'm starting to hate Windows (speed,
conflicts, etc…) , I'm going to go for NT as soon as I can, means as soon as
Acad13 NT is available.
Christophe
>>I'm really puzzled by this one, and I'm starting to hate Windows (speed,
conflicts, etc…) , I'm going to go for NT as soon as I can, means as soon as
Acad13 NT is available.
I'm puzzled as well – please voice this one on the ACAD forum. We really can
only help you from the 3DS side on ASOFT.
But some good news for you – your current version of R13 will run very well
under NT. On my system it loads at least twice as fast and hums along fine
there after. You might consider loading NT with a dual-DOS boot and giving it a
try. You don't even have to reinstall R13 – just make it a new program item and
it'll work fine.
– Phil
Yes I have already tried acad forum and they are also puzzled. So am I.
BTW Normally I will not be able to run under NT, I'm in the hardware locked
world so I will have to wait for NT version of acad, planned somewhere in
April.
BTW thanks for your help so far, I think he only way to find out what it is is
going to be to reinstall Windows completly on my PC, a hughe task, couple of
days work
Christophe