♥ PosetteForever ♥

Poser 4 <br /> and the trouble with Big Texture Maps: <br /> So, I started playing around with Mil Dragon from DAZ (I had this promblem with others as well) <br /> Poser 4 runs pretty smooth when posing the dragon but when it comes down to rendering.... <br /> it drags a little.....I mean freezes up the system or just takes forever. <img src="https://www.posetteforever.com/images/smiles/eusa_eh.gif" alt="" /> <br /> <br /> Now, I found somewhat of a solution aleast for my problems and maybe they'll help you as well <br /> I started in the texture folders: <br /> I'll do the example of the dragon since I've been working with it <br /> Mil Dragon folder has 12 Tex maps and 12 Bum maps and some Trans maps also (ones I'll be using there more but you get the idea) <br /> First lets look at the size of the texture body map which will be used on 4 material zones.(body, belly feet and hands) <br /> The Tex map is 1,274KB and the Bum map is 1,600KB. <br /> Now I'm I wrong in think that the poser program is using that TeX 1,274KB x4 and Bum 1,600KB x4 <br /> for those materials. <img src="https://www.posetteforever.com/images/smiles/eusa_think.gif" alt="" /> <br /> And I'm so not a cumputer wiz so I'm asuming that's alot of memory being used. <img src="https://www.posetteforever.com/images/smiles/XXfart.gif" alt="" /> <br /> Now the head is the same KB size as the body but being used on 13 different material zones. <br /> So, again I'm asuming that all the Textures combine are like tring to open a small program inside <br /> of poser when you hit that render button (that's alot of <img src="https://www.posetteforever.com/images/smiles/XXfart.gif" alt="" /> ). <br /> It's way more then my system can handle and maybe some of yours too... <br /> <br /> So the solution: <br /> was to size the dragon body Tex map down in size: I did it in pixels the original body was 4090 x 2678 I cut that to 1000 x 655. <br /> Cutting the size down to 151KB and the Bum map to 175KB. <br /> Holy New Year Diet! -Batman <br /> Then I went on to resizing the rest of the body parts. It didn't take that long and the results <br /> out weight my time in doing so... <br /> <br /> The test render with Dragon standing alone about 10 - 20 secounds (it's pretty fast and it looks fine to me). <br /> I just opened dragon hit pose and added all in render options (will very using 1024 map size on lights <img src="https://www.posetteforever.com/images/smiles/thumb.gif" alt="" /> ) <br /> and hit render....... <br /> I'm working on Jan. pic with props and Lucy and its still under a minute (test rendering) <br /> Now, I'm just playing around here and its nice to use some other models that were made for <br /> faster and more up to date system but still could work with in my poser 4 and my slow <img src="https://www.posetteforever.com/images/smiles/new_cussing.gif" alt="" /> computer. <br /> <br /> So, if you're still using poser 4 and have questions or solutions drop'm here..... <br /> Cause I got tons of questions that need answering .... <br /> <br /> <br /> Like Why do I get missing body parts when I load the same characters in a scene? <img src="https://www.posetteforever.com/images/smiles/new_shocked.gif" alt="" />

Hi maovin <br /> <br /> I remember a discussion about the right size of a texture map, in any case, you're right, if you're not going to show pores, a texture map can be scaled down relating to the dimensions of the final render... And you save memory. <br /> <br /> What parts are you missing there ? Maybe backfacing polygons ?

I had to look up backface polys and I had a laugh <img src="https://www.posetteforever.com/images/smiles/lmao.gif" alt="" /> what is he talking about..... <br /> Duh! <br /> I forgot I asked a question! <br /> I'm using April's P4Vskin and when I load the same two characters one head is there; the other is not. <br /> Also with two EVEs but with the hip. <br /> I'm sure its a ghost in the machine somewhere.....I'll find 'em <br /> Thanks

Sounds like a crosstalk problem....I don't know why this happens, but sometimes P4 does this with textures too. Had that experience too when I used p4. (currently no Poser installed - hdd crashed after I had all my runtimes sorted out and before I could save them to an external drive, so I kinda lost the fun atm <img src="https://www.posetteforever.com/images/smiles/new_cussing.gif" alt="" /> )

That's good advice on the texture maps, maovin and Tormie. <br /> <br /> I also use Poser 4, and have seen the "missing body parts" problem many times. It happens randomly to me when I start to get more than about four or five Posettes or Dorks at a time in a scene with a lot of props. Posfan made a good point about crosstalk which can definitely be a problem, but in my experience missing limbs often seem to be a RAM/memory issue with Poser (made worse by the fact that at least on my machine Poser 4 prefers to run out of phsyical memory and stall rather than utilize virtual memory). One thing that works for me sometimes is just to save the scene, close Poser, maybe reboot my computer or maybe not, and then reopen Poser and the scene. That doesn't always work, though, so here are some other suggestions if you are having the missing limbs issue: <br /> <br /> a) Look at not only the size of texture maps being used in your scene, but also the number of different texture maps Poser is currently holding as active. If you've been making a lot of changes to the elements of your scene Poser may be holding many texture images in memory that you're not currently using (so that if you wanted to change back to them you don't have to pick "Load Map" again). In this case exiting Poser and then restarting it will clear out all the textures that are not currently in use from memory. <br /> <br /> b) If your composition doesn't call for a relative close-up shot, you may not need bump maps at all in the scene. You can get rid of them as described in (a). <br /> <br /> c) Take a look at the complexity of the characters in the scene. Unlike in later versions of Poser with those newfangled injection morphs, in Poser 4 the amount of memory required to use a regular figure can jump dramatically as even a few morph targets are added. If your figure has morph targets that you are not currently using, consider using Morph Manager to make a stripped-down version of the character for use in the current scene by getting rid of any morph target set at zero (just make sure you save them under a different filename that the original). If a human character is not featured prominently in the scene, consider using a "factory default" Posette or Dork as they don't take up much memory. <br /> <br /> d) If you have background or filler objects in your scene, consider whether they need texture maps at all or if you could just set an object color for them instead. <br /> <br /> e) I've found that sometimes if I can't get a character to load from the library without them missing a limb or two, if I make a new Poser scene with just that character and then import this back into the original scene the character will appear properly. <br /> <br /> f)As a last resort consider whether there are elements in your scene that you could render separately and add-in postrender to the final image. <br /> <br /> <br /> As for helping to speed up the render time, here are some suggestions: <br /> <br /> 1) You mentioned you had the lights set at a shadow map size of 1024, which I think is pretty high. Of course it depends on what you're doing, but unless your scene is meant to be lit in a harsh way there's not much benefit in my opinion to going above 512 on the shadow setting and the effect on reducing render time should be very noticeable. <br /> <br /> 2) I may be wrong but in my experience Poser needs less memory to render an image in the workspace as opposed to rendering in a separate window. <br /> <br /> 3) If you haven't already done so, turn off the little Poser Guy that walks across the screen while the image is rendering to let you know what percentage is finished. In the PoserRuntimeScripts folder, rename the file named something like "status.avi" to "no-usestatus.avi" and the little guy (who takes up memory and calls for extra screen redraws) will go on vacation. If you miss him just rename the .avi back to its original name. <br /> <br /> 4) Think about the number of lights you are using. It is almost always better to have fewer lights that are carefully placed, and less lights equal a faster render time. Also consider whether you have any lights for which you could turn off shadows. <br /> <br /> <br /> I would guess that you probably knew most of that stuff already, but perhaps if others are having trouble too these tips might help them. <br /> <br /> <br /> Endosphere

Thanks <br /> Posfan & Endosphere <br /> <br /> <img src="https://www.posetteforever.com/images/smiles/thumb.gif" alt="" />

While catching up with the posts here, I remembered something about Bump files in P4. <br /> <br /> Bump files are usually very big and take a lot of memory. But there's a trick. <br /> <br /> Resave the bump files as JPG files. Then create a MAT Pose with MPE using the JPG Bump file. <br /> <br /> This way Poser 4 is able to read JPG Bump files!! <br /> <br /> You can't apply the JPG bump file manually - Poser won't read it. <br /> <br /> Here's a PS action ready to download to turn b/w bump files into the green P4 bump file.

"... hdd crashed after I had all my runtimes sorted out and before I could save them to an external drive" <br /> <br /> Been there, done that. Except mine was a HUGE 3DS archive, neatly sorted & categorised, duplicated on the two D: drives on my two PCs. Then one D: drive died by inches. While I was still trying to identify cause, then recover from failure, the other D: died... <br /> <br /> They were identical drives, from a bad batch. Maker later left the business... <br /> <br /> I was able to recover *most* of my archive from the upload/download directories on the PCs' C: Drives, but I was never sure what I'd lost, and a lot of the web-sites had vanished... <br /> <br /> Sting in tale: I'd bought three (3) drives together. I'd put the other into a portable USB box, used it for 'take on holiday' stuff with lap-top-- It died a year later, on holiday. <br /> D'uh. <br /> --- <br /> <br /> Um, I found my Poser 4 needed the BigRAM patch, otherwise it fell over in bizarre ways. <br /> <br /> I've got v7, still in box, but I can't install it because the CAD_PC would need to dial out. And the CAD_PC cannot spare Norton's overheads. I'm thinking of getting a Yoggie stick to off-load the firewall's resources, but I can't justify the £ 100... <br /> <br /> And, um, I seem to be 3D-blind at the moment. I can't see meshes in my Mind's Eye or think creatively. Same happened in 2004/5, which took me out of Poser for several years... <br /> <br /> My head hurts... <br /> <img src="https://www.posetteforever.com/images/smiles/very_sad.gif" alt="" />

Hi Nik, welcome back <img src="https://www.posetteforever.com/images/smiles/TFR718 (6).gif" alt="" /> <br /> <br /> Well, it's always a tragedy when you lose your precious data on a borken HD, I use to change them once in a couple of years but if it has to brake, it brakes <img src="https://www.posetteforever.com/images/smiles/eusa_shifty.gif" alt="" /> ... <br /> <br /> In the new case I took last year for the PC I could install the HDs with a huge fan in front of them and another behind, keeping them cool... <br /> <br /> I keep the zipped packages on an external HD and the runtimes on the main HD, I make copies of the works that I make on my own. <br /> <br /> About the inspiration, well, don't worry. It's a while that I'm uninspired , maybe it's the kind of life and work that I have, who knows ? BTW I've not lost the fun and sooner or later it will come back... <br /> <br /> Actually I'm on a (sort of...) Mac for main applications...

Howdy folks! I had a question about the old P4.03 and Memory Patches. <br /> <br /> I understand that SmithMicro has said they cannot distribute these patches because of third party license agreements, but I was wondering if any P4 users had tried what sounds like a potential alternative? <br /> <br /> This was mentioned earlier this year at Rendo, and one member replied that it worked for him, but I never heard anything further. <br /> <br /> Anyway, thought I'd mention it here and see if it might help anyone. (I've not tried it, and do not know the author, Geert De Peuter, but he hosts apps he has written to patch various older MetaCreations products) <br /> <br /> Geert De Peuter's general MetaCreation patch: <br /> <br /> <a class="post-url" href="http://dev.depeuter.org/" target="_blank">http://dev.depeuter.org/</a>

<span style="font-family:Arial;"> </span><span style="font-size:12px;"> </span><span style="color: black;"> </span> <br /> <br /> <br /> @Nance <br /> <br /> Are you having any trouble with Poser 4.03 that you believe would be addressed by a patch and if so, could you elaborate on the trouble? <br /> <br /> I run Poser 4.03 myself and the only time I ever get an "Out of Memory" error is if I try to load a cr2 that references a missing obj in the runtime\geometries folder. I don't believe that qualifies as an actual bug, but rather just a reaction to an unsolvable problem that Poser doesn't know how to deal with. In other words, the problem is unsolvable without the user intervention of finding the referenced obj file so the cr2 can load. The obj must have existed at one point during the creation of the cr2 or it wouldn't be referenced; and therefore it is the user rather than Poser that has made an error (by moving or deleting the file) and the user who must correct the issue. <br /> <br /> I actually have the old Poser 4.03 memory update (Poser4MemoryUpdate.exe, dated 4-9-2002, 914kb) that I downloaded years ago, but in all this time I have never actually installed it, and therefore can't say if it solves any problems or not. The reason I never installed it is that I was never satisfactorily able to determine <i>what exactly it is supposed to do</i> or what alleged problems it is supposed to address, and my philosophy is if it's not broke don't fix it. I looked at the link you provided and after reading the second page describing that fellow's patch I unfortunately don't really understand what his patch is supposed to do either (presumably because I've never noticed any troubles that caused me to say 'hmmm, there ought to be a patch for that.'). <br /> <br /> Do you know what sort of IP rights issues surround the old Curious Labs patch? It sounds like something you may have researched, and the patch file I have doesn't seem to have a licensing agreement. If you knew more about it and could satisfy the PF mods there aren't any IP issues (or what they are if they exist) I would then be happy to upload the patch file to the PF files area for those that have some reason to believe it would help them. It does seem highly unusual (I did a cursory google) that this trivial and antique patch doesn't seem to be available anywhere except a warez site or two, so what could the so-called 'rights' problem be? <br /> <br /> Sorry I couldn't be more helpful without more information.

Thank you Endosphere, but uploading something that refers to a copyrighted program to PF is a nono, it would mean BIG troubles (especially for me <img src="https://www.posetteforever.com/images/smiles/ninjahideh4hbf3.gif" alt="" /> ) <br /> <br /> BTW, and <b>*I'M NOT SUGGESTING IT*</b> if this update is not available anywhere, you and Nance could contact each other by PM... And find a solution ( I'm not suggesting it ... <img src="https://www.posetteforever.com/images/smiles/dontknow.gif" alt="" /> )

Thanks Endo & Tormie. I was following up a post originally made by a member at 3DCommune (who was re-installing P4 and had lost the patches) and I'd hoped perhaps <i>Those-What-Guards-the-Treasures-of-Poser-Past</i> might have a line on that update. <br /> <br /> As I recall, the Memory Patch allowed P4 to address memory greater than 2Gig. With the size of models & textures these days, that gets maxed out pretty fast. <br /> <br /> Sounds like its just more headache than profit for the rights-holders to sort out a distribution scenario. <br /> <br /> And while <i>I would never suggest it either</i>, I suspect the solution <i>that Tormie didn't suggest</i> would not raise anyone's ire if the patch were to be encrypted with RTEncoder using Poser.exe as the Key file. <br /> <br /> I appreciate the input. I figured if anyone might know, you guys would, so I'm going to rest assured that it is no longer officially available anywhere online. <br /> <br /> Thanks again!

After reading about the tales of Hard Drive woe on this thread, I'm beginning to think my collection of 13 1Tb external drives (from 2 different manufacturers) and a 2Tb NAS box for network storage isnt quite as paranoid as I thought it was... Though it has to be said, I could barely fill 3 of them at the moment. But multiple copies at multiple physical locations do tend to make me a little happier. <br /> <br /> Then again, I learned the hard way about losing years of work in a minute. About 10 years ago, my flatmate decided to borrow my PC to check out some floppys he's "aquired" from a pal, and STUPIDLY booted from them. Of course, they were virused, and 2 Gb of hard-won downloads, and 12 years of CGI work went to the bit-bucket in a flash. And this was back in the days when (slow) dial-up ruled supreme, and 2 GB was a monstrous amount of space - and almost impossibe to reliabley back up. It still aggravates me thinking about that. <br /> <br /> Even now, right out of the box, one of my brand-new 1 TB externals started making unhappy noises within minutes of unpacking it. (It says a lot that you can hear a hard-drive head banging away from across the room while you're watching 'The French Connection' in 5.1 surround sound...) I've contacted the store I bought it from and informed them I'm going to run it 'til it fails... then return it.

<span style="font-family:Arial;"> </span><span style="font-size:12px;"> </span><span style="color: black;"> </span> <br /> <br /> <br /> Whoah, 15 terabytes for personal data! Not long ago I would have thought that was excessive, but given the changing nature of data use and management it doesn't seem fanciful at all. That's unfortunate about your just-out-of-the-box HD being a lemon, but on the bright side at least you know to be wary of it rather than having it suddenly fail with no warning as happened to me with an only-several-months-old drive earlier this year. <br /> <br /> Making regular back-ups is definitely a best practice, particularly for nostalgic people like myself who have a lot invested in antique software and arcane files that are irreplaceable. Since my own major HD crash last year where I lost a lot of data, I've been religiously making backups to CDs once a month--which saved me lots of crying when the replacement drive I bought also failed shortly thereafter. <br /> <br /> The threat of lost artwork is yet another great reason for everyone to post their pictures on Posette Forever--if you lose a file locally, you'll still be able to remember and appreciate it here on line. As you said, multiple copies are good but mulitple copies at multiple locations are even better. <br /> <br /> I researched that Poser memory patch thing a little more, and while sadly I did not find anywhere to download it (which is lame--if the current owner of Poser refuses to support older versions it doesn't inspire much confidence that their own current version will still be supported a few years into the future) the details of what the patch was supposed to do is that it allows Poser 4.03 to address installed RAM larger than one gigabyte in volume (not 2 GB). This explains why I never noticed any reason to install it, as my old computer only has 512 MB of RAM (which knowledgeable people told me years ago I was WAY more than I would ever need). <br /> <br /> <img src="https://www.posetteforever.com/images/smiles/new_shocked.gif" alt="" />

OutofMemory Error : "therefore it is the user rather than Poser that has made an error" <br /> <br /> Not necessarily: Too many of my 'classic' downloads from eg Render**sity refer to specific drives rather than 'runtime'. <br /> <br /> One enthusiastic CG Mesh-builder kept most of his work-in-progress OBJs on a T: Drive, waaay down the directory tree. Sometimes, he would correct one of the two CR2 references, sometimes neither. He often stored textures 'obscurely'... <br /> <br /> When I was enthusiastically converting classics for Posette, I learned to use CR2Edit to check and correct the links. <br /> <br /> A superb crafter of 'period' clothes who's now left the business sometimes left links to textures in directories named for family members... <br /> <br /> Many of her 'Read Me' files were Word Docs, which my early version could not read. Opening them with Notepad or WordPad often revealed chunks of her own documents... <br /> <br /> Yet another reason I won't use Word... <br /> --- <br /> <br /> OT: I've now installed enough RAM on this old Browser_PC to let Poser4 & XD work again. Snag is my 3D Bump is 'resting'. I still collect interesting freebies but, sadly, I'm not doing anything with them... <br /> <br /> Um, there's a possibility that I'm due a significant refund from bank. It may pay for a new CAD-Tower, as my current #2 is now obsolete. More likely, I'll just clear the plastic...

<span style="font-family:Arial;"> </span><span style="font-size:12px;"> </span><span style="color: black;"> </span> <br /> <br /> <br /> <br /> @Nik <br /> <br /> That's a good clarification Nik. I shoud have expanded my definition of 'user,' as you are right that it's often the case an original user (creator) of a prop file, rather than the end user (you or me) made an error upstream that confuses Poser. I'm always grateful for free stuff, but it's hard to understand how some folks can be so careless when putting a download together and not include called-for textures, not give a thought to compatibility, etc. <br /> <br /> I also dislike when people make readme files in .doc format, as I dread allowing the memory-hogging and ill-behaved MS Word program to run, although luckily I've never seen the problem you mentioned with personal stuff in a file. I think if I opened a text file for something I downloaded and saw something like: <br /> <br /> <br /> <br /> <div style="" class="spoiler">Thank you for downloading my prop! I spent hundreds of hours making this conforming acne prop for Victoria, and hopefully you will enjoy it as much as I have! <br /> <br /> To use the prop, place the "acne.cr2" file in your runtime\clothing\female folder, load Victoria, load the prop, select either Victoria's face or rear end and with the acne highlighted select 'conform to Victoria.' <br /> <br /> email comments on this prop to <!-- no smilies start --><script type="text/javascript"> <!-- document.write(' </script><noscript>indigestion [at] greasypizza [dot] com</noscript><!-- no smilies end --> <br /> <br /> <br /> Grocery List for 4-8-97 <br /> <br /> Athlete's foot spray (2 cans) <br /> Lima beans <br /> Tampons <br /> Cayenne Pepper <br /> Pork rinds</div> <br /> <br /> <br /> <br /> I would immediately delete the prop without even trying to use it. <br /> <br /> <img src="https://www.posetteforever.com/images/smiles/lmao.gif" alt="" /> <br /> <br /> <br /> <br /> <span style="font-size:10px;">Edit: left out the word 'never' in second paragraph. </span>