01/03/2026 Coming Soon

Understanding the coding process behind a graphics mod from the outside is truly difficult. While it might seem like just "changing a few color settings," behind the captivating visuals of Project-Realish 1.4 lies a massive engineering battle: "forcing" modern technologies onto an aging game engine.

The real challenges in the coding aspect can be summarized as follows:

Overcoming Engine Limits (C++ DLL Injection): ETS 2's Prism3D engine, by its nature, doesn't natively support modern light bounce calculations like SSR or RTGI. Integrating these features externally requires writing custom C++ plugins that directly interfere with the game's memory structure and rendering processes. Ensuring these codes don't conflict with the game and kill FPS is a real nerve-wracking task.

Rewriting Depth Math: To prevent those flawless reflections from flying around or crashing into the truck, you need to process the "Depth Buffer" data. You have to write algorithms that take the complex (logarithmic) depth data provided by the game and instantly convert it into a linear formula that shaders can read. A single comma error in a line can cause the entire screen to flicker.

Massive Data Automation (Python Scripts): It's impossible to manually synchronize thousands of textures, material files (.mat, .sii), and camera angles perfectly. Writing Python scripts that connect all this infrastructure, automatically edit game code, and detect deficiencies means hours of debugging and testing.

In short, behind that single drop of water reflection or perfectly functioning dashboard you see on your screen lies sleepless nights spent hacking the game engine's limits, recalculating the mathematics, and combining thousands of lines of code.

Sıkı Tutunun Yakında Çıkıyor!! | 1.58 | Project Realish 1.4 | #ets2 Beta videosu (YouTube)