Re: NotRoadTypes
Posted: 02 May 2019 21:04
Yay, thank you everybody
The place to talk about Transport Tycoon
https://www.tt-forums.net/
If I read your question right, this has been possible for the longest time. It is set out as a global variable in the NewGRF Specifications. I don't do NML so I can't say if it is supported there, but I would imagine that it is.Andrew350 wrote:(On a related side note, can NewGRFs themselves even detect OpenTTD versions any more? I can't find any info on an updated format, I know it was talked about but don't know if one was ever decided on and implemented.)
wallyweb wrote:Will the sample NewGRF Specifications need modifications or are they complete as linked to in the first post?andythenorth wrote:The first page of this thread has links to forks of NML with NRT support. A proper release of NML will also be needed for this, we'll get to that.
A daunting task.peter1138 wrote:I'll have time to go through them tonight and make them tentatively official. There's a couple of additional flags (town can build and hidden) but no major changes.
grfcodec fortunately just works with NRT, no changes neededarikover wrote:Is an update of grfcodec/nforenum also planned?
Pity. It is so very good at finding missing ";" and line breaks and reminding us of the erers of our waysandythenorth wrote:nforenum is no longer maintained as far as I know, so probably won't get updated unless somebody volunteers
Can you please stop again with the bulls*** spreading? It's part of grfcodec, it's under our wing, it will be updated.andythenorth wrote:nforenum is no longer maintained as far as I know
Yes the feature is there and it still works for releases (I think), but as far as I know it expects a certain format for the nightly version (like r21234 or so), so I'm not sure if it will work with the new format (openttd-20190502-master-blahblahblah). Unless it just works, maybe I just don't know how to write it correctly? I thought I saw some talk on irc about a new internal version number system, but don't recall what ever came of it, if anything.wallyweb wrote:If I read your question right, this has been possible for the longest time. It is set out as a global variable in the NewGRF Specifications. I don't do NML so I can't say if it is supported there, but I would imagine that it is.Andrew350 wrote:(On a related side note, can NewGRFs themselves even detect OpenTTD versions any more? I can't find any info on an updated format, I know it was talked about but don't know if one was ever decided on and implemented.)
I think I see where you are coming from. Stable is currently at 1.9.1 When OTTD went to stable, I think master went to 1.10.0, but that is of little help when there is a new master almost every night. The problem is that github randomly generates a new number. Why not do a test and test for 1.10? If that works, at least you'll know you're not working with stable.Andrew350 wrote:Yes the feature is there and it still works for releases (I think), but as far as I know it expects a certain format for the nightly version (like r21234 or so), so I'm not sure if it will work with the new format (openttd-20190502-master-blahblahblah). Unless it just works, maybe I just don't know how to write it correctly? I thought I saw some talk on irc about a new internal version number system, but don't recall what ever came of it, if anything.
To be more accurate, the most active former maintainers have either left (rubidium), or have said they will not maintain it (frosch).peter1138 wrote:Can you please stop again with the bulls*** spreading? It's part of grfcodec, it's under our wing, it will be updated.
Yeah I thought about that after posting. Honestly I'm a bit skeptical but if it works that might be okay for now (still not ideal though). I'll have to test once I get homewallyweb wrote:Why not do a test and test for 1.10? If that works, at least you'll know you're not working with stable.
Nah, I just started it all with Andy, other people did really more workacs121 wrote:Maybe you should also thank yourself for everything you did for NRT ?
Well, nice to hear that grfcodec already works with NRT, and nice to hear that nforenum was not forgotten...andythenorth wrote:To be more accurate, the most active former maintainers have either left (rubidium), or have said they will not maintain it (frosch).peter1138 wrote:Can you please stop again with the bulls*** spreading? It's part of grfcodec, it's under our wing, it will be updated.
But contributions are welcome https://github.com/OpenTTD/grfcodec
the check for 1.9 vs. 1.10 still works, but with the move to git as the main repository, there is no linear revision number anymore. so you cannot do any checks like "was this before or after NRT merge?" currently, unless someone invents a new counting method, and puts that into the build system. (PRs welcome, i guess)wallyweb wrote:I think I see where you are coming from. Stable is currently at 1.9.1 When OTTD went to stable, I think master went to 1.10.0, but that is of little help when there is a new master almost every night. The problem is that github randomly generates a new number. Why not do a test and test for 1.10? If that works, at least you'll know you're not working with stable.Andrew350 wrote:Yes the feature is there and it still works for releases (I think), but as far as I know it expects a certain format for the nightly version (like r21234 or so), so I'm not sure if it will work with the new format (openttd-20190502-master-blahblahblah). Unless it just works, maybe I just don't know how to write it correctly? I thought I saw some talk on irc about a new internal version number system, but don't recall what ever came of it, if anything.
Eddi wrote:the check for 1.9 vs. 1.10 still works, but with the move to git as the main repository, there is no linear revision number anymore. so you cannot do any checks like "was this before or after NRT merge?" currently, unless someone invents a new counting method, and puts that into the build system. (PRs welcome, i guess)
DISCLAIMER: Not being pushy. I understand that this will be done when it is done.peter1138 wrote:I'll have time to go through them tonight and make them tentatively official. There's a couple of additional flags (town can build and hidden) but no major changes.
no, the GRF only tells the town which roadtypes are available for building in general. the town makes the final decision of which road to build. the decision how that is done might be made available to some town ai type thing in the distant futurewallyweb wrote:If a town can build roads, can a grf tell the town which road type to build in each town zone?
no, properties are fixed, they cannot change depending on town zone. (that would require a callback, and probably some place to cache the callback result)Town zones shift as a town grows. Will the road type evolve and more specifically will the speed limit property follow?
Thanks Eddi. So if I understand you correctly, when a player starts a new game, there will be no speed limits anywhere until the player overbuilds a road with a road type and if the player wants to maintain zone specific speed limits the player will have to monitor the towns as they grow?Eddi wrote:no, the GRF only tells the town which roadtypes are available for building in general. the town makes the final decision of which road to build. the decision how that is done might be made available to some town ai type thing in the distant futurewallyweb wrote:If a town can build roads, can a grf tell the town which road type to build in each town zone?no, properties are fixed, they cannot change depending on town zone. (that would require a callback, and probably some place to cache the callback result)Town zones shift as a town grows. Will the road type evolve and more specifically will the speed limit property follow?