Wed, Jan 8, 8:01 AM CST

Renderosity Forums / Bryce



Welcome to the Bryce Forum

Forum Moderators: TheBryster

Bryce F.A.Q (Last Updated: 2025 Jan 04 3:16 am)

[Gallery]     [Tutorials]


THE PLACE FOR ALL THINGS BRYCE - GOT A PROBLEM? YOU'VE COME TO THE RIGHT PLACE


Subject: Auto CAD Imports


spikey1000 ( ) posted Sun, 01 September 2002 at 1:29 AM · edited Wed, 08 January 2025 at 7:48 AM

I know that this question has been asked but how do import auto cad objects into Bryce?


FWTempest ( ) posted Sun, 01 September 2002 at 1:44 AM

uummm... File menu > import ??? Bryce won't recognize MAX files, and frankly I can't import a DXF file of any size without crashing Bryce, so stay away from those formats.


FWTempest ( ) posted Sun, 01 September 2002 at 1:45 AM

figured I'd try to give some kind of answer before someone said 'RTFM', although that would be good advice.


Erlik ( ) posted Sun, 01 September 2002 at 3:26 AM

I, for instance, don't have any problems with importing DXFs. OTOH, what AutoCAD format? There are several. :-) DXF, DWG, DWT ...

-- erlik


FWTempest ( ) posted Sun, 01 September 2002 at 3:50 AM

Erlik, I don't know what my problem is with DXF's. Bryce4 handled them just fine, but 5 always crashes on me. Even re-installed the prog with same results. An apology to spikey for my short answer earlier, I am posting from work, and they totally ticked me off tonite. Sorry to take it out on you. Erlik is right, it all depends on the format the model is saved in. It must be one that Bryce will recognize to import directly in.


SAMS3D ( ) posted Sun, 01 September 2002 at 5:53 AM

Try exporting the AutoCAD file as a 3DS, then import it into Bryce, should be no problem. Sharen


jsa2001 ( ) posted Sun, 01 September 2002 at 9:22 AM

I have similar problems importing models i make in Rhino, no matter what format i use mostly 3ds file formats they dont import correctly in bryce 4, the models are always fragmented/messed up. Small file sizes seem ok but anything in a big file size just wont cut it and crash or are just fragmented. As much as i like bryce i may try and use another renderer as this is an annoying problem for me now.


Erlik ( ) posted Mon, 02 September 2002 at 4:24 AM

jsa, I'm currently playing with Rhino Evaluation, and might help: when you're exporting, FI, .3ds, don't raise the number of polygons. The middle setting of the slider is just fine. .obj also has a problem with the settings, but I just tried that last night for a minute and don't remember exactly what. I think you should uncheck the bottom check-box in the dialog window that appears when you choose .obj as the export format. I didn't do that and object was "imported" but nothing showed up in Bryce. Also, have you tried playing with the angle of polygons during the export? I'll try checking when I get home. BTW, P4 1.7, 512 RAM, Win 2000.

-- erlik


jsa2001 ( ) posted Mon, 02 September 2002 at 12:42 PM

Well bryce is the problem with inporting because i tried the same mesh in a cutdown version of cinema4d and it works fine, i think bryce has problems with models that are very detailed which my meshes tend to be after i build them in rhino2, i have to lower the polys anyway because the meshes are so big but im sure if i fiddle with different settings then it will import ok, sooner or later, its just a real pain having to mess about like this. i might start looking for another renderer.


Erlik ( ) posted Mon, 02 September 2002 at 3:39 PM

file_22138.jpg

I've played tonight with rhino, and built this woodcarved dragon head. Exported it as obj, checked polygon mesh instead of NURBS, unchecked "export layer names" and voila. Yes, it took a minute to smooth instead of the usual couple of seconds, but it imported without problems. I also upped the number of polygons to the max and first it took Rhino 6-7 minutes to export the (welded) object, and now it's 6 minutes that Bryce is importing. Still hasn't crashed, but I'm too lazy to wait for it to finish.

-- erlik


Erlik ( ) posted Tue, 03 September 2002 at 3:58 AM

New report: After half an hour of waiting for Bryce to import the object, I got fed up and cancelled the operation about halfway through "Bryce is converting the object". I encountered no complaints from Bryce, though, but checking the file, I saw that it was about 120 megs. So, I suspect your problem might have more to do with your computer than with Bryce. Or Cinema has a better handle on the system requests. Or something.

-- erlik


jsa2001 ( ) posted Tue, 03 September 2002 at 3:57 PM

file_22139.jpg

I build my own custom computers this particular one is running at 1870mhz over 1gig of ddr ram and is watercooled, Bryce is just a slow renderer anyway and converts ok but the models just end up broken up like i said with large meshes/file sizes. Small size meshes are just fine, Bryce4 is definitly the problem here, I think if bryce was a faster renderer or converter of differnet file formats then the problems would be much less. As for Cinema4d its maybe the fastest renderer out there or one of the fastest.The mesh above is the model i tried to import.(still wip).


Erlik ( ) posted Tue, 03 September 2002 at 5:03 PM

Hm. Then Bryce 4 really looks like the guilty party. A friend of mine had problems importing dxf from 3D Studio. One part of the model was always rotated around and she couldn't get it into the right place no matter what she did. Ah. The joys of computing. BTW, very nice model.

-- erlik


jsa2001 ( ) posted Tue, 03 September 2002 at 5:21 PM

Dont get me wrong Elrik i love Bryce and will still use it but im now looking at getting cinema art7 to do my texturing and rendering as this should be lighting fast just gonna get some more infor 1st. Thanks for the chat by the way, but im still determind to get this damn model imported into Bryce4 if it kills me. jono.


Privacy Notice

This site uses cookies to deliver the best experience. Our own cookies make user accounts and other features possible. Third-party cookies are used to display relevant ads and to analyze how Renderosity is used. By using our site, you acknowledge that you have read and understood our Terms of Service, including our Cookie Policy and our Privacy Policy.