sky_line/Slipstream

Fork 1

Derender / blacklist: audit the existing derender list and wire Area Search Blacklist to it (FS asset blacklist not present) #426

New issue

Closed

opened 2026-10-05 11:23:52 +00:00 by sky_line · 1 comment

sky_line commented

2026-10-05 11:23:52 +00:00

Owner

Area Search's Blacklist / derender action only hides the object for the current view; it's not a permanent derender.

Why

fsareasearch.cpp (~line 58): "fsassetblacklist.h not present in Alchemy; the 'blacklist (derender)' action is neutered below." Firestorm's Area Search writes to FS's asset blacklist, which Alchemy doesn't have.

What we already have

Alchemy's derender list:

llderenderlist.cpp/.h;
the Derender tab in the Blocked window (floater_blocked.xml → panel_block_derender.xml, class panel_derender_list);
the right-click "Derender" actions.

It may be fully working, or only partly wired up.

Do

Audit the existing derender system: does right-click Derender work (temporary and permanent)? Does the Derender tab list entries, allow removal, and persist across sessions? Does a derendered object stay gone after it re-enters interest / the object cache? This interacts with the VRAM ladder's far-geometry kills and the cache hold (#405 work). Does it work for attachments and avatars (cf. #202)?
Wire Area Search's Blacklist action to the derender list instead of the neutered FS blacklist call: permanent (saved) by default, plus an option for "this session only", matching FS's Area Search UX.
Compare with Firestorm's Asset Blacklist window (blacklist by asset type: objects, textures, sounds, animations, avatars). If FS's version covers more (sound / animation / texture blacklisting), decide whether to extend LLDerenderList or port FS's blacklist window. Don't keep two parallel systems.
Make sure derendered objects interact correctly with the VK pipeline: instance slots, textures and the GPU scene released, nothing left drawing.

Done when

Area Search Blacklist permanently derenders via the derender list.
The Derender tab manages entries (list / remove / persist), and derenders survive relog and re-entry.
A decision recorded on extending to FS-style asset-type blacklisting.

Area Search's **Blacklist / derender** action only hides the object for the current view; it's not a permanent derender. ## Why `fsareasearch.cpp` (~line 58): *"fsassetblacklist.h not present in Alchemy; the 'blacklist (derender)' action is neutered below."* Firestorm's Area Search writes to FS's **asset blacklist**, which Alchemy doesn't have. ## What we already have Alchemy's **derender list**: - `llderenderlist.cpp/.h`; - the **Derender** tab in the Blocked window (`floater_blocked.xml` → `panel_block_derender.xml`, class `panel_derender_list`); - the right-click "Derender" actions. It may be fully working, or only partly wired up. ## Do 1. **Audit the existing derender system:** does right-click Derender work (temporary and permanent)? Does the Derender tab list entries, allow removal, and persist across sessions? Does a derendered object stay gone after it re-enters interest / the object cache? This interacts with the VRAM ladder's far-geometry kills and the cache hold (#405 work). Does it work for attachments and avatars (cf. #202)? 2. **Wire Area Search's Blacklist action** to the derender list instead of the neutered FS blacklist call: permanent (saved) by default, plus an option for "this session only", matching FS's Area Search UX. 3. **Compare with Firestorm's Asset Blacklist window** (blacklist by asset type: objects, textures, sounds, animations, avatars). If FS's version covers more (sound / animation / texture blacklisting), decide whether to extend LLDerenderList or port FS's blacklist window. Don't keep two parallel systems. 4. Make sure derendered objects interact correctly with the VK pipeline: instance slots, textures and the GPU scene released, nothing left drawing. ## Done when - [ ] Area Search Blacklist permanently derenders via the derender list. - [ ] The Derender tab manages entries (list / remove / persist), and derenders survive relog and re-entry. - [ ] A decision recorded on extending to FS-style asset-type blacklisting.

sky_line added the

feature

bug

labels

2026-10-05 11:23:52 +00:00

sky_line referenced this issue

2026-10-05 11:28:21 +00:00

Investigate: Slipstream LSL bridge (FS-style in-world helper), optional / attach-on-demand #428

sky_line added this to the Slipstream project

2026-10-06 15:04:13 +00:00

sky_line added the

status

up-next

label

2026-10-10 04:53:39 +00:00

sky_line referenced this issue from a commit

2026-10-10 22:19:26 +00:00

#426: Area Search Blacklist -> derender list; World menu entry for the list

sky_line commented

2026-10-11 13:12:54 +00:00

Author

Owner

Shipped in 1.3.0 Beta 2: the derender list was audited, Area Search Blacklist feeds it, and it's available under Communicate > Derender / Blacklist List. Owner-tested fine.

sky_line

2026-10-11 13:12:54 +00:00

closed this issue
removed the
status
up-next
label

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

sky_line/Slipstream#426

No description provided.

Rows
Columns