MrNeRF/LichtFeld-Studio

What's wrong Video export can composite four different combinations — meshes alone, splats alone, splats and meshes depth-tested against each other, and split-view — across perspective and orthographic projections. Only the mesh-only perspective combination has been exercised end to end. The splat+mesh combination is the one to worry about: it is the only path where mesh depth is compared against splat depth, and a sign or scale error there would put meshes in front of geometry that should occlude them. It currently has no coverage of any kind. How to fix A headless test that exports a handful of frames from a small fixture scene for each combination and asserts a few known pixels, plus a unit test for the depth comparison itself. linearizeMeshViewDepth is already unit-tested for both projection types and is a good model.

What's wrong Plugins can attach UI to a spot in the interface (a "hook"). The function that removes a hook takes an argument saying which hook to remove — and then ignores it completely. It removes whichever hook was added last. So if plugin A and plugin B both attach something to the same spot, and A unloads, B's UI disappears instead. The code already stores a unique id on every hook for exactly this purpose. Nothing ever reads it. Where src/python/ui_hooks.cpp:53-62: void remove_ui_hook(const std::string& panel, const std::string& section, UIHookCallback /*callback*/) { // <- argument ignored ... if (const auto it = reg.hooks.find(key); it != reg.hooks.end() && !it->second.empty()) { it->second.pop_back(); // <- removes the last one, whoever it is } } The unused id: src/python/ui_hooks.cpp:20 (the id field), assigned at :50 from next_id++. How to fix Make register_ui_hook return the size_t id. Make remove_ui_hoo

We ship 6 themes and a good token system (@{primary}, @{text}, @{alpha(border,0.4)}, @{layered_shadow.4}). But the stylesheets also contain 608 hardcoded colors, and 270 of them are never overridden by any theme rule. Those parts of the UI look exactly the same in Dark, Light, Gruvbox, Nord and both Catppuccin themes. Most of the literals are Catppuccin Mocha values copied into shared files: components.rcss:168 background-color: #89b4fa; /* mocha blue */ components.rcss:194 color: #cdd6f4; /* mocha text */ scene_tree.rcss:1 body { color: #cdd6f4 } python_console_panel.rcss is hardcoded to a different dark palette again (rgb(30, 30, 30), rgb(229, 229, 229)). Where it is worst file not themed / hardcoded has a .theme.rcss? asset_manager.rcss 90 / 156 yes video_extractor.rcss 48 / 48 no python_console_panel.rcss 36 / 79 yes sequencer.rcss 23 / 33 yes histogram_panel.rcss 17 / 54 yes url_import_panel.rcss 15 / 15 no components.rcss 12 / 132 yes