I don't know what software is responsible for the behavior, but I guess it's hijack, but maybe 3.0a10/11 broke something. Anyway, here's my problem:

I gave 3.0a11 a good test as I drove a 3 hours ride. About at mid-distance, just after sunset, I noticed the buttons were not illuminated. I entered the hijack menu and the button brightness was set to 1, as I want it. I turned headlights off, and the button illumination came back on. Went to the menu and value was 1.

I don't precisly remember how things used to work when I had 2.01. What I think I remember is that illumination level was set like the dimmer: a value for headlights on and another value when headlights are off.

What I see now is that the same illumination level is "shown" in the menu whatever i set the headlights to. And I get no button illumination with headlights on, whatever value is entered.

hijack 437, v3.0a11

Didn't Mark add a new button illumination option? That might have affected it.

OK, I had missed that thread I guess. So:

[hijack]
buttonled_dim=1

is working correctly, If I set level 6, leds go down to level 1 when headlights are on. It seems the default behaviour is not though. my usual setting is 1, so (1+1)/2 should still give 1 of illumination if I don't use that preset. In fact, whatever value I enter in the hijack menu gives me no illumination when headlights are turned on... I guess I'll use the config.ini setting for now.

Thanks for pointing out!

Oh shoot. Yeah, there's a bug there.

I'll fix it (already done here) and find a way to upload v439 sometime (on holiday right now).

Don't hurry: Enjoy your holidays instead!

Thanks!