Planeset patch (now supports Planeset 1.5)

[mart3p]

Here is an update on the status of the Planeset patch now that all of the original Planeset 1.2 patch is in the trunk.

In the trunk for Planeset 1.5.
1. Support for vehicle type info. (NewGRF action 2 variable 0x48)
2. Support for reading GRF parameters for unbuilt vehicles. (NewGRF action 2 variable 0x7F )

In my Planeset 1.5 patch (against r5350 - see first post).
3. Support for "Include" strings in NewGRF texts (using formatting code 0x81).
4. New: Now that richk67's new airports are in the trunk I have added a fix that allows the Bell Osprey to be build in Helidepots and Helistations.

Fixed with my Livery Selection\Cargo Subtypes patch.
5. Selection of alternative company liveries for aircraft. Cargo subtypes are also used by Planeset to display different cargo slings for the Chinook helicopter when carrying goods.

Outstanding unsupported features.
6. Sound effects - the airships sound like helicopters. (NewGRF callback 33).

Sound effects I have already sorted. It just needs to be committed

We'll just have to wait.

7. New cargoes - incorrect liveries for some aircraft when carrying coal.
Belugas has started work on new cargoes in the SVN newgrf_lab branch. Again, we'll just have to wait.

8. UTF-8 texts- Planeset 1.5 can display the company livery names of Russian planes in Russian using Cyrillic text. I have got this working (see screenshot) using peter1138's utf8 branch. Another one to look forward to (especially for Grigory1 )

[Grigory1]

Thanks!

[White Rabbit]

It'll still be available in English though, right?

[mart3p]

It'll still be available in English though, right?

Yes it will be, you can set it to English with a GRF parameter.

[mart3p]

Here's a new win 32 exe - now with richk67's new airports! Thanks for all your work on these richk67 and congrats on getting them into the trunk.

Only trouble is, I'm having problems with the local authority, when trying to upgrade my busiest airport to an intercontinental.

[DaleStan]

It'll still be available in English though, right?

Yes it will be, you can set it to English with a GRF parameter.

Or you can just not install the Cyrillic glyphs grf.

[mart3p]

The only part of the Planeset 1.5 patch not in the trunk is the code for handling NewGRF "include" strings. As this is only used for livery selection texts, I have moved this code to the NewGRF Livery Selection/Cargo Subtypes patch. This is now the only patch required to support Planeset 1.5 in OTTD. Note that all this code is already in the MiniIN.

Make sure you are using the latest version of Planesetw.grf (1.5.2) available here.

Screenshot shows various aircraft from Planeset 1.5 at the intercontinental airport.

[White Rabbit]

Did you know that krtaylor is in need of some Planeset screenshots?

[mart3p]

Did you know that krtaylor is in need of some Planeset screenshots?

Yes, I’d seen that but you seem to be doing quite well supplying screenshots yourself . krtaylor is more than welcome to use any of my screenshots from this thread. I will point him this way from the Planeset thread.

[Grigory1]

Problem:
In OpenTTD I wish to share with PlaneSet separate GRF files with planes, with some planes there is no replacement in the list of purchases.
In TTDP all works normally.

[DaleStan]

It's just a wild guess, but I think you might have to provide the GRF file(s) in question.

Possibly your openttd.cfg too.

(Sorry. I'm a bit sour about getting an "It's broken. Fix it." bug report, followed immediately by a question that's answered in the readme.)

[mart3p]

Grigory: Do as DaleStan says - provide the GRFs and your openttd.cfg - and I will look into it.

Latest news on Planeset 1.5 support:
peter1138 added support for NewGRF sound effects to the trunk at r6532.

In the last week peter1138 has added cargo subtypes to the trunk, including support for GRF include strings. The code is based on my patch but includes many improvements by peter1138. This means that the Planeset 1.5 alternative liveries are now available using the nightly build. Thanks peter1138.

[Grigory1]

@DaleStan
@mart3p
GRF+openttd.cfg

[mart3p]

Grigory: Yes I see the problem. It is caused because Planeset 1.5 uses special sprites for the purchase list. These are set using an action 3 with the cargo-type set to 0xFF.

Your 747-8 does not use a special sprite for the purchase list and the one previously loaded by Planeset is not being overwritten by your GRF. The purchase list therefore uses the sprite loaded by Planeset - in this case the Boeing Sonic Cruiser.

This is a bug in OTTD. All data for a vehicle ID needs to be cleared if that vehicle ID is overwritten by another GRF file. This is not currently happening. I will try to find a fix for this.

Another unrelated problem; your 747-8 has incorrect spite offsets in some views, see screenshot.

[Grigory1]

Grigory: Yes I see the problem. It is caused because Planeset 1.5 uses special sprites for the purchase list. These are set using an action 3 with the cargo-type set to 0xFF.

Your 747-8 does not use a special sprite for the purchase list and the one previously loaded by Planeset is not being overwritten by your GRF. The purchase list therefore uses the sprite loaded by Planeset - in this case the Boeing Sonic Cruiser.

This is a bug in OTTD. All data for a vehicle ID needs to be cleared if that vehicle ID is overwritten by another GRF file. This is not currently happening. I will try to find a fix for this.

Thanks mart3p!
I shall hope and wait...
And one more question at planes in PlaneSet different spaciousness for example A380 in TTDP - 150t (real), in OpenTTD - 178t???

Another unrelated problem; your 747-8 has incorrect spite offsets in some views, see screenshot.

I know, it is the test version. I do new version Boeing 747-8 compatible with Planeset for TTDP and OpenTTD (new figure in more real scale + some new liveries and a new code)
And as I not the programmer wish to ask for what these lines in a code are necessary and whether they are necessary for the single plane
1329 * 19 02 03 00 81 7F 00 02 03 02 00 00 00 00 11 00 01 01 10 00
1330 * 16 02 03 01 85 1A 20 80 02 08 47 08 FF 00 00 00 00
And still as it is possible to install correct loading of tourists at me it has turned out 1200 (as valuables) it is necessary - 178

[Wilson]

I have a little bug with Planeset. I use the latest version 1.5.2 of planeset and r6689 of ottd. The problem is when I buy the same type of airplanes several times some have other refit options(liveries). I attached a screenshot.

[DaleStan]

Grigory, Wilson:
If you're trying to ask questions about the Planeset, ask in the Planeset thread, not here.

Alternatively, read the NFO spec for variable 7F and the Planeset readme.

[mart3p]

And one more question at planes in PlaneSet different spaciousness for example A380 in TTDP - 150t (real), in OpenTTD - 178t???

This incorrect capacity of 178t only occurs for coal. Other cargo types are correct at 150t. This is because OTTD doesn't yet support NewCargoes. Planeset remaps cargo ID 1 (coal) to tourists using a cargo translation table. It then sets the capacity for tourists to 178. OTTD has no support for cargo translation tables so cargo ID 1 remains as coal, so the capacity of 178 is applied to coal instead of tourists.

And still as it is possible to install correct loading of tourists at me it has turned out 1200 (as valuables) it is necessary - 178

How are you able to refit to tourists? This can't work without NewCargoes so I don't understand this, or are you talking about TTDPatch?

[Grigory1]

DaleStan
Sorry, I have not simply found the description for variable 7F and 85

mart3p
Has understood, I simply wished to make a file that it worked equally in TTDP and OpenTTD
Thanks

[Kahee]

where can i get this airport?