Is there a limit on the size of the GRAPHICS.DAT?
I can load my current file which has swelled to 514KB. However, if I replace a graphic so that it goes to 525KB, CSBWin crashes when I click on the 'Dungeon' button.
Are there any checks in the original code that could be removed. Perhaps it's more complicated than that....?
Hope it's fixable, I still have a long way to go before all my new gfx are imported...
Limit on size of GRAPHICS.DAT?
Moderator: Zyx
Forum rules
Please read the Forum rules and policies before posting.
Please read the Forum rules and policies before posting.
- Paul Stevens
- CSBwin Guru
- Posts: 4319
- Joined: Sun Apr 08, 2001 6:00 pm
- Location: Madison, Wisconsin, USA
- Gambit37
- Should eat more pies
- Posts: 13720
- Joined: Wed May 31, 2000 1:57 pm
- Location: Location, Location
- Contact:
Oh yes, most of them are resized -- but that's not a problem if you hex edit 0558.dat to reflect the new sizes. This is a massively customised file that has all kinds of new sized images in it. No, the problem I believe is the overall FILE size of the .dat.
Mr. Stevens, I am sending you some sample GRAPHICS.DATS of differing sizes as I type this.
Mr. Stevens, I am sending you some sample GRAPHICS.DATS of differing sizes as I type this.
- Gambit37
- Should eat more pies
- Posts: 13720
- Joined: Wed May 31, 2000 1:57 pm
- Location: Location, Location
- Contact:
Incidentally, the file I am changing is the End Game Scroll -- by saving it out from Photoshop with different amounts of dithering, I can easily generate GRAPHICS.DATS of differing sizes. It's the file dmout0005.bmp as generated by Rain's DMEXTRACT program.
I am wondering if perhaps there is an upper limit on the amount of memory any SINGLE graphic takes? Hmmmm... maybe I could get the GRAPHICS.DAT bigger by adding lots of smaller images and see if that also causes the problem...
I am wondering if perhaps there is an upper limit on the amount of memory any SINGLE graphic takes? Hmmmm... maybe I could get the GRAPHICS.DAT bigger by adding lots of smaller images and see if that also causes the problem...
- Paul Stevens
- CSBwin Guru
- Posts: 4319
- Joined: Sun Apr 08, 2001 6:00 pm
- Location: Madison, Wisconsin, USA
Try CSBwin9.8v22.
There were really two problems. Graphic number 5 was bigger than
32767 and the total sizes of <something> was too big. I doubled the
size of memory allocated (from 1 meg to 2) and 'un-signed' the graphic
sizes. I do not understand the memory allocation and things might break
again. It may come to pass that I will need to study it a bit.
There were really two problems. Graphic number 5 was bigger than
32767 and the total sizes of <something> was too big. I doubled the
size of memory allocated (from 1 meg to 2) and 'un-signed' the graphic
sizes. I do not understand the memory allocation and things might break
again. It may come to pass that I will need to study it a bit.