VOGONS

Common searches


Bugdom

Topic actions

First post, by pseudo3d

User metadata
Rank Newbie
Rank
Newbie

Recently, I acquired the old Pangea game Bugdom to play on my PC (it's been years since I played the Mac version, which is now freeware). But after I installed it I ran into some problems.

It has the first two static logos come up (if a bit stretched)
Either before or during the Pangea song (the logo never appears), I get an error: "Q3View_StartRendering Failed!" and then "Q3Style_Submit Failed"

Apparently, the problem is a very old one, this thread mentions that the problem was assumed to be an out of date OpenGL driver, but that wasn't it.

I tried running it in Windows 95 compatibility mode as administrator with 640 x 480 resolution, and also by dropping my monitor's color depth to 16 bit (default is 32).

I also tried using Compatibility Administrator to sniff out a problem. (Replaced user name with XXXX)
07/25/2018 11:26:05 CorrectFilePaths 1 - CreateFileW corrected path:
c:/windows/atioes.conf
c:\windows\atioes.conf

07/25/2018 11:26:05 CorrectFilePaths 1 - CreateFileW corrected path:
c:/windows/atiapfxxES.blb
c:\windows\atiapfxxES.blb

07/25/2018 11:26:05 CorrectFilePaths 1 - CreateFileW corrected path:
c:/windows/atiogl_perfcount.conf
c:\windows\atiogl_perfcount.conf

07/25/2018 11:26:05 CorrectFilePaths 1 - CreateFileW corrected path:
C:\Users\XXXX\AppData\Local/AMD/GLCache/111d9af697ca9242_f8e70ea2391a130e_11.idx
C:\Users\XXXX\AppData\Local\AMD\GLCache\111d9af697ca9242_f8e70ea2391a130e_11.idx

07/25/2018 11:26:05 CorrectFilePaths 1 - CreateFileW corrected path:
C:\Users\XXXX\AppData\Local/AMD/GLCache/111d9af697ca9242_f8e70ea2391a130e_11.bin
C:\Users\XXXX\AppData\Local\AMD\GLCache\111d9af697ca9242_f8e70ea2391a130e_11.bin

07/25/2018 11:26:11 IgnoreScheduler 3 - [SetThreadPriority] Forcing thread priority to normal.
07/25/2018 11:26:11 IgnoreScheduler 3 - [SetThreadPriority] Forcing thread priority to normal.
07/25/2018 11:26:11 IgnoreScheduler 3 - [SetThreadPriority] Forcing thread priority to normal.
07/25/2018 11:26:11 IgnoreScheduler 3 - [SetThreadPriority] Forcing thread priority to normal.
07/25/2018 11:26:11 IgnoreScheduler 3 - [SetThreadPriority] Forcing thread priority to normal.
07/25/2018 11:26:11 IgnoreScheduler 3 - [SetThreadPriority] Forcing thread priority to normal.
07/25/2018 11:26:18 IgnoreScheduler 3 - [SetThreadPriority] Forcing thread priority to normal.
07/25/2018 11:26:18 EmulateUSER 1 - [ChangeDisplaySettingsA] Changing flags to CDS_FULLSCREEN.
07/25/2018 11:26:18 IgnoreScheduler 3 - [SetThreadPriority] Forcing thread priority to normal.
07/25/2018 11:26:19 IgnoreScheduler 3 - [SetThreadPriority] Forcing thread priority to normal.
07/25/2018 11:26:19 IgnoreScheduler 3 - [SetThreadPriority] Forcing thread priority to normal.
07/25/2018 11:26:19 IgnoreScheduler 3 - [SetThreadPriority] Forcing thread priority to normal.
07/25/2018 11:26:19 IgnoreScheduler 3 - [SetThreadPriority] Forcing thread priority to normal.
07/25/2018 11:26:19 IgnoreScheduler 3 - [SetThreadPriority] Forcing thread priority to normal.
07/25/2018 11:26:19 IgnoreScheduler 3 - [SetThreadPriority] Forcing thread priority to normal.
07/25/2018 11:26:19 IgnoreScheduler 3 - [SetThreadPriority] Forcing thread priority to normal.
07/25/2018 11:26:19 IgnoreScheduler 3 - [SetThreadPriority] Forcing thread priority to normal.
07/25/2018 11:26:19 IgnoreScheduler 3 - [SetThreadPriority] Forcing thread priority to normal.
07/25/2018 11:26:19 IgnoreScheduler 3 - [SetThreadPriority] Forcing thread priority to normal.
07/25/2018 11:26:19 IgnoreScheduler 3 - [SetThreadPriority] Forcing thread priority to normal.

As you can see, I use AMD instead of Nvidia (mistake, I know) and AMD's OpenGL drivers are known to be out of date, but not out of date for 17-year-old titles. As a last resort, I fiddled around with my graphics card's settings for that game but no dice.

Reply 2 of 6, by pseudo3d

User metadata
Rank Newbie
Rank
Newbie
Firtasik wrote:

Thanks! It now starts up and can be run full screen (stretched). I was looking into Quesa as well to try to patch the system call. The problem now is that the player character tends to follow the mouse for movement and constantly moves in one direction, spinning around constantly, with trying to get the right direction a largely futile attempt. (This is not present in menus, where the mouse behaves normally). I suspect that there may be a problem involving mouse emulation, causing it to get the wrong signal in moving around (this could probably fixed by trial and error). In any case, it works but it seems...buggy. 😎

Reply 4 of 6, by ZellSF

User metadata
Rank l33t
Rank
l33t
pseudo3d wrote:
Firtasik wrote:

Thanks! It now starts up and can be run full screen (stretched). I was looking into Quesa as well to try to patch the system call. The problem now is that the player character tends to follow the mouse for movement and constantly moves in one direction, spinning around constantly, with trying to get the right direction a largely futile attempt. (This is not present in menus, where the mouse behaves normally). I suspect that there may be a problem involving mouse emulation, causing it to get the wrong signal in moving around (this could probably fixed by trial and error). In any case, it works but it seems...buggy. 😎

You should be able to fix that by changing options in DxWnd's input tab.

I had no idea DxWnd could force rendering resolution for OpenGL games:

Bugdom 2018-07-26 17-30-14-58.jpg
Filename
Bugdom 2018-07-26 17-30-14-58.jpg
File size
409.18 KiB
Views
1372 views
File license
Fair use/fair dealing exception

Which is great news to me since options to force rendering resolution on OpenGL games are really lacking. Then again all the other OpenGL games I've tried previously didn't like DxWnd 🙁

Bugdom also appears to run with GLDirect, but fog doesn't work.

Reply 5 of 6, by stranno

User metadata
Rank Member
Rank
Member

ZellSF, i'm trying to run it in fullscreen mode but i had no luck so far. Using Fullscreen only flag launches the game in a Window, ALT+ENTER works but it is still a window without the frame. Run in a Window flag doesnt seem to work better and i guess it is not needed at all since it is hooked properly.

I didnt know DXWND had an option to render custom resolutions. Is that the "custom resolution" flag?

Reply 6 of 6, by ZellSF

User metadata
Rank l33t
Rank
l33t

I don't bother with DxWnd's fullscreen mode (I've never had any good results with it), I just set "Position" to "Desktop" and then change my desktop resolution to whatever resolution I need. DxWnd seems to force the rendering resolution for Bugdom to its window size by default.