I get this error with some figures, like This is the error: File has a newer version number then expected Poser will attempt to read it anyway. Then it crashes. What is causing this? Imaginos

The cause is... your using an older version of poser than the version the figure was created in. Example: You use Poser 3.01, and try to load a figure made for Poser4. -Rob

Noooo, I am using the version 4 that I bought in July. Thanks for the idea though. Imaginos

Do you have the patch loaded? Did the person who made the figure have it loaded? If they did and you didn't this might be the cause.

I've seen this as well. Mostly with the ultimate wigs posted a while back. Its harmless. It is, however, a good way for a creator to keep track of his goods by putting in a newer version number.

Let me preface this with the following. I work as a systems manager, and I also use poser 4.0, but I don't know about the internal workings of poser. My suggestions are system based and not Program based. There's probably an easy solution that I am unaware of, but I don't know and am open to suggestions. That said, I've gotten this message with some of the newer postings here on Renderosity. my computer's processor seems to work overtime when this error occurs. I have a P2-400 and 128 MB of RAM and my computer manages to eventually get through this with some heavy processing - but just when I think it's frozen or going to crash, the file loads up. I don't have a solution for the error, but there might be a way to get around the system crash. if you have any other applications open, close them. Try using Ctrl+Alt+Del to shut down all background programs. In the end, when you hit Ctrl+Alt+DEL you should see only these 3: Poser, Systray, and Explorer - close anything else that's open. It might free up some of your system resources to make whatever calculations it's trying to do. If you have a slow processor or not a lot of RAM, the strain might be too much for your system while it's running so many programs. When It's finally loaded up, maybe try an resave it so that next time the error won't occur. Sorry for going on, but like most people who don't know very much, I say a lot. Good luck. Let me know If you had any success.

But not everybody's got 128 Mbytes of RAM. I can't get an elephant's work out of a horse, and there's no point me trying to.

What I mean is that even a slower computer has resources that can be made available. Alot of programs running in the background can slow things down. I've had to do that with 3D Studio Max and it reduced the number of freeze-ups I experienced. Even a high resolution image on your desktop can steal resources from your computer. Your workhorse may have a little more life in it than you realize, provided you get rid of some of the excess bagage. It may not be the right answer, but I think it's worth a shot.

I do not have the patch loaded yet and did get the machine to stop crashung but I still get that error and my machine does go through a heck of alot of processing to open these files it gets that error on. My system PII - 400 128 Ram 32 Meg Vid AGP Win 98 Thanks for the tips. I will go hunt for the patch and run it. Imaginos

You didn't mention whether these are third-party figures or Meta's/Zygote's or a user's figures. I have Cacheforce's "PlanetErotica" CD & the poses (and I think the figures as well) give me that error and there is a slight delay, but it's never crashed on me before. If all the figures are from the same source it may be choking on something in the files after it checks the version number. Someone may have added something to the files Poser can't read.

If you're using Poser 4, check the cr2 causing the problem and see if the first line says Version 4.01. If so, change the 4.01 to 4.0. This has worked for me.

LOL, WarriorDL that is a great fix. Headhunter - they are all 3rd party. I fixed the crashing. I still get the error. Thanks Imaginos

Imaginos, Perhaps you didn't understand my reply. The "example" I gave was just that, an example... I wasn't saying you (read someone other than myself) are using any particular version, only that you were using an older version than the figure was created for... The rest of the example goes like this: figure built in 3.01, open in 3.0 = error figure built in 4.0, open in 3.0 or 3.01 = error figure built in 4.01, open in 3.0, 3.01 or 4.0 = error solution = change version number, Poser will disregard information that does not comply with what Poser understands for that particular version. Maybe I shouldn't have left the other options to deductive reasoning... -Rob

Imaginos, as long as it doesn't crash it's no problem. Poser just doesn't recognize the version # and is giving you a warning. As you've no doubt noticed, it WILL go ahead & read it anyway. Same as the message about "some information in this file does not pertain to figures of this type". It's annoying but nothing to worry about.

Rbtwhiz, sorry about the misunderstanding. Thanks for the help. headhunter, Thanks for the info. I will not worry about the error anymore :) everyone else, thanks for responding Imaginos