editor capture_scene_preview with asset_type: "widget" is an excellent way to review UMG without entering PIE — ~20-50 ms per capture. But the output is always 512×512, and passing width / height returns Unknown param warnings while still capturing at 512².
For a widget authored against a 1200×760 design frame, a square capture cannot show real layout. Aspect-dependent problems — crowding, overflow, alignment against a ScaleBox — either appear when they do not exist or hide when they do. Two rounds of layout conclusions had to be discarded and re-checked in PIE for exactly this reason: the square render showed rows colliding with a bottom button that were not colliding at all at the real aspect.
Ask
Honour width / height (or a single resolution), defaulting to today's 512² so nothing changes for existing callers.
Related
#135 is adding UI-composited PIE capture, which is adjacent — this is the cheaper no-PIE path for the same review loop.
editor capture_scene_previewwithasset_type: "widget"is an excellent way to review UMG without entering PIE — ~20-50 ms per capture. But the output is always 512×512, and passingwidth/heightreturnsUnknown paramwarnings while still capturing at 512².For a widget authored against a 1200×760 design frame, a square capture cannot show real layout. Aspect-dependent problems — crowding, overflow, alignment against a
ScaleBox— either appear when they do not exist or hide when they do. Two rounds of layout conclusions had to be discarded and re-checked in PIE for exactly this reason: the square render showed rows colliding with a bottom button that were not colliding at all at the real aspect.Ask
Honour
width/height(or a singleresolution), defaulting to today's 512² so nothing changes for existing callers.Related
#135 is adding UI-composited PIE capture, which is adjacent — this is the cheaper no-PIE path for the same review loop.