How thirteenag/iii.vc.sa.iv.project2dfx works
Project type and purpose
• Project2DFX is a native-code plugin framework written in C++ that injects into various GTA titles (III, VC, SA, IV, LCS, VCS) to enhance LOD corona rendering.
• It also includes a standalone data-grabber tool (“2DFXDataGrabber”) to extract game data archives, plus configuration files and build scripts.
File structure
• Top-level:
• premake5.lua/bat/exe – cross-platform build orchestration
• includes/ – header + C++ helpers + the entire RwSDK
• source/ – subfolders per game: each contains plugin entrypoint (dllmain.cpp) and CSearchlights logic
• external/ – submodules for IniReader, hooking, injector
• data/ – prebuilt tools (7za.exe), 2DFXDataGrabber binaries + data archives, LOD lights .ini/.dat files
• resources/ – VersionInfo for Windows resources
• readme.md, license, CI configs
• Patterns:
• Plugin per game → separate DLLs built from nearly identical code bases
• Shared engine code in includes/ and external/
• Standalone CLI utility (DataGrabber) in source/2DFXDataGrabber
• Build managed by Premake to generate Visual Studio/AppVeyor/etc. projects
README for additional insights
• Confirms multi-game support, plugin nature, release artifacts (DLLs per game + data archives).
Elements
• Build dependencies (Premake → compile → outputs)
• Runtime call/injection flow (GTA.exe → Injector → Plugin → RwSDK → GPU)
• Data file loading (Plugin → IniReader → data/*.ini, .dat)
• DataGrabber → 7za.exe → extracted archives
• Runtime components in another (e.g., green)
• Data assets in yellow
• Legends or annotations for:
• “Per-game plugin modules”
• Shared code vs per-game specialization
• DataGrabber workflow