Fri, Dec 27, 5:54 AM CST

Renderosity Forums / Poser - OFFICIAL



Welcome to the Poser - OFFICIAL Forum

Forum Coordinators: RedPhantom

Poser - OFFICIAL F.A.Q (Last Updated: 2024 Dec 26 8:04 pm)



Subject: Can't add prop more than once?


azl ( ) posted Sat, 30 December 2000 at 4:41 PM ยท edited Fri, 27 December 2024 at 5:54 AM

I created a simple table prop in 3ds Max with an opening drawer morph. I've processed it through Scaler and UVMapper and imported it into Poser as an OBJ file. I then save the OBJ as a prop. I'm able to load the prop only once into a scene. If I try to load it again, nothing happens. Any suggestions as to why this is happening? (The prop is only about 125 kb in size.) Thanks in advance. azl


Anthony Appleyard ( ) posted Sat, 30 December 2000 at 5:06 PM

Is the second loading going into the same place as the first loading, so you can't see it? Next time load the table, select it, xTran it to move it away from its landing site, load it again.


Nance ( ) posted Sat, 30 December 2000 at 11:08 PM

just a thought, but if it was parented and saved as a "smart prop" will the second one, with identical names, replace the first -- the same as do hair props?? (too lazy to test before suggesting :-p )


azl ( ) posted Sun, 31 December 2000 at 8:56 AM

No, the second loading is not going into the same place as the first. It just isn't getting loaded. No, it's not a smart prop. azl


Steve Cox ( ) posted Fri, 05 January 2001 at 12:13 PM

For anyone who's interested, I think this was related to the length of the prop name in Poser. It seems that there's a problem in Poser with names longer than 28 characters (the one in questions had a 30 character name.) Keeping the name to 28 characters or less fixed it. Has anyone else seen this problem? Steve


azl ( ) posted Sat, 06 January 2001 at 8:22 AM

That's definitely the problem, Steve. Thanks. I've told the folks at Curious Labs as well, who have been trying to fix my problem. azl


Nance ( ) posted Sat, 06 January 2001 at 10:57 AM

Impressive bit of detective work there guys!


azl ( ) posted Sun, 07 January 2001 at 8:48 AM

Steve gets all the kudos on this one. I'd incorrectly pinned the problem on his wonderful UVMapper, when it wasn't responsible at all. I'd spent all this time trying out all kinds of settings when it turned out to be a simple naming problem. Next time, I'll go straight to the expert ;) azl


Anthony Appleyard ( ) posted Mon, 08 January 2001 at 2:32 AM

Perhaps the array for the prop's name in is 28 or 29 bytes ,ong, and the next byte is to store the value "new or replace?" in, and an overlong prop-name overflows.


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.