I've been a Poser user since Poser 2 and I've finally encountered a bug issue that is extremely annoying....and downright serious.

I'm working along on a scene....maybe I've had P7 up for ten minutes....maybe hours. 

I click something different other than what I've been working with (Like working with the materials room and I click over to start posing.......or working with the morph dials and I click over to rotate camera) and Poser completely disappears.

It dosent error out, begin to shut down, freeze, ask to save...nothing....it's just **GONE.
**Control Alt Delete to bring up Windows Task Manager and the program is not to be found in Applications or Processes.

It just happened with the new Service release.

Am I the only one?

Nope, you're not the only one.

This has happened to me on a number of occassions, but only with specific opperations.

For instance, applying a morph target OBJ does this without fail...every time.

No freezing. No error...just dissapears!

Unfortunately I don't have any solution for you either. But then, I haven't installed SR2 yet. Fingers crossed this solves the problem.

The exact same thing happen to me, only it happened when was rendering a scene. It completely rendered the scene, and then poof, poser was gone. now I'm a bit hesitant to use poser 7 sr2. With SR1 this never happened. I like to know what gives. Maybe I'll have to roll back to SR1 and nix SR2. Any suggestions would be appreciated.

I've been having that 'disappearing act' for quite some time now; and exactly like KyReb. If I try to change rooms, delete lights after a render, or just clicking on a node - hello desktop. I don't remember when it started.

24" Intel Core 2 Duo iMac, 2.16 GHz, 2 GB ram, 667 MHz, NVIDIA GeForce 7600 GT, OS 10.4.9

This occasionally happens to me, too, but I've never been able do track down whether it's a driver issue or a Poser issue. I usually just relaunch Poser and load the last save when this happens.

For me, it happens after a render. The render finishes...then poof!...Poser exits most ungracefully. Happened with service release 1 as well. 

Shall we compare systems?

Windows XP Pro (32 bit)
Intel Core 2 Duo (6700)
2 gig memory
ATI Radeon X1950 with 512 meg of memory

Windows XP Home
Pentium(R) D CPU 2.80GHz
4 gig Memory
ATI Radeon X1300pro 256 

Same here.Poser just close sometime and i cannot say the reason
System:
Window Xp Home
Pentium 4
2 gig ddr ram
ATI Radeon 8500

Could we have an ATI driver problem?

I'm also having a problem with Poser 7 closing unexpectedly (it just vanishes) after a render is done and when I delete lights from a scene.  This occurs with both my desktop and laptop with SR 1 installed. However, I don't have any issues with Poser 7 SR1 on my secondary desktop with Vista. 

I also tried an ATi Radeon 1600 Pro instead of the Nvidia GS in my Primary desktop config but the problem didn't go away.

My Primary Desktop Config:
Windows XP Media Center Edition
AMD Athlon 64 3800
2GB RAM
Nvidia 7600 GS

My Secondary Desktop Config:
Windows Vista Home Premium
AMD Athlon 65 X2 5000
2GB RAM
Nvidia 7600 GS

My Laptop:
Windows XP Professional
AMD Turion X2
1GB RAM
ATi Integrated graphics acceleration

I don't think its an ATi driver issue since it happens with my NVIDIA cards also. This issue is very annoying indeed.......

I have had Poser poofs since before SR1. The code is unstable... understatement of the year.  I spent yesterday working with animation. Sheesh. Two poofs, but also:

1. It reset my camera to 278 mm but adjusted the location to suit the focus... until I started the animation render. After 20 frames, I got 10 frames of closeups of the back wall.
2. When I switched IK on or off, my figure was permanently screwed. As in, switching it back didn't fix the figure. Little things like stretching the thighs or waist.
3. Drop to floor also hosed things fairly at random. At one point, Drop to floor caused one foot to RISE to knee height.

etc.

Utter crap.
M

I make it a habit to SAVE OFTEN, especially before I make a move that has proven dodgy in the past. *D.

I still can't figure out why Poser randomly deselects some "collide against" boxes in the cloth room, even after a successful save and orderly shutdown.

I've had the dissapearing thing and the weird drop to the floor thing.  Windows XP home edition,
Core2Duo 2.6 gighrtz processor, 2 gigs ram, and a 526 gig ATI Radeon graphics card.  

Just remember folks, save early and often!  I never do a full render of a pic without saving it first!

Hmmmm....
For the condition known as
PTDT
(Poof To Desk Top)
Doctors will be filling prescriptions soon...

Yes, and it ain't just SR2.

I've had this happen before -- but not with P7 SR2.  P7 did this to me a couple of times when I first installed the program several months ago -- but it hasn't happened again since then.

Actually, the program that has been doing the instant-crash-out-to-desktop thing to me the most in recent days has been IE7.  Must be unstable code...........

me too, after a render... it was going to take hours so I left it rendering overnight, when I got up the render had completed and was playing, but no poser...

The moral of the story?  frequent Ctrl-S  (saves) is your friend... I ctrl-S automatically after every step, often..

-k

I had this when I first instaled SR 2, poofing during a render or just after it had completed, but haven't had it happen the last two days. (Can't say for sure it's linked to SR2 for me, I found Poser 7 unstable at launch and had gone back to Poser 6 while waiting for SR2).  I'll try deleting lights and applying morphs to see if I can duplicate this.

The things I've changed in the set up, in case they are related to my problem "apparently" going away have been to change the preview display from Scree to OpenGL and I also reduced the number of running threads from 4 to 2. (I have a dual core CPU, try setting it to the number of cores you have). I also found Rendering as a seperate process buggy, so uncheck that if it's checked.

One thing I'll also note is that I was having crashes of Poser or even windows itself (while using Poser) that I was able to trace to the CPU overheating during renders.  The weather was really hot here for a few days and the air conditioner in my room wasn't keeping pace too well, so my ambient temps were higher than normal. My setup uses a pretty aggressive CPU fan (I'm a gamer), so it's possible that some people using stock heatsink/fan and system cooling could be having overheating issues even outside of rendering. Might not explain the other crashes (Unless the CPU is already running borderline temps at idle), but I know it was linked to some (or even all) of my render crashes.

I'd recommend using a CPU temp utility, but unless it's one that came from your motherboard manufacturer I'd be hesitant. When trying to track my heat issues, I tried using a downloaded utility I had seen recommended on a site I visit, because it was less obtrusive than the one that came with my motherboard, but the utility itself caused crashes. :(

On warm days now, I watch the CPU temp during renders and if it reaches 60C I go into the Windows Task Manager, Processes and right click Poser.exe and turn off one of my cores for the process under Set affinity... Poser adjusts fine to the loss of one core and completes the render normally. (This setting doesn't survive the closing of the application). Temp usually drops by about 5C after turning off a core. If it's too hot even on one core, I wait until a cooler part of the day. :)

So, try changing your Preview Render settings from Scree to OpenGL, or even vice versa depending on your settings. Try reducing the number of threads Under Edit/General Preferences/Render (try setting it to the number of cores you have). Also, consider whether overheating may be an issue. (When your cpu overheats, corruption of data will start to occur and some applications will just "poof" under those conditions). See if you have a temp. monitor utility available for your motherboard, or just try to isolate whether the problems are more prevelent on days when your computing environment is warmer.

Hope that helps someone! :)

Ok, tried a couple of things that were causing others to crash. Savng a morph target from with in Poser, then loading and applying it back to the figure caused no crashes for me. I haven't tried it with third party morphs though. Tried deleting lights, (before and after a render) manually and with the delete lights script (which is what I usually use). No crashes. Changed rooms multiple times, no crashes.

Deleting lights and changing rooms all change the preview window. Definitely something that could be related to the graphics card. Changing Scree to OpenGL or vice versa could definitely have an impact on that bug. If the switch doesn't fix the problem then it might also be worth updating the graphics card drivers. (If you don't have experience with that, make sure to print and follow the directions on the ATI or NVidia web sites. As long as the directions are followed, it's a pretty smooth process).

Had a "poof" Poser crash today that was repeatable. The Olympus Mons set from Daz would poof Poser if Smoothing was on in the render settings. It would go through the initial render set up, but as soon as it got to the piont where it should start the actual render, poof!

This instance was not overheating, so even though I found many cases where heat was the cause, there are still some bugs that will cause the app to crash with out a peep. Hard to supbit debugging info in a bug report if there is no error message.

It was that set in particular, I'll be looking out for other similar crashes.