Feature Request: Integrate Web-Based Radar from cs2_webradar
Overview
This feature request proposes integrating the browser-based radar functionality from clauadv/cs2_webradar into DragonBurn to allow remote radar viewing capabilities.
Motivation
The current radar feature in DragonBurn works well but is limited to the application window. Adding web-based radar functionality would allow:
- Remote viewing of radar on secondary devices (phones, tablets, second monitors)
- Sharing radar information with teammates through network configuration
- More detailed visualization options through the web interface
Technical Implementation
Components to Integrate
- WebSocket Server: Add the WebSocket server from cs2_webradar to stream radar data
- React Web Application: Incorporate the web-based radar visualization interface
- Data Bridge: Create a bridge to feed DragonBurn's kernel-mode data to the WebSocket server
Proposed Integration Approach
1. Memory Data Extraction
Since DragonBurn already has kernel-mode memory access, we should:
- Use DragonBurn's existing memory reading for player positions, map information
- Format the data similar to what cs2_webradar's usermode component sends
2. WebSocket Implementation
Add a WebSocket server component to DragonBurn that:
// Example implementation based on cs2_webradar's approach
void StartWebSocketServer() {
// Initialize WebSocket server on port 22006
// Listen on path "/cs2_webradar"
// Forward memory data from DragonBurn's memory reader
}
3. Web App Integration
- Include the React application from cs2_webradar in the DragonBurn distribution
- Adapt the connection settings to work with DragonBurn's WebSocket
- Add configuration options for local/remote usage
4. Network Configuration
Add user settings for:
- Enabling/disabling the web radar
- Port configuration
- LAN/WAN access controls
- Optional authentication for security
Benefits
- Enhanced team coordination with shared radar
- Flexible viewing options
- Leverages existing open-source code (cs2_webradar is GPL-3.0 licensed)
Notes
- The cs2_webradar repository already has most of the necessary code
- Since DragonBurn already has kernel-mode access, we don't need cs2_webradar's usermode memory reading
- This integration should maintain DragonBurn's existing security and detection avoidance features
References
- clauadv/cs2_webradar
- GPL-3.0 license requires us to maintain the same license for derived components
Thanks for using our software! We will look into and fix your issue asap.
I could honestly try to do that! 👍
@Juse2Good pls try to add it i tried too but i failed misserably
@Undertaker-afk part of learning is failing
@SamlonDev i know but i failed 10 times befor getting something that remotly resembles anything i had as a goal. The webradar turned dragonburn from a lightweight thing into a disk monster and a game and cheat crasher, it worked 2 out of 27 times and everytime the frametime spiked to 18ms and my fps got down to 5 and it still failed to send the data to the webradar instance in the browser
Mayb a little of network basics
@wqq-z thats not it i just miserably failed trying to add a usermode app into another and not effecting the functionality of any
hey, im currently working on this releasing it on a fork soon ilyk once i've made it into a clean code. @Undertaker-afk
@Juse2Good nice can you share it here when your done
yeah! making the "commit" after i got some free time. at 4pm utc 2+
@Juse2Good did you find a good way of integrating all the stuff and i would recommend you for @itzlaith fork tgat has vis check and map parsing and improved performance
this code is GPLv3, while the project is MIT. Including it would require the project to be relicensed under GPLv3.