Memby

Solution: The issue was resolved by copying the clean files from the source directory (`D:\Ymir Work\`, which is just a local path on my computer) to their respective target paths within the pack. # | Source (D:\Ymir Work\) | Target Pack | Target Path | |---|--------------------------------------|-------------|----------------------------------------------| | 1 | effect\hit\blow_1\7-2.dds | PC | pc/assassin/effect/7-2.dds | | 2 | effect\monster\16-bottom.dds | PC | pc/assassin/effect/16-bottom.jpg | | 3 | effect\hit\blow_1\w_ring.dds | PC | pc/shaman/effect/w_ring.jpg | | 4 | effect\monster\white_sphere.dds | PC | pc/shaman/effect/white_sphere.jpg | | 5 | effect\monster2\healer\wind.dds | PC | pc/shaman/effect/wind.jpg | | 6 | effect\monster\w_star.dds | PC | pc/shaman/effect/w_star.jpg | | 7 | seasons\season1\effect\pc\shaman\effect | PC | pc/shaman/effect/jigam.jpg | | 8 | seasons\season1\effect\pc\shaman\effect | PC | pc/shaman/effect/jigam_ring.jpg | | 9 | seasons\season1\effect\pc\shaman\effect | PC | pc/shaman/effect/gyeokgong_triple_loop_2.jpg | |10 | seasons\season1\effect\pc\shaman\effect | PC | pc/shaman/effect/noe_w_ring.jpg | |11 | effect\etc\gathering\star.dds | guild | guild/effect/star.jpg | (Note: Items 1–6 and 11 are .dds files in the source but saved as .jpg in the target path; the content remains identical, only the file extension/name was adjusted without actual format conversion.)

up

up

I used the same files on a different machine with a Ryzen 9 7950X processor, RTX 4080(16GB) graphics card, and Windows 11 Pro, and I didn't encounter any issues.

Update: Yesterday, I moved from Windows 10 Pro to Windows 11 Pro. I did a clean setup with only the essential files and apps, yet the primary issue(Issue 1) remains. At this point, is it safe to say that the RTX 4090 is the source of the problem?

up

Hi guys,I'm running into some issues with the server files I've been developing, as shown in the videos below. 1- When hitting any mob/slot in a Windows 10 environment, a white square appears instead of the intended skill/hit effect. This occurs in both Debug and Release modes. 2-Graphical corruptions occur in a Windows 10 environment after switching the system graphics settings to CPU rendering. Files Informations: Server / Side: - Boost: 1.73.0 - DevIL: 1.7.8 - Crypto++: 8.4.0 - LZO: 2.10 - GCC: 9 - C++ Standard: C++14 Client Side: - Granny: 2.11.8 - libjpeg: 9a - Python: 2.7 - Crypto++: 8.4.0 - DevIL: 1.7.8 - LZO: 2.10 - C++ Standard: C++14 Client Granny: v2.11.8 (Fully converted .gr2 assets). Compiler (Client/Dump): Visual Studio 2022. Compiler (Server): GCC 9. Database: MySQL 5.6 (Fully compatible). Tools: Custom dump_proto synced with protoreader.cpp. System Specifications (Affected Machine) OS: Microsoft Windows 10 Pro (Version 10.0.19045 Build 19045) CPU: AMD Ryzen 9 7950X3D (16-Core, 32 Threads, 4201 MHz) RAM: 64.0 GB GPU: NVIDIA GeForce RTX 4090 (24GB GDDR6X) Driver: Game Ready Driver - 591.74 (Jan 5, 2026) DirectX: DX 12 (Feature Level 12_1) Display: DELL AW2723DF (2560x1440 @ 280Hz, G-SYNC Compatible) Test Results & Cross-Platform Comparison Test 1: Windows 11 + RTX 4070 (Physical Machine) Result: Stable. Both Issue 1 and Issue 2 are not present. Everything works as intended. Test 2: Windows 10 + VirtualBox VM (Guest OS) VM Specs: 2GB RAM / VirtualBox Graphics Adapter. Issue 1 Result: Stable. No white square effects observed. Issue 2 Result: Reproduced. The graphical glitches mentioned in the video are present. Summary of Findings Issue 1 seems specific to the Windows 10 + RTX 4090 environment, as it does not occur on the RTX 4070 or the VirtualBox environment. Issue 2 is reproducible in the VirtualBox VM environment but works fine on the Windows 11 + RTX 4070 setup, suggesting a possible compatibility issue with Windows 10's software rendering or specific driver interactions. Additionally, Issue 1 is not limited to player-initiated hits. The white square artifacts also appear when mobs hit the player. Furthermore, I am encountering the same issue when mobs (specifically tested with Vnum 1079 and 1089) cast skills on the player. This indicates that the issue is likely a global rendering problem affecting all hit/skill effect particles in the game environment. No errors are being logged in the syserr.txt files regarding these issues. The client continues to run without any log output or crashes, which suggests this is purely a graphical rendering/driver compatibility issue.