Oli Scherer

I have created a workaround: https://github.com/DerKarlos/OSMeta/commit/0d59b7e565709b35deff2d9e90f98442ddc38662?diff=unified&w=1 this works fine, as only web/wasm will follow your rules. native doesn't understand them anyway and just loads the file 😆

We could load the raw osm files for this information. Though I don't know yet how to map the osm2world tile coordinates to lat/lon in order to know which osm...

The issue with putting this information into the glb files is that we then have to "reverse engineer" the information to be able to figure out road lane directions and...

The function that computes the score for each tile (to decide which one to load next) is https://github.com/DerKarlos/OSMeta/blob/dfd870703d7d9ddc9e1c9adc0bb958ab49d1daf8/src/tilemap.rs#L50 to add information like player look direction, we need to pass it...

We're using fog already, but it's very subtle. We need to tune it up when the sky is smaller

how do I compute the tile x,y coordinates from lat/lon? The web-app already supports `?x,y` for tile coordinates, but we should switch to a `key=value` system

> May be dynamically according to the Sky size. that's already happening. we can tune the parameters though. There are also other fog systems we can try out

That worked great! I removed everything that I didn't need again afterwards, but since it's an explicit removal commit, we can revert it whenever we need something from it.

This is deep in the engine, only processing values we gave the engine, not in our code. So there's not much we can debug, except add more debugging messages or...

I've had a situation before where I saw an issue in our code in the backtrace. Any panic will cause this. Panicking is safe, too, so this can happen on...