Moderator: Graphics Moderators
av8 Aviators Aircraft Set version 2.2 as downloaded from BaNaNaS says:PikkaBird wrote:The first av8 version to test for OpenGFX+ Airports and disable its own changes if found will be version 2200.
(Although I believe the duplicate-entries problem has been solved.)
Thanks for that update. It seems that I received the translation before the parameters were added...Kraks wrote:GRF params are still in English... At least for Russian.planetmaker wrote:Code: Select all
- Add: translations for Dutch, German, Russian, Spanish and Traditional Chinese
upd:
Here is the translation:Code: Select all
EN Disable airport noise limits RU Отключить уровни шума аэропортов EN Disable airport date restrictions RU Отключить ограничения аэропортов по датам EN Airport maintenance costs RU Стоимости обслуживания аэропортов EN normal RU обычные
Ah, that's unfortunate. But yes, it should still work in the sense that the airports are not duplicate (av8 won't define them), but OpenGFX+ Airports won't respect av8's cost parameters in that case as they're bound to av8 version 2200 or later in OpenGFX+ Airport's source:Supercheese wrote:av8 Aviators Aircraft Set version 2.2 as downloaded from BaNaNaS says:PikkaBird wrote:The first av8 version to test for OpenGFX+ Airports and disable its own changes if found will be version 2200.
Version: 2150
Accordingly, OGFX+ Airports still complains about the maintenance parameter.
Code: Select all
#define GRF_PRESENT_AV8 (av8_compatibility & 0x01)
#define GRF_NEW_VERSION_AV8 (av8_compatibility & 0x02)
#define GRF_MAINTENANCE_AV8 (av8_compatibility & 0x04)
#define GRF_SPECIALS_AV8 (av8_compatibility == 0x07)
av8_compatibility = grf_future_status(GRFID_AV8) |
(param[GRFID_AV8, 254] >= 2200) << 1 |
(param[GRFID_AV8, 5] & 0x00000001) << 2;
if (GRF_PRESENT_AV8 && GRF_MAINTENANCE_AV8 && !GRF_NEW_VERSION_AV8) {
error(WARNING, string(STR_WARNING_OLD_AV8_WITH_PARAM));
}
Code: Select all
if GRF_SPECIALS_AV8 { property { maintenance_cost: 1; } }
STR_WARNING_OLD_AV8_WITH_PARAM :Вы активировали уменьшение стоимости обслуживания аэропортов в старой версии av8. Это приведёт к появлению второго набора аэропортов в игре. Рекомендуется использовать av8 версии 2.20 или выше.planetmaker wrote:STR_WARNING_OLD_AV8_WITH_PARAM :You have activated reduced maintenance costs in an old version of av8. This will introduce a 2nd set of airports. For best user experience use av8 v2.20 or newer.
STR_PARAM_DISABLE_NOISE_DESC :Sets the noise generated by every airport to 0. This allows you to build an unlimited amount of airports if you play with the setting "Allow town controlled noise level for airports" on.
STR_PARAM_DISABLE_DATE_DESC :Allows all airports to be built regardless of current year.
STR_PARAM_MAINTENANCE_COSTS_DESC :Sets the level of the yearly maintenance costs for the airports
My mistake. I'll upload a new version later today.Supercheese wrote: Version: 2150
I'm finding them one by one by pure chance! 
Thanks for the translation. It will be available from tomorrows nightly build onward as well as the upcoming 0.4.2 releaseVoyager One wrote:You'd really need to tell me about all things needing translations!
OpenGFX+ Airports was started in 2010 under the name "Climate-dependent AirPort Tiles" by Yexo. So he chose with "CAP\0" an ID which fit the project, something very common for multi-person projects, thus totally in accordance to the guidelines with choosing a grfID when there's not a unique code developer. ChillCore explained already in his other postings in the other thread everything else what there is to say wrt grfIDs - there simply is no "reserved" grfID range. As there's no comprehensive list of existing NewGRFs, one can only try to check for existing grfIDs. And the best place I know is the list of grfs seen on servers in the last years which Rubidium compiles sometimes.Yousei wrote:Hi, I just found out in CanadianSet Thread why I can't use OGFX Airport with it.
It seems you used conflicting, inconsistent IDs.
Would be nice to see those two working together.
Can't be done by NewGRF (or any other method short of patching the game). NewGRFs can't define new airport statemachines, let alone create arbitrary ones during the game, so all GRF-provided airports have to behave like [a rotated version of] one of the existing airport types. They can be bigger (on two sides only IIRC) and use different graphics, but the actual way aircraft move on them can't be changed.skippern wrote:What I really miss with Airports is the ability to "free draw" airports.
That would be here: http://www.tt-forums.net/viewtopic.php?f=32&t=38709Eddi wrote:there was an "airport minigame" somewhere, that could be used to create a statemachine that could then be imported via a newgrf (but the statemachine specs are not implemented yet, also the specs were never actually finalized)
Indeed, given that users of OpenTTD have a choice to choose 8bpp or 32bpp, I see no issue in adding 32bpp sprites to the project.Eddy Arfik wrote:Being able to rotate airports is incredibly useful sometimes, but it looks funny with zBase, so I've created a 32bpp version using the zBase sprites, rendering new rotations for buildings where needed. My question is should I change the GRF ID before posting a link, or leave it unchanged to keep it compatable with existing savegames?
On the contrary, I imagine the new renders would be very useful if uploaded to the repository.Eddy Arfik wrote:Seeing as I didn't exactly follow the correct build process, I basically hacked something together using grfcodec, and a few new renders from the existing zBase .blend files, I don't think I have anything worth adding to the repository, so I'll just call it zBase+ Airports
link to grf
https://mega.co.nz/#!oBMxXagT!yiqIvJ45q ... ucitxOtO7Y
link to spritesheet + .nfo
https://mega.co.nz/#!kMF1TLQa!Jd85o3Z2V ... ii5fAdkr7Q
Users browsing this forum: No registered users and 76 guests
