The International Simutrans Forum

 

Author Topic: Brick rail elevated way introduction date  (Read 20764 times)

0 Members and 1 Guest are viewing this topic.

Offline Lord Vetinari

  • *
  • Posts: 125
Brick rail elevated way introduction date
« on: December 28, 2010, 04:54:10 PM »
Hi, happy holidays!

I just started a new map, and that made me remember that the brick rail elevated way becomes available a lot of time after it's bridge counterpart. I don't remember the exact dates, but I do know that the bridge is already available in 1820 (when I started this particular game) and in 1834 I still can't build the el.
Isn't it better if they both appear at the same time? Other than the fact that in RL they are almost the same thing, there are a lot of things that in the game can be done only with an elevated way, such as diagonal bridges (doesn't work on "sea" water, but it's still usefull for rivers), bridges that don't require slopes, curved overpasses, etc.

Offline jamespetts gb

  • Simutrans-Extended project coordinator
  • Devotee
  • *
  • Posts: 18745
  • Cake baker
    • Bridgewater-Brunel
  • Languages: EN
Re: Brick rail elevated way introduction date
« Reply #1 on: December 28, 2010, 04:57:32 PM »
Ahh, this has been corrected for Pak128.Britain-Ex - one could do likewise for Standard with the following code .dat file:

Code: [Select]
Obj=way
Name=BrickViaductElevatedEarly
waytype=track
system_type=1
intro_year=1815
intro_month=9
retire_year=1926
retire_month=10
topspeed=115
max_weight=80
max_height=5
cost=295000
maintenance=923
icon=> ./images/brick-viaduct-elevated.3.4
cursor=./images/brick-viaduct-elevated.3.5
Image[-][0]=./images/brick-viaduct-elevated.1.2,0,32
Image[N][0]=./images/brick-viaduct-elevated.1.5,0,32
Image[S][0]=./images/brick-viaduct-elevated.2.1,0,32
Image[E][0]=./images/brick-viaduct-elevated.2.2,0,32
Image[W][0]=./images/brick-viaduct-elevated.2.0,0,32
Image[NS][0]=./images/brick-viaduct-elevated.1.0,0,32
Image[EW][0]=./images/brick-viaduct-elevated.1.1,0,32
Image[NSE][0]=./images/brick-viaduct-elevated.0.2,0,32
Image[NSW][0]=./images/brick-viaduct-elevated.0.4,0,32
Image[NEW][0]=./images/brick-viaduct-elevated.0.1,0,32
Image[SEW][0]=./images/brick-viaduct-elevated.0.3,0,32
Image[NSEW][0]=./images/brick-viaduct-elevated.1.2,0,32
Image[NE][0]=./images/brick-viaduct-elevated.3.0,0,32
Image[SE][0]=./images/brick-viaduct-elevated.2.3,0,32
Image[NW][0]=./images/brick-viaduct-elevated.2.4,0,32
Image[SW][0]=./images/brick-viaduct-elevated.2.5,0,32
ImageUp[3][0]=./images/brick-viaduct-elevated.1.3,0,32
ImageUp[6][0]=./images/brick-viaduct-elevated.1.4,0,32
ImageUp[9][0]=./images/brick-viaduct-elevated.0.0,0,32
ImageUp[12][0]=./images/brick-viaduct-elevated.0.5,0,30
Image[-][1]=./images/brick-viaduct-elevated-snow.1.2,0,32
Image[N][1]=./images/brick-viaduct-elevated-snow.1.5,0,32
Image[S][1]=./images/brick-viaduct-elevated-snow.2.1,0,32
Image[E][1]=./images/brick-viaduct-elevated-snow.2.2,0,32
Image[W][1]=./images/brick-viaduct-elevated-snow.2.0,0,32
Image[NS][1]=./images/brick-viaduct-elevated-snow.1.0,0,32
Image[EW][1]=./images/brick-viaduct-elevated-snow.1.1,0,32
Image[NSE][1]=./images/brick-viaduct-elevated-snow.0.2,0,32
Image[NSW][1]=./images/brick-viaduct-elevated-snow.0.4,0,32
Image[NEW][1]=./images/brick-viaduct-elevated-snow.0.1,0,32
Image[SEW][1]=./images/brick-viaduct-elevated-snow.0.3,0,32
Image[NSEW][1]=./images/brick-viaduct-elevated-snow.1.2,0,32
Image[NE][1]=./images/brick-viaduct-elevated-snow.3.0,0,32
Image[SE][1]=./images/brick-viaduct-elevated-snow.2.3,0,32
Image[NW][1]=./images/brick-viaduct-elevated-snow.2.4,0,32
Image[SW][1]=./images/brick-viaduct-elevated-snow.2.5,0,32
ImageUp[3][1]=./images/brick-viaduct-elevated-snow.1.3,0,32
ImageUp[6][1]=./images/brick-viaduct-elevated-snow.1.4,0,32
ImageUp[9][1]=./images/brick-viaduct-elevated-snow.0.0,0,32
ImageUp[12][1]=./images/brick-viaduct-elevated-snow.0.5,0,30

Offline Lord Vetinari

  • *
  • Posts: 125
Re: Brick rail elevated way introduction date
« Reply #2 on: December 29, 2010, 10:32:52 AM »
Thanks, I'll make my version of the viaduct.
By the way, I see retire_year=1926. Is there a newer elevated way in standard?

Offline jamespetts gb

  • Simutrans-Extended project coordinator
  • Devotee
  • *
  • Posts: 18745
  • Cake baker
    • Bridgewater-Brunel
  • Languages: EN
Re: Brick rail elevated way introduction date
« Reply #3 on: December 29, 2010, 11:13:05 AM »
The normal elevated way has an introduction date of 1835 and a retire date of 1954; in Experimental, there are new concrete elevated ways (albeit without their own graphics yet) which have no retirement date.

Incidentally, didn't you do a graphic for a brick bridge for Pak128.Britain some time ago? Whatever happened to that? It would be most useful to differentiate between the types.

Offline Lord Vetinari

  • *
  • Posts: 125
Re: Brick rail elevated way introduction date
« Reply #4 on: December 29, 2010, 08:53:45 PM »
You're right, I did. I think I still have the png and dat archived somewhere.

It wasn't enough in style and it was pixel art, so, since Photoshop filters weren't enough, I basically had to remake it from scratch if I wanted to fix it. I used it as a placeholder for my games untill pak Britain had it's first "official" bridge, then I deleted the .pak file.

Offline jamespetts gb

  • Simutrans-Extended project coordinator
  • Devotee
  • *
  • Posts: 18745
  • Cake baker
    • Bridgewater-Brunel
  • Languages: EN
Re: Brick rail elevated way introduction date
« Reply #5 on: December 29, 2010, 09:09:51 PM »
Would you mind uploading the .png file? I'd like to have a go at seeing if I can make it fit the style using the GIMP.

Offline Lord Vetinari

  • *
  • Posts: 125
Re: Brick rail elevated way introduction date
« Reply #6 on: December 29, 2010, 10:34:58 PM »
Sure, no problem. I upload it via Imageshack because it seems that the file excedes the attachment size limit:

I hope that's the right file, I remember I made a lot of versions to fix some small issues as I found them. If you find that something is not right, I'll search for the original photoshop file (but I'm not sure that I kept it).
There is no snow version.

This is the dat:

Code: [Select]
Obj=bridge
name=BrickRail
#copyright=
waytype=track
cost=50000
maintenance=1000
topspeed=110
max_lenght=10
max_height=1
intro_year=1830
intro_month=9
cursor=brick_rail_bridge.2.0
icon=> brick_rail_bridge.2.1
BackImage[NS]=brick_rail_bridge.2.2
FrontImage[NS]=brick_rail_bridge.3.2
BackImage[EW]=brick_rail_bridge.2.3
FrontImage[EW]=brick_rail_bridge.3.3
BackStart[N]=brick_rail_bridge.1.2
FrontStart[N]=brick_rail_bridge.0.2
BackStart[S]=brick_rail_bridge.1.0
FrontStart[S]=brick_rail_bridge.0.0
BackStart[E]=brick_rail_bridge.1.1
FrontStart[E]=brick_rail_bridge.0.1
BackStart[W]=brick_rail_bridge.1.3
FrontStart[W]=brick_rail_bridge.0.3
BackRamp[N]=brick_rail_bridge.5.0
FrontRamp[N]=brick_rail_bridge.4.0
BackRamp[S]=brick_rail_bridge.5.2
FrontRamp[S]=brick_rail_bridge.4.2
BackRamp[E]=brick_rail_bridge.5.3
FrontRamp[E]=brick_rail_bridge.4.3
BackRamp[W]=brick_rail_bridge.5.1
FrontRamp[W]=brick_rail_bridge.4.1

I remember I set the intro year to September 1830 because the bridge was vaguely inspired by one of Stephenson's bridges of the Liverpool-Manchester railway, but you can change it as you please.

Offline jamespetts gb

  • Simutrans-Extended project coordinator
  • Devotee
  • *
  • Posts: 18745
  • Cake baker
    • Bridgewater-Brunel
  • Languages: EN
Re: Brick rail elevated way introduction date
« Reply #7 on: December 29, 2010, 10:48:41 PM »
Thank you very much!

Offline jamespetts gb

  • Simutrans-Extended project coordinator
  • Devotee
  • *
  • Posts: 18745
  • Cake baker
    • Bridgewater-Brunel
  • Languages: EN
Re: Brick rail elevated way introduction date
« Reply #8 on: December 29, 2010, 11:57:29 PM »
Hmm, I don't think that these tiles have been cut correctly: here's what it looks like in the game:



Uploaded with ImageShack.us

Offline VS

  • Senior Plumber (Devotee)
  • Devotee
  • *
  • Posts: 4855
  • Vladimír Slávik
    • VS's Simutrans site
  • Languages: CS,EN
Re: Brick rail elevated way introduction date
« Reply #9 on: December 30, 2010, 12:05:56 AM »
...just offset them lower then? The nearer pillar goes out of normally aligned picture, so if you align according to it, it goes up.

Offline Lord Vetinari

  • *
  • Posts: 125
Re: Brick rail elevated way introduction date
« Reply #10 on: December 30, 2010, 09:56:23 AM »
Yeah, I remember that at first I had the same problem, but not how I fixed it. It means that the file is old, then. I can see another couple of small issues too (the lower front start overlaps the nex image by two pixels and the end on the opposite is a couple of pixel too short, so ther will be a gap).

Maybe, since there is nothing that actually overlaps the tracks, we may paste everything together so that we don't need front/back images anymore...

Tonight I'm leaving for New Year's eve, but I'll be back in a couple of days and I should be on holiday untill the 8th of January, so, if you don't find a solution, I can try to work on it next week.
« Last Edit: December 30, 2010, 10:02:54 AM by Lord Vetinari »

Offline jamespetts gb

  • Simutrans-Extended project coordinator
  • Devotee
  • *
  • Posts: 18745
  • Cake baker
    • Bridgewater-Brunel
  • Languages: EN
Re: Brick rail elevated way introduction date
« Reply #11 on: December 30, 2010, 11:11:55 AM »
I have no idea about cutting tiles for bridges, so this may have to await your return. Bon voyage!

Offline ӔO

  • Devotees (Inactive)
  • *
  • Posts: 2345
  • Hopefully helpful
  • Languages: en, jp
Re: Brick rail elevated way introduction date
« Reply #12 on: December 30, 2010, 11:45:40 AM »
For bridges with parts underneath the deck, try using offset ,0,32
The game automatically assumes that all bridges will only have the structure above deck.

this should work, they are the same offsets used for the brick viaduct.
Code: [Select]
Obj=bridge
name=BrickRail
#copyright=
waytype=track
cost=50000
maintenance=1000
topspeed=110
max_lenght=10
max_height=1
intro_year=1830
intro_month=9
cursor=brick_rail_bridge.2.0
icon=> brick_rail_bridge.2.1
BackImage[NS]=brick_rail_bridge.2.2,0,32
FrontImage[NS]=brick_rail_bridge.3.2,0,32
BackImage[EW]=brick_rail_bridge.2.3,0,32
FrontImage[EW]=brick_rail_bridge.3.3,0,32
BackStart[N]=brick_rail_bridge.1.2,0,32
FrontStart[N]=brick_rail_bridge.0.2,0,32
BackStart[S]=brick_rail_bridge.1.0,0,32
FrontStart[S]=brick_rail_bridge.0.0,0,32
BackStart[E]=brick_rail_bridge.1.1,0,32
FrontStart[E]=brick_rail_bridge.0.1,0,32
BackStart[W]=brick_rail_bridge.1.3,0,32
FrontStart[W]=brick_rail_bridge.0.3,0,32
BackRamp[N]=brick_rail_bridge.5.0
FrontRamp[N]=brick_rail_bridge.4.0
BackRamp[S]=brick_rail_bridge.5.2
FrontRamp[S]=brick_rail_bridge.4.2
BackRamp[E]=brick_rail_bridge.5.3
FrontRamp[E]=brick_rail_bridge.4.3
BackRamp[W]=brick_rail_bridge.5.1
FrontRamp[W]=brick_rail_bridge.4.1

Pillars were missing, but I guess they're not necessary for a max_height=1 bridge.
If pillars are to be used, then these lines should be added.
Code: [Select]
pillar_asymmetric=1
backPillar[S]=brick_rail_bridge.3.0,0,32
backPillar[W]=brick_rail_bridge.3.1,0,32

Offline Lord Vetinari

  • *
  • Posts: 125
Re: Brick rail elevated way introduction date
« Reply #13 on: December 30, 2010, 02:08:10 PM »
AEO and VS are right. It's the offset, I forgot! I have enough time to fix it.

This should work, I also fixed those pixel issues.



And this is the right dat:

Code: [Select]
Obj=bridge
name=BrickRail
#copyright=
waytype=track
cost=50000
maintenance=1000
topspeed=110
max_lenght=10
intro_year=1830
intro_month=9
cursor=brick_rail_bridge.2.0
icon=> brick_rail_bridge.2.1
BackImage[NS]=brick_rail_bridge.2.2
FrontImage[NS]=brick_rail_bridge.3.2,0,32
BackImage[EW]=brick_rail_bridge.2.3
FrontImage[EW]=brick_rail_bridge.3.3,0,32
BackStart[N]=brick_rail_bridge.1.2,0,32
FrontStart[N]=brick_rail_bridge.0.2
BackStart[S]=brick_rail_bridge.1.0
FrontStart[S]=brick_rail_bridge.0.0,0,32
BackStart[E]=brick_rail_bridge.1.1
FrontStart[E]=brick_rail_bridge.0.1,0,32
BackStart[W]=brick_rail_bridge.1.3,0,32
FrontStart[W]=brick_rail_bridge.0.3
BackRamp[N]=brick_rail_bridge.5.0
FrontRamp[N]=brick_rail_bridge.4.0
BackRamp[S]=brick_rail_bridge.5.2
FrontRamp[S]=brick_rail_bridge.4.2
BackRamp[E]=brick_rail_bridge.5.3
FrontRamp[E]=brick_rail_bridge.4.3
BackRamp[W]=brick_rail_bridge.5.1
FrontRamp[W]=brick_rail_bridge.4.1
backPillar[S]=brick_rail_bridge.3.0
backPillar[W]=brick_rail_bridge.3.1

I put max_height=1 because There were some alignement problems with the pillars that I were too lazy to fix (:P), but now that I look at the image in Photoshop everything seems right, so I added them too.

All back images and front_start 0.2 and 0.3 should be at the right place, so no offset needed (if I remember it right).
I'll test it myself, but I don't have makeobj anymore, and I can't find a place on the forum to download it.

If there's something else, I'll look at it Sunday or Monday. Happy new year everybody!
« Last Edit: December 30, 2010, 02:17:12 PM by Lord Vetinari »

Offline jamespetts gb

  • Simutrans-Extended project coordinator
  • Devotee
  • *
  • Posts: 18745
  • Cake baker
    • Bridgewater-Brunel
  • Languages: EN
Re: Brick rail elevated way introduction date
« Reply #14 on: December 30, 2010, 05:35:39 PM »
Ahh, that's lovely! I attach a modified version with the saturation and lightness turned down and a hint of Gaussian blur applied to make it fit better with other Pak128.Britain items. It'll be used as the graphic for the existing early brick rail bridge in Pak128.Britain-Ex, with the following .dat file:

Code: [Select]
Obj=bridge
name=BrickViaductEarly
waytype=track
intro_year=1815
intro_month=9
retire_year=1926
retire_month=10
topspeed=115
max_weight=80
max_height=5
cost=360000
maintenance=1485
cursor=images/brick_rail_bridge.2.0
icon=> images/brick_rail_bridge.2.1
BackImage[NS]=images/brick_rail_bridge.2.2
FrontImage[NS]=images/brick_rail_bridge.3.2,0,32
BackImage[EW]=images/brick_rail_bridge.2.3
FrontImage[EW]=images/brick_rail_bridge.3.3,0,32
BackStart[N]=images/brick_rail_bridge.1.2,0,32
FrontStart[N]=images/brick_rail_bridge.0.2
BackStart[S]=images/brick_rail_bridge.1.0
FrontStart[S]=images/brick_rail_bridge.0.0,0,32
BackStart[E]=images/brick_rail_bridge.1.1
FrontStart[E]=images/brick_rail_bridge.0.1,0,32
BackStart[W]=images/brick_rail_bridge.1.3,0,32
FrontStart[W]=images/brick_rail_bridge.0.3
BackRamp[N]=images/brick_rail_bridge.5.0
FrontRamp[N]=images/brick_rail_bridge.4.0
BackRamp[S]=images/brick_rail_bridge.5.2
FrontRamp[S]=images/brick_rail_bridge.4.2
BackRamp[E]=images/brick_rail_bridge.5.3
FrontRamp[E]=images/brick_rail_bridge.4.3
BackRamp[W]=images/brick_rail_bridge.5.1
FrontRamp[W]=images/brick_rail_bridge.4.1
backPillar[S]=images/brick_rail_bridge.3.0
backPillar[W]=images/brick_rail_bridge.3.1
-----
Obj=bridge
name=BrickViaduct
waytype=track
intro_year=1835
intro_month=2
retire_year=1948
retire_month=7
topspeed=200
max_weight=136
cost=435000
maintenance=1520
pillar_distance=1
pillar_asymmetric=1
cursor=images/brick-viaduct-175.2.1
icon=> images/brick-viaduct-175.2.0
BackImage[NS]=images/brick-viaduct-175.0.5,0,32
FrontImage[NS]=images/brick-viaduct-175.1.5,0,32
BackImage[EW]=images/brick-viaduct-175.0.4,0,32
FrontImage[EW]=images/brick-viaduct-175.1.5,0,32
BackStart[N]=images/brick-viaduct-175.0.0,0,32
FrontStart[N]=images/brick-viaduct-175.1.0,0,32
BackStart[S]=images/brick-viaduct-175.0.2,0,32
FrontStart[S]=images/brick-viaduct-175.1.2,0,32
BackStart[E]=images/brick-viaduct-175.0.1,0,32
FrontStart[E]=images/brick-viaduct-175.1.1,0,32
BackStart[W]=images/brick-viaduct-175.0.3,0,32
FrontStart[W]=images/brick-viaduct-175.1.3,0,32
BackRamp[N]=images/brick-viaduct-175.0.6
BackRamp[S]=images/brick-viaduct-175.0.8
BackRamp[E]=images/brick-viaduct-175.0.9
BackRamp[W]=images/brick-viaduct-175.0.7
FrontRamp[N]=images/brick-viaduct-175.1.6
FrontRamp[S]=images/brick-viaduct-175.1.8
FrontRamp[E]=images/brick-viaduct-175.1.9
FrontRamp[W]=images/brick-viaduct-175.1.7
backPillar[S]=images/brick-viaduct-175.2.3
backPillar[W]=images/brick-viaduct-175.2.2
BackImage[NS][1]=images/brick-viaduct-snow.0.5,0,32
FrontImage[NS][1]=images/brick-viaduct-snow.1.5,0,32
BackImage[EW][1]=images/brick-viaduct-snow.0.4,0,32
FrontImage[EW][1]=images/brick-viaduct-snow.1.5,0,32
BackStart[N][1]=images/brick-viaduct-snow.0.0,0,32
FrontStart[N][1]=images/brick-viaduct-snow.1.0,0,32
BackStart[S][1]=images/brick-viaduct-snow.0.2,0,32
FrontStart[S][1]=images/brick-viaduct-snow.1.2,0,32
BackStart[E][1]=images/brick-viaduct-snow.0.1,0,32
FrontStart[E][1]=images/brick-viaduct-snow.1.1,0,32
BackStart[W][1]=images/brick-viaduct-snow.0.3,0,32
FrontStart[W][1]=images/brick-viaduct-snow.1.3,0,32
BackRamp[N][1]=images/brick-viaduct-snow.0.6
BackRamp[S][1]=images/brick-viaduct-snow.0.8
BackRamp[E][1]=images/brick-viaduct-snow.0.9
BackRamp[W][1]=images/brick-viaduct-snow.0.7
FrontRamp[N][1]=images/brick-viaduct-snow.1.6
FrontRamp[S][1]=images/brick-viaduct-snow.1.8
FrontRamp[E][1]=images/brick-viaduct-snow.1.9
FrontRamp[W][1]=images/brick-viaduct-snow.1.7
backPillar[S][1]=images/brick-viaduct-snow.2.3
backPillar[W][1]=images/brick-viaduct-snow.2.2



Thank you for your contribution!

Offline jamespetts gb

  • Simutrans-Extended project coordinator
  • Devotee
  • *
  • Posts: 18745
  • Cake baker
    • Bridgewater-Brunel
  • Languages: EN
Re: Brick rail elevated way introduction date
« Reply #15 on: December 31, 2010, 07:07:45 PM »
Ahh, we seem to have some more problems with this, actually, that I hadn't spotted initially: see below for examples of (1) misaligned lead-ins; and (2) missing pillars:



Uploaded with ImageShack.us

Offline wlindley us

  • Devotee
  • *
  • Posts: 978
    • Hacking for fun and profit since 1977
  • Languages: EN, DE
Re: Brick rail elevated way introduction date
« Reply #16 on: December 31, 2010, 07:32:50 PM »
Well, that is characteristic of what the earliest railway bridges were predisposed to do.

Offline ӔO

  • Devotees (Inactive)
  • *
  • Posts: 2345
  • Hopefully helpful
  • Languages: en, jp
Re: Brick rail elevated way introduction date
« Reply #17 on: December 31, 2010, 07:48:08 PM »
this should get it working.
assuming you didn't move around the parts.
Code: [Select]
Obj=bridge
name=BrickViaductEarly
waytype=track
intro_year=1815
intro_month=9
retire_year=1926
retire_month=10
topspeed=115
max_weight=80
max_height=5
cost=360000
maintenance=1485
pillar_distance=1
pillar_asymmetric=1

cursor=images/brick_rail_bridge.2.0
icon=> images/brick_rail_bridge.2.1
BackImage[NS]=images/brick_rail_bridge.2.2
FrontImage[NS]=images/brick_rail_bridge.3.2,0,32
BackImage[EW]=images/brick_rail_bridge.2.3
FrontImage[EW]=images/brick_rail_bridge.3.3,0,32
BackStart[N]=images/brick_rail_bridge.1.2
FrontStart[N]=images/brick_rail_bridge.0.2
BackStart[S]=images/brick_rail_bridge.1.0
FrontStart[S]=images/brick_rail_bridge.0.0,-4,32
BackStart[E]=images/brick_rail_bridge.1.1
FrontStart[E]=images/brick_rail_bridge.0.1,4,32
BackStart[W]=images/brick_rail_bridge.1.3
FrontStart[W]=images/brick_rail_bridge.0.3
BackRamp[N]=images/brick_rail_bridge.5.0
FrontRamp[N]=images/brick_rail_bridge.4.0
BackRamp[S]=images/brick_rail_bridge.5.2
FrontRamp[S]=images/brick_rail_bridge.4.2
BackRamp[E]=images/brick_rail_bridge.5.3
FrontRamp[E]=images/brick_rail_bridge.4.3
BackRamp[W]=images/brick_rail_bridge.5.1
FrontRamp[W]=images/brick_rail_bridge.4.1
backPillar[S]=images/brick_rail_bridge.3.0,0,-32
backPillar[W]=images/brick_rail_bridge.3.1,0,-32

Offline jamespetts gb

  • Simutrans-Extended project coordinator
  • Devotee
  • *
  • Posts: 18745
  • Cake baker
    • Bridgewater-Brunel
  • Languages: EN
Re: Brick rail elevated way introduction date
« Reply #18 on: December 31, 2010, 07:56:05 PM »
Thank you - this has solved the pillar problem but not the first tile misalignment problem. Any ideas, anyone, for a solution for that? This is a beautiful bridge and it'd be good to be able to use it.

Offline ӔO

  • Devotees (Inactive)
  • *
  • Posts: 2345
  • Hopefully helpful
  • Languages: en, jp
Re: Brick rail elevated way introduction date
« Reply #19 on: December 31, 2010, 08:09:11 PM »
the numbers after the tile number are in X,Y offset.
Counter intuitively and not following foundations of math, -1 will move the image to the left or up and +1 will move it to the right or down.

I think image 0.0 needs another -4 on Y and image 0.2 needs +4 on Y.

How does this one work?
Code: [Select]
Obj=bridge
name=BrickViaductEarly
waytype=track
intro_year=1815
intro_month=9
retire_year=1926
retire_month=10
topspeed=115
max_weight=80
max_height=5
cost=360000
maintenance=1485
pillar_distance=1
pillar_asymmetric=1

cursor=images/brick_rail_bridge.2.0
icon=> images/brick_rail_bridge.2.1
BackImage[NS]=images/brick_rail_bridge.2.2
FrontImage[NS]=images/brick_rail_bridge.3.2,0,32
BackImage[EW]=images/brick_rail_bridge.2.3
FrontImage[EW]=images/brick_rail_bridge.3.3,0,32
BackStart[N]=images/brick_rail_bridge.1.2
FrontStart[N]=images/brick_rail_bridge.0.2,0.4
BackStart[S]=images/brick_rail_bridge.1.0
FrontStart[S]=images/brick_rail_bridge.0.0,-4,28
BackStart[E]=images/brick_rail_bridge.1.1
FrontStart[E]=images/brick_rail_bridge.0.1,4,32
BackStart[W]=images/brick_rail_bridge.1.3
FrontStart[W]=images/brick_rail_bridge.0.3
BackRamp[N]=images/brick_rail_bridge.5.0
FrontRamp[N]=images/brick_rail_bridge.4.0
BackRamp[S]=images/brick_rail_bridge.5.2
FrontRamp[S]=images/brick_rail_bridge.4.2
BackRamp[E]=images/brick_rail_bridge.5.3
FrontRamp[E]=images/brick_rail_bridge.4.3
BackRamp[W]=images/brick_rail_bridge.5.1
FrontRamp[W]=images/brick_rail_bridge.4.1
backPillar[S]=images/brick_rail_bridge.3.0,0,-32
backPillar[W]=images/brick_rail_bridge.3.1,0,-32

Offline VS

  • Senior Plumber (Devotee)
  • Devotee
  • *
  • Posts: 4855
  • Vladimír Slávik
    • VS's Simutrans site
  • Languages: CS,EN
Re: Brick rail elevated way introduction date
« Reply #20 on: December 31, 2010, 08:27:04 PM »
Offtopic:

Counter intuitively and not following foundations of math, -1 will move the image to the left or up and +1 will move it to the right or down.

The key is that screen has 0,0 in top left corner. Everything else follows. Graphs on the other hand are drawn with 0,0 at bottom left corner. (It's not math that cares which way are + and -, it's the man :P )

Offline ӔO

  • Devotees (Inactive)
  • *
  • Posts: 2345
  • Hopefully helpful
  • Languages: en, jp
Re: Brick rail elevated way introduction date
« Reply #21 on: December 31, 2010, 08:39:32 PM »
even then, f(x)=x to g(x)=(x-1)-1 in math transforms graphs to the right and down by 1 each.
which is exactly the opposite of what happens in simutrans.

Offline jamespetts gb

  • Simutrans-Extended project coordinator
  • Devotee
  • *
  • Posts: 18745
  • Cake baker
    • Bridgewater-Brunel
  • Languages: EN
Re: Brick rail elevated way introduction date
« Reply #22 on: December 31, 2010, 08:51:55 PM »
Hmm, problem's still there, I'm afraid, albeit now only with the other corner of the bridge:



Uploaded with ImageShack.us

Offline ӔO

  • Devotees (Inactive)
  • *
  • Posts: 2345
  • Hopefully helpful
  • Languages: en, jp
Re: Brick rail elevated way introduction date
« Reply #23 on: December 31, 2010, 09:06:48 PM »
hmm, the latest dat I posted up works fine for my game.

if image 0.0 and 0.1 are at the same height, and use the same Y offset, they should give the same results.

Offline jamespetts gb

  • Simutrans-Extended project coordinator
  • Devotee
  • *
  • Posts: 18745
  • Cake baker
    • Bridgewater-Brunel
  • Languages: EN
Re: Brick rail elevated way introduction date
« Reply #24 on: December 31, 2010, 09:49:23 PM »
That is odd indeed.

Offline Václav

  • Devotee
  • *
  • Posts: 3267
  • formerly VaclavMacurek
  • Languages: CZ, EN
Re: Brick rail elevated way introduction date
« Reply #25 on: January 01, 2011, 03:16:46 PM »
Seeing this topic and problems with making of that bridge it reminds my beginning with making bridges - my problem was in wrong elevation of way - but here all seems be okay.

... and reading dat file code, I would like to ask you for explaining of offsets - if it is not described anywhere.

I beg your pardon for disturbing from hard work on your pakset and its objects.

Offline Lord Vetinari

  • *
  • Posts: 125
Re: Brick rail elevated way introduction date
« Reply #26 on: January 01, 2011, 11:50:06 PM »
I'm back.

It seems that I added some problems. I should never do things in haste, the result is that I forget something. I'm sorry.
It seems that while I said that back images don't need offsets, I actually forgot to remove them from the code of the two start tiles. Well, you already fixed that.

I don't know why the last part behaves like that.
I can however spot another couple of problems: First, if you look closely at the last image posted by James, you can see some sharp lines on the white columns and a double sized column at the end. I bet that those are the pillars that somehow get in the way. I'd try removing their offsets.
Maybe the pillars have a role in the odd behaviour of that end part...

Second, it's a small one, the tile front_start [n] (that is, image 0.2) is two pixel too high. 0.3 may require the same adjustment, but I'd test it first.

Third, that tile that is behaving oddly is four pixels too much to the left. You can see that it's column is right above the column of the front straight part, if we just move down the tile, the two columns will overlap. I think that we should change those 4 points of horizontal offset. I don't know how much, however.

« Last Edit: January 01, 2011, 11:56:47 PM by Lord Vetinari »

Offline ӔO

  • Devotees (Inactive)
  • *
  • Posts: 2345
  • Hopefully helpful
  • Languages: en, jp
Re: Brick rail elevated way introduction date
« Reply #27 on: January 02, 2011, 01:49:19 AM »
Seeing this topic and problems with making of that bridge it reminds my beginning with making bridges - my problem was in wrong elevation of way - but here all seems be okay.

... and reading dat file code, I would like to ask you for explaining of offsets - if it is not described anywhere.

I beg your pardon for disturbing from hard work on your pakset and its objects.

image # row, # column, X offset, Y offset.
if X is positive, the image moves right.
if X is negative, the image moves left.
if Y is positive, the image moves down.
if Y is negative, the image moves up.

One tile height, Y, is 32.
I'm not sure about tile width, but I think 32 will move the image half a tile horizontally, or on X.

Offline Václav

  • Devotee
  • *
  • Posts: 3267
  • formerly VaclavMacurek
  • Languages: CZ, EN
Re: Brick rail elevated way introduction date
« Reply #28 on: January 02, 2011, 12:18:28 PM »
Thanks. Now I can repaint this viaduct

to shape with pillars on edges of tile - and so it will be better

but it has to wait until finishing currently prepared building

Offline The Hood

  • Moderator
  • *
  • Posts: 2889
  • pak128.Britain developer
Re: Brick rail elevated way introduction date
« Reply #29 on: January 02, 2011, 06:06:26 PM »
James's modified graphics fit very nicely into the pak style so I'd happily include them once the alignment problems are ironed out.  To do this can you not just take the png and dat from the bridge already in the pak and mimic the alignment and offsets with yours?

Offline Václav

  • Devotee
  • *
  • Posts: 3267
  • formerly VaclavMacurek
  • Languages: CZ, EN
Re: Brick rail elevated way introduction date
« Reply #30 on: January 02, 2011, 10:11:36 PM »
The Hood, I have to say that I don't understand these words

Quote
To do this can you not just take the png and dat from the bridge already in the pak and mimic the alignment and offsets with yours?

much. And I am worried about you did not understand me too.

I did not know about offsets - before reading this topic.

When I started making objects for Simutrans (few years ago) I wanted to paint viaduct like this

but because I did not know about offsets, I had to create that viaduct from my screenshot published above as it is - with pillars in the middle of tile.

And you see, it is not good - for crossing with else ways of all types. And with using of offsets, I can remake it.

Is it clear, now?

I think highly about Pak128.Britain - but it is too dark for me. So I cannot use its objects for that reason - and I would like to use many ones of Pak128.Britain because they are so good.
« Last Edit: January 02, 2011, 10:27:28 PM by VaclavMacurek »

Offline The Hood

  • Moderator
  • *
  • Posts: 2889
  • pak128.Britain developer
Re: Brick rail elevated way introduction date
« Reply #31 on: January 02, 2011, 11:10:12 PM »
@Vaclav,

I was referring more to Lord Vetinari's viaduct, but the same would apply to you.  Take the png and dat for the kierongreen's pak128.Britain viaduct from the pak128.Britain repository on sourceforge, and use that as a template: i.e. make the arches and pillars lign up in the same places as those on the existing one, and modify the dat file in the same way.  This would make your viaduct work as per the pak128.Britain one.

If you find pak128.Britain objects too dark and want to use some of them, you could always take the source image and lighten it up in the gimp and re-make it - that's the good thing about open source releases!

Offline Lord Vetinari

  • *
  • Posts: 125
Re: Brick rail elevated way introduction date
« Reply #32 on: January 03, 2011, 08:06:23 PM »
I tried, but my bridge is not the same size of the existing rail bridge, so there are still adjustment to do.
I'd better redownload Makeobj and do some tests via trial and error myself. Where I can find it?

Offline ӔO

  • Devotees (Inactive)
  • *
  • Posts: 2345
  • Hopefully helpful
  • Languages: en, jp
Re: Brick rail elevated way introduction date
« Reply #33 on: January 11, 2011, 07:55:47 PM »
going back on the main topic, there are no trains that really need elevated or brick viaducts until at least 1830.

1825 is when you first get the SDR locomotion, which does 30km/h
1828 is when you first get passenger carriages for rail.

It would seem odd that there is such a large and costly infrastructure already in place, before rail really kicked off.

Offline jamespetts gb

  • Simutrans-Extended project coordinator
  • Devotee
  • *
  • Posts: 18745
  • Cake baker
    • Bridgewater-Brunel
  • Languages: EN
Re: Brick rail elevated way introduction date
« Reply #34 on: January 11, 2011, 11:18:43 PM »
I suppose that the answer to that point is that it was perfectly possible to build such things before 1830, but there was no particular economic incentive to do so. By making them available before 1830, that realistic situation is accurately simulated.