Rerun

Migrating from 0.20 to 0.21

Near clip plane for Spatial2D views now defaults to 0.1 in 3D scene units. near-clip-plane-for-spatial2d-views-now-defaults-to-01-in-3d-scene-units

Previously, the clip plane was set an arbitrary value that worked reasonably for cameras with large focal lengths, but become problematic for cameras with smaller focal length values. This value is now normalized based on the focal length of the camera.

If the default value of 0.1 is still too large for your use-case it can be configured using the new near_clip_plane of the VisualBounds2D blueprint property, either through the UI, or through the SDK in Python:

rr.send_blueprint(
    rrb.Spatial2DView(
        origin="world/cam",
        contents="/**",
        visual_bounds=rrb.VisualBounds2D(
            near_clip_plane=0.01,
        ),
    )
)

Types and fields got renamed from .*space_view.*/.*SpaceView.* to .*view.*/.*View.* types-and-fields-got-renamed-from-spaceviewspaceview-to-viewview

Various types and fields got changed to refer to "views" rather than "space views". This exclusively affects the Python blueprint sdk:

Field/argument changes:

  • ViewportBlueprint(...auto_views=...) -> ViewportBlueprint(...auto_views=...)
  • Blueprint(...auto_views=...) -> Blueprint(...auto_views=...)

Type changes

Utilities
  • SpaceView -> View
Archetypes
  • SpaceViewBlueprint -> ViewBlueprint
  • SpaceViewContents -> ViewContents
Components
  • AutoSpaceViews -> AutoViews
  • SpaceViewClass -> ViewClass
  • SpaceViewOrigin -> ViewOrigin
  • SpaceViewMaximized -> ViewMaximized

3D transform arrow visualization show up less often by default 3d-transform-arrow-visualization-show-up-less-often-by-default

Previously, the viewer would show 3 arrows for every logged transform if any of the following was true:

  • enabled visualizer via VisualizerOverrides or ui
  • AxisLength component is present as well
  • there's a pinhole camera at the same path
  • no other visualizer would be active by default on the path

For many usecases this led to too many arrows being shown by default. We therefore removed the last condition - arrows will no longer show by default if they're the only visualizer. The easiest way to opt-in to transform arrows is to set AxisLength (axis_length field on the Transform3D archetype) on your transforms.

Privacy policy