dx9-ffp-port

To port a DX9 game to fixed-function pipeline for RTX Remix, copy the remix-comp-proxy template into patches/<GameName>/ and implement per-game hooks under src/comp. This workflow modifies renderer.cpp and ffp_state to route draws correctly, enabling RTX Remix compatibility for shader-based titles.

White geometry in DX9 RTX Remix setups indicates incorrect draw routing or missing fixed-function state handling. You can diagnose and resolve this by customizing per-game hooks in renderer.cpp and managing matrix handling in ffp_state within the copied remix-comp-proxy framework.

Building a d3d9 proxy for DX9 patching involves creating patches in patches/<GameName>/, customizing hooks in src/comp, and configuring remix-comp-proxy.ini. After implementing the framework, build the d3d9.dll proxy to deploy and run the Remix-enabled rendering chain for testing.

Yes, you can use RTX Remix with shader-based DX9 titles exhibiting missing objects or incorrect transforms. The skill prescribes a structured porting workflow to convert these games to the fixed-function pipeline, resolving visual issues by managing rendering routing and matrix handling.

The best way to handle matrix transforms when porting DX9 games to fixed-function pipeline is by managing ffp_state within the remix-comp-proxy framework. Correct matrix handling in this file ensures visual transforms are reproduced accurately for RTX Remix compatibility.

Yes, you need to edit remix-comp-proxy.ini to manage patch deployment for RTX Remix. Configuring this file within the patches/<GameName>/ directory is a required step to build the d3d9.dll proxy and run the rendering chain successfully.