Skip to content

Comments

Show rail scanner in first person spectator#260

Merged
GooberRF merged 2 commits intoGooberRF:masterfrom
nickalreadyinuse:spectate-rail
Feb 24, 2026
Merged

Show rail scanner in first person spectator#260
GooberRF merged 2 commits intoGooberRF:masterfrom
nickalreadyinuse:spectate-rail

Conversation

@nickalreadyinuse
Copy link

@nickalreadyinuse nickalreadyinuse commented Feb 23, 2026

Copy link

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Implements rail gun scanner rendering/overlay support in first-person spectate by synchronizing scanner state over the network and redirecting scanner texture rendering + HUD behavior to the spectated player.

Changes:

  • Add rf::weapon_has_scanner(...) helper for identifying scanner-capable weapons.
  • Hook railgun scanner rendering paths to render the correct viewpoint/bitmap during spectate, and adjust HUD/scoping overlay behavior.
  • Sync scanner state via entity state flags so spectators can see the scanner state remotely.

Reviewed changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated 3 comments.

File Description
game_patch/rf/weapon.h Exposes weapon_has_scanner for scanner weapon detection.
game_patch/misc/player_fpgun.cpp Redirects rail scanner rendering for spectate and changes render target behavior for the scanner bitmap.
game_patch/hud/multi_spectate.cpp Adds scanner state replication + early frame sync and HUD/scope overlay handling while scanning in spectate.
docs/CHANGELOG.md Notes the new “Sync rail scanner in first person spectate” change.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@GooberRF GooberRF merged commit ac8a644 into GooberRF:master Feb 24, 2026
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants