Feature Request Bug? Camera elevation and 3d buildings

[jarlrmai]

When you enable 3d buildings the camera elevation tries to follow the lidar/terrain map, but it is often annoying when you want to position the camera from a building as it will jump up and down on micro adjustments

If you disable AGL then the camera elevation is not adjustable for me

Firefox latest W11 etc

 

[Mick West]

Please post a sitch where this is a problem (both the jumping and the "not adjustable" camera.

 

[Mick West]

If you increase the elevation and the object does not move, that might be because the elevation (relative to sea level) is underground. If the position is underground, then the object is displayed snapped to the surface, so try a bigger number. This will especially be an issue at higher elevations. e.g. in Denver.

 

[jarlrmai]

https://www.metabunk.org/sitrec/?custom=11433/airbornepyrotechnics.co.uk reddit bristol/20260719_122454.js

disabling AGL and raising it up more does make it come up, but then its still affected by the 3d buildings

 

[Mick West]

disabling AGL and raising it up more does make it come up, but then its still affected by the 3d buildings

Unfortunately, there is a "ground level" when you have 3D buildings enabled. The normal elevation data is too low resolition, so the "ground", (e.g. the street) is hard to determine. What's a building? What's a tree? What's a hill? I try to determine this agoritmigly, but it's messy.

I could add another checkbox so that AGL "Altitide" is above the elevation map, but things they get confusing with how alitude is specified for anaysis.

No easy answer here. I think what I lean towards is changing the AGL toggle so it does not change the camera position, just the Altitude number.