[Bug/Question] #2

[TesterTim]

Environment

- MarkBench Test Version: 1.0.0
- OS:  Windows 11 22H2
- GPU: RX 6650M
- CPU: Ryzen 7 6800H

What happened?

I am trying to make a harness for Furmark but I am having some issues.

python .\furmark_runner.py --benchmark_mode "GPU stress test" --resolution "1920x1080" --resolution_scale "2x" --anti_aliasing "4x MSAA" is the command that I am running and all it does it open FurMark and then doesnt do anything.

This is my YMAL Manifest :

friendly_name: "FurMark Benchmark" executable: "FurMark.exe" process_name: "FurMark.exe" disable_presentmon: false hidden: 1 output_dir: "results" options:

• name: resolution type: select values: ["1280x720", "1920x1080", "2560x1440", "3840x2160"]
• name: benchmark_mode type: select values: ["GPU stress test", "Burn-in test", "Benchmarking"]
• name: resolution_scale type: select values: ["1x", "2x", "3x", "4x"]
• name: anti_aliasing type: select values: ["Off", "2x MSAA", "4x MSAA", "8x MSAA"]

This is my python script: (Copy and Paste from your github since I am new to this and learning) import os import sys

Default installation directory and executable name

DEFAULT_FURMARK_DIR = "C:\Program Files (x86)\Geeks3D\Benchmarks\FurMark" EXECUTABLE = "FurMark.exe"

Construct absolute path to FurMark executable

ABS_EXECUTABLE_PATH = os.path.join(DEFAULT_FURMARK_DIR, EXECUTABLE)

Check if FurMark executable exists

if not os.path.isfile(ABS_EXECUTABLE_PATH): raise ValueError('No FurMark installation detected! Default installation expected to be present on the system.')

Extract command-line arguments passed to the script (excluding script name)

args = sys.argv[1:]

Construct the command to execute FurMark

command = f'"{ABS_EXECUTABLE_PATH}" ' for arg in args: command += arg + ' '

Remove trailing whitespace

command = command.rstrip()

Execute the command

os.system(command)

File name is furmark_runner.py

Relevant log output

No response

Anything else?

No response

[TesterTim]

Like I said it opens the file but doesnt run anything.

[nharris-lmg]

The formatting of your code in your comment needs to be within ``` ``` lines so it doesn't turn into a bunch of headers like it has.

Better yet if put your code in your own fork on a branch, or even a gist I will be happy to take a closer look.