Moderator: OpenTTD Developers
Karn,i had already done that,it works fine on my new games,but for saved games or saved scenery it crashes.Karn wrote:You have to do one more thing: In title screen click on NewGRF Settings, then click on Huge airports OpenGFX, then click on Add. Now it should work.
You can use OpenGFX+ Airports ONLY with OpenTTD 1.2.0-RC1 or newer. But these "huge airports" require both, a changed OpenTTD and a different NewGRF.lekkimsm2500 wrote:So you're saying i can't apply both to 1.2.0 and OpenGFX + airports
Why not build it straith in, fine tune the grafics a bit and build it in the new OpenTTD.planetmaker wrote:You can use OpenGFX+ Airports ONLY with OpenTTD 1.2.0-RC1 or newer. But these "huge airports" require both, a changed OpenTTD and a different NewGRF.lekkimsm2500 wrote:So you're saying i can't apply both to 1.2.0 and OpenGFX + airports
This way it gets something new and not just only a more bugs free version.
Their are many people out there who likes to play openttd but understand s*** about patching things and wait that it get build in strait away ore a patch comes out thats easy to install without all the coding parts.
I do not speak about exe patches, but like a zip where there are maps with the patch aplyt and justhave to unzip and replace. Simple and easy.
I play a lot of games with mods, and the patches are WAY easy to aply there.
One reason is that you would need to provide binaries for over many platforms, ranging from Apples, to Windows, to Unix, for several different version of the OSes, for 32bit and 64bit.Why not build it straith in, fine tune the grafics a bit and build it in the new OpenTTD.
A patch author does not have all those machines available, prepared for compiling OpenTTD.
A second reason is that the above binaries are WAY bigger than a source code patch file. This increases the bandwidth very much, which is not freely available.
Note that due to the GPL license, you always have to publish the patch file anyway.
A third reason is that providing binaries slows down development. People have to spend time and effort in making all these executables, time they otherwise can spend improving the patch.
A fourth reason is that this is the "Development" forum. Here, proofs of concept are published rather than slick end-products. In a company such code never leaves the house.
Here, it gets published so others can experiment with the changes, and improve them / give feedback.
If you want to join in bleeding edge development, you are welcome. If you don't know about compiling or about C++, this is probably not a forum for you.
Chillcore is maintaining a patchpack with popular patches, and providing binaries (using our compile farm). That seems like the best alternative.
Bad news is that after changing, you need to apply the patch to a fresh copy of OpenTTD source code, and compile the combination.
Also, you become incompatible with everybody else, including all other users of this patch.
Users browsing this forum: Bing [Bot] and 4 guests