Fri, Jan 3, 9:37 AM CST

Renderosity Forums / Poser - OFFICIAL



Welcome to the Poser - OFFICIAL Forum

Forum Coordinators: RedPhantom

Poser - OFFICIAL F.A.Q (Last Updated: 2025 Jan 03 8:14 am)



Subject: obj. file go bad???


KimberlyC ( ) posted Thu, 15 November 2001 at 9:39 PM · edited Fri, 03 January 2025 at 9:05 AM

i just got acouple things ..about a week ago..i've used them 2 times...and now when i try to use one of them..it says it can't open the obj. does anyone know...y that is happening...and/or how to fix it.... Thx!!



_____________________
.::That which does not kill us makes us stronger::.
-- Friedrich Nietzsche


Mesh_Magick ( ) posted Thu, 15 November 2001 at 9:50 PM

Yeah this happens to me alot from some of the items I obtained from poser world, I do not know what causes, But I can tell you what is happening. The rsr files are becomming corrupted each time you load the figure into poser, What you need to do toi get the figure to load is delete the rsr file in the riuntime geometrys folder, how to permanently fix this problem I don't know yet.


KimberlyC ( ) posted Thu, 15 November 2001 at 9:54 PM

thanks...i'll try it :O) ... Angel :)



_____________________
.::That which does not kill us makes us stronger::.
-- Friedrich Nietzsche


rodzilla ( ) posted Thu, 15 November 2001 at 10:13 PM

i've never had this prob myself but seen lot's of messages about it...now this is just a thought but, would making the offending rsr files "read only" be a way around this??i assume once created poser doesn't need to modify them?does it?just right click on the file go to properties and check the lil box...that SHOULD prevent the file from getting screwed up by whatever is doing it...or am i way off base and just not understanding the purpose and use of these files?


KimberlyC ( ) posted Thu, 15 November 2001 at 10:18 PM

dunno..smile...but i went ahead and put one of them on read me only....soo...lets hope for the best..thanks both of u... :)



_____________________
.::That which does not kill us makes us stronger::.
-- Friedrich Nietzsche


Mesh_Magick ( ) posted Thu, 15 November 2001 at 11:41 PM

I think poser modifys them because I did not save resave the file, When I was done I deleted it, now if this saves a copy of it on the clipboard or in windows temp then maybe that had something to do with it, But the rsr files do become corrupted and then the cr2 script can't locate the obj geometry for some strange reason, deleting the rsr files clears it up and allows the figure to generate a new rsr file that becomes corrupted maybe when you exit poser?


KimberlyC ( ) posted Thu, 15 November 2001 at 11:44 PM

i'm thinking it maybe cause..my poser has a hard time closing so i have to alt ctrl delete so it'll close...



_____________________
.::That which does not kill us makes us stronger::.
-- Friedrich Nietzsche


Stormrage ( ) posted Thu, 15 November 2001 at 11:55 PM

Making the rsr's read only keeps the file from going corrupt and also makes it load easier. Poser rewrites the rsr's (at least on pc's ) so if it loads bad on one load it will corrupt. Delete the rsr load it, once done set the attribute to read only and the next times you load it it won't do that. ryuslilangel, I have to control alt delete when I run out of memory with poser. That could be the problem you are having. Not sure but it sounds like it.


KimberlyC ( ) posted Thu, 15 November 2001 at 11:59 PM

run out of memory with poser....can u explain alil...is that a bad thing..cause that has happened ever since i started using poser....



_____________________
.::That which does not kill us makes us stronger::.
-- Friedrich Nietzsche


Stormrage ( ) posted Fri, 16 November 2001 at 12:12 AM

how much memory do you have on your computer? The objs props textures and everything (including poser itself) take up memory If you have other things running this also takes up memory. More you have running the less you have to work with. And the more you load the less you have to work with in memory


KimberlyC ( ) posted Fri, 16 November 2001 at 12:18 AM

Capacity 14.2GB....and have about....9.04GB free....



_____________________
.::That which does not kill us makes us stronger::.
-- Friedrich Nietzsche


Stormrage ( ) posted Fri, 16 November 2001 at 12:30 AM

shaking head no S what i mean is memory.. That's harddrive space.. Memory.. My computer is a 133 mhz system with 128 megs RAM-Random Access memory. But how much Memory or RAM does your computer have?


KimberlyC ( ) posted Fri, 16 November 2001 at 12:34 AM

63.0 MB of RAM...sowwy....i feel silly :)



_____________________
.::That which does not kill us makes us stronger::.
-- Friedrich Nietzsche


Stormrage ( ) posted Fri, 16 November 2001 at 12:38 AM

S Don't feel silly.. :) It's late S Ummm yeah 63 mb RAM is a little low for poser You might think about getting more RAM for your computer. I have 128 and even I am thinking of getting much much more memory


KimberlyC ( ) posted Fri, 16 November 2001 at 12:40 AM

yea..i'm having a hard time of adding a second person like micheal with vikky..etc..or adding a prop...slows it down badly most of the time..... :)



_____________________
.::That which does not kill us makes us stronger::.
-- Friedrich Nietzsche


Stormrage ( ) posted Fri, 16 November 2001 at 12:44 AM

Mike and vicky are higher density meshes than posette or dork.. All your memory is in use.. Windows uses memory, if you run anyother programs along with Poser you are using up your memory so adding more than one figure in the scene is really pushing it for poser. Not sure where you are located but Up here in canada the price of RAM is really cheap.. 40 dollars for 256 megs.. if your computer can be upgraded I would definately do that as soon as you can. You'll find Poser and your comp runs a lot better Storm


KimberlyC ( ) posted Fri, 16 November 2001 at 12:47 AM

Yea...i've been thinking of upgrading it alil..things will run better with a lil more memory smile... :)



_____________________
.::That which does not kill us makes us stronger::.
-- Friedrich Nietzsche


Mesh_Magick ( ) posted Fri, 16 November 2001 at 12:55 AM

I have a 2 gig chip on mine 256 megabytes but still runs slow when I load large textures and renders slow when multiple lights are in the scene or multiple figures, I hope poser 5 when it comes out runs a faster and takes better advantage of memory.


Mesh_Magick ( ) posted Fri, 16 November 2001 at 12:57 AM

I have 20 gig hard drive a my c drive will this slow it down? I figure the computer has to read the entire drn thing before rendering I guess.


boblowery ( ) posted Fri, 16 November 2001 at 5:08 AM

The following is what I think. If your drive is a 20gig drive and you have only one partition you are writing your rsr file at the same time that the OS is writing the swap file and the files become fragmented. This could cause corrupt files. A suggestion would be that you save all your data files to another media {another partition or burn a cd} then next time you have to reformat {you will eventually need to do this} you partition the drive with about 3.5 to 5 gigs for the OS and OS related files {printer, scanner or other hardware files also utilitys like zippers ect. that must be loaded with the OS}. This size partition will allow room for swap files. One nice feature of partitioning is that you will not have to give up files when reformat time comes. Also there will be no need to reload Poser, Bryce, RDD or several other programs as they will work without reinstalling every time you format. Also 64 megs of RAM is a little below what is needed to effeciently run any of your graphics programs, 128 is just about minimum and the more you can get a hold of the better you will like the performance of the machine. Think of RAM as horsepower in a truck and the program as the load. The more horse power, the faster you climb that big hill.


Jim Burton ( ) posted Fri, 16 November 2001 at 8:56 AM

Incidently, I would say 128 Mb is about the minimum to work nicely with 1 Vickie and her clothing, with Dina at least 256 Mb. That is on a PC, I'd say Mac's need more, I seldom can open Vickie II on my Mac with 256 Mb, Dina never opens. Vickie has twice the polygons of the Posette, Dina 4 times that of Vickie, many of us aren't quite ready for Dina yet- Even my "new" computer with 512 Mb has barfed on two Dina's, I gotta fill that last RAM slot, memory is cheap right now, I remember paying $560 for 8 Mb back in the "good old days!"


Goldfire ( ) posted Fri, 16 November 2001 at 9:42 AM

ruys, I started out with 64 mgs of RAM and quickly upgraded to 128, ruys; it really speeds things up because the computer is not contstantly swapping stuff to the harddrive. RAM's cheap, too. Next computer I told my hubby we ARE getting at least 256 mgs of RAM. I still have problems because I tend to do very complex peices with lots of figures and props.


praxis22 ( ) posted Fri, 16 November 2001 at 10:21 AM

Hi, I have the "bad .obj" problem all the time, usually becuse I run out of memory and have to dump out of poser. So I'm assuming it writes back to .rsr files or something and dumping out of the prog corrupts them. Not sure why. Running something like memmax, etc. will help you keep memory free but it doesn't seem to completely solve the problem. Chalk this one up as a "classic" poser bug. The good news is deleting the .rsr always works. I have the same problem every time I open Billy-T's "angel toga" & sandals, I just accept it as part of life's rich pattern :) later jb


DraX ( ) posted Fri, 16 November 2001 at 11:34 AM

Hmmm... this is one of the reasons I love Pro-Pack so much.... rsr files are completely null and void, it only references the object file itself.


Maz ( ) posted Fri, 16 November 2001 at 7:13 PM

I have to say I've never come across the 'bad obj' problem even on my laptop with only 64MB of RAM. I've had all sorts of other problems, but not that one. My new machine is a 1.4GHz AMD Athlon machine with 512 MB of RAM and that really does zoom along when working with Poser. I've never bothered with Pro Pack, mainly 'cos I couldn't work out what it offered me. Anyone care to explain?


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.