Keith opened this issue on May 11, 2007 · 124 posts
kuroyume0161 posted Sat, 12 May 2007 at 12:17 PM
Quote - I wouldn't consider that good filenames. Why? Because there's a good chance that they aren't unique because another merchant will probably make a product using the same names. And if you want to use both products in the same scene you'll end up with one working outfit and one that loaded the wrong obj-files... Filenames that are not unique are the biggest problem as Poser will only load one texture/object with the same name no matter how correct the path of the references is.
I'd blame this more on Poser's poor referencing than anything else. Poser should do what my code does when referencing geometry and textures:
This way, as long as V4WarriorPlate.obj is in Runtime:Geometries:[ProductName] or [Merchant] or [Merchant][ProductName]. File paths are still limited - not as much as before, but if you start specifying 200 character names:
C:Program Filese-frontierPoser 7RuntimeGeometriesJoeBob3DV4 Warrior PrincessJoeBob3D_V4WarriorPrincess_Plate01_FrontPlate_Chest.obj
it's gonna get frustrating all around - and it's insane... Aren't the Poser files large enough already to make this type of unnecessarily extended naming unfortunate? Just use a good folder structure:
JoeBob3DV4WarriorPrincessPlate.obj
JoeBob3DV4WarriorPrincessPlate.obj
Qualified on Poser's ability to reference Plate.obj. Otherwise, use JBV4WP_Plate.obj for some foresaken brevity and uniqueness. You cannot fault vendors for Poser's shortcomings in these regards. tyvm
C makes it easy to shoot yourself in the
foot. C++ makes it harder, but when you do, you blow your whole leg
off.
-- Bjarne
Stroustrup
Contact Me | Kuroyume's DevelopmentZone