Grf codec problems

Post by **WWTBAM** » 27 Nov 2005 06:31

When grf codec asks for target grf and sprites source parth what do i put.

Jezulkim · Post by **Jezulkim** » 27 Nov 2005 13:55

For target grf write the name of the grf file you want to encode.
And for the sprite source path write the name of the folder where you have the sprites, usually the folder is "sprites".

PvvS · Post by **PvvS** » 01 Jan 2006 13:53

My problem:
Decode its first grf , and like result me will originate defective graphic art . I was trying uz perhaps everything

Wile E. Coyote · Post by **Wile E. Coyote** » 01 Jan 2006 22:02

It happens when PCX from which you encode GRF is small AFAIK (but I don't know why). I know only this sollution:
you must have PCX image which you drew and which is not corrupted. Copy sprites from it to this "corrupted" PCX, and then encode GRF. Sprites will be OK.

Website · Post by **Lakie** » 01 Jan 2006 22:13

Chances are your Orginal pcx file isn't 800 pixils in width.
I'm not sure what multiple it has to be of, but if it isn't of that multiple then you get that type of distorion.
I tend to avoid making pcx files which are not 800 pixils wide for that reason.

~ Lakie

Flamelord · Post by **Flamelord** » 02 Jan 2006 00:58

Strange, because I have made a quicky GRF with a PCX file that only included two paper wagons. It was much less than 800 pixels wide.

DaleStan · Post by **DaleStan** » 02 Jan 2006 05:07

I can state definitively that the GIMP (at least, 2.2.10) does not experience this problem. I just saved a PCX with widths of 275, 271, 269, 263, and 257, and had no problems with any of the encodes. Note that, with the exception of the first one (275), all are prime numbers. I believe that this proves either:
(1) The width must be a multiple of at least one of 275, 271, 269, 263, 257, (and possibly some other numbers)
--OR-- (and far more likely, IMO)
(2) The width must be a multiple of one.

If anyone who uses other graphics programs could do a similar procedure, and post all PCX/NFO pairs that do not work, that will probably cause grfcodec to get fixed faster. The first one for the list of misbehaving PCXen is Flamelord's, here.

PvvS · Post by **PvvS** » 02 Jan 2006 09:08

My original NFO and PCX files

Website · Post by **Lakie** » 02 Jan 2006 13:59

I can't get it to compile right, but if I change the width of the pcx file to 280, it compiles fine.
Maybe it's just my computer?

~ Lakie

DaleStan · Post by **DaleStan** » 03 Jan 2006 03:45

Lakie wrote:I can't get it to compile right, but if I change the width of the pcx file to 280, it compiles fine.

And again, opening it in GIMP and saving it (no changes) causes it encode and decode just fine.

From the other thread:

George wrote:The problem is not in PCX, but in grfcodec and this is the way to fix it (I do not know why, but it is)

You seem to be quite fond of these random fixes that just happen to work. I'd much rather make my PCX one pixel narrower/wider (see below) than struggle to figure out which compression byte needs to change to 03.

michael blunck wrote:Apparently, grfcodec has problems with .pcx files with an uneven picture width which have been converted from .bmp files with that odd width.

This is a known bug which has been in existence since the first version of grfcodec.

Website · Post by **Lakie** » 03 Jan 2006 10:24

Heh, how strange, must be the way my software causes such an issue for me then.

Oh, and I've known about grfcodec being less than perfect for quite a while.

~ Lakie

PvvS · Post by **PvvS** » 03 Jan 2006 14:16

Use to generation graphic designer Paint Shop Pro. Somewhere on forum we're him also saw advise .

Transport Tycoon Forums

Grf codec problems

Grf codec problems

Who is online