Tue, Feb 4, 2:50 AM CST

Renderosity Forums / Poser - OFFICIAL



Welcome to the Poser - OFFICIAL Forum

Forum Coordinators: RedPhantom

Poser - OFFICIAL F.A.Q (Last Updated: 2025 Feb 03 12:46 am)



Subject: Poser 4.0.3 Error Message


adtgeni ( ) posted Wed, 17 December 2003 at 11:42 AM ยท edited Tue, 04 February 2025 at 2:47 AM

Hi, I'm in trouble - after adding a new character by importing a poser file into an existing scenery I get the error (trying to translate it as good as I can, I'm using a localized version): 'The colour scheme doesn't exist or cannot be chosen' every time I try to render. Since I spent a lot of work already, I really like to keep the work as it is... is there a way I can locate the colour information that doesn't seem to fit, does the message point to something totally different from colour issues, or do I just have to forget it? Hopefully yours, Gerhard


geep ( ) posted Wed, 17 December 2003 at 12:43 PM

Um ... " ... importing a poser file into an existing scenery ..." Importing into what? ;=]

Remember ... "With Poser, all things are possible, and poseable!"


cheers,

dr geep ... :o]

edited 10/5/2019



RHaseltine ( ) posted Wed, 17 December 2003 at 12:44 PM

Is it giving a file name for a texture, such as a .jpg or .bum file? If it is then try opening that file (many should open if double-clicked, but .bum files will not). If the error names a .bum file try switching off bump maps (in Poser 4 it is one of the tick-boxes at the top right of the Render>Render options dialogue) and try to render again.


RHaseltine ( ) posted Wed, 17 December 2003 at 12:46 PM

Dr. Geep, I suspect he means loading a figure into a scene.


geep ( ) posted Wed, 17 December 2003 at 12:49 PM

If the Figure was done in Poser and then saved to the Figures library, there should be no problem so I guess I don't understand the question. More info, please. ;=]

Remember ... "With Poser, all things are possible, and poseable!"


cheers,

dr geep ... :o]

edited 10/5/2019



adtgeni ( ) posted Wed, 17 December 2003 at 1:15 PM

OK, maybe I wasn't precise enough - sorry for that. What I called a scene is of course a loaded *.pz3 file (5 Michael 2.0, 4 Michael 3.0, Clothing, Props etc.) into which I imported a separate *.pz3 file with a single Vicky & clothing. The resulting document is quite big (approx.. 245MB on disk), but I've done bigger ones. Ever since that import I get the error message above when I try to render. I already replaced the imported character with a less poly mesh, but the error keeps coming. I also checked every texture and basic colourization and re-applied everything on the Vicky character... Cheers, Gerhard


RHaseltine ( ) posted Wed, 17 December 2003 at 1:38 PM

Have you tried it with bump maps disabled? The PZ3 file doesn't include textures, so it may be that those are adding enough extra memory requirement that you are running out and getting this error as a result.


geep ( ) posted Wed, 17 December 2003 at 1:49 PM

Hi Gerhard, Importing a .pz3 file on top of another .pz3 file may confuse Poser especially if any labels (i.e., names) have any spaces in them. Poser uses a "space" character for a delimiter in names. Examples: box 1 box 2 box 3 ... etc. ... will appear to Poser as "box" (only 1 object) Whereas ... box_1 box_2 box_3 ... etc. ... will appear to Poser as 3 separate objects. The other possibility is that when you use extremely large file sizes, some of the data may get truncated. (i.e., lost) ********************************** I suggest that you load one of the .pz3 files and then save the Figures and/or props in the proper Poser library. Then load the 2nd .pz3 file. (Do NOT import it ...... just "open" it.) Now ... load the Figure(s) and/or prop(s) ... (from the 1st .pz3) ... into the current scene from Poser's library. cheers, dr geep ;=]

Remember ... "With Poser, all things are possible, and poseable!"


cheers,

dr geep ... :o]

edited 10/5/2019



adtgeni ( ) posted Wed, 17 December 2003 at 3:46 PM

Many thanks for the efforts... but I guess this just doesn't lead to the heart of the problem (I tried your suggestions, but... ). I don't believe this is really about textures, or bump maps, or physical memory. It must be some internal error, most likely some value overflow that fitted into the file format nevertheless... sigh. I guess I have to redo that from the beginning...


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.