Hey all.

Looking for some way NOT to use Daz studio to import poser objs into bryce.
My problem is this. Most of the time when I do something in poser then export, then try to import into bryce, CRASH DETECTED notice in bryce 6.1. right before it finishes loading. UHG!
Before anyone starts asking questions:
My objs are in a folder with all the textures used for the object(s) so I and Bryce, don't have to search for them while loading.
I don't try to import a lot of stuff at once. I try for individual objs.
I have tried minimizing the texture sizes used on the objs from Poser also, thinking that a 3000x3000 tex material might be too much for Bryce, but that hasnt worked either
Sometimes I can import, most times not. Like going to a casino.
I have also tested the theory that maybe I have too much in my Bryce scene, so I have tried to import with NOTHING in the Bryce scene, just open Bryce and import, CRASH DETECTED, so thats not it.
Really wish that Bryce would get updated.
I usually just want to import a human figure(s) into bryce because it looks much better than PW in CS2.
Anything anyone can suggest? Anyone have similar probs/experiences? Anyone have C4 in an obj format I can import into Bryce and blow it up?
It really puts a kink in the creative process. OK, more like a washed out bridge over a 1000 ft deep canyon.
Thanks in advance.

Dragon

First thing I would suggest is to use Bryce 5.5, if you can get hold of it,  for importing meshes that have been exported from Poser. Bryce 5.5 is more stable.

If this is not possible, check the filenames of the textures that are involved when you get a crash, and see if they are unusually long. Bryce does not like loading long texture names. I'm not sure what the limit is, but if you have any over 20 characters I'd advise shortening them. Unfortunately this will mean either loading them manually or editing the .mtl file.

If there are no long texture file names, try to find out what is upsetting Bryce by process of elimination. Remove the textures and the .mtl file from your import folder, and just import the mesh untextured. If this works OK, put the .mtl file back with one of the textures and try the load again. Keep adding the textures back in and re-loading until you find out which one is causing the issue.

None of this messing about is good for the creative process, but unfortunately in digital art  you generally end up having to be part artist and part engineer........  8-)

Well, I'm running Vista and we all know Vista is not backwards compatible friendly. I've had to upgrade all my progs with the latest because Vista won't load older stuff.

I just removed the mtl file,(don't know what it is or what it means or how to edit it), and it loaded fine. I have NOT put the textures in before and its loaded fine, which is why I thought before that the file sizes were too big for bryce.
Now to figure out what textures make it crash.

Thank you.

 The .mtl is the Material File and is a text document describing all textures , their locations and where they apply on the model. It can be opened and edited in any text editor.. ...

 Are you using 6.1.13.1?To find the version, hold down the Control key and select About Bryce 6.1 from the Help menu.
Also what version of Poser?
And as Bobby suggests, open the .MTL in a text editor and make sure that the path to the textures is pointing to the right place.
For example, the .MTL statement:
"map_Kd MyHardDrive/Users/danielwhiteside/Documents/bulidings/slat_facade_2.psd"
is the path to the diffuse texture map.

Something I've noticed in Poser (at least in version 5)...there's two choices for .obj
Don't know if they fixed it in later versions, but I use the lower one in the list.

Poser objects tend to scale funny, so depending on what you're importing, it may show up as tiny objects (providing they get there...;)

Along this topic, does anyone know if there has ther been a fix for the Daz tp Bruce bridge since the last Daz upgrade  ruined it?

 The D|S bridge fix is supposed to be out "soon" - the last post at the DAZ BryceTalk forum said it was in final testing.

Thanks Dan.