Page 1 of 1

ccol2w

Posted: 07 Mar 2006 10:23
by bobingabout
i upgraded to a newer nightly last night to find that a renamed version of TTDPatches ccol2w.grf was included, i though "Oh, Great, finally the colours will look better on the UKRS" to find that, it simply maps the second CC to be the same as the first... i was kinda expecting the menu to be very simular to TTDP where you can select seperate second colours for different situations. like having a unique scheme on DMUs.

my question is, what are the future plans for this ccol2w?

Posted: 07 Mar 2006 11:41
by peter1138
Bobingabout, I do things in stages. Perhaps this will happen...

Image

By the way, the GRF file contains the same colour maps as TTDPatch's file, but the the NewGRF actions are removed -- this is why it was renamed.

Posted: 07 Mar 2006 12:58
by bobingabout
that looks cool

yer, i figured it would be improved, eventually. atleast we don't have all that nasty green in everyones trains anymore, i was just enquiring as to what was planned, since i havn't seen it anywhere on these forums.

any plans for a 3rd CC? like what would happen in 32bpp?

Posted: 07 Mar 2006 13:37
by peter1138
No. The colour maps are "brute forced", so there is effectively a 16 by 16 array holding the colour maps for each combination. This array thus requires 256 colour maps. Three company colours using this scheme would require a cube of 16 * 16 * 16, or 4096 colour maps.

Now, if you wanted to allow more than 16 colours... let's not go there :-)

Posted: 07 Mar 2006 14:46
by bobingabout
well, i hope its something for the future, even if its long after this 2cc patch, and 32bpp only.
also, are there any other newgrf things being developed/planned?

Posted: 07 Mar 2006 17:01
by DaleStan
bobingabout wrote:also, are there any other newgrf things being developed/planned?
You mean besides "everything that TTDPatch supports but OpenTTD does not"?

Peter1138 is doing good work, but OpenTTD still lags behind TTDPatch in newgrf support.

Peter has said that there are a few newgrf bits he does not intend to implement, but I get the impression that those are things like action 4s that modify the strings now found in the *.lng files, not things like newcargos or UTF-8 support.

Posted: 07 Mar 2006 17:11
by PikkaBird
bobingabout wrote: any plans for a 3rd CC? like what would happen in 32bpp?
It's hard enough finding space on a sprite for two company colours, never mind three. :P

Posted: 07 Mar 2006 18:39
by belugas
DaleStan wrote:Peter has said that there are a few newgrf bits he does not intend to implement, but I get the impression that those are things like action 4s that modify the strings now found in the *.lng files
I already wrote an action 4 implementation. It does not handle the new scheme of langID yet, but will be in a certain distance future :)
It was not that hard to do, anyway...

Posted: 07 Mar 2006 19:47
by DaleStan
What happens, using your implementation, if I attempt to change IDs 0050 ("\7C tonne of coal") and 0070 ("\7C tonnes of coal")?

If you manage to produce a coherent result from that, I'd be very impressed. Especially since Open uses the same string for both of those.

Posted: 08 Mar 2006 00:57
by belugas
DaleStan wrote:What happens, using your implementation, if I attempt to change IDs 0050 ("\7C tonne of coal") and 0070 ("\7C tonnes of coal")?

If you manage to produce a coherent result from that, I'd be very impressed. Especially since Open uses the same string for both of those.
Hem... Is this a sarcasm or a warning ?
Either way, as you raised it youself, both systems are using different schemes. So I would be really surprised myself if they'll present the same results...
But the goal is not to blindly duplicate functionnalities, here. Rather to use what is available for OTTD's advantage without having to reinvent the wheel.
I'm sure you do understand that. Right?

Posted: 08 Mar 2006 01:36
by DaleStan
Neither, I think. I misspoke, and then you read what I said, not what I meant.
I meant "modify the generic strings now found in the *.lng files."

Action 4 must be able to set at least the xx, Cxxx and Dxxx IDs. The Cxxx and Dxxx are not in the .lng files, but the xx IDs are (AIUI).

Many of the other OpenTTD strings can no longer be changed with an action 4, because they require both UTF-8 support[0] and a "construct plural" control character.

[0] Or some other way of getting Open to draw the Unicode glyphs attached to 7B..A0, AA, AC, AD, AF, and B4..B8, rather than using their Latin-TTD functions: control characters and special TTD-specific characters.

Posted: 09 Mar 2006 10:29
by bobingabout
i just want to be able to play UKRS in its true nature, including this:
http://www.pikkarail.com/ttdp/ukrs/industries.htm

also, I've noticed a bug, and a slight problem with some newGRF stuff, dunno if the devs know, so, i'll mention it here.

variable wagon length.
when you are dealing with engines or waggons, when the train turns around, it does it as if the last wagon/train is full sized. so if its only 5/8, then 3/8 of a length is sticking out of the station before it even starts moving...

wagon re-fitting. after playing UKRS in TTDP, i've noticed that re-fits have different prices, and some are even free. in OTTD they are all the same cost. some re-fits cost more than the waggons themselves, which can be annoying, since you need to make a coal train in the first place before you can turn it into an iron ore train, and this initial train, the wagons cost twice as much as they do when you clone it.

also since i'm reporting bugs, although this 1 has nothing to do with newGRF(well, maybe a little to do with the variable waggon ones).

vehicle and wagon replacements. I've noticed that there is an option to sell parts of a train when the replacement would be larger than the original, but there isn't anything that says it should be mage bigger when replace it with something smaller.

if you replace a single engine with a 2 headded, the last wagon is sold, but replace the other way, and the train shrinks. simularly, with the vcariable wagon length, replace small wagons with large wagons and the train only replaces it to be the maximum of the length it was before, in UKRS with 8 small wagons, it only builds back 5 larger ones. however, do it the other way, and you only have 5 small waggons. i think what it should do in this case is consider the length the train is now (eg, require a 3 tile station, which is length 6) and replace the wagons/engines to be the same length.

so when i replace my 7/8 engine with a 8/8 engine, and 8 5/8 wagons with 8/8 waggons, it normally removes a carrage, making the new train only have 4 wagons when it should have 5, all because the engine is 1/8 of a unit short, it shouldn't.

who should i talk to about this autoreplace?

Posted: 09 Mar 2006 11:00
by peter1138

Posted: 09 Mar 2006 12:02
by bobingabout
reported :P unfortunatly, i accidently put wagon refit as a core task, instead of newGRF... all priority low.