Hi all, a newbie here...
The answer is probably staring right back at me, but I can't see it.
Using makeobj on bulk-carriage.dat with the following original lines compiles perfectly:
Using makobj on this lumber wagon returns a warning message:
"WARNING: More freightimagetype (0) than freight_images (0)!"
The .dat compiles, and the pak seems to work correctly.
This warning occurs with both the original pak64 SVN 'horses.dat' and my slightly modified shown above. I have looked at this closely, and cannot spot any inconsistency.
1) Can anyone spot an error in the wood wagon image data list?
2) Can anyone tell me what the warning is telling me?
3) Is there any documentation available on makeobj error messages?
Thanks in advance for any help forthcoming.
This code of pak64 here is wrong. The  freightimage will be ignored ...
There is no list of error messages; there can be even error messages from libpng printed in between.
Sorry, prissi, I don't understand. Why does one compile without a warning and the other with? And what would be the correct syntax?
The first has FreightImageType[n] and FreightImage[n][?] both set for all n=0..3.
The second says FreightImageType and FreightImageType, but has FreightImage[?] - twice without the first index, which implies [ 0]. So you end up one set of cargo images short. Additionally, the images are set twice, each time to different values. Not sure which is actually used, but that doesn't matter much.
You probably copy-pasted the FreightImage lines from a vehicle that does not specify more than one cargo graphic. In that case, the first index is omitted (defaults to 0 as already said) and FreightImageType too, since the 0-th one is implicitly assumed to be the same as what is set in freight=?
Thank you VS, I see it now...
I am getting old...
Actually, prissi is correct, the (incorrect) lines are from the 'horses.dat' file in the current SVN. I only changed to a newly modified .png.
VS, I think we are even. I recently re-introduced you to hex editors, you've re-introduced me to dimensioning arrays.
Just think of all the awesome concepts we could explore! :P