News:

Want to praise Simutrans?
Your feedback is important for us ;D.

[solved] Lossin scripts for PAK128.britain on nightly-Server

Started by wernieman, October 23, 2011, 05:47:43 PM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

wernieman

Hey,

I do a big mistake (or my Server do) and loos the Scripts for making PAK128.britain on the nightly-Server and ... I have no Backup for this :o(
it was a "long time" ... that I programm this script. So .. could somebody explain me, how to generte the PAK on Linux?

THANKS!!

Werner

I hope you understand my English

greenling

Opening hours 20:00 - 23:00
(In Night from friday on saturday and saturday on sunday it possibly that i be keep longer in Forum.)
I am The Assistant from Pakfilearcheologist!
Working on a big Problem!

wernieman

I hope you understand my English

jamespetts

Quote from: greenling/As.fr.Ar.fo.Si. on October 23, 2011, 06:12:58 PM
Wernieman why do you make nightly in the Night?


I expect that it'd have to be called a "daily" if it was made during the day.
Download Simutrans-Extended.

Want to help with development? See here for things to do for coding, and here for information on how to make graphics/objects.

Follow Simutrans-Extended on Facebook.

prissi

This was build with MOSE http://www.simutrans-forum.de/forum/thread.php?threadid=4585 . However, I still fail to see the advantage to normal make ...

I just made a Makefile similar to pak64 and pak64.japan for it. I also found out that on simutranslator lots of stuff is missing from pak128 britain.

wernieman

So I build the PAK like PAK64?

And this way work in the Future too?

I think, "mose" was build, because some peaple have Problem to use "make" in Windows ....
I hope you understand my English

prissi

Well Mose also uses python to run makescripts. However, the mose script interferes with my installation. Anyway, the makefile will work like pak64 until new directories are added. Then those need to be added to the makefile too.

sdog

there's already a Makefile for pak128.britain, why not using that?

EDIT: apparently the Makefile wasn't added to the svn :-(

It's not a big deal to have a Makefile, mose.py (or VS script) in parallel in a pak. When building one can pick what works best.

The Hood

I've always used MOSE and that's what is in SVN.  But I have no problem if you want to use make instead.  Do you need me to help in any way?  Not that I have a lot of time...

wernieman

At the Moment I have not enough time ... so it need some days to make it O.K.
I hope you understand my English

wernieman

I try to rebuid my Script, but I got some Problems ....

with make
simutrans@hedwig ~/PAK/PAK128.britain $ make
Makefile:101: warning: overriding recipe for target `grounds'
Makefile:86: warning: ignoring old recipe for target `grounds'
===> COPY
===> OUTSIDE with REVISION and grounds
Makeobj version 52 for simutrans Nightly 110.0.7 and higher
Makeobj version 52 for simutrans Nightly 110.0.7 and higher
===> PAK64 gui/gui64
Makeobj version 52 for simutrans Nightly 110.0.7 and higher
libpng warning: Interlace handling should be turned on when using png_read_image
libpng warning: Interlace handling should be turned on when using png_read_image
===> PAK128 air
Makeobj version 52 for simutrans Nightly 110.0.7 and higher
Error:: No such file or directory
ERROR IN CLASS image_writer_t: cannot open air/images/BAC111_200_BUA.png
make: *** [air] Error 1
s


And with mose (i found an old Version of the Script)
simutrans@hedwig ~/PAK/PAK128.britain $ /usr/bin/python mose.py -x makeALL.mos >${home}/PAK/PAK128.britain/info.txt
Makeobj version 52 for simutrans Nightly 110.0.7 and higher
Error:: No such file or directory
ERROR IN CLASS image_writer_t: cannot open ./air/images/BAC111_200_BUA.png
Makeobj version 52 for simutrans Nightly 110.0.7 and higher
Error:: No such file or directory
ERROR IN CLASS image_writer_t: cannot open ./air/images/BAC111_200_BUA.png
Makeobj version 52 for simutrans Nightly 110.0.7 and higher
libpng warning: Invalid pHYs after IDAT
libpng warning: Invalid pHYs after IDAT
libpng warning: Invalid pHYs after IDAT
...........


It is the newest Version of the Pak ...
URL: https://simutrans.svn.sourceforge.net/svnroot/simutrans/pak128.Britain
Repository Root: https://simutrans.svn.sourceforge.net/svnroot/simutrans
Repository UUID: e96eaf88-093e-0410-925f-862d53288611
Revision: 596
Node Kind: directory
Schedule: normal
Last Changed Author: Prissi
Last Changed Rev: 596
Last Changed Date: 2011-10-28 16:48:35 +0200 (Fri, 28 Oct 2011)


Did someone have the same problem?

It is a Linux System and I work in the PAK-Direktory ....
I hope you understand my English

The Hood

At a guess - Linux typically doesn't like case differences, and I notice these two have .PNG instead of .png.  I will change this in SVN.

wlindley

Whilst the svn is being changed, could I volunteer to make all the directories consistent by ensuring all the images are in directories called images/ instead of mixed with the .dat's?

prissi

I would rather suggest to get rid of the images folder at all. Those are a pain in the ** to upload single objects to simutranslator.

By the way, there were tons of strings on simutranslator, which were not from the pak set. I think those may stem from the experimental version. The en.tab has several error. However, here are the orphan entries: (Some of them are obviously objects in pak128.BritainEx, which are omitted from standard, like the ThornycroftAmazonTractor family. Maybe adding them would make sense.

(Also both paksets could change folder on sf, and just have a different makefile. This woudl make synchronising those paks much easier. Even more since there are lots of experimetnal entries in the vehicles at least.)

JH_IND_1750_00
JH_IND_1860_00
JH_IND_1860_01
JH_IND_60_00
JH_IND_80_00
JH_RES_1750_00
JH_RES_70_00
JH_RES_70_01
JH_RES_70_02
JH_RES_70_03
KG_COM_00_15
KG_COM_00_16
KG_COM_00_17
KG_COM_00_18
KG_COM_00_19
KG_COM_1880_0
KG_COM_1880_1
KG_COM_1880_2
KG_COM_1970_0
KG_RES_00_13
KG_RES_00_14
KG_RES_00_15
KG_RES_00_16
KG_RES_00_17
KG_RES_02_17
KG_RES_04_01
KG_RES_04_02
KG_RES_04_90-0
KG_RES_04_90-1
KG_RES_1600_00
KG_RES_1700_00
KG_RES_1700_01
KG_RES_1880_1
KG_RES_1890-1
KG_RES_1920_00
KG_RES_1930_01
KG_RES_1960_04
KG_RES_60_00
KG_RES_60_01
KG_RES_60_02
KG_RES_60_03
KG_RES_80_00
KG_RES_80_01
KG_RES_80_02
Nelson-Column
PowerDest
PowerSource
ArableFarm1750
ArableFarm1840
ArableFarm1910
ArableFarm1945
ArableFarm1975
Bakery1750
Bakery1840
Bakery1910
Bakery1945
Bakery1975
Bookshop1860
Bookshop1920
Bookshop1950
Bookshop1970
Brewery1750
Brewery1840
Brewery1910
Brewery1945
Brewery1975
Brickworks1800
Brickworks1850
Brickworks1905
Brickworks1960
Brickworks1985
BuildersYard1750
BuildersYard1800
BuildersYard1850
BuildersYard1905
BuildersYard1960
BuildersYard1985
Butchery1820
Butchery1840
Butchery1910
Butchery1945
CarDealership1910
CarDealership1925
CarDealership1950
CarDealership1970
CarFactory1910
CarFactory1925
CarFactory1950
CarFactory1970
CattleFarm1750
CattleFarm1840
CattleFarm1910
CattleFarm1945
CattleFarm1975
CementWorks1800
CementWorks1850
CementWorks1905
CementWorks1960
CementWorks1985
Chemist1860
Chemist1955
Chemist1975
ChinaShop1750
ChinaShop1850
ChinaShop1905
ClayPit1750
ClayPit1850
ClayPit1905
ClayPit1960
ClayPit1985
ClothesShop1750
ClothesShop1840
ClothesShop1910
ClothesShop1945
CoalMine1750
CoalMine1850
CoalMine1920
CoalMine1950
CoalMine1970
CoalPowerStation1910kraftwerk
CoalPowerStation1920kraftwerk
CoalPowerStation1955kraftwerk
CoalPowerStation1970kraftwerk
CoalYard1750
CoalYard1850
CoalYard1920
Dairy
Dairy1750
Dairy1840
Dairy1910
Dairy1945
Dairy1975
DepartmentStore1907
DepartmentStore1935
DepartmentStore1960
DepartmentStore1990
FishingGround1750
FishingGround1840
FishingGround1910
FishingGround1945
FishingGround1975
Fishmongers1820
Fishmongers1840
Fishmongers1910
Fishmongers1945
ForestSawmill1750
ForestSawmill1850
ForestSawmill1920
ForestSawmill1950
ForestSawmill1970
FurnitureFactory1750
FurnitureFactory1850
FurnitureFactory1920
FurnitureFactory1950
FurnitureFactory1970
FurnitureShop1750
FurnitureShop1850
FurnitureShop1920
FurnitureShop1950
GrainFarm1750
GrainFarm1840
GrainFarm1910
GrainFarm1945
GrainFarm1975
GrainMill
GrainMill1750
GrainMill1840
GrainMill1910
GrainMill1945
GrainMill1975
Greengrocers1820
Greengrocers1840
Greengrocers1910
Greengrocers1945
HardwareFactory1790
HardwareFactory1850
HardwareFactory1920
HardwareFactory1950
HardwareShop1790
HardwareShop1850
HardwareShop1920
IronOreMine
IronOreMine1750
IronOreMine1850
IronOreMine1920
IronOreMine1950
IronOreMine1970
Newsagent1860
Newsagent1920
Newsagent1950
Newsagent1970
OilRefinery
OilRefinery1910
OilRefinery1925
OilRefinery1955
OilRefinery1975
OilRig1955
OilRig1975
OilWell1910
OilWell1925
OilWell1955
Orchard1750
Orchard1840
Orchard1910
Orchard1945
Orchard1975
PaperMill1860
PaperMill1920
PaperMill1950
PaperMill1970
PetrolStation
PetrolStation1910
PetrolStation1925
PetrolStation1955
PetrolStation1975
PharmaceuticalFactory1860
PharmaceuticalFactory1920
PharmaceuticalFactory1955
PharmaceuticalFactory1975
Pottery1750
Pottery1850
Pottery1905
Pottery1960
Printworks1860
Printworks1920
Printworks1950
Printworks1970
Pub1750
Pub1840
Pub1910
Pub1945
Quarry1750
Quarry1850
Quarry1905
Quarry1960
Quarry1985
SheepFarm1750
SheepFarm1840
SheepFarm1910
SheepFarm1945
SheepFarm1975
Slaughterhouse1750
Slaughterhouse1840
Slaughterhouse1910
Slaughterhouse1945
Slaughterhouse1975
SteelMill1790
SteelMill1850
SteelMill1920
SteelMill1950
TextileMill1750
TextileMill1840
TextileMill1910
TextileMill1945
TextileMill1975
Concrete
corn
cotton
electronics
Ethanol
fertilizer
food
glass
goods_
Holz
Sand
waste
CATEGORY_01
CATEGORY_02
CATEGORY_03
CATEGORY_04
CATEGORY_06
AustinMaestroPost
AustinMorrisEAPost
BuildersYard1750
CarFactory1970
CartMail
DAFLFBulk
FishingGround1910
Fishmongers1945
FodenCompoundLivestock
FordEscortPost
FordTransitConnectPost
HorseBargeCool
KTypeDouble
LeylandDAF200Piece
LeylandDAF85RigidBulk
LeylandGBulk
LeylandSherpaPiece
LivestockDrover
MailBike
MorrisJ4Piece
OmnibusDoubleGardenseat
OmnibusSingle
ScammellCrusader
ScammellScarab
SR-MerchantNavy 4-6-2(Green)
SR-MerchantNavy 4-6-2Tender(Green)
STypeDouble
ThornycroftAmazonTractor
ThornycroftBTBulk
ThornycroftQArticTractor
ThornycroftQCBulk
ThornycroftQRigidBulk
ThornycroftStagBulk
ThornycroftSteamVanPiece
Crossing1


Byte the way, RES/COM/IND should always start with R, C, or I and should end with _levelnr. As such the KG_COM are breaking the scheme ...

wernieman

O.K. .. at now, it works.

but ... could somebody look to this "error/warning" Message?
libpng warning: Invalid pHYs after IDAT
libpng warning: Invalid pHYs after IDAT
libpng warning: Invalid pHYs after IDAT
libpng warning: Invalid pHYs after IDAT
libpng warning: Invalid pHYs after IDAT
libpng warning: Invalid pHYs after IDAT
libpng warning: Invalid pHYs after IDAT
libpng warning: Invalid pHYs after IDAT


I get very much of them

P.S. I is better to use the makefile or the mose-script??
I hope you understand my English

wlindley

I believe that pHYs message is because a .png file had a transparency layer -- which makeobj ignores.  One of these days, makeobj really ought to be updated to understand transparency in addition to the reserved "light blue in lieu of transparent" color. 

prissi

No, those are extra data in the HDF-structure of PNG. (The PNG is a subset of a far mightier format: The HDF-files, which is a 1000+ page definition. Program can add extra chunks, and chunks can exceed their predefined size. Some applications (among them aparently Photoshop) save broken PNGs in certain versions. Loading and Saving in any other program will repair this. But I never bothered with this, also pak64 has one of them.

sdog

we could fix it with a simple imagemagick script, opening and resaving? perhaps it might be worth a try to get rid of the annoying error messages.

ps.: may i suggest to split this off, in it's own thread. This question has been raised before, and might be more easily available for reference then.

Ashley

If you're going to run through all the .png files I'd suggest also running them all through a tool like pngout (http://advsys.net/ken/utils.htm) since this can save a lot of space which means quicker source downloads/checkouts.
Use Firefox? Interested in IPv6? Try SixOrNot the IPv6 status indicator for Firefox.
Why not try playing Simutrans online? See the Game Servers board for details.

VS

pHYs specifies DPI which is irrelevant to Simutrans...

My projects... Tools for messing with Simutrans graphics. Graphic archive - templates and some other stuff for painters. Development logs for most recent information on what is going on. And of course pak128!

wlindley

Since Simutrans is not only a Free Software package but also under source code control, it would be far better to sacrifice a little bandwidth and put sng (Scriptable Network Graphics) files in the repository... .sng's are .png's but converted to a human-readable text representation so you actually have a chance at seeing sensible diff's in your revision logs.  Unfortunately sng hasn't caught on as much as it should.

See the SourceForge page:

QuoteSNG is a specialized markup language for expressing the contents of a PNG (Portable Network Graphics) in an editable, all-text form.

I am highly dubious of 'pngout's claims to optimization; png is a simple format, it isn't magic.

Ashley

Pngout typically halves the size of png files made with photoshop, at least in my experience... I think it depends on how badly the file was made in the first place, e.g. Photoshop puts a lot of extra cruft into the file.
Use Firefox? Interested in IPv6? Try SixOrNot the IPv6 status indicator for Firefox.
Why not try playing Simutrans online? See the Game Servers board for details.

wernieman

The Discussion is good ... but ....  should I use the make version or the mose??

I is very important for the future, because which Version is support by the creator of the PAK?
I hope you understand my English

The Hood

Most pak128.Britain obtain ate from Gimp - does that also mess up pngs in the same way?

I have no preference between mode or make - are there any diffetences?

sdog

i'd suggest make for two reasons. First it is more similar workflow to building the other paks and the binaries. Secondly you have two dependencies with mose, development of the pak-set and development of the script.

mose and make can be used for the same pak set, side by side. Regardless if the Hood uses it, the Makefile can be kept up to date by quite a lot of people. (For example we're maintaining a very similar makefile in pak.britain experimental.)

prissi

make also includes revision information into the ouside.pak. Until this is added to the mose script, I would rather use the makefile.

The Hood

OK, let's run with make for official releases from now on then.

wernieman

Hey,

with the next build of the nightly-PAKs, there must be nightly PAK128.britain!

The Server build the PAK with the Makefile.

Werner
I hope you understand my English

The Hood