A little help with the commandline usage of Graveyard Duck

[Pennywise]

I dunno maybe I'm doing something wrong this being a Python program and all, but let's say I type this in in cp.

graveduck.py -d Gyruss.fds 161CE G.bin

I end up getting like an invalid syntax error. I've already installed python and updated the paths so cp recognizes Python.

[Klarth]

This could be wrong, but don't you launch it like: "python graveduck.py -d Gyruss.fds 161CE G.bin"

[Pennywise]

I wish that would work, but it doesn't. I think the error stem from just the usage of graveduck.py. The error always stays the same regardless if I add anything else.

This might be an error caused by having the latest version of python when this program was meant for an earlier version perhaps. The exact error I'm getting is basically this:

except ImportError, err:

Syntax error: invalid syntax

[BRPXQZME]

Use Python 2. Almost everything still does.

[Pennywise]

Python 2 runs the program fine, but now I have an issue with the offset. I can't get it to accept anything. I've tried 161CE, $161CE, 000161CE and still nothing. It says:

ValueError: invalid literal for int() with base 10: '161CE'

[Vehek]

The "base 10" in the error message means it was expecting a decimal number, not a hex number.

[Gil Galad]

Yes, it needs a decimal number. I've had a lot of success using it on Dracula II which is what it was originally designed for.

D- contacted me and to tell you this.

Use the latest graveyardduck from (https://bitbucket.org/dsobodash/graveyardduck/). It is programmed to work in python 2.6 or 2.7. Python 3.0 is basically a different language.

He also fixed a bug.

If an RLE was more than 124 bytes, it would completely fail during compression. Basically, if you had more than 124 0x00s in a row, you would be up shit creek.

[Pennywise]

This last bug was something I ran into and was eventually going to post about to see if anyone knew what the hell was going on. I bet D has added his utility to the list stuff on RHDN that's outdated, but I thank him nonetheless.

My game in question is another FDS game programmed by the wizards at Konami and I'm pretty sure the duck works fine with it. The output looked good, but I need to recompress it back into the game to see if it works flawlessly.

[Gil Galad]

This last bug was something I ran into and was eventually going to post about to see if anyone knew what the hell was going on. I bet D has added his utility to the list stuff on RHDN that's outdated, but I thank him nonetheless.

I don't believe I understand what you mean, if you could explain?

Also, D- told me that he just updated Graveyarduck to use hexadecimal numbers. Go back to that page and download it again.

EDIT:

With the new version, make sure you use 0x = hex. For example.

0x12AB

0 = octal

[Pennywise]

If you mean the first part, then basically what happened was that when I decompressed the graphic data, I wanted to test to see if everything was ok by compressing it back in unaltered, but I believe I got an error that I believe was this bug D said he fixed. I'm not on that though and will test it out tomorrow. If the second part, I seem to recall D mentioning somewhere else about the Der Langrisser patch at RHDN is not the latest patch available. It's been a while, but I could just be overstating, generalizing etc. So pay no heed to that comment. You and D both have my thanks.