as i continue to play with ArcRotateCamera i think i found another bug. Could you guys please confirm or deny this is the case?
There is an option to define a custom
upVector on ArcRotateCamera to override the default Y axis (we use Z in our app) and there is also an option to define
mapPanning flag which eliminates the transform on Y axis - this seems hardcoded here: https://github.com/BabylonJS/Babylon.js/blob/master/packages/dev/core/src/Cameras/arcRotateCamera.ts#L946
→ however the two flags are not in sync with each other - shouldnt the
mapPanning flag eliminate transform on the axis that we defined using the
upVector instead of the hardcoded Y? At least thats what i would intuitively expect if i configure them both.
Thank you and have a nice day.