Found while fixing #58, which had the same shape.
sh_show_rmcount is registered with the engine (src/backend/cvars.c) and documented in docs/capabilities.md and the site guide, but nothing in the backend ever reads it back. Grep for its read index B2_CVAR_SH_SHOW_RMCOUNT returns exactly one hit: its own #define. So setting it does nothing.
This is not the same fix as #58. There the switch just needed wiring to a path that already existed. Here the thing it is supposed to switch on -- an on-screen render-node count -- has no renderer hook to hang off, so this is a feature to build rather than a wire to connect.
Filing it so it is tracked rather than rediscovered by a user. Until it is either implemented or removed, the cvar and its documentation promise something the build does not do.
Worth deciding which: implement it, or drop the cvar and its two doc entries.
Found while fixing #58, which had the same shape.
sh_show_rmcountis registered with the engine (src/backend/cvars.c) and documented indocs/capabilities.mdand the site guide, but nothing in the backend ever reads it back. Grep for its read indexB2_CVAR_SH_SHOW_RMCOUNTreturns exactly one hit: its own#define. So setting it does nothing.This is not the same fix as #58. There the switch just needed wiring to a path that already existed. Here the thing it is supposed to switch on -- an on-screen render-node count -- has no renderer hook to hang off, so this is a feature to build rather than a wire to connect.
Filing it so it is tracked rather than rediscovered by a user. Until it is either implemented or removed, the cvar and its documentation promise something the build does not do.
Worth deciding which: implement it, or drop the cvar and its two doc entries.