Does anyone know of any way around Bryce's repeated crashing when you attempt to use a second Image texture? Windows XP Nvidia GeForce go 6800 (drivers recently updated) Fed up Inclined to go play with Cinema until Daz fixes this. (Sob!)

You've got Bryce & Studio updated? Studio updated to 1.2 - sept 2005 Bryce updated to 5.5c - july 2005 Just making sure. I don't get crashing with image texture until I do this thing I do...ya know when you click Load, and you browse for the texture? Sometimes while with the browsing window up, I'll right click on a jpg, choose Open to look at it (and make sure its the one I was thiinking of)...and then B5.5 will crash, sometimes. AS

Fran, I have run into this too. One thing that I tried that seems to help head off my crashes is to put my image textures that I'm going to use in Bryce's main folder. Of course I always save after I add the first image texture so that at least I still have that point accomplished if Bryce crashes. I don't know that this will help in ver.5.5. I'm still on 5.1.

Hmmmm... Hey fran... Sorry I have been to busy but I saw your post and said Hey I need to help... I use Image Textures all of the time and some times upto 25 - 30 different Image textures...Resolutions of 1000x1000 or better... Now what is the file format that you are importing into the Picture Editor...? How big is the Resolution of the Image...?

oooh I had this happen to me once. I had an image i wanted to use on a wall, resolution was 2000x1800 BMP. i change it from the bmp to jpg and it all seemed to work fine then. I wonder if that could be your problem Fran.

AS, Bryce is version c but I don't want to update to Daz 1.0.2. or whatever it is, as I've seen all the wails it causes I'm waiting for those bugs to be fixed first. I dont use Daz much as it's so terribly difficult to find anything in the mess it calls directories RHasletine has tried to explain how to sort it out but I just don't understand him so I've given up using Daz at all now. There have been occasions where I've simply HAD to use Daz (not having Poser) but it takes hours and hours to do anything so I try not to think about things that need figures. And AS, I didn't know you COULD right click on an image's name to view it while still in Bryce, so it's not that. (and yes, I gave in and sent a bug report to Daz why I dont know! Pretty pointless exercise.) danamo, I haven't tried putting the jpeg I'm using in the main bryce folder...not sure which one would be classed as "Main", but I think it could cause me lots of problems in the long run I have millions of images, eventually having numerous copies would, I think, help to slow down my computer. So I'm not sure about that. But both images I want to use are in the same folder does that help? foleypro Almost all my images are jpegs, (a very few are bmp) these two are jpg and the first pic is 1100 x 844 and the second is 1024 x 1024 that's the one Bryce keeps crashing on. CrazyDawg, Er, no, not this time all jpegs.

Thank god for Vue :) /me runs and dives under the ned for cover...

Under the ned? CrazyDawg, what are you doing trying to hide under a donkey? Lol!

(( and the second is 1024 x 1024 that's the one Bryce keeps crashing on.)) How many characters are used in the image's file name? Bryce does not like file names to be over 32 character ( including spaces )

Stephen Ray, Ah... I'd forgotten about that... duh! well I've checked... and the smaller one - the first image I used is only 26 before the file extension - 30 with .jpg and no spaces at all... "CraquelureLatticeMintyGrey.jpg" so it's not that. And the second image is larger in size but it's name is smaller: "CraquelureBase.jpg" (that's the one on which Bryce crashes)

Yea usually the long file name problem only hits when you try to save. I seem to recall this happening to me in B5.5 a few times ( I don't uses B5.5 very much ). I believe it hit me once or twice in B5. It struck when I entered the material room via the light or tree lab. After I restarted it worked okay. 1. Is it crashing when you try to load 2 textures to one object ( via 2 texture windows ) 2. Or are you trying to replace the texture that is already loaded on the object? 3. Or are you trying to load the second texture in the Alpha window of the Image Library ? My point is if you can narrow down the steps to reproduce the crash, you may be able to find a work around to avoid the crash. Or at least warn others what makes this bug strike. Something else to check: 4. If you launch a new project and try to load the textures ( just as a test ) does it crash ? ( if it crashes a new launched project, every attempted to load the tex, It could be a problem with the tex map ) If that's the case make a back-up tex and try saving it out of and image editor. Here's a bug, I found will crash Bryce every time ( I posted it at DAZ forum, But not here ) Grouping Bryce Trees, saving to the Object Library then export/import the file ( like if you were sharing it ) When the file is imported into the library, it will crash B5 and B5.5 whenever the grouped tree object is selected, or when attempted to add it to the scene The work around this bug is to create new empty library ( I keep a blank back-ups of all Bryce Libraries ) then load the group tree objects ( as many a you need ) to the new empty library. Then the library can be shared by browsing to the Bryce preset folder and making a copy of that library. With instruction that it needs to be dropped into the Preset/Object folder of your choose. instead of importing it into the object library.

1. No. 2. Yes. 3. Yes. I tried again from scratch, with 1 cube, loaded the 1st texture, saved it, created a 2nd cube, loaded the second texture - left the mat lab - it didn't crash!!! Saved it as fast as possible! Fainted with surprise... Put the same image in bump for 1 cube - saved - still didn't crash! Did the same for cube 2 - saved, still didn't crash. Now all this is fine and dandy if all you want to do is play with 2 cubes - but what if you want to add image textures to a spaceship, made with lots of this and that, with lots of things in the scene - how are you supposed to manage?

Well that means the image files are fine. Something I have always been suspicious about B5 is it has a problem when more than one command is activated. Have you ever experienced the pause after it appears to be done saving a scene file. I have tried selecting other commands while in this pause and it corrupts the saved scene file. ( this has happened on more than one occasion ). I know when many programs try to call up to much memory at once ( like hitting multiple undo at once ) they are prone to crash. When a large scene file is open, it seems Bryce will do the command, and while it's still loading the info into memory ( or swapping to disk ) it lets you do another command, but then has a problem storing the info to memory and crashes. Thinking back I do recall a problem when using the Mil 2 Dragon. I was loading high rez textures ( mil dragon ) body, head, bump, trans, spectral, and I always uses the same image in the alpha window. I never mix trans or bump with the color channel maps. And sometimes when I copy/paste to the alpha window. Bryce crashed. I had a large number of tex maps in the Image Library when it happened. As soon as the image loaded I would copy/paste to the alpha window. After the second crash trying to load the same texture to the alpha window. I tried again but waited for 1/2 a minute before copy/pasting, and it worked, so I figured sometimes I just had to wait for Bryce to catch up to itself. Same as when I save now, I never click anything while Bryce is in that pause after saving.

I haven't had that problem, nor have I noticed any particular pause while saving, there is an area under the render button, where you see things like "saving doc settings" and "saving objects" and stuff like that - I just wait until that's stopped before doing anything else. Maybe that's why I haven't had it crash on me for that? Also, I don't think I've done many very big scenes, I think the biggest was the "Station Approach" image in my gallery. The station itself wasn't too bad except that I used an awful lot of small models of a "knutt" - sort of like a bolt but made by me with my then minimal modeling skills. Plus a few platforms with glass domes and a lot of glass landing lights etc, and the ship in the foreground and the various nebulae - But that didn't use image based textures at all, gawd knows what might have happened if it did. I probably wouldn't have finished the picture at all.