Wed, Nov 13, 6:30 AM CST

Renderosity Forums / Poser - OFFICIAL



Welcome to the Poser - OFFICIAL Forum

Forum Coordinators: RedPhantom

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



Subject: Executable Crash


l3st4t ( ) posted Mon, 27 August 2007 at 9:41 AM · edited Wed, 13 November 2024 at 6:23 AM

Hi all I'm working with Poser7 and Victoria 4 and Michael 3.

I was wondering if anybody of you has ever experienced the problem I had.

I create a new document, I load both V4 and M3 (have to say that are  previously morphed models and saved as models) and I start posing.

Once I'm done with the first pose, I save the scene.

Then, I start posing again on the base of that previously saved file.

Once I'm done, I "Save as" this scene too, paying attention on switching the name into a new one(obviously, in order not to overwrite it).

here comes the pain in the a**: once i try to either load the first file or the other, the executable crashes and quits Poser7.

I noticed that it something that happens randomly, because I tried once again to load V4 and M3, posing 'em in two different positions and then again save those two different scenes as two different files, but it runs smooth.

I don't know either it's a problem with M3 or V4 or the executable itself. one thing is sure, it never happened before (at least with V3) .And believe me, after hours working it's really frustrating.

Please please please help me if you can or at least send over tons of handkerchiefs for I'm swimming in tears.


pjz99 ( ) posted Mon, 27 August 2007 at 10:14 AM

Depending on when you downloaded V4, you may have buggy morph data.  The latest version out for download seems to be OK.  In any case, try turning off "Use external binary morph targets" in Edit -> General Preferences -> Misc.  This may not help you recover a broken file, but it can help you avoid this kind of problem in the future.

Caveats are your save times will take longer, and file sizes will be much bigger.

My Freebies


l3st4t ( ) posted Mon, 27 August 2007 at 12:04 PM · edited Mon, 27 August 2007 at 12:05 PM

First of all, thanks for the answer. Well, I do not exactly remember when I downloaded the V4, but it was the base model included in the V4 pro bundle pack (and I'm actually working with "Helena").
I'll be trying by changing the Gen Pref settings as you suggested. Don't you think that reinstalling another V4 base may solve the problem? Or it is just a morph related problem?


Morgano ( ) posted Mon, 27 August 2007 at 6:30 PM

V4 has had two versions.   In the original, she was nude and bald.   In the Vicky 4.1 edition, she loads wearing a fuzzy bikini and has an anti-typhus hairdo.   I don't think that installing V4.1 can rescue your file (assuming that it was created with basic V4), although...

...V4.1 needs the folders called "DAZ People" in the main Poser directory path, i.e. not in an external runtime.   If you installed V4 into the main Poser runtime, so that you can replace V4 with V4.1 in the same directory path, I suppose that you just may have a chance to re-open the file that way.   If you are lucky and one or other saved file opens, immediately follow what pjz99 said.

Otherwise, you need to play tricks to save memory, I suspect.   Close anything that doesn't need to be running, before trying to open your file.   Once Poser is open, minimise it and then maximise it again, before attempting to open the file.   You may find that a reasonable amount of memory is freed by these gimmicks.   Again, if ever you get the saved file opened this way, refer to the instructions from pjz99.


pakled ( ) posted Mon, 27 August 2007 at 9:26 PM

oh, ok..I always considered 'crash' and 'executable' to be antonyms..;)

I wish I'd said that.. The Staircase Wit

anahl nathrak uth vas betude doth yel dyenvey..;)


l3st4t ( ) posted Tue, 28 August 2007 at 3:27 AM

Quote - oh, ok..I always considered 'crash' and 'executable' to be antonyms..;)

As a matter of fact, they should be! LOL :)


l3st4t ( ) posted Tue, 28 August 2007 at 3:55 AM · edited Tue, 28 August 2007 at 3:59 AM

Quote - V4 has had two versions.   In the original, she was nude and bald.   In the Vicky 4.1 edition, she loads wearing a fuzzy bikini and has an anti-typhus hairdo.   I don't think that installing V4.1 can rescue your file (assuming that it was created with basic V4), although...

...V4.1 needs the folders called "DAZ People" in the main Poser directory path, i.e. not in an external runtime.   If you installed V4 into the main Poser runtime, so that you can replace V4 with V4.1 in the same directory path, I suppose that you just may have a chance to re-open the file that way.   If you are lucky and one or other saved file opens, immediately follow what pjz99 said.

Otherwise, you need to play tricks to save memory, I suspect.   Close anything that doesn't need to be running, before trying to open your file.   Once Poser is open, minimise it and then maximise it again, before attempting to open the file.   You may find that a reasonable amount of memory is freed by these gimmicks.   Again, if ever you get the saved file opened this way, refer to the instructions from pjz99.

Yep, nude and bald, it's definitely that V4 we're talking about.
Regarding the folders/directory, once installed I managed them in a very personal manner...I wonder if that might be the reason why V4 screwed up (and not by the meaning we all like LOL)

First of all I made sure to put everything in the "Downloads" path in order to leave the Poser1-7 stuff aside. Then, in the Figures dir we have the DAZ people dir which contains subs I named M3, V3, V4..Each one contains folders like Models, Characters, Hair, Clothing, Poses, Morphs, Materials. I did it manually, sometimes...ehr...Renaming some folders ^_^

I know, it might seem sick and you can call me Adrian Monk (LOL) but if those add-ons won't work because of this, then I don't want Poser anymore! (LOL)

Jokes aside, yesterday I tried again by following the pjz99 suggestion and with the same figures which caused the application to crash. Everything runned smooth, and today I'll be trying to turn the "binary morph" option back on again. That's just to check whether it's a lack of memory problem or not.

Concerning the V4.1...I know you'll be laughing at me, but I'd rather go on with the actual V4 as long as it doesn't cause crashes,  'cause I'm too scared to completely mess up Poser LOL ^_^

Thanks Anyway, I'll be keeping the community updated on this issue for anyone who might experience those kind of problems :)


pjz99 ( ) posted Tue, 28 August 2007 at 6:21 AM · edited Tue, 28 August 2007 at 6:25 AM

Quote - Yep, nude and bald, it's definitely that V4 we're talking about.

Then you have the bugged version, and may experience crashes in a few different ways..  Don't worry, you still get the nude texture with v4.1, just the default "free" texture with the crappy blue undies and swirly painted hair is added in besides.

ps:

Quote - Each one contains folders like Models, Characters, Hair, Clothing, Poses, Morphs, Materials. I did it manually, sometimes...ehr...Renaming some folders

Then there is a good chance you broke some of your content even if you don't realize it now, because many things within different content files refer to file/pathnames that you may have just renamed.

My Freebies


l3st4t ( ) posted Tue, 28 August 2007 at 7:02 AM · edited Tue, 28 August 2007 at 7:04 AM

Quote -
Then you have the bugged version, and may experience crashes in a few different ways..  Don't worry, you still get the nude texture with v4.1, just the default "free" texture with the crappy blue undies and swirly painted hair is added in besides.

So do you suggest me to update to 4.1?

Quote -
Then there is a good chance you broke some of your content even if you don't realize it now, because many things within different content files refer to file/pathnames that you may have just renamed.

Well, I tried not to rename any of the add-on folders I've installed, at least not the ones which were requested to be kept untouched as specified into their ReadmeS.
If by chance I ever unintentionally broke some path,  do you know if there's a way different by the straight  uninstalling/reinstalling content to check out and eventually correct the broken paths?

Thanks a lot for your steady assistance Pjz99, it's something anyone should pay for  :)


pjz99 ( ) posted Tue, 28 August 2007 at 8:18 AM

Yes I strongly recommend you switch to 4.1, if nothing else to get access to a good number of new face morphs that aren't included in vanilla V4, but also to fix that bugged morph data.

Uninstalling your content will probably no longer work since you've renamed directories.  Most of the content distributed in zip files isn't really "uninstallable" anyhow, but you can delete the files you copied in if you knew where you renamed them to.  I don't even want to try to advise you as to which is safe to rename and which is not, because there's really a lot of variables.

My Freebies


mofolicious ( ) posted Tue, 28 August 2007 at 2:41 PM

Here is what worked for me, I had the exact same problem.  Go into general preferences and change the number of "undo's" to 10 instead of 100.


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.