dke opened this issue on Jul 11, 2002 ยท 21 posts
dke posted Sat, 13 July 2002 at 9:11 AM
Well, there's two main ways to use it to enhance Poser scenes, and specifically regarding Poser figures and/or props. The quick, easy, and painless way, is just to create your scene in the normal way using the normal resolution figures and props. Once the scene is laid out nicely, the figures and poses tweaked, and all the texture, bump, and trans maps tested, then you can use HiRes as a last-second tweak before your final render. At that point, just export any foreground figures or props, or anything that is close enough to the camera for the resolution of the item to be noticeable, and then convert just these temporary objs to a higher resolution. Finally, hide the original item in Poser, import the new Hi-Res version, set the texture information, and go have a coffee while the final render runs :) For a quick example/results of doing this, have a peek at the second set of images in the Hi-Res Gallery: About The galleries a little sparse at the moment, but I've been answering people's questions instead of rendering pictures :) This approach has several advantages to it: 1) It's quick, easy, and painless 2) You can use exactly the same scene creation process you do now 3) You do the scene creation using the standard low(er) resolution models, so it's obviously faster than it would be if you were using high-resolution models throughout the whole process 4) You don't need to muck about converting cr2's to reference higher resolution objs and morph targets 5) You only convert those exact items that are close enough to the camera for it to be required. 6) You only need enough free disk space to store a few high-resolution models at a time, and only temporarily. 7) You don't need any in-depth, technical knowledge of Poser cr2's/pp2's/pz2's/etc. All you need to know is how to export, import, and apply textures. So even the newest user can use this approach and get the full benefits. 8) It's quick, easy, and painless :) This is actually how I use it most of the time. The Hi-Res conversion really is quick and easy: a) Click the Import Toolbar Button b) Click the Subdivide Toolbar Button c) Maybe Click the Subdivide Toolbar Button again or a few more times d) Click the Export Toolbar Button I suppose if you had a busted clicker-finger it could be painful, but it's usually not. :) Whew! You'd think I was writting a long-winded tutorial here :) Mind if I use your question as an entry in the FAQ? It's a pretty good question, and even one I have a decent answer to :) The second method is to go whole-hog and convert the figure/prop/etc into a clickable Poser object, and then you can use that throughout the whole process. Converting them isn't that complicated, but it can get a bit tedious. Doing it does have some significant advantages though: 1) You only ever have to do it once for any figure or prop. In fact there's a good chance that you wont even have to do it. I've already created the Hi-Res cr2 for Posette, and once I get it cleaned up a bit, will be posting that as a free dl on the website. You will still need the program to create the initial high-resolution version of the orginal obj, but given you have that, I will be posting whatever cr2 conversions I get time to do, and if other user's want to share or swap their own high-resolution cr2's/etc. that would reduce the overall effort on any individual person. 2) The higher resolution version offers some significant opportunities for adding much more detailed and realistic morph targets. For example, adding individual ribs to the standard resolution models is virtually impossible due to the large polygons, but if you double the polygon density then it becomes much more feasible. 3) If you are doing a lot of animations then this is probably the way to go. You definately don't want to stop between every frame and do the conversion, so the time invested in doing the conversion would be well spent. Well I hope I haven't bored you :) and/or put anybody to sleep. I can just hear somebody thinking "(scroll, scroll, scroll)... When DOES this answer end?!"