I am trying to submit this following message to the tech support page at Curious Labs but I click the submit button and nothing happens, so I thought I would post it here and see if any of the astute members here might have a solution.

To preface a bit, this concerns Creepy Clown, created by Don Tatro, Dr Legume and BadCo(me). Creepy Clown can be found at Http://www.creepyclown.com You may be familiar with him and you may not. The following was brought to my attention at the Bryce news group. People, using all different systems and OS's were having this same problem so I did a few tests and thought I would ask you all if you know a solution to this problem. We all have the upgrades for the Pro Pack so that is not a solution.

This is my reply to people in the Bryce group who were having
trouble exporting Creepy Deluxe from the Poser Pro Pack and
then trying to import him into Bryce5:

Ok, I just did a test. I run Windows2000 Pro Service Pack2.
I exported from the Pro Pack and got the same error as you
all are getting. This happens with Creepy Deluxe. I then tried
my version of Creepy and it gets the error also. I then tried my
version of Creepy before I added a shoe fix(Don made some
new shoes), and he imported just fine. OMG ! It really is the
damn shoes !:^> (sorry, but it is)

A quick test and I was able to export the Creepy Deluxe
without the shoes and he imports into Bryce5 just fine so
there is somthing wierd about the shoes and the Pro Pack
OBJ export that is giving this error. I tried exporting and
then importing JUST the shoes and got the same error.

I have tried different combinations. I get the same error
exporting from Poser Pro Pack(PPP) and importing to
Bryce5(B5), as I do importing to Bryce4(B4). I do not
get the error exporting from regular Poser 4.03(P4) and
importing into either B5 or B4. So it is a combination of
exporting the Creepy Shoes as an OBJ from the PPP that
is the problem. Exporting the Creepy Shoes as an OBJ
from Poser 4.03 causes no problems.

Any help would be appreciated.

Thanks in advance,

BadCo

Have you opened the obj file in a text editor to see if there are any lines which seem totally different between the clown and the shoes. Theres a TUt on rosity I think about what the bits in an Obj file mean. Just a suggestion :)

are you getting a "bad media" error?

Sturkwurk, Yes.

I've hit that error many times, and regretfully don't know the fix, sorry... I hadnt heard of anyone else hitting it either, glad to see I'm not alone. My work around was just to open the file in a Poser Four (non pro) and resave the obj file. Doug

Man! Creepy the Clown Without Shoes-is about as sick as sick is! My nightmares are about chainsaw wielding SHOELESS clowns-and if ProPack can't handle it-shit! will the world keep spinning?

P.S. -been visiting these poser sites since they started up, but this thread pretty much immortalizes Poser as far as I'm concerned.

If this is the problem I think it is (file error - i/o bad media), then there is a fix to it, posted back in March in the Bryce Yahoo!Groups mail list. I've used it several times with no problems. What you need to do is open the exported obj file in WordPad or another text editor, replace #IND with a space character, save the file (you can rename it at first until you are comfortable with this), and then import it into Bryce. These obj files can be quite large, so be prepared for long waits as the file opens and as you are replacing the text. Hope this helps. -darlisa

I cannot find #IND anywhere in the obj file. I am familiar
with editing obj's and cr2's. I did a find and nothing came up. the only, # is at the begining and I saw no difference between the obj that works and the one that doesn't, at least there. Can you be a bit more specific ? I would appreciate it greatly ! Thank you for your time.

I don't know enough about it to give any more information that that, so, I'll post what the Bryce list message said: "Mixed up with the vn lines are hash characters + some extra characters e.g. #IND after each of the three numbers. (Each line should be vn 1.2 -.9 1.4 for example, but appears as vn -1.#IND -1.#IND -1.#IND). The fault seems to occur with -1 and 1 values particularly. The hack:- edit the object file, replacing every occurrence of #IND with a space character. The Bryce import then works fine. So far, I haven't seen any untoward effects on the renders." The only other solution I've seen is listed somewhere in a message thread here at 'rosity, and that is to run the obj file through UVMapper, saving the obj file using the default settings, although you'll lose your texture settings. You can also run it through Grouper. Sorry that I can't be more help than this. -dar

Thank you for your help Dar ! I really appreciate it ! It gives me somthing to go on and maybe I can figure this out ! Thanks for taking your time to help me !:^>

You're welcome, hope it did help in some way. -dar