not sure, but try these combos
pic.pixels[byt] = savegame->picture[byt];
or
pic.pixels[byt] = (savegame->picture)[byt];
or
(pic.pixels)[byt] = (savegame->picture)[byt];

Accessing arrayed structure elements is always a fuzzy part for me...

Also, make sure savegame->picsize is being saved correctly.

Hmmm ...

the first two combos end in a compiler error.

With the last one I get the same result as before ... crash in function.

savegame->picsize is correct, but the crash occurs with the first call of the line in the for-loop.

Maybe pic.pixels is read-only?

I also tried to use bmap_lock and bmap_unlock.

Any other idea?

As a workaround I'm currently using the following code:

I changed from char to var in the struct.

To save the picture in my struct:


And to load it back:


This works fine, but I think the other version would be faster, wouldn't it?
But it seems writing directly into pic.pixels is crashing the engine.

Regards,
Pegamode.

Hmm, yes mine would be much faster....if it was working!

I'll look into it today and actually compile and test this time.
I'll post back my results when Im done.

Sorry for the inconveniance.

Dammit. Looks like this is a dead issue, except by using the
pixel_for_bmap and pixel_to_bmap functions, which are fairly slow.

BMAPs seem to jump back and forth with whether the ACTUAL data is stored
in the friendly *pixels data blocks and the evil *d3dtex data blocks,which are too complex.

I'll keep looking into it, but I dont have very high hopes, either on chance
of sucess OR time to resolve...

I'll give you a hand with pixel_for_bmap and pixel_to_bmap if you want, as a
savegame function doesnt really need speed.

Hi EvilSOB,

thanks for your help and the time you spent in that issue.

My pixel_for_bmap and pixel_to_bmap code works fine so far and it is as you said, I don't need speed.

It would have been nice if the char-version was working, but in my case pixel_... functions work as well.

Maybe we should ask Conitec if there is a chance to get this working with using a char-array.

Regards,
Pegamode.

So why the preference of a CHAR array rather than a VAR array?
I only looked into this as I saw a potential shortcut for you that didnt pan out.

If you dont want to have VARs in your struct you could use FLOATs instead.
Change your struct to float picture[20000]; and replace you encoding line
savegame->picture[z] = pixel_for_bmap(screenshot_pic,x,y);
with
savegame->picture[z] = floatv(pixel_for_bmap(screenshot_pic,x,y));

and your decoding line
pixel_to_bmap(pic,x,y,savegame->picture[z]);
MAY need to change to
pixel_to_bmap(pic,x,y,(var)savegame->picture[z]);

Then all the data will be stored as a clean single FLOAT for every pixel.
Also would it possible be better to store the picture data is a TWO dimensional
array like this? float picture[245][110];

Hi EvilSOB,

I tried your idea to use float instead of var, but then all colors in the saved picture are wrong ?!?

So now I changed to var picture[245][110];

Maybe
savegame->picture[z] = (float)pixel_for_bmap(screenshot_pic,x,y);
instead of
savegame->picture[z] = floatv(pixel_for_bmap(screenshot_pic,x,y));
Its possible the floatv function does something off to the pixel data.

But if you are happy with VAR's then its no propblem.

I think I can live with the VARs.

Thanks for your help.

Now I have all my data (screenshot included) in one single savegame file.
That's great.