grfcodec. Expected more data during tile decoding

[Muzzly]

Hello,

I have problem decoding newshipsw.grf file from this tar.gz

with grfcodec-6.0.0-windows-win32 :

Code: Select all

...\grfcodec-6.0.0-windows-win32>grfcodec.exe -d newshipsw.grf
Found grf container version 1
Decoding:
Sprite 0 at 0,   0% done
Error: expected more data during tile decoding for sprite 21

Code: Select all

...\grfcodec-6.0.0-windows-win32>dir sprites

 Directory of ...\grfcodec-6.0.0-windows-win32\sprites

05.06.2012  15:00    <DIR>          .
05.06.2012  15:00    <DIR>          ..
05.06.2012  15:01                 0 newshipsw.32.png
05.06.2012  15:01             1.419 newshipsw.nfo
05.06.2012  15:01                 0 newshipsw.png

Files *.png have zero size.


with grfcodec_0.9.10-win decoding works:

Code: Select all

...\grfcodec_0.9.10-win>grfcodec.exe -d newshipsw.grf
GRFCodec version 0.9.10 - Copyright (C) 2000-2005 by Josef Drexler
Decoding:
newshipsw.grf has 751 sprites, maxx 93, maxy 67, maxs 2798.

Code: Select all

...\grfcodec_0.9.10-win>dir sprites

 Directory of ...\grfcodec_0.9.10-win\sprites

05.06.2012  13:19    <DIR>          .
05.06.2012  13:19    <DIR>          ..
05.06.2012  15:04            40.724 newshipsw.nfo
05.06.2012  15:04           900.838 newshipsw.pcx

Is this a bug of 6.0.0 version or am I doing something wrong ?

[michael blunck]

I have problem decoding newshipsw.grf file from this tar.gz

Since when is NewShips on Bananas? And with a faked "license"?

The original (with its correct license) can be found here: http://www.ttdpatch.net/newgrf.html

regards
Michael

[Muzzly]

Since when is NewShips on Bananas? And with a faked "license"?

If this question is directed to me, I cannot answer it

[FooBar]

Since when is NewShips on Bananas?

Like a month or so, it appears. An OpenTTD dev should be able to tell you who put it up and can take it down for you again. As somebody obviously ignored both your license and the bananas TOS.

[Muzzly]

SOLVED

with latest trunk version ( grfcodec-trunk-r935-windows-win32 ) it works.

[michael blunck]

SOLVED

with latest trunk version ( grfcodec-trunk-r935-windows-win32 ) it works.

I´d like to inform you that the NewShips grf found on Bananas is an unauthorized version of my original NewShips grf and a copyright infringement, insofar that my original license (which is NOT GPL) had been removed and the original grf has been repackaged with a fake GPL license.

I´ve already requested both the OTTD people responsible for Bananas, as well U Twente to remove that infringing piece of software.

I´d like to remember you that NewShips is not under the GPL, so any modifications made by you (or others) may not be distributed to the public in turn. But o/c you may use a modified grf for strictly private purposes.

regards
Michael

[Eddi]

as well U Twente

note that i don't think this is practical, since this won't make it disappear from any of the mirrors

[TrueBrain]

as well U Twente

note that i don't think this is practical, since this won't make it disappear from any of the mirrors

In fact, this is the worst a person can do, as it doesn't benefit anyone. Let us review the possibilities:

- They remove the file. Next rsync (daily) the file is back. Result: none.
- They remove their mirror. We lose a complete mirror. Result: useless.
- They inform us. Result: minimal (the user in question could have contacted us too; useless waste of resources)

Short, it is completely useless to email the owner of a mirror. Instead, he should contact us (and only us) as we are in charge of BaNaNaS and its file distribution.

Also, just for the record and shake of documentation: emailing individual developers is silly (at best) and frowned upon. Our website clearly states, and every developer always says, to contact info@ for any questions, requests or other problems. Emails to that email address are handled relative fast (we are still volunteers, so give us some time there), but at least someone is always assigned who is not on a holiday or heavily involved in personal life stuff. Developers among each other know how to contact who for which request, and stuff gets delegated quickly. The base line I try to make:

Do not email individual developers for your issues, problems, comments, ... This is inefficient and most developers simply ignore it. If you find any offending entry on BaNaNaS, either come to our IRC channel, or email info@ to report the file in question. It will be investigated, and appropriated actions will be taken (won't be the first time, nor the last time).


This concludes the general broadcast on information how to deal with BaNaNaS content in violation of its ToS. Thank you for listening, and a good day.


PS: the GRF in question is in violation and will be removed within the next 24h.

[michael blunck]

[...]

Then fix your contact information. "General Information" doesn´t sound to be the right place for reporting abuse. Instead, w/r to constant copyright and ToS problems with "bananas", that site needs a reliable contact address.

regards
Michael