Forum: Poser - OFFICIAL


Subject: P6 crashes when try & access file menu - runtimes, morph targets

jehllm opened this issue on Aug 09, 2005 ยท 6 posts


jehllm posted Tue, 09 August 2005 at 7:00 AM

Hi - just installed P6 on a new machine, and everytime I try and access the rest of the computer, P6 just crashes in a flash and is gone. So if try and add a new runtime, access morph targets - any access to the file menu and it disappears. Rest of programs seem to be running OK. anyone else seen this? thanks!


grylin posted Tue, 09 August 2005 at 8:05 AM

yes, i have a similar problem :( dunno how t fix it tho yet :P but i am defragmenting everything, and cleaning up ' my computer w norton . maybe it'll help :) do u have norton?of u do, try to run 'one button checkup' that should fix some probs on ur pc. or try to get the sr1 upate:) hope everythg works out for ya :P


DCArt posted Tue, 09 August 2005 at 8:31 AM

Have you updated your graphics drivers?



Khai posted Tue, 09 August 2005 at 8:54 AM

also switch your OpenGL settings from software to hardware in Poser 6. to get there : small black arrow at the top right hand corner of the workspace - render settings - preview settings tab.


jehllm posted Tue, 09 August 2005 at 11:54 AM

Hi - thanks for the advice - it is only P6 that does it, P5 can find files and work with the file system. Have the latest graphics drivers - am a little leary of downloading from the NvDia website because the card is in a Dell and they sometimes fuss with the cards. P6 loads files from the libraries, but vanishes as soon as it tries to go out to the rest of the computer. Does anyone know the Curious Labs tech support e-mail address? tried to e-mail them but don't have outlook setup and so the e-mail didn't seem to go anywhere. thanks!


DCArt posted Tue, 09 August 2005 at 11:59 AM

Have the latest graphics drivers - am a little leary of downloading from the NvDia website because the card is in a Dell and they sometimes fuss with the cards. Hmmm ... I would verify the date of the Dell drivers. They might not be the most current version that is on NVidia's site. The symptoms that you describe have very frequently been resolved with updated video drivers.