How do I install the Deploy And Test Game skill?

Run npx skillmds@latest add nvidiagameworks/deploy-and-test-game in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Deploy And Test Game safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Deploy And Test Game?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Deploy And Test Game free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Deploy And Test Game?

nvidiagameworks (@nvidiagameworks) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Deploy And Test Game by nvidiagameworks

Name: Deploy And Test Game
Author: nvidiagameworks

File contents

Deploy and Test a Game

All commands run in PowerShell from the repo root unless otherwise noted.

Game Targets

gametargets.conf (INI-style, not checked into git) defines the user's local game targets. Each section has:

outputdir — the .trex folder where built DLLs are deployed
workingdir — the game's working directory
commandline — executable and arguments

The file should already be configured by the developer.

To list available targets:

python vsgen/get_game_target_list.py

This outputs GameName,outputdir per line.

Build, Deploy, and Launch

The recommended configuration for development is debugoptimized (_Comp64DebugOptimized).

Step 1: Build (incremental)

cd _Comp64DebugOptimized; meson compile -v

Step 2: Deploy to a Game Target

Deploy built artifacts (d3d9.dll, DLSS, NRD, USD libs, etc.) to a game's .trex folder:

meson install -C _Comp64DebugOptimized --tags <GameTarget> --only-changed

The tag is the section name from gametargets.conf (e.g. Portal, HalfLife2_RTX). The --only-changed flag skips files that haven't changed.

Step 3: Launch the Game

Parse the target's workingdir and commandline from gametargets.conf, then launch:

$env:DXVK_CONFIG_FILE = "<repo_root>\dxvk.conf"
Start-Process -FilePath "<workingdir>\<executable>" -ArgumentList "<args>" -WorkingDirectory "<workingdir>"

Debugging Crashes

The runtime automatically generates .dmp crash dump files. When a crash occurs, analyze the dump to get the call stack and crash context.

The Bridge (32-bit Games)

For 32-bit games, a two-process architecture is used:

The game loads a 32-bit d3d9.dll (bridge client) which intercepts D3D9 calls
The client automatically launches NvRemixBridge.exe (64-bit server) from the .trex folder
The server loads the 64-bit d3d9.dll (the actual Remix runtime) and renders into the game window
Communication between client and server uses shared-memory circular queues

When debugging bridge-based games, both processes may need inspection. The bridge disables IPC timeouts when a debugger is attached, so breakpoints won't cause disconnects. Bridge-specific configuration is in bridge.conf.

---name: deploy-and-test-gamedescription: Deploy built dxvk-remix to a game and launch it. Use when the user asks to deploy, test, run, or debug a game with Remix, or when built changes need to be tested in a running game.---# Deploy and Test a GameAll commands run in PowerShell from the repo root unless otherwise noted.## Game Targets`gametargets.conf` (INI-style, not checked into git) defines the user's local game targets. Each section has:- `outputdir` — the `.trex` folder where built DLLs are deployed- `workingdir` — the game's working directory- `commandline` — executable and argumentsThe file should already be configured by the developer.To list available targets:```powershellpython vsgen/get_game_target_list.py```This outputs `GameName,outputdir` per line.## Build, Deploy, and LaunchThe recommended configuration for development is **debugoptimized** (`_Comp64DebugOptimized`).### Step 1: Build (incremental)```powershellcd _Comp64DebugOptimized; meson compile -v```### Step 2: Deploy to a Game TargetDeploy built artifacts (d3d9.dll, DLSS, NRD, USD libs, etc.) to a game's `.trex` folder:```powershellmeson install -C _Comp64DebugOptimized --tags <GameTarget> --only-changed```The tag is the section name from `gametargets.conf` (e.g. `Portal`, `HalfLife2_RTX`). The `--only-changed` flag skips files that haven't changed.### Step 3: Launch the GameParse the target's `workingdir` and `commandline` from `gametargets.conf`, then launch:```powershell$env:DXVK_CONFIG_FILE = "<repo_root>\dxvk.conf"Start-Process -FilePath "<workingdir>\<executable>" -ArgumentList "<args>" -WorkingDirectory "<workingdir>"```## Debugging CrashesThe runtime automatically generates `.dmp` crash dump files. When a crash occurs, analyze the dump to get the call stack and crash context.## The Bridge (32-bit Games)For 32-bit games, a two-process architecture is used:1. The game loads a **32-bit `d3d9.dll`** (bridge client) which intercepts D3D9 calls2. The client automatically launches **`NvRemixBridge.exe`** (64-bit server) from the `.trex` folder3. The server loads the **64-bit `d3d9.dll`** (the actual Remix runtime) and renders into the game window4. Communication between client and server uses shared-memory circular queuesWhen debugging bridge-based games, both processes may need inspection. The bridge disables IPC timeouts when a debugger is attached, so breakpoints won't cause disconnects. Bridge-specific configuration is in `bridge.conf`.

Frequently asked questions

Deploy And Test Game