seduced2cheat opened this issue on Feb 10, 2004 ยท 8 posts
seduced2cheat posted Tue, 10 February 2004 at 8:41 PM
OK. I have Michael 3 installed and am trying to load a figure and it is telling me I have memory issues. What's going on? I can load Vicky and the Freak, just not Mike. Is there something wrong or do I really need more memory. Also, how can I allocate more memory to Poser? Thanks, S2C
seduced2cheat posted Tue, 10 February 2004 at 8:54 PM
Additionally, read the FAQ and the .OBJ file is in the correct folder.
EnglishBob posted Wed, 11 February 2004 at 5:31 AM
If you have Windows (or, I think, later Mac OSs) you can't allocate more memory to anything - no matter, this particular error message from Poser is usually an indication that something else has gone wrong which the programmers haven't provided a message for. If the OBJ is in the wrong place, it should tell you that first of all before you get the memory error; but the DAZ installer shouldn't make that mistake. A few questions first. What version of Poser, and what operating system? Did Mike ever work, or have you just installed him?
seduced2cheat posted Wed, 11 February 2004 at 6:56 AM
Poser 4 and Windows XP. Yes, mike did work. Thanks for the help. In my searches I turned up an article from DAZ Faq that said take out the .rsr files. Did this and lo and behold! Mike works! I think this may have solved the problem. Also, for anyone reading this message and they are trying to load Hi Res maps for Millenium figures in P4, change the files indicated in the folders to bump maps by loading the jpeg into poser and it will auto convert(I have Poser Artist which I am assuming is POser 4 repackaged). After this is done, the program should auto load the correct textures as a MAT pose. If you don't, it will keep searching for a .bum that isn't there. Thanks for the help. Think this problem is solved. S2C
EnglishBob posted Wed, 11 February 2004 at 7:10 AM
Good stuff. Glad it's fixed. The dreaded RSR problem will do that, because Poser 4 (= Poser Artist) uses the RSR in place of the OBJ for faster loading. If there is no RSR, it makes one; after that, the OBJ is ignored. As to why the RSR gets corrupted, that's unclear: but if you write protect the RSR after it's been regenerated that should avoid it in the future.
seduced2cheat posted Wed, 11 February 2004 at 11:14 AM
Thanks. I will try that S2C
AGentleMuse posted Thu, 05 August 2004 at 10:25 AM
Just had to reply and say Thanks to you all!, was having a problem loading V3 and it kept saying cannot read runtime/obj etc etc, then would get the more memory message needed, I was at my wits end as this had been happening every few days so I was constantly uninstalling, reinstalling, lo and behold I come searching for answers delete the rsr and she loaded up first go! So big Thankyou's from this untechie newbie at poser lol hugs all Jen
EnglishBob posted Thu, 05 August 2004 at 10:46 AM
Nice to hear a success story. :) This problem with the RSRs is something that Poser 4 is plagued with. I think they tend to get corrupted if Poser crashes for some other reason, hence the write protect advice. Additionally, kudos to you for actually searching the forum for an answer, instead of just posting the same old question again which is what most members seem to do. :D