Graphics lock up \ VOGONS

Graphics lock up

Topic actions

First post, by tumultTransmuted

Posted on 2018-03-16, 00:00

tumultTransmuted Offline

Rank Newbie

Rank: Newbie
Posts: 2
Joined: 2018-03-15, 23:27

I'm in love with this program. I've used it on Might and Magic 6/7 with perfect results.

BUT, I just picked up FFXI again and have noticed an issue that I only run into when using DGVoodoo. Every once in a while, the graphics lock up and I have to end task and re-open the game. The game is still running and I can hear the action, but the graphics have frozen.

This doesn't happen when I'm running the game alone or with just Windower, only when I'm using DGVoodoo.

I also noticed it happens more often depending on how much VRAM I have allocated to it via DGVoodoo. I currently use 4095MB (increase the cap please? I have 11GB of VRAM 😜) but the issue happens much faster with 256 or 1024MB of VRAM.

My specs if it helps:

1i7-4770k @ 4.6GHz
21080ti (11GB VRAM) w/ latest nVidia drivers (as of 2018-03-15)
332GB RAM @ 2400 MHz
4Gigabyte Z77X-UD3H
5SSD
6Windows 10 with all updates
7
8DGVoodoo WIP 43
9
10Disable and passthru to real DirectX, unchecked
11
12dgVoodoo Virtual 3D Accelerated Card
13VRAM 4095 MB
14Texturing: Force Anisotropic 4x
15                No mipmapping, unchecked
16Resolution: 2560x1440
17Behavior: Application controlled fullscreen/windowed state, checked
18               Disable Alt-Enter to toggle screen state, checked
19Antialiasing: 8x
20Misc: Bilinear blit stretch checked
21         Apply Phong shading when possible, checked
22         Fast video memory access, checked
23         Force vSync, unchecked
24         dgVoodoo watermark, unchecked

And sorry, I haven't kept a good eye on VRAM usage to definitively say if that's the issue though it is my hunch.

Edit: I did check the VRAM usage the last two times this happened and both times my VRAM was totally maxed out. Nothing open except Final Fantasy XI.

Reply 1 of 3, by Dege

Posted on 2018-03-20, 18:18

Dege Offline

Rank l33t

Rank: l33t
Posts: 3064
Joined: 2003-09-04, 11:06

Hmm, it sounds strange. 4GB as virtual video memory should more than enough for FFXI.

Does the debug layer say something useful when the lockup occur?

tumultTransmuted wrote:
I currently use 4095MB (increase the cap please? I have 11GB of VRAM ) but the issue happens much faster with 256 or 1024MB of VRAM.

But I can't. 4GB is the maximum for 32 bit. 😀

Reply 2 of 3, by tumultTransmuted

Posted on 2018-03-30, 02:49

tumultTransmuted Offline

Rank Newbie

Rank: Newbie
Posts: 2
Joined: 2018-03-15, 23:27

Dege wrote:
Hmm, it sounds strange. 4GB as virtual video memory should more than enough for FFXI.

Does the debug layer say something useful when the lockup occur?

I'm actually not even sure how to look at that!

Dege wrote:
But I can't. 4GB is the maximum for 32 bit. 😀

I was afraid that was going to be your answer. There's no way around that, like intercepting the calls and forcing them to use 64bit memory space? Can't say I know much about memory management on a base level-- barely functioning for basic programming here. ( I made a CLI calculator once 😜) I just recall modifying exes of certain programs (WoW.exe, looking at you) to accept 64 bit memory and they worked just fine like that.

Anyway, I upgraded my nVidia drivers and that issue disappeared. So it probably wasn't a problem with the program anyway! 🤣

Reply 3 of 3, by Dege

Posted on 2018-04-01, 09:36

Dege Offline

Rank l33t

Rank: l33t
Posts: 3064
Joined: 2003-09-04, 11:06

tumultTransmuted wrote:

Anyway, I upgraded my nVidia drivers and that issue disappeared. So it probably wasn't a problem with the program anyway! 🤣

It's great!!

tumultTransmuted wrote:
I was afraid that was going to be your answer. There's no way around that, like intercepting the calls and forcing them to use 64bit memory space? Can't say I know much about memory management on a base level-- barely functioning for basic programming here. ( I made a CLI calculator once 😜) I just recall modifying exes of certain programs (WoW.exe, looking at you) to accept 64 bit memory and they worked just fine like that.

I don't really know... dgVoodoo is 32 bit, using 32 bit version of D3D11.
But, since most of the resources are located on the GPU side, theoretically it could utilize more than 4GB from it.

Go to top of page Go to top of page

Back to dgVoodoo General