Hi and greeting everybody,

so I was just starting to play LOL3 (formerly having played both 1&2, great games, and I thought I'd check out the 3rd for once) and noticed that the framerate seemes to be capped at 30/31fps.

I tried tinkering with Nglide and my AMD settings, and also looked into the options but there is no combination of settings I tried which could remove this cap.

I remember playing LOL2 and having the same problem, but after enabling Hardware acceleration and using dxwnd (for windowed mode) it ran smoothly at 40-60 fps.
Since LOL3 seemed to use bascially the same Westwood-Engine I figured I just had to do the exact thing for LOL3, but alas in LOL3s options there is the whole Acceleration part in options.ini missing:

for example in LOL2 there is a section like this:
[Acceleration]
Acceleration_VGA_Automap=No
Acceleration_VGA_Movies=No
Acceleration_Use4444=No
Acceleration_Filtering=On
Acceleration_Card=Primary
Acceleration_Toggle=On

but in LOL3 there is only (under "Video"):
Acceleration_Filtering=On
All other options from LOL2 are missing. I tried using them anyway (trial and error-style) but it didn't net me any results either.

And I'm even unsure whether this acceleration is the "limiter" anyways, since it is capped with either Voodoo or Direct3D in LOL3 (I can chosse between those with my AMD card it seems, even at max resoultion).

So I was wondering if there is any way to remove the frame-limiter, or is this hardcoded?
The weird thing is, I saw a (german) Let's Play of LOL3 and it ran buttersmooth, so it seems to be possible. But how? Maybe someone else has an idea, or if it is hardcoded somehow. Because even Kikoskias Let's Play of LOL3 (from 2009) seems to be running at 30fps.

I love tinkering with old games on modern hardware (though I still use Win7 64bit), but for now I am at a loss what to try next. Using DXWND doesn't work either, because LOL3 will always go into fullscreen mode, even if I set DXWND up to play in windowed mode.

Little Update:
Alright, I at least got DXWND to run with LOL3, so that it can be run in windowed mode.
It still runs at 31fps, even in windowed mode.
It wasn't my skill though, there was a fellow named gho who provided the configuration, over at sourceforge. Just import his config into dxwnd & change the paths (if necessary) and voila! Works!

search for "Unable to run Lands of Lore 3 in a Window " (I can't post links)

Still no luck with the framerate though. I searched through LOL3.DAT but only found some "fps" entries, which I changed somewhat but without any result regarding the framerate.

Lots of games back then had capped framerates around 30. So not unusual if that’s the case. I think Doom was at 35 and Dark Forces 25. Rather janky when you are used to today’s framerates. You can get somewhat accustomed to it if you keep playing.

The screen redraw rate is likely tied in to the game-state update, so if increased could make the game unplayable.

Hi, how do got i work with DXWnd?! I tried it and the game wont start, do you have a config file og DXWnd?!

There's a couple things you need to do.
Import "Lands of Lore 3 (GOG).dxw" into DXWnd from DXWnd's export folder
Modify the "Path" of the config to your GOG install path's LOL3.DAT

*Now I haven't been able to get DXWnd to run LOL3.exe with the launch arguments, so I did a work around and created a .bat file that launches the game with the correct arguments.
So my lol3.bat file contains: Create your own version of lol3.bat that points to your GOG Lands of Lore 3 install folder
Modify "Launch" in the DXWnd config to point to the newly created lol3.bat

Having typed all that, I actually prefer just running it with dgVoodoo2 in glide mode at 1024x768. No DXWnd needed. Though if you want to run it in a Window, you'll need DXWnd

EDIT: Instead of creating the .bat file the new way of properly launching lol3.exe with arguments is to have "Launch" pointed to your LOL3.exe
e.g. "D:\Games\GOG\Lands of Lore 3 DxWnd\LOL3.EXE"
and then in the "Hook" tab under ""Command line:" put the following Note: You can also switch -NO_ASSERTS for -WEAK. This will remove the error on the loading screen and allow quicker loading. I'm unsure if it affects graphical quality though.