Descriptive Problem Summary:
I've chained some plane_masters into a vis_stack via render target/source relays.
I'm having some definite issues with the renderer, and I went to use RenderIcon to inspect what was going on, and found that it's spitting out blank icons for this particular object. Seems like a bug, or there's something poorly documented going on here.
ID:2924221
 May 9 2024, 11:39 am
|
|||||||||||||
Not a bug
| |||||||||||||
Lummox JR resolved issue (Not a bug)
| |
Marked not a bug, but I want to explore ideas for providing something along the lines of what you were looking for.
| |
The icon you're passing to RenderIcon() is a HUD object with a couple of relays using render_source to show plane masters. However, RenderIcon() only operates on a single object which may or may not be on the map; it does not take the map into consideration at all. Because it's working only with the HUD object and its children, it doesn't see the plane masters that are being relayed. There's no corresponding render_target for the relays to use, so they're blank.
I don't see this as a trivial thing to change. It would kind of require RenderIcon() to handle an entire list of objects at once, and also take into account how they're positioned, etc. At that point it seems like it'd be easier to render the entire screen.