Re: dgVoodoo 2.7.x and related WIP versions
Posted on Yesterday, 20:19
Addendum: getting a very similar lag using the RTSS scanline sync!
Re: dgVoodoo 2.7.x and related WIP versions
Posted on Yesterday, 20:08
Bad mouse lag in Unreal 2 menu using the frame limiter (80 FPS). Just starting the game, NOT pausing it. UT 2004 input too feels "strange" (in both game scaling set to "centered", to play @1920x1440)
Re: dgVoodoo 2.7.x and related WIP versions
Posted on 2021-04-09, 09:41
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
Re: dgVoodoo 2.7.x and related WIP versions
Posted on 2021-04-08, 22:07
FPS limiter for Glide or D3D too?
Re: Stalker lighting problem
Posted on 2021-04-08, 22:06
Well, let's wait a stable release of OpenXRay then! Will test OGSR too ( if you wanna take a look, OGSR is specifically intended as a "drag&drop" SHoC engine replacement! -> https://github.com/OGSR/OGSR-Engine )
Re: Stalker lighting problem
Posted on 2021-04-07, 10:27
This is a good thing ? (Open X-Ray implementation -> https://ci.appveyor.com/project/OpenXRay/xray-16/history )
Re: FEAR crash
Posted on 2021-03-31, 20:13
It literally runs having hiccups on the star menu too using the debug version!
Re: dgVoodoo 2.7.x and related WIP versions
Posted on 2021-03-31, 12:39
1) Man, there's the RTSS overlay in the screenshot. You obviously can see "D3D12". The "other" values are the VRAM quantity and the Fast Video Memory Access. Of course I've tested with them @default: same crash 2) I'm just using the dgv2 control panel to set the values, there's no "human error" …
Re: dgVoodoo 2.7.x and related WIP versions
Posted on 2021-03-31, 08:10
Copying the stock dgVoodoo.conf to the game folder eliminates a lot of variables. It will also only take a minute, so I don't see why you need to be so difficult about it. Because it's the same that dgVoodoo2 creates and because I've compared the 2 txt files and the only differences are my chosen …
Re: dgVoodoo 2.7.x and related WIP versions
Posted on 2021-03-30, 18:07
ZellSF wrote on 2021-03-30, 17:28: Potentially another AMD driver bug, but try with the stock config as already mentioned. But why? They're plain txt file with the options. Comparing the 2 files I see the obvious different values and nothing more. The "default" file is no magic 😐
Re: dgVoodoo 2.7.x and related WIP versions
Posted on 2021-03-30, 17:22
For me FEAR *benchmark* crashes ONLY with dgVoodoo2. No crash with DXVK or MS D3D9. And it crashes specifically after the first scene. In the same exact point everytime.
Re: dgVoodoo 2.7.x and related WIP versions
Posted on 2021-03-30, 15:16
With D3D11 the situation is even worse! (Radeon VGA)
Re: dgVoodoo 2.7.x and related WIP versions
Posted on 2021-03-30, 15:09
lowenz wrote on 2021-03-28, 00:43: FEAR 1.08 integrated benchmark crashes after the first combat scene @2560x1440. The game itself suggests that the possible issue is the VRAM (->4096 MB) for that resolution https://postimg.cc/56rnGdC4 I confim the crash with the lastest WIP No crash with DXVK or …
Re: dgVoodoo 2.7.x and related WIP versions
Posted on 2021-03-30, 14:57
Works fine here with the default (256 MB) VRAM setting. Try copying dgVoodoo.conf from the dgVoodoo archive to the game directory to make sure you're using stock settings.Clipboard01.jpg Nope https://i.postimg.cc/25cqhpTL/FEAR-2021-03-30-16-53-41-905.jpg There's an error in RAM quantity detection, …
Re: dgVoodoo 2.7.x and related WIP versions
Posted on 2021-03-28, 23:11
ZellSF wrote on 2021-03-28, 17:34: Works fine here with the default (256 MB) VRAM setting. Try copying dgVoodoo.conf from the dgVoodoo archive to the game directory to make sure you're using stock settings.Clipboard01.jpg Resolution? Got the problem at the specific resolution of 2560x1440.
FEAR crash
Posted on 2021-03-28, 00:43
FEAR 1.08 integrated benchmark crashes after the first combat scene @2560x1440. The game itself suggests that the possible issue is the VRAM (->4096 MB) for that resolution https://postimg.cc/56rnGdC4
Re: Stalker lighting problem
Posted on 2021-03-25, 17:03
DXVK 1.8.1 working right (just reporting) in STALKER SoC. 90% "native" d3d9 driver performance
Re: Codename Outbreak crash
Posted on 2021-03-24, 13:59
I got that error yesterday for ALL presets too, not only for 4096 (otherwise I would not asked for a new preset with 128 MB of VRAM). It seems erratic, maybe related to the GPU "real" driver.
Re: dgVoodoo 2.7.x and related WIP versions
Posted on 2021-03-24, 13:32
Dege wrote on 2021-03-24, 13:19: Ok, I've patched it to 2.1 but it's still running. Let's move this into a separate topic. Strange, now I got that error only setting the VRAM to 4096!
Re: dgVoodoo 2.7.x and related WIP versions
Posted on 2021-03-24, 13:09
Then just edit the VRAM value of another card? Yes, but think about people not wanting to "mess with options". That's who I was thinking of. Adding more graphic cards would be adding more options, and not very useful since the box isn't likely to list that graphic card (the box for Codename: …
Page 1 of 70