The above posts and solutions seems fine for certain situations....BUT I don't think it's a TOTAL solution. I've been having similar problems for months using building props and characters which use to render fine in Poser 4 but no longer in Poser 5. If you look at the image below you can see defects in the original building. And where the defect is it's on the same plane (Material section). If I try to render using the above methods all it does is change everthing. You still see the defective area. I have contacted Sams 3D (it's there original Haunter House)about this and there web site led me to this post. I've been told (from another source)that it appears to be broken verticies in the original model which to me is a defect in the original. Am I right or not? If this is the case then the original model (MESH) needs to be re-made if it is to be used correctly in Poser 5. The problem we are all seeing now is that Poser 4 did not see these defects and rendered them fine. Poser 5 sees them and this is the result. I've also encountered this problem with Andix 3D Modelz. Funny thing is I never see this with Travelers or Transponds (Runtime DNA)work nor do I see it in Marforno's (MnD Productions). This tells me that the ways those others mrechants are creating there original meshes for Poser 5 are doing it correctly FOR POSER. But the others are using a method that is not totally correct for the texture shading models needed for Poser 5. Can Curious Labs fix this? Is it a bug in Poser 5? I'm starting to have my doubts. There seems to be more than one problem here yet we are complaining about similar problems that Poser 5 is now seeing. I've been on this for over 6 months and still can't get a difinitive answer other than the broken verticies in the original model. I even contacted Curious Labs about this with no response.

Hey Allen, Here is what your car looks like after some modifcations. I was a little disapointed that the LWO model from Honda had the steering wheel on the right side inside of the US's left. Had to fix that. I still want MY CAR MODELED as this version is the older more box type looking car. Any takers?

Here is what my car looks like today with the new Euro converted Lights and Chrome Fender Flares and side panel trim. Also added are new Fog lights and Front wheel chrome wind deflectors and Stripping on the back quarter panels. It's hard to tell in the smaller images But who ever works on the car to model it with have larger images to go by. Also done on the car is a 3 coat Black metallic "Lamborgini" paint job.

Still Caleb68.....we get into the issue of ...is it really necessary to have such a small prop have such a large texture map? I hardly think so. In my opinion were going way overboard on getting detail here. Unless I'm doing an exteme close up of the prop it's totally unnecessary. Like I said before. I down sized it to 3500 pixels and that was more than enough. In my opinion this is more like a conflict issue with Poser not being able want to use a texture map larger than it wants to (than a memory issue). If you read my specs above on my machine. a 1400 MHZ machime running 512MB or RAM is more than enough. I even went so far as to partition my duel 80 GIG hard drive so that Windows has it's own partition and can run with no interference. I still would like to know how others were able to use that file and not I. Were they using that large texture map like I was? If so how did they get around it? I had my machime optimized so that I took full advantage of RAM and memory and had not conflict issues like in the past.

Last night after looking at the Poser screen of my error and thinking how come I'm getting this error and nobody else is....I started to stare at the supplied png thumb that was supplied with this prop. I looked at it and shook my head. How come this png thumb is too big. It's supposed to be 91x91 pixels. How could renderosity even approve this size. Then it hit me........file size....holy @#it. What's the file size of the supplied jpg's? I know for a fact that Poser can't render (or work with) texture maps larger than 4000x4000 pixels. Even Curious Labs doesn't recomend it. I had a problem in the past with errors and freeze ups in Poser 4. So I checked out the file sizes of the two supplied jpg.s Well what do you know...the Stairs jpg is 5000x3411. One dimension was too big. The Subway building jpg was 400x2163. HUMMMMMM...I though....Stairs prop won't load....Street prop does load. How can I test this out? Then I remembered that there were supplied OBJ files with this prop. So I thought why don't I just import the OBJ's resize and position them and add the textures manually. Well I did...and what do you know happened? As soon as I clicked on the 5000x3411 jpg to load it I got the error message again. Well that was it. That's why that prop would not load. It was my Poser program saying that It can't handle the file size. Rightfully so. So I re-sized that jpg file to 3500x2388 and it loaded fine with NO errors. Now my question to all of you is this? Why did I have the problem and nobody else seems to have this problem? We all know that the texture map file sizes should be no bigger than 4000x4000. Why did renderosity let this go through? Is there something I'm missing or don't know? Why was the oversized png file ok'd? Can someone explain this to me? Is there a way to get Poser to render larger image maps without getting errors? Should it even be done? And my last question.....Why the heck make a 5000x3411 texture map for such a small prop? Was that really necessary. My re sized one was more than enough. Why are so many of the merchants going past this boundry for the sake of more detail? Come on get with it. Look at the problems your causing. Now it's OVER.....I never forget this and I hope we all learned from today's lesson. DEVON

You better believe it's the file I downloaded today and NOT my computer. I did a test of the Props and first re downloaded the files to get a second copy. Then reinstalled them. Then I decide to save the two parented props as seperate props and Lo and Behold......the Street prop works but the Stairs prop is bad. The only way we will know for sure is if someone takes my bad stairs prop and tries it out. I need a new file "Fresh" and Not from the server that the current one is on and re test it. I can tell you this after doing this test....It's the Prop file that is BAD. Not my computer or Poser 5. See the attached pics for Proof.

I checked Microsofts Knowledge base and could not find anything on this error. This has to be a Poser 5 problem . I did update to the first patch but did not install the second beta Patch. Was wondering if this might solve the problem. I never got this error message before using Poser 4 Pro pack on this same machine. This started with Poser 5 and only this file....so far.

Thanks Caleb68 for the suggestion. I did find a spotLight 1_shadow_0001.tmp file in there and took it out but that did not help. If anyone knows what that exception error means we might be able to know what the problem is. I know Microsoft has definitions for all there error messages. Wonder if the People at Curious labs can tell us what this is. I've contacted them on a few ocassions about problems but they never answer me.

Well I can't figure this out. I can't see this being a system error if we all are Running Windows XP Professional. I even disable my Virus protection because of past problems. Don't seem to be having any problems with other files. Can't figure this out. Anyone have any suggestions? Could this file be bad after the download or something? I have a 14oo MHZ ADM Athalon with 512 MB of ram. Does anyone know what that error message means?

Attached Link: http://home.cfl.rr.com/greenhornet2002/

You might not claim to understand much about lights, but you hit the nail on the head on this one my good man. You were right. It worked. My problem was I was saving all the subset lights much like when saving props. I had a bad habit of saving props the wrong way in the past. I kept forgetting to save the sub sets or parented props to it to get the entire package. I thought all this time I had to do the same thing with the lights. Never realised or tested it out the other way. Go figure. Thanks what's so great about the Renderosity community. Always a fellow helping hand member.....I thank you so very much. DEVON

Hey at least I can use the lwo files of that car for junk yard parts. hehehee

Attached Link: 1990 Honda CRX model

Just wanted to clear this up. I want my CRX model to look EXACTLY like my own car. NOT any basic stock look. Unlike the other image above, mine will have the rear wing and louvers along with the exact style chrome wheels. I will also have chrome acent fender flares and side panels put on next month. That's why I'm waiting before I want it done. I also have neon lights under the car ala "Fast and the Furious" which I was hoping to have modeled.

Attached Link: 1990 Honda CRX model

That's the ORIGINAL 1985 Version 1 CAR.....THAT"S NOT the look of my car and NOT what I'm Looking for. I have VERSION 3 and my car looks way different as you can see in the pictures. But it's a start if you can take the model and change and/or add to it. Thanks DEVON

I finally found the problem. Thanks to everyone for your help. I just wanted to let you know that I had a computer technician come over to look at my computer and found out the following. I did not have a Volcan 6 cooling fan on the CPU as I was told. So that needs to be corrected and My Motherboard was found to have heat spots on it and a voltage regulation problem. Since this started around the time I installed Windows XP we have to assume XP caused the problem since it allows the Hardware to run faster than Windows 98...hence that's why things got hotter.

Glad to know your Poser Folder is 18.9 GB. I thought mine was big at 11GB. It seems that I only had problems with them loading when I got down to the bottom of the list. Usually around the t's to the z's. Maybe it's a problem with the PNG thumb generations. I'll look into that. I was only having problems with the Pose folder. I'm running Windows XP professional...1400MHZ AMD Athalon with 512MB RAM and G-Force 3 64MD video card. Thanks for your reply.