Dutch Trainset v2.0

[Purno]

> Articulated engines are a pain to code [...]

I can try to help with that. Articulated engines are handled by callback 16 [...]

We´ve been there. He needs a recipe for GRFMaker.

Indeed. Thanks anyways

Not all real MU consists are possible [...]

Every real MU consist is possible to code, though not in GRFMaker. Possibly.

regards
Michael

It is codable in GRFMaker, but I just don't think it's really worth the effort (at least, not yet), because it's a hell of a job with too little to gain IMO. The Dutch Trainset team always wanted a perfect set, but I came to the conclusion that if we ever want to release a GRF we have to be less perfectionistic.

[MJS]

Obviously, there can be a version 2 that further fancifies some of the stuff. (Or a version 0.2, depending on your numbering system.)

[lobster]

i vote for an unorthodox numbering system. perhaps we should call all versions "0.42".

[Samwise]

i vote for an unorthodox numbering system. perhaps we should call all versions "0.42".

Version 0.42a, 0.42b.. etc ?

[Hyronymus]

Just start with version 0.01, followed by a letter for small fixes and a new number for new releases.

[BlueEagle_nl]

I received an email of my contact at the Spoorwegmuseum. He contacted one of his colleagues which could help us updating the vehicle list with correct passenger coach/locomotive combinations.

I've updated the first tab of the Infosheet (see attachment) with the information received. Please read all the notes placed along the page, which contain some extra info.

All locs for which Allowed Veh-ID's has not been set, were only used for goods or mail transport.

[EDIT]Also, the ICR Pax should be called the ICRm, my contact replied later. This is changed in the Infosheet[/EDIT]

For more information, or the original mails, please send me a mail.

[Purno]

Just start with version 0.01, followed by a letter for small fixes and a new number for new releases.

I never really understood the use of those 00.00.00.00.00.00 thingy system. Lets just start with Release 1, with the next release being Release 2. Why making it more complicated than necessary? Besides, we got the GRF-ID to distinguish versions.

...

Nice work! But it doesn't clear up much for me. Another problem is that quite some wagons are not drawn yet. And then there is the problem that not all passenger coaches are as long while they share the same VehID.

[FooBar]

Besides, we got the GRF-ID to distinguish versions.

I don't think GRFID is meant for that. Having different GRFIDs means that you can have different versions active at the same time; a bit odd.

Myself, I use only one grfid per set, which stays the same for the whole set's life. Version numbering is indicated in the sets title in the NewGRF window, and in the Windows filename (the dos filename doesn't have room for that).

As for version numbering, I use a whole bunch of different numbering systems:
- r1, r2, r3 etc. for the Dutch Tramset (currently r18).
- Some personal GRFs got v1.0 right from the beginning
- My New Tramtracks started with v0.1 and are currently bearing v0.4.1. I don't think it will ever get to v1.0 as new terrain sets keep spawning lately, so my set never gets to a point where it can be considered 'finished' (i.e. v1.0).

So pick one If I'd have to choose, I'd go for the rx system for the Dutch Trainset. Easy yet effective.

[eis_os]

While it's not the clear on the wiki, the general style is:

Don't change the GRFID of your GRF if the version is compatible.
Sample: You have a train set and add new vehicles and the old one still work.
(The user upgrades and will have the new features, the grf is active when loading)

However you have to change the GRFID if you set is incompatible. You change the vehicle id scheme completely as example.

The user upgrades, because it's not in the Savegame stored, it will be deactivated, TTDPatch will revert to default ones, the user can see it's incompatible.
It's a good idea to use a different name too, this way the user can play old and new savegames...

[Purno]

Strange, I've read somewhere the GRF ID consisted four digits for the author's name, two digits for the GRF, and two digits for the revision.

Anyways, IIUC, the compatibility you are talking about, does not include backwards compatibility?

[DaleStan]

Different definitions of "version".

If I write a Word document, then change it twice, I now have three versions (version number) of the document. But the format version (ie, the GRFID) remains the same, since it's still a Word document.

[eis_os]

You mean here as example:

http://wiki.ttdpatch.net/tiki-index.php?page=Action8

A reason I wrote "While it's not the clear on the wiki"... But I did explain the details why and when to change the GRFID... I explained in detail why and when you should change or not change the GRFID...

It's generally creator's initials (2 Bytes) + setid + version.

[BlueEagle_nl]

Purno, if you want, I can send you the full e-mail in which my contact gives the information, which lists each loc and the carriages which have been linked to them.

[Purno]

Can you post it at the forums instead? Such info should be available to the public. (Leave out e-mail addresses of course).

[BlueEagle_nl]

Freely translated from the e-mail, only included the statistic-part of the mail, not the full mail!
Locname - Coach names
NS 1200 E - AB 7200 / ABCd 7300 ("Bolkop") / AB7c / Plan D / Plan E / Plan W / later also ICR
NS 1300 E - AB 7200 / ABCd 7300 ("Bolkop") / AB7c / Plan D / Plan E / Plan W / later also ICR
NS 1500 E - used only AB 7351 / Bc 7000 for The Hague - Venlo v.v. service
NS 1600 E - first Plan E / Plan W / later ICR; now only for cargo service
NS 1700 E - most of them using DDARs; some of them drive as an 1800 E
NS 1800 E - developed from the NS 1600 E series; drive with ICR / ICK / ICRm / incidentally Benelux-coaches
NS 2100 S - AB7c / AB 7200 / ABCd 7300 ("Bolkop") / Plan D
NS 2200 DE - Cargo service, incidentally for passenger trains using AB 7200
NS 2400 DE - Cargo Service
NS 2600 DE - Plan D
NS 3900 S - AB7c / AB 7200 / ABCd 7300 ("Bolkop") / Plan D
NS 4600 S - Cargo Service
NS 4700 S - Cargo Service
NS 5000 S - Train only for local passenger transport, using wooden coaches
NS 6200 S - Cargo Service
NS 6300 S - Cargo Service, incidentally used for passenger transport in Limburg, using wooden coaches
NS 6400 DE - Cargo Service
NMBS Reeks 11.8 - Benelux
NMBS Reeks 25.5 - Benelux

E = Electric / DE = Diesel/Electric / S = Steam

I'm missing the NS 3700 S series. Their services are the same as the NS 3900 S series. Note by Paffy: I didn't include the 3700s for their info was already filled into the Infosheet

The AB7c are kinda problem. They were luxurious, wooden coaches of after 1900. They always drive in combination with C9's or C10's, and mostly in international trains pulled by 3700s or 3900s, until ca. 1936. They don't fit in the current time!

The AB 7200 and ABC 7300 are part of the international rolling stock; after the start of Plan D services, they were used in national trains.

It is not possible to make a standard combination of Locs and coaches. The stock was and still is used in random order, so different than in other countries.

Let me know when and if the full conversation is necessary here. I'll type out a .doc then containing the mails.

[MJS]

Apart from the coaches and the sprite realignment, have major issues come up in alpha testing?

[lobster]

well, i've been test playing this baby for quite some time (as i literally stated earlier), and it's truly playable already. i've managed to make a good game with common difficulty options, and enjoyed it thoroughly.

anyway, i've discussed the most problems with Purno already. things like the tenders, some carriages... it's mainly small, minor things.

[Purno]

This weekend I'm staying over at my GF's house. After monday I should have some time available, so by then I"d like a list of all conclusions of the playtesters so I can work on it. (Though I have other interests too).

[MJS]

Sounds good! Many thanks for your continuous efforts on the coding, Purno, especially as it's not your native habitat.

[Purno]

Indeed, but GRFMaker eases up a lot of things on coding.