search

PeterTh / gedosato

The Generic DownSampling Tool
GNU General Public License v3.0
463 stars 166 forks source link

Downsampling Diablo 3 with build 0.12.1249 #88

Open Aexrael opened 10 years ago

Aexrael commented 10 years ago

Diablo 3 suffers from peculiar issue where the mouse cursor is only visible in 1/4 of the screen, notably the top left area. Various mouse fixes are enabled in order to get the positioning corrected.

I'm not sure what to do to fix this.

Both modifyGetClientRect and modifyGetWindowRect are set to true by default.

PeterTh commented 10 years ago

Hmm, interesting. I'll have a look at some point.

kussii commented 9 years ago

i got the same issue

kussii commented 9 years ago

sorry for the duplicate post heres a Screenshot of the restriction of the mouse http://gyazo.com/aff9d0366c91aa8d259c2ebc89314e4b (Life is Feudal Your Own) GeDoSaTo version 0.13.1448 if the mouse pointer is moved into the black area it disappears

DAOWAce commented 9 years ago

From testing, it seems to work in two ways.

A: Set interceptWindowProc to true, everything else default. Doesn't seem to be working now in my later tests.

or

B: Set modifyGetClientRect and modifyGetWindowRect to false.

I haven't run tests long enough to see what the differences are between these methods, if any, but both of them appear to function just fine.

Other than that, I haven't tested AA/Post (have them disabled), but I assume they will need a pshash to work properly. Corrupts the UI as expected.

Edit: injectPSHash 873685df half works. Literally that, it makes it not affect half of the UI. Still trying to get a better one but I'm close to giving up.

The game seems to run pretty damn great at normal 4K. I'm getting 90 FPS uncapped with everything maxed out.

Only downside is that if you use DarkD3 you're gonna have really bad text corruption. Downsampling seems to negatively affect the text on the UI and running DarkD3 (even without sharpness) further corrupts it, making it really hard to read. As much as I'd love to port over DarkD3's settings (it's a custom InjectFXAA), I don't know anything about this shader stuff. I've compared the settings files, but there's a large amount of differences and I don't have the knowledge required to port it over. If a PSHash fixes the text issues with raw downsampling then there should be no problems, but I doubt it will work (plus I've never successfully got a working PSHash when I tried it for one game).

As a bonus for you 21:9 users (which Blizzard hates), open D3Prefs.txt, change DisplayModeWindowMode to 2 (borderless) set the DisplayModeWidth and DisplayModeHeight to your downsampled resolution then mark the file read only. Startup the game with GeDoSaTo running (configured for 21:9) and bam, downsampling to 21:9. Unfortunately, the text doesn't seem to be quite right compared to 16:9 downsampling.