Gorky17 has depth issues with forced resolution or antialiasing, all 3D elements get forced on top of 2D backgrounds even when they're supposed to be behind. Without anything forced there's some major visual glitches when zooming in and fast video memory access is required to run the game.
wrote:Is there any chance of future support? Lots of games use it. […]
wrote:Independently on that, Indeo is not compatible with dgvoodoo. It needs extra support like DirectShow.
Is there any chance of future support? Lots of games use it.
What i haven tried is changing the video format/container. Maybe that can work unless its hardcoded in Indeo.
I supposed it was not supported since LAV filters are my default codec suite.
Yes, I'm planning to support it in the future.
wrote:1) "Stretch with AR" upscale filtering/blurring is not applied when dgVoodoo2 detect a forced resolution = monitor native resolution and this is the correct behaviour and the result is truly beautiful!
But the filtering (and so the resulting blur) *IS* applied if the forced resolution has the same height of the monitor native resolution but not the length! Or viceversa (I didn't test this scenario). I think it would be a good thing to automatically disable the filtering in those cases too! (same vertical pixel number detected OR same horizontal pixel number detected)
Indeed, it should work with no filtering in those cases. I'll fix it.
wrote:2) Sometimes forced resolution creates this unwanted frame tesselletion: is it avoidable?
Unfortunately not. It's because of stretched polygons with mismatching texture coordinates.
---
I've been being busy with testing all my stuffs and found some thing is broken, for example, Lego Racers and Breath Of Fire 4.
I'd like to fix all regression bugs before releasing a new version.
Found another D3D8 game where AF16x is not applied (Pandora Tomorrow was the other one): Enclave.
In Sacred there's a strange "white border" around the player shadow (and ONLY the player one)
Dege, i cant get 60Hz with my 970G1. The monitor is perfectly capable aswell as the graphic card.
If i set the 60Hz manually it still render 59,97FPS.
Any idea about this?
For Windows 59 Hz=60 Hz, so do not worry.
Maybe update the *monitor* drivers.
wrote:For Windows 59 Hz=60 Hz, so do not worry.
Maybe update the *monitor* drivers.
It gives me the same result with my monitors and with my Blackmagic Video Assist.
I have seen 60Hz in earlier posts so i dont know where is the problem.
As for Breath of Fire 4, crashing is not fault of dgVoodoo.
This game runs with a 64KB stack (what a tiny one... but I guess this had to run on Win95 with 4MB RAM) and it's even divided into more parts inside the game (16KB).
Edit: probably the same is true for all early Capcom games like Megaman1.
Running it through dgVoodoo causes internal stack overflow and the game crashes. Instead of struggling with keeping the stack usage low (somehow) in dgVoodoo, I patched the game exe:
http://dege.fw.hu/Patches/BOF4Patch.zip
Now it should run even with 2.51.
wrote:Dege, i cant get 60Hz with my 970G1. The monitor is perfectly capable aswell as the graphic card. […]
Dege, i cant get 60Hz with my 970G1. The monitor is perfectly capable aswell as the graphic card.
If i set the 60Hz manually it still render 59,97FPS.
Any idea about this?
Could you attach a dgVoodoo.conf file plz, in which the resolution and refresh rate is set to 1920x1080, 59Hz, plz?
I guess your monitor doesn't support 60Hz but "only" 59.97Hz. These refresh rates are given in rational forms, like 5997/100,
and for displaying the result to the user, Windows may round it up while dgVoodoo rounds that down.
wrote:Found another D3D8 game where AF16x is not applied (Pandora Tomorrow was the other one): Enclave.
Does forcing AF16x is applied for other D3D11 games? 😀
Ok, it's a stupid question, I guess it is.
Yes, it's applied :p
wrote:Could you attach a dgVoodoo.conf file plz, in which the resolution and refresh rate is set to 1920x1080, 59Hz, plz?
I guess your monitor doesn't support 60Hz but "only" 59.97Hz. These refresh rates are given in rational forms, like 5997/100,
and for displaying the result to the user, Windows may round it up while dgVoodoo rounds that down.
Here.
https://googledrive.com/host/0B26GcDMRksJgYkV … E/dgVoodoo.conf
My monitor is a LG 24EA53V-P, it support 60hz, but i have tried with the Blackmagic device aswell, same thing.
Thanks.
The frequency rational in the config file is 59954/1000, it's 59.954Hz.
dgVoodoo truncate it for displaying, that's why you see 59Hz in the setup. I could modify it to rounding though.
Edit: it's messy a bit. One of my monitors supports the same 59954/1000 refresh rate for all (except one) display modes, at least that's what DXGI reports. In spite of that, Windows (7) display settings dialog lists each mode twice (32 bit, truecolor), one with 59Hz and another with 60Hz.
Edit2: I think I cancel "rounding" mode. DirectX Caps Viewer (DX11) lists the available display modes in exactly the same form as dgVoodoo.
I forgot about Outlaws. Unfortunately Outlaws, Thief and a third game (I cannot remember now) can only be played with 'Unspecified' scaling method, otherwise the mouse is captured into the upper left corner of the screen. It's because these games interpret mouse coordinates in an other way than most of the games, and dgVoodoo has no chance to figure out what way to go.
It could be workarounded - by yet another user option... 😵
wrote:I forgot about Outlaws. Unfortunately Outlaws, Thief and a third game (I cannot remember now) can only be played with 'Unspecified' scaling method, otherwise the mouse is captured into the upper left corner of the screen. It's because these games interpret mouse coordinates in an other way than most of the games, and dgVoodoo has no chance to figure out what way to go.
It could be workarounded - by yet another user option... 😵
That sucks. Also, what about the renderer mode switch send it to windowed mode?
Thief -> NewDark
It would be madness to not use it.
wrote:Edit2: I think I cancel "rounding" mode. DirectX Caps Viewer (DX11) lists the available display modes in exactly the same form as dgVoodoo.
So, isnt there any way to output 60hz? I dont understand if it is a monitor fault, graphic card fault, Windows 10 fault or dgVoodoo fault.
wrote:That sucks. Also, what about the renderer mode switich send it to windowed mode?
Didn't check it yet.
wrote:wrote:Edit2: I think I cancel "rounding" mode. DirectX Caps Viewer (DX11) lists the available display modes in exactly the same form as dgVoodoo.
So, isnt there any way to output 60hz? I dont understand if it is a monitor fault, graphic card fault, Windows 10 fault or dgVoodoo fault.
It's not a fault. The monitor supports 59.954Hz and when this value, as a number, is displayed to the user, it appears as 59Hz (in e.g. dgVoodoo setup, DX Caps Viewer) or 60Hz (e.g. Windows display settings) depending on how it's converted to an integer number.
But, when the display mode in question is set on the monitor, then dgVoodoo sets exactly 59.954Hz so the real supported one is used.
(That's why I wrote in the readme that one should always choose the refresh freq from the dropdown list instead of typing it manually.
Because if you type 59, then 59.000Hz is sent to the display driver instead of 59.954Hz.)
wrote:Thief -> NewDark
It would be madness to not use it.
I didn't know about, thanks!
wrote:I didn't know about, thanks!
!!!!!!!
😁
The all NewDark thing.....it's something like a spy story in the Thief Community 😁
No one knows who is "Corbeau" yet :p
Omikron: The Nomad Soul
The main menu logo is not fully transparent (?):
vs
http://www.mobygames.com/game/windows/omikron … meShotId,30893/
11 1 111 11 1 1 1 1 1 11 1 1 111 1 111 1 1 1 1 111
Enclave (dynamic? -> torch) lighting problem:
Default D3D8 (Win7)
dgVoodoo2
AF16x (in game option, not forced!) not applied:
