Compare commits

..

No commits in common. "11d99ac058598822c8998f4eda8a2af59dd6e174" and "1ff3b23a2ad5da671c693efb2ee176c356ae4c2d" have entirely different histories.

2 changed files with 2 additions and 5 deletions

View File

@ -13,11 +13,7 @@ toolchain must be installed.
## Usage
1. Ensure the game process is running (Being in the main menu should suffice).
2. Run the `cs2-dumper` executable.
- Note that some memflow connectors may require elevated privileges to work.
- Ensure that you have the appropriate config file in the same directory as the `cs2-dumper` executable:
- For Linux: `config_linux.json`
- For Windows: `config_win.json`
2. Run the `cs2-dumper` executable (Note that some memflow connectors require elevated privileges).
When running the executable without providing an optional memflow connector name, it will default to using the
memflow-native cross-platform OS layer to read the game's memory. However, any existing memflow connectors should work

View File

@ -30,6 +30,7 @@ pub fn interfaces(process: &mut IntoProcessInstanceArcBox<'_>) -> Result<Interfa
process
.module_list()?
.iter()
.filter(|module| !module.name.starts_with("nvidia")) // Temporary workaround for upstream bug: https://github.com/memflow/memflow-native/blob/1b063fc573957498b88a13b6120120480bc65ea5/src/linux/mem.rs#L168
.filter_map(|module| {
let buf = process.read_raw(module.base, module.size as _).ok()?;