BK Enhanced Tunnel Set v1.2 (9-April-2011) [update]

[Eddi]

Either because nobody is interested in it or because those who are interested don't want to learn the skill to make it happen.

or maybe because it is very complicated and the people who have the skills are otherwise preoccupied

[wallyweb]

Either because nobody is interested in it or because those who are interested don't want to learn the skill to make it happen.

or maybe because it is very complicated and the people who have the skills are otherwise preoccupied

This goes back a couple (few?) years, but if I remember correctly, eis_os had several issues to contend with when developing enhanced tunnels, but he persevered and eventually made them work. Any chance the OTTD challenges might be similar to what he encountered?

[Eddi]

probably not at all, since the OpenTTD codebase is much more flexible than the TTDPatch codebase, the problems won't be so much technical in nature, but more logical in nature ("how can we achieve this" vs. "what do we actually want to have"). the requirements how "clean" the feature is implemented will be much higher for being accepted into the OpenTTD codebase.

[charityalbumman]

Version 1.2 needs uploading to the bananas system:

http://bananas.openttd.org/en/newgrf/

[wallyweb]

Version 1.2 needs uploading to the bananas system:

http://bananas.openttd.org/en/newgrf/

Look for Canadian (BK) Tunnels v1.6

[suburbansky]

The tunnel always looks the same, regardless of climate and/or parameters... Is that because I use OpenTTD instead of a Patch, or am I doing something wrong?

[wallyweb]

Which version of BK tunnels are you using?

[suburbansky]

The latest one, v 1.2.

[wallyweb]

The latest one, v 1.2.

Actually the latest one is linked to here, a couple of posts above this one.

[suburbansky]

OK, thanks - I tried that one, but now the NewGRF won't work at all...

[wallyweb]

OK, thanks - I tried that one, but now the NewGRF won't work at all...

If you are using any other Canadian GRFs that are not at version 1.6, they need to be updated. Explanation is here.

[suburbansky]

Now I'm confused... Which of my NewGRFs makes a fuss now?

[OzTrans]

Now I'm confused... Which of my NewGRFs makes a fuss now?

OpenGfx Airports v0.4.1 is not compatible with any Canadian graphic files. The creators of OpenGfx Airports refuse to fix the problem; but you can request an update by PM (from me) of "Canadian (OG) Airports v0.4.2", which has the same functionality ...

[ISA]

Now I'm confused... Which of my NewGRFs makes a fuss now?

OpenGfx Airports v0.4.1 is not compatible with any Canadian graphic files. The creators of OpenGfx Airports refuse to fix the problem; but you can request an update by PM (from me) of "Canadian (OG) Airports v0.4.2", which has the same functionality ...

Had the same problem yesterday! Found out the problem by activating grf's one by one!

[planetmaker]

Now I'm confused... Which of my NewGRFs makes a fuss now?

OpenGfx Airports v0.4.1 is not compatible with any Canadian graphic files. The creators of OpenGfx Airports refuse to fix the problem; but you can request an update by PM (from me) of "Canadian (OG) Airports v0.4.2", which has the same functionality ...

Just to elaborate on the "problem": You chose somewhen against the unwritten rules grfIDs in the range CAXX. And likely Yexo somewhen chose CAYY for the airports grf. At a time where neither your grf were available nor AirportsPlus (now OpenGFX+Airports) was available. And now you claim that Yexo (or me or someone else) needs to change the grfID of OpenGFX+Airports - depsite there being no problem for both to co-exist nicels, no technical reasons whatsoever for any move like that from any side - there can be 64k NewGRFs with a grfID of the type CAxy, and no two which were published did ever collide.

Making up this "problem" obviously backfires, though and causes real problems for your users: people fail to find updates for your NewGRFs as can be seen here and elsewhere

[V453000 :)]

[enjoy your pointlessly caused problems]
with love

[Twyster]

This conversation (which I hope I am reading into correctly) is p***ing me off. GRF developers need to stop being stubborn and get with the program. Why should the Canadian graphics be incompatible with OpenGFX+ Airports just because neither side is willing to yield?!

Look, I may not have any authority, but I hereby make a request as close in nature to a demand as is reasonable that OzTrans or Yexo fix this problem as soon as possible. This is unfair, stupid, annoying and aggrivating, and I've had enough of it!

[wallyweb]

This conversation (which I hope I am reading into correctly) is p***ing me off. GRF developers need to stop being stubborn and get with the program. Why should the Canadian graphics be incompatible with OpenGFX+ Airports just because neither side is willing to yield?!

Look, I may not have any authority, but I hereby make a request as close in nature to a demand as is reasonable that OzTrans or Yexo fix this problem as soon as possible. This is unfair, stupid, annoying and aggrivating, and I've had enough of it!

Posted here earlier today:

As wallyweb mentioned, at present, the only non-Canadian GRF that could give you problems is OpenGfx Airports. Should that be the case, there is an updated version (Canadian (OG) Airports v0.4.2) available on request.

PM a request to OzTrans ... problem solved.

[Twyster]

This conversation (which I hope I am reading into correctly) is p***ing me off. GRF developers need to stop being stubborn and get with the program. Why should the Canadian graphics be incompatible with OpenGFX+ Airports just because neither side is willing to yield?!

Look, I may not have any authority, but I hereby make a request as close in nature to a demand as is reasonable that OzTrans or Yexo fix this problem as soon as possible. This is unfair, stupid, annoying and aggrivating, and I've had enough of it!

Posted here earlier today:

As wallyweb mentioned, at present, the only non-Canadian GRF that could give you problems is OpenGfx Airports. Should that be the case, there is an updated version (Canadian (OG) Airports v0.4.2) available on request.

PM a request to OzTrans ... problem solved.

That's what I was getting at when I said what I did, that people have asked OzTrans to fix it and he refuses to and places the burden on Yexo. Now when I say "as close in nature to a demand as is reasonable" I mean "please fix this and if you don't I will vocally protest it", so my goal is not to be demanding for my own sake but to prevent this kind of thing from negatively impacting everyone.

I'll PM a copy of this entire post to OzTrans and Yexo, but if either or both of them don't listen I will post a condemnation of the work ethic of those that were uncooperative in the relevant topics and never again use any of their GRFs.

[wallyweb]

I'll PM a copy of this entire post to OzTrans and Yexo, but if either or both of them don't listen I will post a condemnation of the work ethic of those that were uncooperative in the relevant topics and never again use any of their GRFs.

Have a nice day.
And please don't let the screen door slam on your way out.