Fixed Poser, but not sure for how long. Help?

Upirium

So I mentioned a while back I was having Poser issues (Pro2014)

I had installed CCleaner and ran the general temp file cleanup and shit started going wrong after that. Mostly Adobe Flash errors.

But then it started crashing spontaneously. I installed a driver update for the graphics card, then installed Driver Booster and restarted and things got weird after that. It stopped crashing but I could no longer easily move the paremeter dials. They just wouldn't move. It would freeze up and it would move maybe .1 value. This isn't even an exaguration. I'd sit there trying to move it for at least one minut enad it would get up to like, one.

Camera was really buggy and laggy, too.

It was mostly a problem wtih G2 and DAZ figures though, which I don't understand.

I tried everything I could think of. I rolled back the driver, it didn't work. I uninstalled Driver Booster, not even having used the update feature for it, I only checked the drivers. Did nothing.

I restarted about a hundred times and nothing.

I had to do a System Restore. I had to do it twice, I don't know what happened. I had avast installed, and it said it failed, but I uninstalled avast and tried it again. I noticed for some weird reason McAfee was back on my system but I was like whatever, and tried again. It failed because of McAfee, so I did some chekcing and realized the first one had indeed set it bakc to the state I wanted it to. Before I installed DriverBooster, CCleaner, and unrelated I believe... Clive Barker's Jericho, which was no longer installed when it came back.

Poser started working again. No actual crashes really and I could move the dials again.

I did work on it yesterday. I did three renders, saved four files, and then I quit. This was spread out over time but whatever. I hadn't restarted yet, but today I pulled my computer back up out of sleep and found somehow I'm guessing the save file from the latest two files which were the same scene more or less were corrupted. Poser crashed upon loading it, so I thought whatever, I'll just redo it. It wasn't that hard.

But when I loaded the base figure...I found I could not move the dials.

I restarted and it seems to have fixed the problem but I am very scared that one day I will just not be able to move them again and I don't understand why this would happen.

Can someone give me some advice? Reassure me? Did it just need to be restarted? I'm still very scared.

It sounds dumb I'm sure but since I am very badly disabled I am no longer able to draw like I used to, but creativity flows in my veins and I find now the only way I can get that out is to use Poser...and without it, I am pretty much nothing.

edit

I've found that for some reason even though I redid the picture I still cannot load it when it's redone and this is the only one

I think it has to do with adding Reptilian 6 legs to G2M

and after Poser crashes like six times it slows down again...

What is the cause for this?

edit

I restarted

but it's back again

and I don't know what to do

please help

edit:

It is not working again after I deleted all the files that seemed to be buggy but idk how long this is going to work

edit:

I will also note here exactly what was on this figure, though I don't know if that's the problem.

He had Lilith Strigoia for V4 wings parented to his chest

He had the tail for Jezebeth for V4 parented to his pelvis.

He was wearing Jungle Girl skirt

and in the seocnd instance, Jungle Girl necklace.

He had Reptilian 6 legs.

He had instances of Creature Creator used on him (teeth, claws, ears)

 

icprncss

Sorry but I don't have any assurances for you as I have no idea what caused the problems in the first place.  You would need to go back and review all of the Windows crash logs and the Poser crash logs.  In the end, a long drawn out process that may, in the end tell you nothing of value.

If the problem persists or returns, you have a couple of options.  The most radical is to back up your files and do a clean install of the OS.  The do a clean install of Poser and yor other apps.  Time consuming and a pain but it will get you back to the beginning.  If you do go for a clean install, I recommend installing and using Toolwiz's TimeFreeze.  It's free so it won't cost you anything.  I find it useful but you would take a look at the site and decide if it something you would find useful.

A less radical option is to uninstall Poser.  Completely.  Back up any files you don't want to lose to another drive or flash drive.  Then delete eveything, including any left over registry entries.  Same goes for Flash and Air.  Delete both of them.  You posted McAfee reappeared on your system.  That's probably from one of your system restores.  If you it isn't supposed to be on the system, get rid of it.  Once you have everything cleared out and cleaned up, you might want to run defrag and any hardware checks if you haven't done them lately.

After you are done with house cleaning re-install Poser.  Flash and Air are part of Poser's installation.  In fact, if you don't use Flash or Air for any other app or any other reason, you can block the auto updates through the fire wall.  I have multiple versions of Poser running on the same workstation at home (P5 through Pro 2014) without a problem.  In fact, SMS tech support told me back in the P8/Pro 2010 days that the version of Flash and/or Air that installs with Poser is optimized to work with Poser. 

What does SMS tech support tell you?

Upirium

icprncss said:

Sorry but I don't have any assurances for you as I have no idea what caused the problems in the first place.  You would need to go back and review all of the Windows crash logs and the Poser crash logs.  In the end, a long drawn out process that may, in the end tell you nothing of value.

If the problem persists or returns, you have a couple of options.  The most radical is to back up your files and do a clean install of the OS.  The do a clean install of Poser and yor other apps.  Time consuming and a pain but it will get you back to the beginning.  If you do go for a clean install, I recommend installing and using Toolwiz's TimeFreeze.  It's free so it won't cost you anything.  I find it useful but you would take a look at the site and decide if it something you would find useful.

A less radical option is to uninstall Poser.  Completely.  Back up any files you don't want to lose to another drive or flash drive.  Then delete eveything, including any left over registry entries.  Same goes for Flash and Air.  Delete both of them.  You posted McAfee reappeared on your system.  That's probably from one of your system restores.  If you it isn't supposed to be on the system, get rid of it.  Once you have everything cleared out and cleaned up, you might want to run defrag and any hardware checks if you haven't done them lately.

After you are done with house cleaning re-install Poser.  Flash and Air are part of Poser's installation.  In fact, if you don't use Flash or Air for any other app or any other reason, you can block the auto updates through the fire wall.  I have multiple versions of Poser running on the same workstation at home (P5 through Pro 2014) without a problem.  In fact, SMS tech support told me back in the P8/Pro 2010 days that the version of Flash and/or Air that installs with Poser is optimized to work with Poser. 

What does SMS tech support tell you?

as an update, it seems to be working again...for the time being

I don't know how or why

I deleted all the offending poser files (I had like six or something that were crashing, more or less everything with reptilian 6 legs. And jungle girl outfit? idk why that would matter though)

I thought of completely uninstalling Poser and I already had done that before this happened but didn't uninstall the files from the Program Files folders.

I am really scared of mess with the registry tbh

Here's the poser crash logs from when I tried to load those files.

Faulting application name: PoserPro.exe, version: 10.0.4.27796, time stamp: 0x53d9b4ab
Faulting module name: ntdll.dll, version: 6.3.9600.17936, time stamp: 0x55a68e0c
Exception code: 0xc0000005
Fault offset: 0x000000000003518c
Faulting process id: 0x19a0
Faulting application start time: 0x01d0d91d79fa31df
Faulting application path: C:\Program Files\Smith Micro\Poser Pro 2014\PoserPro.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: 4fcc986d-4511-11e5-827a-90489ad6d78e
Faulting package full name:
Faulting package-relative application ID:

 

 

edit:

I will also note here and in the main post exactly what was on this figure, though I don't know if that's the problem.

He had Lilith Strigoia for V4 wings parented to his chest

He had the tail for Jezebeth for V4 parented to his pelvis.

He was wearing Jungle Girl skirt

and in the seocnd instance, Jungle Girl necklace.

He had Reptilian 6 legs.

He had instances of Creature Creator used on him (teeth, claws, ears)

Edited for language

Tobor

I keep pretty tight ship and I have issues like this with Poser 2014. In all, I find fairly buggy, which is one reason I don't use it as much these days. Sometimes, it will crash within seconds of loading (likely having to do with the content navigator). Restart ,it's fine. I've learned not to touch even the mouse when Poser is loading.

I think in general it's a good idea to regularly restart your machine when using any 3D appliications. Happens with Daz Studio too sometimes. A few weeks ago, Daz crashed, and then wouldn't restart. Double-clicking on the icon did nothing but load it into memory, where nothing happened after that. Had to restart.

In case you didn't know, Poser's file format is less structured than the one Daz now uses, and is prone to fault. The files can get huge, especially if you have a lot of morphs loaded. Uf a file gets corrupted, it could cause Poser to crash when the scene loads. This also happens if the scene is set for a display mode that your system doesn't like. There are some tools (try Renderosity and Runtime DNA for cleaning up, fixing, and managing Poser scene files. For example, there's one (Poser File Editor, or PoserEd) that in addition to cleaning up files will insert full paths for content, if you're having trouble with Poser finding it in the runtimes.

On the slow dials issue: first thing to try is switch to wireframe view. The shader settings for your graphics card may have changed with all your uninstalls/installs/reinstalls. Going to a regular wireframe view will skip the realtime texture shader. If the dials now move, then your problem is in a graphics card setting, and/or the OpenGL settings in Poser.

Upirium

Tobor said:

I keep pretty tight ship and I have issues like this with Poser 2014. In all, I find fairly buggy, which is one reason I don't use it as much these days. Sometimes, it will crash within seconds of loading (likely having to do with the content navigator). Restart ,it's fine. I've learned not to touch even the mouse when Poser is loading.

I think in general it's a good idea to regularly restart your machine when using any 3D appliications. Happens with Daz Studio too sometimes. A few weeks ago, Daz crashed, and then wouldn't restart. Double-clicking on the icon did nothing but load it into memory, where nothing happened after that. Had to restart.

In case you didn't know, Poser's file format is less structured than the one Daz now uses, and is prone to fault. The files can get huge, especially if you have a lot of morphs loaded. Uf a file gets corrupted, it could cause Poser to crash when the scene loads. This also happens if the scene is set for a display mode that your system doesn't like. There are some tools (try Renderosity and Runtime DNA for cleaning up, fixing, and managing Poser scene files. For example, there's one (Poser File Editor, or PoserEd) that in addition to cleaning up files will insert full paths for content, if you're having trouble with Poser finding it in the runtimes.

On the slow dials issue: first thing to try is switch to wireframe view. The shader settings for your graphics card may have changed with all your uninstalls/installs/reinstalls. Going to a regular wireframe view will skip the realtime texture shader. If the dials now move, then your problem is in a graphics card setting, and/or the OpenGL settings in Poser.

I should note that I tried this before I system restored, the wirefram thing anyway.

And changing OpenGL to SREED or whatever it's called.

Pretty uch everything I could think of

the only thing that woudl work was arestore

and I'm still not sure why I needed to restart poser twice

I had only deleted the figure from the library that I had saved and not the files themselves where I saved the scene

could this have caused the issue?

DarkSpartan

iDiru said:

Tobor said:

I keep pretty tight ship and I have issues like this with Poser 2014. In all, I find fairly buggy, which is one reason I don't use it as much these days. Sometimes, it will crash within seconds of loading (likely having to do with the content navigator). Restart ,it's fine. I've learned not to touch even the mouse when Poser is loading.

I think in general it's a good idea to regularly restart your machine when using any 3D appliications. Happens with Daz Studio too sometimes. A few weeks ago, Daz crashed, and then wouldn't restart. Double-clicking on the icon did nothing but load it into memory, where nothing happened after that. Had to restart.

In case you didn't know, Poser's file format is less structured than the one Daz now uses, and is prone to fault. The files can get huge, especially if you have a lot of morphs loaded. Uf a file gets corrupted, it could cause Poser to crash when the scene loads. This also happens if the scene is set for a display mode that your system doesn't like. There are some tools (try Renderosity and Runtime DNA for cleaning up, fixing, and managing Poser scene files. For example, there's one (Poser File Editor, or PoserEd) that in addition to cleaning up files will insert full paths for content, if you're having trouble with Poser finding it in the runtimes.

On the slow dials issue: first thing to try is switch to wireframe view. The shader settings for your graphics card may have changed with all your uninstalls/installs/reinstalls. Going to a regular wireframe view will skip the realtime texture shader. If the dials now move, then your problem is in a graphics card setting, and/or the OpenGL settings in Poser.

I should note that I tried this before I system restored, the wirefram thing anyway.

And changing OpenGL to SREED or whatever it's called.

Pretty uch everything I could think of

the only thing that woudl work was arestore

and I'm still not sure why I needed to restart poser twice

I had only deleted the figure from the library that I had saved and not the files themselves where I saved the scene

could this have caused the issue?

It's not very likely. Poser can be squirrelly sometimes, but it's usually not this bad unless there's something else going on in the background. I would say go back through all the content you've installed recently, and remove anything you've installed up to a week prior to the onset of the problem. Save the rest of your Runtime to an external hard drive, and put this Poser install out of its misery.

Redownload the content you removed, reinstall Poser and add the external drive copy as a separate Runtime. If it's still working after that, then reinstall any content you redownloaded in step three to the external runtime. Then operate Poser normally. If you stop having the problem sum total, then you're good to go. You can recopy the external runtime to the regular folder if you like, or what have you.

If that brings the problem back, then start with a clean copy of WinBlows, and install your working files first-- with a complete redownload if possible (including Poser). If you can't redownload your Poser executables, you may have to put out a couple of bucks for their extended downlaod service or try an alternate software.

Truth be told, the thing that finally prompted me to finally make the switch from Poser to Studio was that G2 by way of the DSON importer made my life far more difficult than it had to be-- with the same sorts of symptoms you describe. Slow reactions, dials that hated me, etc. I like the Genesis line better than Generation 4, so I came out ahead using the soft that does the job natively. If I ever get the urge to render Aiko 3 again, then I'll switch back to Poser until it passes.

Upirium

DarkSpartan said:

iDiru said:

Tobor said:

I keep pretty tight ship and I have issues like this with Poser 2014. In all, I find fairly buggy, which is one reason I don't use it as much these days. Sometimes, it will crash within seconds of loading (likely having to do with the content navigator). Restart ,it's fine. I've learned not to touch even the mouse when Poser is loading.

I think in general it's a good idea to regularly restart your machine when using any 3D appliications. Happens with Daz Studio too sometimes. A few weeks ago, Daz crashed, and then wouldn't restart. Double-clicking on the icon did nothing but load it into memory, where nothing happened after that. Had to restart.

In case you didn't know, Poser's file format is less structured than the one Daz now uses, and is prone to fault. The files can get huge, especially if you have a lot of morphs loaded. Uf a file gets corrupted, it could cause Poser to crash when the scene loads. This also happens if the scene is set for a display mode that your system doesn't like. There are some tools (try Renderosity and Runtime DNA for cleaning up, fixing, and managing Poser scene files. For example, there's one (Poser File Editor, or PoserEd) that in addition to cleaning up files will insert full paths for content, if you're having trouble with Poser finding it in the runtimes.

On the slow dials issue: first thing to try is switch to wireframe view. The shader settings for your graphics card may have changed with all your uninstalls/installs/reinstalls. Going to a regular wireframe view will skip the realtime texture shader. If the dials now move, then your problem is in a graphics card setting, and/or the OpenGL settings in Poser.

I should note that I tried this before I system restored, the wirefram thing anyway.

And changing OpenGL to SREED or whatever it's called.

Pretty uch everything I could think of

the only thing that woudl work was arestore

and I'm still not sure why I needed to restart poser twice

I had only deleted the figure from the library that I had saved and not the files themselves where I saved the scene

could this have caused the issue?

It's not very likely. Poser can be squirrelly sometimes, but it's usually not this bad unless there's something else going on in the background. I would say go back through all the content you've installed recently, and remove anything you've installed up to a week prior to the onset of the problem. Save the rest of your Runtime to an external hard drive, and put this Poser install out of its misery.

Redownload the content you removed, reinstall Poser and add the external drive copy as a separate Runtime. If it's still working after that, then reinstall any content you redownloaded in step three to the external runtime. Then operate Poser normally. If you stop having the problem sum total, then you're good to go. You can recopy the external runtime to the regular folder if you like, or what have you.

If that brings the problem back, then start with a clean copy of WinBlows, and install your working files first-- with a complete redownload if possible (including Poser). If you can't redownload your Poser executables, you may have to put out a couple of bucks for their extended downlaod service or try an alternate software.

Truth be told, the thing that finally prompted me to finally make the switch from Poser to Studio was that G2 by way of the DSON importer made my life far more difficult than it had to be-- with the same sorts of symptoms you describe. Slow reactions, dials that hated me, etc. I like the Genesis line better than Generation 4, so I came out ahead using the soft that does the job natively. If I ever get the urge to render Aiko 3 again, then I'll switch back to Poser until it passes.

I think I may have narrowed the problem down to...something DSON related.

Poser works fine with any other thing than DAZ Figures

but DAZ figures previously worked fine.

it is just a recent thing

I had to restart three more times last night and it just kept getting progressively worse after each picture I did.

Someone told me to set the Subdivision levels to 0 and that made them move a lot better but I don't understand why...

it feels like the more times I use DSON, the worse it gets.