Impact decals (bullet/blast) don't show on detail brushes

[GooberRF]

Bullet and blast decals don't show on detail brushes (or brushes that don't touch the "main" level geometry). They only show on normal brushes and moving brushes. On the PS2 version, I believe they showed on detail brushes and normal brushes, but not movers.

Decals placed in RED seem to have no issue displaying on detail brushes, though.

This is an RF bug, not specific to Dash.

[rafalh]

I don't think it should be fixed, especially not for old maps. I used to shoot brushes and find ones that don't show decals to determine which are different from others.

[GooberRF]

That's a good point, especially for some run maps. Maybe it could be a clientside option in that case? That way if a client wanted to use it to tell the difference between brushes they could still have an option to do that. I say that because I think the fact that it doesn't show bullet decals on detail brushes is an RF bug, and it's something that should ideally work properly. I think it would be best for the default behaviour to show bullet decals on all geometry, but a clientside option to restore the legacy behaviour (ie. no bullet decals on detail brushes) would be fine for run maps and such. While it's still a relatively small issue, this bug will become more visible as time goes on and more mappers use single-sided faces to efficiently construct organic shapes (which has to be detail to avoid geometry holes). This is visible in RoMeK's Doomsday and BATEMAN's Shadowgrounds maps from RFU5 as examples - the majority of the terrain in Doomsday, and all of the terrain and canyon walls in Shadowgrounds can't have bullet/blast decals because they're set to detail, which doesn't look very good.

…

On Fri, Dec 18, 2020, 6:31 PM Rafał Harabień ***@***.***> wrote: I don't think it should be fixed, especially not for old maps. I used to shoot brushes and find ones that don't show decals to determine which are different from others. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#40 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AEHEWKV27IWDCTQSKS4EMZTSVPGLPANCNFSM4VBVKZRA> .