Forum Moderators: Staff
Poser Technical F.A.Q (Last Updated: 2024 Dec 04 2:47 am)
Welcome to the Poser Technical Forum.
Where computer nerds can Pull out their slide rules and not get laughed at. Pocket protectors are not required. ;-)
This is the place you come to ask questions and share new ideas about using the internal file structure of Poser to push the program past it's normal limits.
New users are encouraged to read the FAQ sections here and on the Poser forum before asking questions.
Now that's weird. A possible cause: do you use .BUM files for bump maps? Poser 5 may not handle .BUM files correctly. It may be a file type problem too, I'm not completely sure what file formats are valid for P5. If you want somebody to test your prop, I have P5, a reasonable knowledge of pp2 files, and a free weekend coming up.
The pen is mightier than the sword. But if you literally want to have some impact, use a typewriter
Well, I did some tests and your package works perfectly on my system, both in the main runtime and in an alternate runtime. Why the tester ran into those texture problems is beyond me.
The pen is mightier than the sword. But if you literally want to have some impact, use a typewriter
I am having a similar problem, just two users have trouble loading my latest character because it's looking for bump maps. My understanding was that Poser 5 should create them from the .jpg maps provided. One user said they followed the directions and created the .bum before loading and it still hung up. It was suggested by one of them that the bump node should be plugged into "bump" instead of "gradient bump" where it defaults to from Poser 4. Is that correct? I have Poser 5 and they load fine for me so I can't test the problem either.
"Your work is to keep cranking the flywheel that turns the gears
that spin the belt in the engine of belief that keeps you and your
desk in midair."
Annie Dillard
Poser 5 handles bump maps the same way as ProPack. So it SHOULD work with .jpg bump maps. As it always has done, on all five of my systems that I've run P5 on.
The pen is mightier than the sword. But if you literally want to have some impact, use a typewriter
Could it be the patch? They both said they had the latest one, I have a previous one myself. It looks like either way I am going to have to make separate cr2 and mat pose files for Poser 5 users. I'd like to find a way to correct for the problem within one file, at least for the CR2.
"Your work is to keep cranking the flywheel that turns the gears
that spin the belt in the engine of belief that keeps you and your
desk in midair."
Annie Dillard
I've run the tests with Poser 5 SR4.1 on WinXP/SP2, the latest patches. So I don't think it's related to the patch version.
The pen is mightier than the sword. But if you literally want to have some impact, use a typewriter
Hi, Mat Pose Edit is what I used to create my mat files and there was a problem with those too. It doesn't seem to have a version number but I know I've had it for quite a while, since before Poser 5 I think. Is there a newer version I should looking for? Or is there something I need to do within the program I'm not aware of?
"Your work is to keep cranking the flywheel that turns the gears
that spin the belt in the engine of belief that keeps you and your
desk in midair."
Annie Dillard
Attached Link: http://koti.mbnet.fi/%7Eilaripih/MPEHome/
You've been producing Poser content for years, and I'm shocked that you aren't up-to-date. There have been at least two new versions in the past couple years. I suggest you visit the MAT Pose Edit Home page for info. You can also talk to Scourge. He's very helpful.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.
Hm. I'm having a problem with some stuff I'm working on. In Poser4 and in ProPack, there's no problem. Take the item into Poser5 and it complains it can't find the textures. I've been over every inch of the pp2 files and double checked spelling, capitalization, full ":" separated path info starting from Runtime, everything I can think of. Unfortunately, I don't yet have P5 so I can't get in to test it out. Are there any known issues or common texture-finding problems that P5 has? And if so, are there work-arounds?