git://git.nikiroo.be / gofetch.git / blame
| Commit | Line | Data |
|---|---|---|
| 254d5bc3 NR |
1 | [WINE/TRICKS] D3DX9 VS DIRECTX9? \r |
| 2 | \r | |
| 3 | [linux_gaming] 2018-10-09_09-00\r | |
| 4 | \r | |
| 5 | o Reference: 2018-10-09_09-00__Wine_tricks__D3DX9_vs_\r | |
| 6 | o News link: https://www.reddit.com/r/linux_gaming/comments/9lc2je/winetricks_d3dx9_vs_directx9/\r | |
| 7 | o Source link: \r | |
| 8 | \r | |
| 9 | \r | |
| 10 | Hi! I have league of legends all set up on my desktop pc,\r | |
| 11 | running arch with proprietary nvidia drivers, and all I had to\r | |
| 12 | run the game is winetricks d3dx9. Now I try to install it on\r | |
| 13 | my arch laptop as well, but this time the game crashes when it\r | |
| 14 | tries to run (the launcher works as intended tho). So I tried\r | |
| 15 | a million thing to eventually find that winetricks directx9\r | |
| 16 | works. Now the game runs surprisingly well for a 13" laptop\r | |
| 17 | with only intel integrated graphics. So my question is: whats\r | |
| 18 | the difference between the d3dx9 winetricks package and the\r | |
| 19 | directx9 one? I noticed d3dx9 never spawns any ui, while the\r | |
| 20 | directx9 package prompts an old looking install wizard. My\r | |
| 21 | theory is that d3dx9 is just a part of the directx9 package,\r | |
| 22 | tho I am quite confused as to why my tower needs only d3dx9\r | |
| 23 | while the laptop needed another one. Thanks for any clue\r | |
| 24 | \r | |
| 25 | \r | |
| 26 | ** _clement_\r | |
| 27 | DirectX is a collection of API, the most common being Direct3D\r | |
| 28 | (for 3D graphics). D3DX is an extension (the "x" in the name)\r | |
| 29 | library for Direct3D.\r | |
| 30 | \r | |
| 31 | ** ionlydosupport\r | |
| 32 | league of legends need wine staging..\r | |
| 33 | anti cheat stuff\r | |
| 34 | \r | |
| 35 | ** SurelyNotAnOctopus\r | |
| 36 | Both are using the exact same packages (pacman -S\r | |
| 37 | wine-staging && pacman -S $(pactree -l wine-staging))\r | |
| 38 | \r | |
| 39 | \r | |
| 40 | ** thedoogster\r | |
| 41 | IIRC one of them installs a lot more ? I had a weird issue at\r | |
| 42 | one point where I needed to install d3dx9 to play the Monkey\r | |
| 43 | Island Special Editions.\r | |
| 44 | \r | |
| 45 | ** breell\r | |
| 46 | I'm not sure but look at the verbs in winetricks, there are\r | |
| 47 | comments about that:\r | |
| 48 | [1]https://github.com/Winetricks/winetricks/blob/master/src/wine-\r | |
| 49 | tricks#L6514\r | |
| 50 | \r | |
| 51 | \r | |
| 52 | \r | |
| 53 | \r | |
| 54 | [1]\r | |
| 55 | https://github.com/Winetricks/winetricks/blob/master/src/winetri-\r | |
| 56 | cks#L6514\r | |
| 57 | \r | |
| 58 | ** Adam_Stambaugh0\r | |
| 59 | Try sticking to d3dx9_36 if you need it. Otherwise, WINE's\r | |
| 60 | builtin alternative should be fine. D3dx9 just extracks the\r | |
| 61 | components needed from the directx9 installer. Directx9 installs\r | |
| 62 | the whole thing, even the parts that tend to conflict with WINE.\r | |
| 63 | The game on the intel laptop was probably trying to run a bit of\r | |
| 64 | different code for the intel chipset, something that wasn't\r | |
| 65 | properly handled by WINE's alternative.\r | |
| 66 | \r | |
| 67 | ** DesertFroggo\r | |
| 68 | Just play Dota 2...\r | |
| 69 | \r | |
| 70 | \r |