Michael Bechtold

Understood, Robert. I did give you the objective, the reason and the high level solution approach. But I delegated all related development to Claude, hence I had to ask Claude to address your questions. The difference is that you are deep into MOBAC since ages, and I am just an elaborated user with findings (e.g. the mixed multi layer tiles) and needs beyond status quo. Hence my only option to employ something like Claude. The approach it took, with me testing, and in many cases IN-validating its...

@Robert: explanation makes sense?

Hat mir doch keine Ruhe gelassen: Let me verify these technical points against the actual source rather than trust memory alone — Robert's questions are sharp and specific, so the answers need to be precise. Confirmed — Robert is completely right on point 1. transparent exists in the pristine baseline (predates any of our patches), with a working getter and already wired into RendererJob. Our transparentLayer field in CustomMapsforge.java is genuinely redundant — worse, it maps to the same XML tag...

Hello Robert, the purpose of the boring color mechanics is this: when there are tiles to which two adjacent layers with mapsforge maps contribute you have to merge two internal tiles into one final result (the new debug tile ID feature gives a nice illustration of what can happen). You need a tiebreak what to use and what to ignore. The critical cases are when e.g. one layer provides the north, the other the south of a tile. The boring color should be the background color of your theme. Then valid...

Hi Robert, coming back to your ask, here are my comments (assuming that you kept the zip file with the java patches as well as the .md): 1) original MOBAC 2.3.x and betas fail at the border areas between two or more layers with mapsforge maps: one of the pair "wins" and can leave part of bordering tile blank. The fix patch merges the "overlapping" tiles taking all relevant data from both. This also includes a "debug" feature by which you can specify x/y/z and a target directory to dump each layer...

HI Robert, just took your latest and joined my additions from July - well, Claude did ;-). It includes an .md file for what, why and how. Cheers Michael

Cool!! TXs

Look at the coordinate numbers on the axis. They are jumping up and down. Such must not be.