Andreas Reich
Andreas Reich
This happens consistently in presence of a map view. The map view is needed because that's what adds the custom texture
We landed that fix by now. Confirmed the crash no longer repros
so.. what exactly regressed? Something about dynamic bounds?
@jprochazk please use more helpful titles and tagging in the future. Even with the screenshot "something regressed" is not something that will ever show up in a search
That is for all views. But I noticed now that this doesn't repro so far anywhere except the following rrd + rbl: https://drive.google.com/file/d/13LqtoFHFbwrqESvszptPXXLeOyUP7UQy/view?usp=sharing
yes, we should likely do some adjustments there on a per example basis. For some examples we may also want to turn it off
No change that I'm aware of, no But yeah we don't do software rendering on dev machines right now since the setup is a bit tedious/invasive and depends on platform...
> Opened an issue for that and linked it in a comment: > > * [Support `Opacity` for `VideoFrameReference` #9832](https://github.com/rerun-io/rerun/issues/9832) thanks!
This would imply dragging in a lot of stuff to rerun_c, meaning we should make this opt-in. But having two rerun_c artifacts seems a bit cumbersome. Not a 'quick issue'...
(via discussion with @jleibs:) Alternatively to embedding the wasm blobs in the SDK (both in C++ and Python!) we could instead let the rerun cli do the work. We'd start...