Mon, Nov 25, 6:31 PM CST

Renderosity Forums / Poser - OFFICIAL



Welcome to the Poser - OFFICIAL Forum

Forum Coordinators: RedPhantom

Poser - OFFICIAL F.A.Q (Last Updated: 2024 Nov 25 12:38 pm)



Subject: Multiple Figures Causing Pose 6.02 Crash...help?


JAG ( ) posted Sun, 09 April 2006 at 5:29 PM · edited Sun, 03 November 2024 at 3:04 PM

Recently I've purchased the Luke/Laura figures from Daz3d. Ever since beginning to use them...any time I put them together in a scene or combine them with any other figures...Poser starts to render...I get the "Loading Textures" window...and then my main window where the figures are visible goes blank and the whole of Poser locks up and has to manually killed via CTRL-ALT-DELETE. Rendering in Firefly produces an error message about a texture that's too large...to increase bucket sizes. Well, no textures in the scenes are larger than 2000x2000 pixels and I've made sure none are over 1mb in file size and have checked and double checked this. All characters and textures load fine and render until I put them together in one scene and try this...then crash. I originally thought it was perhaps a memory issue since the Daz teen figures are higher density meshes. I was originally working with 1gb of RAM. I have since added another gig and now have 2gb of RAM running on a 3.06ghz processor with a Radeon Graphics card that's got 256mb of onboard RAM. Can somebody tell me what the hell is going on here and why I can't now render more than one character per scene? Well in regards to one of them being Daz MilTeen anyways. I can still render other models together with no problem. It just seems to be a MilTeen related issue somehow I think. Any suggestions appreciated... JAG


JAG ( ) posted Sun, 09 April 2006 at 5:44 PM

Addendum: I have loaded this Pz3 scene file in my old Poser 4.0 version...and though I lost my Pmd-morph data...the file opens...and renders just fine. So it's apparently a P6 problem that's going on here somehow or the other. Am I the only moron out here with this issue or what??? HELP?


JAG ( ) posted Sun, 09 April 2006 at 6:11 PM

Also, I've already installed the service pack 2.0...so I don't know what's up with that. I found a reference at e-frontiers about some sort of issue similar to mine and it says the service pack was supposed to correct it. Anyway, I'm gonna try reloading the service pack and see if that does any good...but again...any help here would be appreciated most greatly!


adp001 ( ) posted Mon, 10 April 2006 at 3:08 AM

I recently saw this here while working with only one figure. But this figure was using

  • a texturemap
  • a highlightmap
  • a bumpmap
  • a displacementmap
  • some shaders

All in high resolution. I disallowed using displacements and Poser renders as usual.

While using displacements, Poser has to subdivide the figures geometry internaly based on the displacementmap. This may need a lot more memory.

Another "memory eater" I often have in scenes I created is raytraced light with very soft shadows (available in P6 only).




Tyger_purr ( ) posted Mon, 10 April 2006 at 7:46 AM

are you using texture filtering? if i recall correctly this eats up memory.

My Homepage - Free stuff and Galleries


svdl ( ) posted Mon, 10 April 2006 at 7:27 PM

Quote - " ...and though I lost my Pmd-morph data..."

This is what it's all about. P4 will open and render the scene fine since all morph data have been stripped. This will save quite a bit of memory. What happens when you tell Poser 6 not to use external binary morphs? Right know they're not very stable. Turn them off in Edit ->Preferences, save your scene, restart Poser, and see what happens.

The pen is mightier than the sword. But if you literally want to have some impact, use a typewriter

My gallery   My freestuff


Privacy Notice

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.