Fixing bicubic + Lanczos filters combined with integer scaling = ?
Fow now i see that both of these filters works as the nearest filter... (and this happen also with bilinear filter)
It only happens under some additional circumstances, using the CRT scaling filter was the one I reported.
GTA2 freezes with 3dfx mode (ALL dgVoodoo2 versions, and i think also dgVoodoo1 when XP was supported); this happen expecially when triple buffer is enabled (and this game doesn't support it)
It's happening also with nGlide program
Some years's ago with a very old PC with windows 98 GTA2 was freezing with triple buffer (in regedit there is a setting of it for GTA2) and this with a 3dfx Voodoo3 2000
in dgVoodoo2 where is Triple Buffer option? I have to disable it
with Half-life there are two cursors in-game with dgVoodoo2 (this with ddraw mode at least) and these don't work properly
I release some additions and bugfixes to the latest WIP:
=========================
WIP79_1:
=========================
- Fixing a D3D12 cache bug (nv Chameleon demo)
- Implementing missing point-type fillmode (nv tech demos)
- Adding option DirectXExt\Default3DRenderFormat
- Fixing a bug with forced MSAA in D3D11/12 DX backend
- Glide fixings (Test Drive 5)
- Finetunig Glide (configured to Dosbox environment) window handling for Dosbox
http://dege.fw.hu/temp/dgVoodooWIP79_1.zip
http://dege.fw.hu/temp/dgVoodooWIP79_1_dbg.zip
Basically I intend this to be the next version, if no serious problems reported.
I released v2.74. It's the same as WIP79_1 with a minor Glide change + an FPS limiter added.
http://dege.fw.hu/dgVoodoo2/bin/dgVoodoo2_74.zip
http://dege.fw.hu/dgVoodoo2/bin/dgVoodoo2_74_dbg.zip
FPS limiter for Glide or D3D too?
Shouldn't 60 be one of the preset FPS limits (I know you can probably just type in a number)? It's going to be more useful than 1000.
lowenz wrote on 2021-04-08, 22:07:FPS limiter for Glide or D3D too?
For both, the presentation layer is common for them.
ZellSF wrote on 2021-04-09, 06:37:Shouldn't 60 be one of the preset FPS limits (I know you can probably just type in a number)? It's going to be more useful than 1000.
I didn't have much idea for the most useful ones (but I guess limiting into range 25-60 makes the most sense, for old games), but I can change the preset in a subsequent patch version.
Here's what I'm thinking of potential framerate limit settings that makes sense:
15/20/25 = just general "low" framerates for games that pushed graphics and just expected 3D rendering to be slow.
30/35/60/70 = "common" "low" refresh rates, or halves of them. Likely targets, games might have been running so close refresh rate mismatch judder wasn't so bad.
That's for the compatibility part of it at least, some people might want to limit FPS to their refresh rate, or their refresh rate - 3 (common with variable sync monitors).
Also I'm struggling to close dgVoodooCpl.exe with the newest version, any idea why that would be? It frequently just seems to freeze, rather than close. WIP79_1 and earlier are fine.
This is regardless of if I'm closing with "OK" or the titlebar button.
I have a guess what could be the culprit. I'll change it and also add the values of your suggestion to the preset.
Update: Ok, I fixed the problem. Plz re-download 2.74 with the updated CPL.
Yes, same problem with the control panel.
Preset for FPS limiter?
Typical options:
*30/60
*Vsync classic values (60,75,85,120,144)
Other options:
*Vsync classic values (60,75,85,120,144) + some FPS -> VSync testing
*Vsync classic values (60,75,85,120,144) - some FPS -> Adaptive Sync testing
ZellSF wrote on 2021-04-09, 07:52:Here's what I'm thinking of potential framerate limit settings that makes sense: […]
Here's what I'm thinking of potential framerate limit settings that makes sense:
15/20/25 = just general "low" framerates for games that pushed graphics and just expected 3D rendering to be slow.
30/35/60/70 = "common" "low" refresh rates, or halves of them. Likely targets, games might have been running so close refresh rate mismatch judder wasn't so bad.
That's for the compatibility part of it at least, some people might want to limit FPS to their refresh rate, or their refresh rate - 3 (common with variable sync monitors).
There are also some 12 fps games
With Midtown Madness 1 in Direct 12 mode some graphics effect are missing; also some fonts are still corrupted, and this happen also when Cleartype is disabled
FulValBot wrote on 2021-04-11, 16:26:With Midtown Madness 1 in Direct 12 mode some graphics effect are missing; also some fonts are still corrupted, and this happen also when Cleartype is disabled
Works fine here. By more specific? Post screenshots?
I know that works fine, but smoke effect is missing...
That doesn't appear to be related to dgVoodoo (or the D3D12 render specifically):
https://www.pcgamingwiki.com/wiki/Midtown_Mad … e_not_appearing
And fonts look fine; it's something with your setup: make sure dgVoodoo.conf is stock and make sure font smoothing is off.
Font smoothing change nothing in this game, and if i disable that it disable Cleartype too...
Cleartype definitely breaks Midtown Madness' fonts; if they don't for you it's because Windows is applying the built-in compatibility mode (your exe is named midtown.exe).
Which brings us to the other point; try with a stock dgVoodoo.conf.
Yes i see that it was using Midtown.exe and fonts was broken
i forgot to edit desktop shortcut... i have already both .exe files...
yes, i confirm that with renamed .exe all fonts are good when Cleartype is disabled