@Cuzoe Yes, I was talking about the images, my bad. 
Well, just fyi - I have a facelift model, BCM replaced for one with pin C29, full working RGB ambient lights.
Ambient lights installed (RGB): Door strips (F+R), pocket lights (F), center console, cig.lighter, footwell (F+R), dashboard/glovebox, roof, door sills
Still looking for a nice solution for the cup holders. Ruined 3 center consoles already for testing purposes.
Gateway arrived Monday, hopefully going to replace it this weekend. DCC slider
So now you know why I appreciated your previous post about the gca files.
So, what do I want to accomplish? Well, I'll try my best to explain myself.
If you look at those accents on your screen, they are ambient dependent.
If you look at the extracted images, they are just white.
So somewhere, somehow, the images are 'marked/signed' as let's call it ambient overlay.
A couple of examples (don't mind my bad photos and dirty screen):
img_52 is an accent image. img_53 isn't.
img_52 and img 53:
The same for the tiles:
img_2300 (just white):
If you look at the Drive Mode selection screen, there is also an accent color/overlay, but orange.
img_2256, also just a white colored image):
The orange overlay is also present on some other images. As an example in the OPS screen to disable/enable sound.
Also just a white image.
So my thoughts were, there must be something in the hex-data (mcf file) that marks an image to be non-overlay/ambient overlay/orange overlay.
Why do I want to find the data in the first place? Well I hate the orange on the drive mode selection screen.
I want to change it to ambient dependent instead of the orange.
I hope that I explained it good/understandable enough.
Thank you man for your effort and patience.
dvw.r
Well, just fyi - I have a facelift model, BCM replaced for one with pin C29, full working RGB ambient lights.
Ambient lights installed (RGB): Door strips (F+R), pocket lights (F), center console, cig.lighter, footwell (F+R), dashboard/glovebox, roof, door sills
Still looking for a nice solution for the cup holders. Ruined 3 center consoles already for testing purposes.
Gateway arrived Monday, hopefully going to replace it this weekend. DCC slider
So now you know why I appreciated your previous post about the gca files.
So, what do I want to accomplish? Well, I'll try my best to explain myself.
If you look at those accents on your screen, they are ambient dependent.
If you look at the extracted images, they are just white.
So somewhere, somehow, the images are 'marked/signed' as let's call it ambient overlay.
A couple of examples (don't mind my bad photos and dirty screen):
img_52 is an accent image. img_53 isn't.
img_52 and img 53:
The same for the tiles:
img_2300 (just white):
If you look at the Drive Mode selection screen, there is also an accent color/overlay, but orange.
img_2256, also just a white colored image):
The orange overlay is also present on some other images. As an example in the OPS screen to disable/enable sound.
Also just a white image.
So my thoughts were, there must be something in the hex-data (mcf file) that marks an image to be non-overlay/ambient overlay/orange overlay.
Why do I want to find the data in the first place? Well I hate the orange on the drive mode selection screen.
I want to change it to ambient dependent instead of the orange.
I hope that I explained it good/understandable enough.
Thank you man for your effort and patience.
dvw.r