Forum Coordinators: RedPhantom
Poser - OFFICIAL F.A.Q (Last Updated: 2024 Dec 23 1:20 pm)
Well, first off, it keeps happening because you're on a PC, but that's another story altogether, I think. =) Frankly, this is a shining example of why computer engineers are not users: these enigmatic error messages that no doubt mean something to somebody, but few people I know. And it's no better on a Mac these days -- we get the all-purpose "error type 1" message, which usually means a conflict with something, somewhere, but no idea what and no idea how to fix it save go through some absurd, time-intensive testing of the extensions. Chances are it's something to do with your .rsr file. Try deleting that and starting afresh: Poser will rebuild your .rsr file for you, and maybe this time it'll get it right. =)
It also means that you need to download the current P4 patch available for free at the CuriousLabs site. It takes care of this as well as some other problems with the initial release that made it prone to freezing up.
I think we need a little more info to be able to help you out. When exactly do you get the error message? When you load the prop? Or when you move or manipulate it? In other words, what action do you think caused the error? And, oh, which prop exactly is it? A possible solution: delete the .rsr file of the prop (like VirtualSite said). Poser will generate a new one. As soon as Poser created it, make the file 'read-only', so it won't be screwed again (excuse my language) :) Hope it helps
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.
I am trying to use a prop (did I mention I was new?) and I keep getting this message ... "Caught C exception Access_violation trapped at 1b:47d299" Could you please tell me what this is and WHY it keeps happening?