The GOG wrapper is not configured correctly in your screenshot (the other one cannot be configured correctly as it doesn't support alternate scaling methods). Maybe try it in fullscreen with 1280x960 and integer scaling enabled as neither of those screens are 1:2 integer-scaled with nearest neighbor upscaling. They're 1:2 integer-scaled with bilinear/bicubic, which means only slightly less distortion than non-integer bilinear/bicubic scaling. The screenshot I've attached is what the game looks like with its native resolution enlarged losslessly with nearest neighbor scaling to 1280x960. The image is as sharp as it can be (pixel-perfect), and many purists prefer that. I like to see pixels.

Here's an article about it: http://tanalin.com/en/articles/lossless-scaling/

For what it's worth, IntegerScaler, the app offered elsewhere on the linked site, is compatible with either D1 wrapper and will allow me to play TheHell without blur. :)

Thank you for posting screenshots from both Diablo wrappers, though.

But it is :D That's why I said that the other wrapper does the same thing. If it doesn't use integer scaling but bilinear, then maybe you should tell the GOG support about it :) Either way I'm fine with the provided wrapper in TheHell.

No, it is not. My screenshot is of integer scaling using nearest neighbor achieved via IntegerScaler. The GOG wrapper supports proper integer scaling with nearest neighbor. If I owned it, I would show you a screenshot from it. Others have confirmed to me that it does indeed support integer scaling with nearest neighbor and can look just like my screenshot: pixel perfect, in other words.

You need to read the article I linked because you appear not to understand what integer scaling and pixel perfect scaling is. Otherwise you would never say 'if it doesn't use integer scaling but bilinear', because you'd know these two things are not mutually exclusive.

OK, "lossless integer scaling". Happy now?
As you said yourself, there's only slightly less distortion, meaning almost no difference between bilinear integer scaling and bilinear non-integer scaling, which is why I don't distinguish the two. I don't care about it. And I did read the article, and I even tried the IntegerScaler. And I won't be using it.

The screenshot is from DX wrapper made by GOG, with Windowed mode - integer scaling selected. If you don't believe me, don't. I also don't care.

Did all those things. Wierd.

I guess I'll put the CD back on my shelf for now :) I don't remember if I really enjoyed Hellfire or not so I was mostly curious to look again. I'm a bit of a Diablo purist and I recall it being sacraligious lol.

Ok so i've just tried it. And copying the following files from the Hellfire CD to a new folder in your Diablo folder then adding Hellfire Enchanced (so skipping to step 4 after copying these files from the CD seems to work for me.) I can't be 100% for this as I already have the reg entries installed from when I installed it.

You will need:

hellfire.exe
hellfire.mpq
HELLFRUI.DLL
hfmonk.mpq
hfmusic.mpq
hfvoice.mpq
language.inf *
sierra.inf *
Smackw32.dll *
Standard.snp *
storm.dll

(I did try deleting some of these files and whilst Hellfire ran I dont know if you will encounter issues down line, these files have a * next to them so i'm not sure they are needed.)

The GOG wrapper supports integer scaling (locking scaling to an integer factor) AND nearest neighbor. That's lossless, pixel perfect scaling. Some people like it blurry, and some like it sharp. You like it blurry and that's perfectly fine. Your life will be easier, and if you can view and read fuzzy graphics, you're probably not as migraine-prone as I am. Fortunately, the GOG wrapper supports either sharp or blurry filtering. I don't know why you can't get integer scaling + nearest neighbor to work as the GOG wrapper should automatically select nearest neighbor when an integer factor is used.

Like I said in my first reply to you, try fullscreen with the GOG wrapper. Or don't, as you're content with the way things are. I don't want others to leave with the mistaken impression that pixel perfect scaling isn't available via the GOG wrapper when that is a large part of the appeal of the new wrapper.

The gallery in this article has integer-locked nearest neighbor shots using the GOG wrapper. Check out gallery image 2 and view the screenshot fullscreen to see the individual pixels are in tact: https://arstechnica.com/gaming/2019/03/original-diablo-is-now-on-sale-for-10-drm-free-but-not-on-blizzards-app/

Thanks. I'll give this a try :)

No problem. Let me know if the game runs this way for you and i'll update the main post with it.

Son of a *#$&, that worked! Lol... thanks!

Great! :D

i can't seem to run integer scaling fullscreened, my display mode is set to Same as desktop, and it appears in a small area like in the attached screenshot. how do you make it fullscreen?

my Nvidia CP is set to perform scaling on GPU and keep aspect ratio mode, and not ticking the override.

the only way it can fullscreen with integer scaling is by choosing Set by application (Default) for display mode, but then screenshots are 640x480 only.

Your screenshot is 1600x900. Integer-locked resolutions for 640x480 are 1280x960 (2x2), 1920x1440 (3x3), etc. If your display is 1600x900 native, it cannot fit a 2x scaled 640x480 image due to insufficient vertical resolution. On a 1920x1080 display, the game image will be twice as large as in your screenshot and the borders will still be present (because 1920x1080 is not cleanly divisible by 640x480), but they will be much smaller. On a 1440p display, you'll only have borders on the sides because 480 * 3 = 1440.

There's a similar issue for 1920x1080 displays: 1920x1200 is the minimum native display resolution for cleanly scaling up 800x600 games. That means I cannot integer scale 800x600 games. A 1440p display is ideal for effectively scaling a great number of low resolution games without having to rely on very large integers.

Wow, that first screenshot is really interesting. I'd expect the image to be blurred, but it looks good. Sometime I'll have to try a custom resolution of ~2132x1200 to see what happens with 800x600 content.

When you force 1920x1080, is text on the desktop artifacted? Occasional lines of double thickness? I think the whole image is just smashed inward, but your screenshot looks a lot better than the bilinear shots.

Edit: Ah, of course the screenshot looks great to me, it's in my native resolution. On your monitor it would have been blurry downscaled. Not a good solution I'm afraid. :/