{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreichwtmn2x4zbbcima2legfmb6gyi6xvjc6744mcvb5wzuvkamutsq",
    "uri": "at://did:plc:i7budt2wflrcfy6jtvfocbix/app.bsky.feed.post/3mmu4sk3x3q42"
  },
  "path": "/viewtopic.php?p=1279270#p1279270",
  "publishedAt": "2026-05-27T14:30:03.000Z",
  "site": "https://www.tt-forums.net",
  "tags": [
    "https://docs.google.com/spreadsheets/d/ ... p=drive_fs",
    "https://en.wikipedia.org/wiki/UAC_TurboTrain",
    "https://ru.wikipedia.org/wiki/%D0%92%D0%9B22",
    "nemethv",
    "@VEHIDCODE"
  ],
  "textContent": "> Me again -> https://docs.google.com/spreadsheets/d/ ... p=drive_fs\n>\n> So that's an excel file with all the steam engines, their wiki links and the withdrawal dates i could find. Not all have data, not all dates are the \"first\" and i've generally excluded items where withdrawal was due to war damage or similar.\n> See what your thoughts are about the dates, and if ok i can merge them into the dataset.\n\nI've updated the file here. It now contains all vehicles, not just steam.\n... but the same note from before applies -> not all withdrawal dates are the \"earliest\" because such info isn't always definitely available. Withdrawals due to accidents and damage don't count.\nalso a lot of vehicles are new or still in service w/o withdrawals. thus my suggestion are that\n- we always take a minimum of n years for availability regardless of anything. eg. https://en.wikipedia.org/wiki/UAC_TurboTrain had a lifespan of 8 years, I don't think it's sensible to keep such a low value.\n\nThe below are for MODEL LIFE\n- we lower the never-expires to anything build after 1990\n- if the expiry date would come to higher than idk 2025 the vehicle never expires. (this lines up with 1990+35)\n\nI didn't always mark the still-in-service items but did mark the ones that seem to have outlive their standard age (ie were intro'd a \"long time ago\" whatever that is and are still in service) with a 2030 w/d date - also I didnt' really bother looking up expiration dates for vehicles where the possible date, if any, would certainly fall into the 'never expires' period.\n\nAlso if someone is willing to dig into stuff eg https://ru.wikipedia.org/wiki/%D0%92%D0%9B22 the first one was retired in the 70s but there is literally just one still operating. I marked it as 70s retirement. Perhaps read through the data if time-rich....:/\n\nThe current formula is\n\nCode:\n\n\n    =IF(ISNUMBER([@[WITHDRAWAL_YEAR]]), MAX([@[WITHDRAWAL_YEAR]]-[@[INTRODUCTION_YEAR]], IFS(OR(ISNUMBER(SEARCH(\"powered\",[@VEHIDCODE])),ISNUMBER(SEARCH(\"_wagon_\",[@VEHIDCODE])),ISNUMBER(SEARCH(\"_coach_\",[@VEHIDCODE]))), 25, ISNUMBER(SEARCH(\"mtro_\",[@VEHIDCODE])), 50, [@[INTRODUCTION_YEAR]]<1950, 30, [@[INTRODUCTION_YEAR]]<2000, 40, TRUE, 45)), IFS(OR(ISNUMBER(SEARCH(\"powered\",[@VEHIDCODE])),ISNUMBER(SEARCH(\"_wagon_\",[@VEHIDCODE])),ISNUMBER(SEARCH(\"_coach_\",[@VEHIDCODE]))), 25, ISNUMBER(SEARCH(\"mtro_\",[@VEHIDCODE])), 50, [@[INTRODUCTION_YEAR]]<1950, 30, [@[INTRODUCTION_YEAR]]<2000, 40, TRUE, 45))\n\n(yeah sorry no formatting)\n\nI've updated the googledrive grf with the above if anyone wants to play around.\nalternatively if someone prefers I can update either the excel file in github and/or all the nml files so they are easier to diff.\n\nStatistics: Posted by nemethv — 27 May 2026 14:30\n\n* * *",
  "title": "Graphics Development • Re: [OTTD] 2cc TrainsInNML",
  "updatedAt": "2026-05-27T14:30:03.000Z"
}