Last week I posted a message in this forum about the DAZ Hi-Res textures for Vicky and Mike locking up my Athlon 1800 w/512 megs of RAM...Damn! I decided to try SteffyZZ's Asia which is at least as big as Daz's (4000 x 4000). The result is that I have been rendering at 2000 x 1500...600dpi for the last two or three hours without a single lockup. This is with the bump maps applied. The Daz textures, even when reduced to 2500 x 2500 would lock up the computer after 2 or 3 renders. The problem appears to lie with the Daz textures, although I have no clue as to why. To clarify, I used the Asia texture at full resolution (4000 x 4000) and rendered at 2000 x 1500 on the screen.

Hi, You are having the same problem I had before I upgraded to Windows XP. The hi-res textures are very memory intensive, apparently ('But I have 512mb-is'nt that enough???'I thought) Then I found out that it's most likely windows 98 which doesn't handel memory very efectivly after you upgrade past 128 mb) I thought my Mike Hi-res texture was bugged or broken too but the second i went to win XP it renders EVERYTHING no problem (in fact Poser hasn't bombed out once yet-YIPPIIIIIIII!!!) I think win 2000 and NT work as good for this as XP. Hope this was a help :)

I had Windows ME, and it sometimes had a devil of a time working with Poser. I now have Windows XP Home Edition, and it is almost flawless.

Oh goody! Thanks Ron. I was worried. ;=] You said "almost." What's not? (in XP, that is) ;=]

Well... you know... it's Windows, for one thing... =)

Your pic is awsome! We keep getting closer and closer to reality. (i.e., photographic) Re: your question ... I don't believe it has anything to do with the textures - the lockup, I mean. It has something to do with the way Windows manages (or doesn't) available memory. (regardless of the amount of RAM) A case in point... I started with 128MB of RAM. Very few lockups. I increased RAM to 384MB. Had frequent lockups. (after several renders) I decreased RAM to 256MB. Less lockups, but they still occur. I haven't noticed any lockups when I am only using small props with little or no texturing. It may be that lockup would still occur after many, many renders, also. I don't know. But it appears to be a "system" (i.e., swapfile size, use, etc.) type of problem and no fault of the textures [per se]. cheers, dr geep <------------------------------(lookin' fer the key to open up them lockups) ;=]

I have had some trouble with the daz3d vicky 2 hires textures, but I decided my problem was that I was using the wrong Material pose. I was using the poser pro one (I think it has P or PP at the end of the name). For some reason, I was thinking that the p4 was refering to the v2p4 figure, so I was avoinding it intentionally. I figure it has something to do with the way poser was interpretting those jpgs (instead of bum files) worth trying out (I also resized the textures to various sizes less than original , since I seldom do close ups where the extra detail is worth the memory.) For the record, I am running AMD tb 750, 256M ram and winME

When I ran Windows 2000 Pro (for a few months), sometimes I got an error saying there was insufficient disk space to render at this resolution. I had a 30GB hard drive with tons of free space! That seems to be a fluke between Windows 2000 and Poser. I got that message once with Windows XP, and only once. I cleaned out the recycle bin, my temp and temporary internet files, then I ran Norton Speed Disk (similar to defrag). The problem went away. The problem was not Windows XP. It was a Poser problem. Ron

Thanks Ron. I'll store that l'il tidbit of info away for future ref. ;=]

If you are running Win98 SE with over 256 MBs of RAM turn Virtual Memory OFF. This will solve 99% of your problems

I think the problem is letting Windows set the Virtual Memory. All those having trouble maybe should set it 512 MB min and max and use Norton Speed Disk to (Optimize swap file) Then we all might get a bit closer to the truth. At the moment from this and previous posts nothing makes any sense as everyone is contradicting each other

If you don't have Norton Speed Disk, and want to defragment your swap file, set virtual memory to 0. Restart. Defragment your hard disk. When finished defragging, set the size to what ever you want (I am pretty sure you can set the minimum in windows 9x...I know you can on 2K) Restart If you don't force the file size, it will get fragmented as you move files on and off of that partition.