Just fired this off the CL yech support. Now getting "Caught C exception access_violation trapped at 1b:0" after changing a bump map for a displacement map. was able to clear the error and go back to the pose room and it seemed to be ok till I attempted to select render options and i got the error again, I cleared that error. and attempted to render with the currebt settings p4 render engine using everything except anti-alias and ignore shader trees. it did the render and on a second pass anti-alias render which it did without error. I was also able to save the image and the pzz. I then attempted to re-select the render options and still got the same error as above. also on this system i was required to re-register and after resetting my preferences, and restaring the system. the parameter window, figure circle were still in the wrong place and set to active. This was after following the instructions with the updater and doing a re boot after the install. system specs OS win2K with SR3 1Ghz athelon thunderbird 1024 MB sdram pc133 Gforce2 400 MX video 2 40 gb hdd ata 66 7200 rpm (1 hdd is OS, the other is poser) followed a renderosity thread and turned down video HW acel one notch. video passes all daigs and has no problems in any other application

Seems to happen when firefly is used I shut down the system and re started clean loaded poser, verified the patch was in and then loaded a V2 and a steph. I was able to set the option to firefly with displacement off and do all polygons and once i hit render I got the exact same Caught C error as above, then poser locked out hard and the system needed shut down to regain control of the system. However with one figure the firefly will render. and poser4 render engine seems unaffected. The patch on an up note does now seem to render in poser4 mode faster.

Hi, So far I've seen three of them, all of them trapped at 1b. So the question is, what's at 1b? I'm asumuming it's protected memory, a hunch tells me it only appears after the programs been active a while, but you were obviously expecting it, so what is it? later jb

"The SR1 patch may display a Caught C Exception dialog, followed by an alpha-numeric sequence. If you encounter a C exception, please forward off the alpha-numeric sequence or a screen shot to bugs@curiouslabs.com If you encounter this warning dialog, click OK to exit, save a copy of your file, and restart Poser." Well, someone knew this might be a problem, but it doesn't say what the 1b exception is related to. Don't understand the following either: "The SR1 patch may not correctly install if you have uncompressed the content files originally installed with Poser 5. If you have uncompressed these files, please recompress them before installing the patch." What does this mean?

You can run a python script which will uncompress all the content files, odds are if you're not sure what this means, then you haven't done it! cheers, -J

reiss-studio, I think you're right. :-) I'm a little concerned about the "reregister(?)" issue and other things. I think I'm going to wait on installing this sucker until we know if it does more good than harm.

Attached Link: http://www.reiss-studio.com

Well there shouldn't be a "re-register" issue. But the patch will only work once you have registered Poser 5. It won't work on a Poser during the trial period. So people might have tried to install the patch over an unregistered Poser 5, and been forced to authorize while installing the patch. I've been told that the patch is much more stable than the original P5 release, and now tells you when an error is happening which is why people actually *SEE* an error dialog, as opposed to the app just crashing when something is wrong, after a while. with the error dialog popping-up, CL can now debug the problems much quicker for the *next* patch :) -J

Yes, you're right. It's very disconcerting to just have the program stop, shut down or, worse, freeze the OS altogether. I'd rather see an error dialog than nothing.

If you do notice a C exception error, please send the ENTIRE error message along with the steps to reproduce the problem and your complete system specs to bugs@curiouslabs.com. The mor einformation you provide, the better we will be able to analyze the problem and create a better solution. Thanks! :-) Anthony Hernandez Curious Labs

So Anthony, I haven't got the error (Yet). But now I'm curious.. What is it? What's going on that you guys expected potential problems with in the renderer. Tom

Got it. I saved as per the instructions, but when I tried opening the .pz3 file, the view screen was all white and the menu controls we disabled. I was able to import the scene however. I had to reset the lights and the camera, but at least I didn't lose 3 hours of work. This is the first thing that really p*sses me off. I'm a programmer, and to release something with this kind of warning because you expect the problem to happen is very unprofessional. I know we all wanted the patch A.S.A.P, but I'd rather they didn't include the "fix" that caused this problem. We're in effect, alpha testing for them. I get paid for this kind of work, my rate is $50 an hour. Are we going to get compensated? CL owes us for this one. Kupa, you listening? How about making the Millenium figures fully P5 complient? Or changing the registration system? I was pretty happy with P5 (still am, really), but this kind of thing gets in my craw. I love all the new features, and everything worked for me BEFORE I installed the fix. The problem happens with using displacement maps in production firefly for me. If I do a production render, even with raytracing on, and don't use displacement maps. I don't get the error. The render turned out pretty good, and I'm posting it. It would have been better with the maps. P4 renders work just fine. When you send your error code to CL, be sure to inlude your ops system and hardware configuration. It may be specific to one of these. Rant over. I won't even talk about how dorky Don is.

pdxjims - if you're a programmer, you probably know all about C's nasty tendency to poke its prying little fingers into all sorts of memory locations where it's not supposed to go. The CL gang at least TELLS us that this is what's happening, most other apps just keel over and that's it. I agree we're alpha testing for CL, but we're alpha testing for M$, too. And Adobe. And Corel. And...