- Joined
- Dec 25, 2020
- Messages
- 8,693 (5.33/day)
- Location
- São Paulo, Brazil
Processor | 13th Gen Intel Core i9-13900KS |
---|---|
Motherboard | ASUS ROG Maximus Z790 Apex Encore |
Cooling | Pichau Lunara ARGB 360 + Honeywell PTM7950 |
Memory | 32 GB G.Skill Trident Z5 RGB @ 7600 MT/s |
Video Card(s) | Palit GameRock OC GeForce RTX 5090 32 GB |
Storage | 500 GB WD Black SN750 + 4x 300 GB WD VelociRaptor WD3000HLFS HDDs |
Display(s) | 55-inch LG G3 OLED |
Case | Cooler Master MasterFrame 700 benchtable |
Power Supply | EVGA 1300 G2 1.3kW 80+ Gold |
Mouse | Microsoft Classic IntelliMouse |
Keyboard | IBM Model M type 1391405 |
Software | Windows 10 Pro 22H2 |
Benchmark Scores | I pulled a Qiqi~ |
But CUDA is not absent, only 32bit does, what if DXVK translates everything to 64bit?
Its worth checking, i would but im on a pre-order list for over a month and it may take 2-3 months more lol, i pre-ordered in 4 shops just in case
DXVK does not make a 32-bit application 64-bit, it simply intercepts and does just-in-time (JIT) translation of DirectX runtime calls and converts them into the open-source Vulkan API. This program was designed essentially as a way to run DirectX games on Linux, because it does not support DirectX and does not have the WDDM display driver model available. While DXVK also runs on Windows, its usefulness tends to be quite limited, often niched to workaround some game engine bugs in some hardware configurations.
You have to understand, 32 and 64 bit applications are binary incompatible. The reason you can run 32 bit apps on 64 bit Windows unmodified is due to the "Windows on Windows 64" (WoW64) compatibility system, and it's only fully seamless as it is because the required instructions to execute these programs are still present and there is a way to manage their memory without affecting the rest of the system. This is because of a decision that the industry took at the very beginning of the 64-bit era, which is basically choosing to extend the existing x86 architecture instead of adopting a new 64-bit ISA (this is the story of the AMD Athlon 64 and the Intel Itanium processor, I could tell you all about it sometime but it's not the scope of this thread - to put it in simple terms, AMD's proposal won over Intel's).
On a pure 64-bit system, a 32-bit executable will not run. Therefore, it stands to reason that you cannot run 32-bit applications on a 64-bit runtime. This is why .NET and Visual C++ include both a "x86" and a "x64" DLL, they aren't interchangeable with one another. It's as simple as this: no 32-bit CUDA, no 32-bit PhysX.