Attached Link: http://www.renderosity.com/viewed.ez?galleryid=175184&Start=13&Artist=CryptoPooka&ByArtist=Yes

This is also a composite shot -- four separate renders. There's a cheat you can use when compositing complex scenes where you want the shadows to fall correctly against other objects. One of the renders has character A in place, but naked. A shows shadows on B, B makes shadows. When you render A fully equipped, you don't even need B in the scene because you already have the working shadows. Etc. Also, don't delete a primary figure from a scene, it'll change your lighting. When you composite, make objects invisible while leaving "cast shadows" on. Even if you can't see it, the software can and treats it accordingly. If you want a background image without all the trouble of compositing, take the square, size it how you need it, and UV map it at the new size, then apply the background. You won't get much distortion that way.

The important question, I think, since it looks so much like a Giger texture is, WAS the original painting you took the snippet from a Giger piece? Mimicking Giger work is an entire category of fan art. If you aren't actually using his, but it looks like his style, that should be more than acceptable. If it wasn't, you're clear. If it was, I'd say there's a problem.

Went through this when Poser went belly up on me. I think I might have been better off just reinstalling the extras after I reinstalled Poser, but I just moved the old directories ... and got a LOT of the .obj file errors. I finally had to sit down and go through them, one at a time, loading to see what would load, then killing the rsrs of the ones that didn't.

Heck, Lee, I'm still waiting for good web gear and shoulder rigs. Once again, though, with some of the gear I want, exact duplicates are Right Out. Ah, someday .... DNA is definitely managing to keep me occupied and interested. Yay, more toys.

Yep, registry was deflicted. Tried to totally reinstall, and got an error message that I was told (subtlely) that happens a lot when a hacked copy is used. ACK! Me no think so. Ended up on the phone with CL tech help. Told me I'd probably have to reinstall Windows to repair the registry. HA! Not! Asked if replacing it with a backup would work (poor tech), and sure enough .... no problem. New install worked fine, and everything but Michael worked. Since Michael was giving me the errors on the old drive, and was now giving them on the new, I tested, went from total basic Poser figure, through Vickies, and only Michael failed repeatedly. Since Michael was loaded when the fatal 3DS error occurred, I figure he got corrupted too somehow. Walkin away for a while to breathe, then I'm gonna reinstall him and hope it works. I'm totally at a loss if it doesn't.

So, I'm on the phone. "Sounds like your registry has gone bad. You might have to reinstall Windows to fix it." Blank Pooka stare. "Why can't I just replace it with my backup copy of the registry?" Choir of Angels begins to sing, there's a pause on the other end. "You have a backup?" I could swear there's awe in the tech's voice. "Um. Yeah. I make them regularly, especially before an install or after an uninstall, just in case." Another pause. Heavenly choir gets louder. Pooka smacks the cherubs with a big book. Silence reigns. "Give that a try, tell me what happens." Altogether now, children ... can we say "Hallelujia?" Knew you could. Installs fine, no errors. Updates fine, no errors. Go to load my character. BAM. Crap. Get the Bad Obj error. Crash. Try again, working way up the Poser ladder. Default. Change to Business dude. No problem. Switch to a Poser 4 base character. No problem. Upgrade to Vicky 1. No problem. Upgrade to Vicky 2. No problem. Go to load Michael. Crash and burn. The millenium man gone bad. There's a story in there somewhere. Off to reinstall Michael 1 and 2. Will report back on progress because I'm just annoying that way.

98 (blech, gotta upgrade), only have 256 MB, added a 128 and doubled me. Didn't think the paging file would make a difference in those circumstances.

BIOS shows it clean, all RAM registers accordingly. I checked the registry after getting the error and made sure that the original wonked out version was gone. Same error. Guess I'll remove the chip and try again and see if it repeats. Then switch out and try again. Then futz around with Virtual and see if that's hiccuping. Urgh squared.

I'm doing it from the original disk, and I haven't used it since I installed after I first bought it. NOTHING in the freakin documentation at all. I haven't called Curious Labs yet, I'd really rather know that I've tried EVERYTHING first, before some tech tells me to make one little change that I forgot and I look like an idiot. Done that before, so I have a feeling I'm on the Curious Lab "People Too Stupid to Turn the Computer On, Much Less Use It" warning list for tech support. All the problem started after I tried to load a 3DS file that was obviously screwed up somehow. It killed the installed Poser and wouldn't let anything work, and now I can't reinstall, either. I do have a new RAM chip in, and I did just install a new external hard drive, so maybe something in there went wonky. And Poser WORKS, it just doesn't work on anything after the basic basic come with the disk figures. Urgh. I'm gonna have to make that phone call, aren't I?

Done that. Patched, and patched again. Deleted the appropriate RSRs in the Geometries folder. The initial one on my main drive stopped working a few days ago. The copy I installed on my external only works for the basic, no matter how many times I try to upgrade it. Maybe it's trying to tell me something.

It's almost as bad as getting everything Just Right, and forgetting that you haven't saved recently ... and then you hit Render, and Poser locks or crashes, and you lose all the 'just so perfect' changes you just finished. ARGH!

I think about the only left that can help my laptop is a priest. Anyone know a good exorcist? The weird thing is that I can still render Liya. All of the men cause Poser to fail. I wonder if it's trying to tell me something ....

Yep. And killed a retarded swap file. And defragged. And checked drive space. And ...

Yeah, that's what I'm afraid of. I'm really trying to avoid the reinstall until after I pick up the new external drive, but if I'm not going to be able to work at all ... ugh. It's definitely not the usual .obj error on the first one, I tried deleting the .rsr just in case, newp. And I've used that character over and over without problems till now. The second loads everything just fine, THEN throws errors when I try to render. Feh.

Win 98 here, and I can verify the Poser/Windows memory problem. Adding another 128 HELPED, and I don't have to render nearly as many composite scenes now, but if I throw something into a scene like seriously high-poly hair, forget it. I lock all over again. Really, you can drop everything but Poser, and you'll still have problems with a scene that simple so long as you're only running 128 and a 350 mhz processor. You've got a dual problem there. I can't even run Poser on my slower machine.