Wed, Nov 20, 9:38 AM CST

Renderosity Forums / Poser - OFFICIAL



Welcome to the Poser - OFFICIAL Forum

Forum Coordinators: RedPhantom

Poser - OFFICIAL F.A.Q (Last Updated: 2024 Nov 20 6:12 am)



Subject: AAARRRGGGHH... Going potty with out of memory


Royfitz ( ) posted Tue, 29 December 2020 at 7:10 PM ยท edited Wed, 20 November 2024 at 9:26 AM

I've posted umpteen times today, trying to get Daz V4 to install. All sorted, it worked - ONCE.

Now, every time I try to open the V4 figure I get 'out of memory' and it won't work. HOW do I allocate more memory - even if it's possible???


HartyBart ( ) posted Tue, 29 December 2020 at 7:18 PM

Did you first 'initialise' V4? This is a one-time operation that must be done after first installing, and is accomplished by running the two Windows .BAT files likely to be found down in: Studio . content . Runtime . Libraries . !DAZ



Learn the Secrets of Poser 11 and Line-art Filters.


Rhia474 ( ) posted Tue, 29 December 2020 at 7:34 PM

Also, you are using a very old version of Poser with an old Windows. So yes, it is quite possible. Try the initializing first, then try emptying your cache.


randym77 ( ) posted Tue, 29 December 2020 at 9:21 PM

Just in case you missed this from the DAZ ReadMe file:

Why is it taking so long to load V4 in Poser?

As mentioned in the "What's new in Victoria 4.2" section above, "Due to the way Poser reads the ExP files, it is strongly recommended that Victoria 4.2 be kept in the default Poser Runtime. DAZ Studio users can place Victoria 4.2 in an external folder if desired."

The .cr2 file can be moved to an external Runtime, but the files in the Libraries:!DAZ folder should be kept in the default Poser Runtime. If the !DAZ folder is moved to an external Runtime, Poser first looks in the default Runtime, then starts looking through all files on all hard drives for the files. This can take a very long time to complete, as much as 15-20 minutes.

FWIW, I have V4 in an external runtime, but I keep all the !DAZ stuff in the primary runtime.

And you should try to clean up the extra files from your aborted install attempts. Multiple copies of the morph files can confuse Poser.

I don't think it's the size of V4 that's the problem. IIRC, without morphs, she's the same size or smaller than V3. I think V3 actually has more polys than V4.


hborre ( ) posted Tue, 29 December 2020 at 10:49 PM

@randym77: That statement isn't true about installing V4 into the default Poser runtime and it really needs to be updated. It was true when DAZ was packaging everything in .exe files but not anymore. On another computer, I installed V4 and all her morph packages into a secondary runtime located on a separate HD. No problems loading her into Poser.

@HartyBart: If you're only using Poser, as Royfitz is doing, you only need to initialize the one .bat file as needed.

Since we have no idea how antiquated the Operating System is and we are already working with P5, there is no telling if V4 will actually load at all, given that DAZ is suggesting a minimum requirement of P6.


randym77 ( ) posted Wed, 30 December 2020 at 5:00 AM

He said in another thread he's using Windows 7.


ghostman ( ) posted Wed, 30 December 2020 at 5:14 AM

Everytime I've updated Poser and then added my V4 Runtime it took longer to load the first time. Once I've resaved my V4 it went smoother again the next times I loaded her.

"Dream like you'll live forever. Live like you'll die tomorrow."

Join PoserLounge Chat


randym77 ( ) posted Wed, 30 December 2020 at 5:50 AM

Re-saving might fix the "wrong version" error message, too. Something I've run into now that I'm using both Poser 11 and 12.


Royfitz ( ) posted Wed, 30 December 2020 at 11:47 AM

Many thanks for all the advice chaps. I haven't given up on V4 completely - yet...


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.