It seems that you're using an outdated browser. Some things may not work as they should (or don't work at all).
We suggest you upgrade newer and better browser like: Chrome, Firefox, Internet Explorer or Opera

×
Thought I'd just start a new thread here as opposed to adding to the one in which people, including me, talk about not being able to get it to run in Win10x64...

I'm running Win10x64 Insider's build 14271, with an 8-core AMD FX cpu and an AMD R9 380 4GB...running the latest 16.2 Crimson drivers.

1) (The following only applies for people with AMD GPUS!) Open your SERVICES up and find two of them: AMD External Events Utility & and AMD Fuel. STOP (capitals to emphasize) both services and then set each service property to disabled (so that when you reboot you will not have to repeat these steps until you change GPU drivers.) It does not appear that the Crimson drivers actually use either service any more--so there's no need for them. Indeed, most importantly, I discovered that as long as the services were running in memory they conflicted with the game and would cause it to crash immediately after trying to run it in Win10x64.

2) I'm running the current GOG version, which is the DVD version of the game

3) I'm using the FFDshow_rev4533_20140929_clsid.exe installer version of FFDshow (which may or may not be the latest available--it was the latest version I could find.)

4) After installing FFDshow to c:\program files x86 , you'll want to look into the directory and grab the FFDshow.ax file there and copy it to your main Overseer game directory--be sure and and rename the old version to ffdshow.axOLD first, however.

Also, during the FFDshow install be sure and select the MPEG2/Libavec option when asked--it's the only option in the install you need to select.

5) Set the Win10x64 compatibility options for "All Users" in the Overseer shortcut as follows:

a) Win98/ME mode
b) Run as Administrator

Leave all other settings blank


6)Use your GPU options for the game executable (overseer.exe) to run:

*max Multisampling or Supersampling mode your hardware can support (4x or 8x EQ, etc.)
*max Anisotropic filtering (16x, etc.)
*VSYNC always ON (very important for this game, I found.)
*Texture Filtering Quality: High(est)
*Surface Format Optimization: OFF
*Shader Cache: AMD Optimized
*Tessellation Mode: Use Application settings

*Vsync on is pretty much a requirement as the game does not like Vsync off, I found. These D3d rendering settings look great and make a noticeable improvement in the rendered portions of the game--Tex's office, Anastasi Ruins, Warehouse, etc. ad infintum--and of course don't interfere with the Xing Mpeg 2 playback at all.

7) Best sound option: turn 3d sound OFF in the game options (this might be required for stability, don't know.)

8) Best Music Option in the game by far: Install CoolSoft's Virtual Midi Synth to your system, and set up the Virtual Midi Synth to be your default in the CoolSoft VMSynth setup program for all of your Windows needs. When configuring Overseer, however, do not select the CoolSoft Virtual Midi Synth from within the game as your midi device--select instead Microsoft Midi Mapper. Even though you select for MMM, what will actually play through the game is the CoolSoft Virtual Midi Synth--and man does it sound great. At one time I had the gravis ultrasound emulation set up for Over seer and several other games--CoolSoft VirtualMidi Synth sounds--to me--so much better that it is now the default in all of my Midi games...!

That's it...This may or may not help someone who doesn't use an AMD GPU...don't know...but one thing I hate is when my games stop working for some reason...;) I won't rest until I right such wrongs!...;)
Post Script: This is really strange, but I just discovered that Overseer DVD is continuing to work fine even though the AMD External Events Utility service is running and resident in memory...! The other day I had to disable the service to get it to run...!

Post Script 2: May have figured it out...It appears that the AMD Fuel service--which only the Catalysts install--was the culprit, apparently. The Crimson 16.2 AMD drivers do not install the AMD Fuel service any longer...

So...if you have recently installed the 16.2 Crimsons on top of a recent Catalyst install, you'll need to stop and then permanently disable only the AMD Fuel service. However, if you uninstalled the Catalysts before installing the Crimson 16.2's, then only the AMD External Events Utility service will be installed and running, and you need not touch it as it does not interfere with the program in WIn10x64. Follow the rest of the original instructions and the game should run fine.
Post edited March 04, 2016 by waltc