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

×
Community
General discussionUpdate, run dark(45 posts)(45 posts)
(45 posts)
Pages:
1
2
3
This is my favourite topic
Posted June 20, 2016
avatar
misscrabtree456: I see now that this was the plan all along.
avatar
phaolo: ???
It's a well-known side effect of the doomsday device they're building, in gOg HQ.
Posted June 20, 2016
avatar
adaliabooks: Would the OP like to share some details of the games in question, so people might be able to help? [...]
And his system, if I may add.


avatar
adaliabooks: [...]

That screen shot certainly suggests something is not right, but I'm fairly certain it will be on your end and not something Gog os purposefully doing...
Is "Gog os" a new operating system that only the OP has the privilege of using? ;-P


Jokes aside - I'm fairly certain that if this was a widely spread issue caused by updates, the place would have been on fire already.
Posted June 20, 2016
avatar
tinyE: That's it! The T-Rex in Tomb Raider 1 was too hard to kill.
I'm done buying games here!
LOL.
Years ago, on the PS1, I encountered a gamebreaking bug in the Natla mines, instead >:|
Damn you Gog!


.
avatar
almabrds: It's a well-known side effect of the doomsday device they're building, in gOg HQ.
But.. weren't the Gogbears enough?
Post edited June 20, 2016 by phaolo
Posted June 20, 2016
avatar
tinyE: That's it! The T-Rex in Tomb Raider 1 was too hard to kill.
I'm done buying games here!
avatar
phaolo: LOL.
Years ago, on the PS1, I encountered a gamebreaking bug in the Natla mines, instead >:|
Damn you Gog!

.
avatar
almabrds: It's a well-known side effect of the doomsday device they're building, in gOg HQ.
avatar
phaolo: But.. weren't the Gogbears enough?
I only mentioned that because I'm currently on a major TR binge. :P
Posted June 20, 2016
avatar
almabrds: It's a well-known side effect of the doomsday device they're building, in gOg HQ.
avatar
phaolo: But.. weren't the Gogbears enough?
While their bites hurt a lot, we are talking about the whole world here. Can you imagine how many bears would need to be trained?
It would be like using bat bomb to destroy the world!
There are better options out there.
Posted June 20, 2016
avatar
phaolo: Years ago, on the PS1, I encountered a gamebreaking bug in the Natla mines, instead >:|
Damn you Gog!
Thanks Ogogma. /s
Posted June 21, 2016
avatar
almabrds: bat bomb
Bat bomb.. incredible.
What next, nuclear ants?
Posted June 21, 2016
avatar
Smannesman: I've seen a few topics where people seem to have the same issue, mostly when running fullscreen while windowed mode seems fine.
I was thinking about that, when I ctrl alt del to stop the game (black screen of death) on this last updated game there was a small window that looked fine. BTW, I did find the graphic adjustment file which I couldn't find before I posted and I got this game working like one other one. Now if Gog could give some support on Master of Magic which no setting works, I am a happy camper again.
Posted June 21, 2016
avatar
skeletonbow: You could actually contact GOG support as they do actually support the games. They may or may not be able to help you determine the cause of the problem but they'll certainly try - unlike pretty much every other game distributor online. They've helped me sort out many problems with games including:

- Blitzkrieg graphics problems
- The Nations, Alien Nations, Robin Hood blurry graphics (disable morphological filtering in ATI control panel)
- numerous other odd quirks, none of which are problems created by or caused by GOG whatsoever, and none of which they have any obligation to do anything about - but they do anyway.

Think about it, before online gaming where did people buy games? At Walmart, EB Games, Zellers, Target, other game retail stores. If those people had graphics problems with their games did they go apeshit angry at Walmart about it?

No, of course not. Why? Because Walmart didn't hire the programmers to write the game. Walmart just sells the games and if you have a problem with the game then contact the video game publisher or your video driver manufacturer - the two prime culprits of any video game problem other than problems specific to your own computer (ie: viruses, broken hardware, etc.)

How is this even a GOG problem at all? It isn't. But GOG's awesome support nonetheless supports the games to the best of their ability anyway even though they didn't write them in the first place. Something you wont get from any other video game retailer.

So stop shopping at GOG if you wish, but good luck getting any support from Steam, Origin, Uplay, or any other retailer for your games. It's always fun to have someone to blame whether they're responsible or not though isn't it.
I did contact Gog and sent them a screen shot and file of my computer stats. I figured forums are your best shot. As you noted good luck getting tech support. I know all about Steam, their idea of support is "we got your money, sucks to be you." There is a game (No Mans Sky) coming out on both Gog and Steam, I plan on buying it on Gog. We'll see how this works out. The games were working fine on the same machine, the only thing I can think of is my graphics card is always updating. Which I don't like, if it isn't broke don't fix it type of thing.
avatar
adaliabooks: Would the OP like to share some details of the games in question, so people might be able to help?

That screen shot certainly suggests something is not right, but I'm fairly certain it will be on your end and not something Gog os purposefully doing...
The reason I went off like that was I updated Colonization and it went dark, making it the 3rd game from Gog to this recently. I got one fixed by running it in openGL, the other Master of Magic nothing works, this is a game that worked fine. I have since gotten Colonization to work. Went I posted, it was a WTF are you doing to the games type of thing since they were working fine.
Post edited June 21, 2016 by misscrabtree456
Posted June 21, 2016
avatar
noir_7: If this was a thread requesting help he would have answered the questions if the first few posters about his system and details.
Instead it appears to be some kinda rant.
Here is some of what I sent Gog:
------------------
System Information
------------------
Time of this report: 6/19/2016, 22:07:50
Machine name:
Operating System: Windows 7 Professional 64-bit (6.1, Build 7601) Service Pack 1 (7601.win7sp1_gdr.150715-0600)
Language: English (Regional Setting: English)
System Manufacturer: ASUS
System Model: All Series
BIOS: BIOS Date: 05/15/15 09:49:33 Ver: 05.06.05
Processor: Intel(R) Core(TM) i7-5820K CPU @ 3.30GHz (12 CPUs), ~3.3GHz
Memory: 32768MB RAM
Available OS Memory: 32666MB RAM
Page File: 5024MB used, 60307MB available
Windows Dir: C:\Windows
DirectX Version: DirectX 11
DX Setup Parameters: Not found
User DPI Setting: Using System DPI
System DPI Setting: 96 DPI (100 percent)
DWM DPI Scaling: Disabled
DxDiag Version: 6.01.7601.17514 32bit Unicode

------------
DxDiag Notes
------------
Display Tab 1: No problems found.
Sound Tab 1: No problems found.
Sound Tab 2: No problems found.
Input Tab: No problems found.

--------------------
DirectX Debug Levels
--------------------
Direct3D: 0/4 (retail)
DirectDraw: 0/4 (retail)
DirectInput: 0/5 (retail)
DirectMusic: 0/5 (retail)
DirectPlay: 0/9 (retail)
DirectSound: 0/5 (retail)
DirectShow: 0/6 (retail)

---------------
Display Devices
---------------
Card name: NVIDIA GeForce GTX 960
Manufacturer: NVIDIA
Chip type: GeForce GTX 960
DAC type: Integrated RAMDAC
Device Key: Enum\PCI\VEN_10DE&DEV_1401&SUBSYS_29603842&REV_A1
Display Memory: 4017 MB
Dedicated Memory: 1969 MB
Shared Memory: 2048 MB
Current Mode: 1920 x 1200 (32 bit) (59Hz)
Monitor Name: LG W2452(Digital)
Monitor Model: W2452
Monitor Id: GSM5694
Native Mode: 1920 x 1200(p) (59.950Hz)
Output Type: DVI
Driver Name: nvd3dumx.dll,nvwgf2umx.dll,nvwgf2umx.dll,nvd3dum,nvwgf2um,nvwgf2um
Driver File Version: 10.18.0013.6839 (English)
Driver Version: 10.18.13.6839
DDI Version: 11
Driver Model: WDDM 1.1
Driver Attributes: Final Retail
Driver Date/Size: 6/3/2016 03:38:10, 17290416 bytes
WHQL Logo'd: Yes
WHQL Date Stamp:
Device Identifier: {D7B71E3E-5741-11CF-4541-6D091CC2C735}
Vendor ID: 0x10DE
Device ID: 0x1401
SubSys ID: 0x29603842
Revision ID: 0x00A1
Driver Strong Name: oem95.inf:NVIDIA_Devices.NTamd64.6.1:Section032:10.18.13.6839:pci\ven_10de&dev_1401
Rank Of Driver: 00E62001
Video Accel:
Deinterlace Caps: {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch
{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch
{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch
{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch
{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
D3D9 Overlay: Supported
DXVA-HD: Supported
DDraw Status: Enabled
D3D Status: Enabled
AGP Status: Enabled
Posted June 21, 2016
avatar
skeletonbow:
avatar
misscrabtree456: I did contact Gog and sent them a screen shot and file of my computer stats. I figured forums are your best shot. As you noted good luck getting tech support. I know all about Steam, their idea of support is "we got your money, sucks to be you." There is a game (No Mans Sky) coming out on both Gog and Steam, I plan on buying it on Gog. We'll see how this works out. The games were working fine on the same machine, the only thing I can think of is my graphics card is always updating. Which I don't like, if it isn't broke don't fix it type of thing.
It's probably overly obvious, but a game being on the extreme dark side of things would have me suspecting that the gamma correction is misconfigured in the game's graphics settings or in the video driver control panel (although that's less likely if it only occurs with one game). There could potentially be other video driver settings that could cause malfunction with some video games but not others also. I learned that the hard way, as I had morphological filtering enabled in the AMD control center by default and it ended up causing the problems in the games I mentioned in my last post. I've had driver level anti-aliasing cause problems in some games as well as other driver level settings causing issues too. I've also had things that dynamically change the CPU frequency such as AMD's Turbocore and Cool n Quiet technologies cause some games to malfunction. Some of these things are extremely difficult to figure out the root cause, either as an end user, or even as tech support at a game company or retailer. In my cases, they were all caused ultimately due to user error in turning those settings on by default if I'm not mistaken. :)

Definitely check the gamma correction setting on the game even if you've never touched it personally (assuming it has such a setting). I just reread your original post and you're saying it's happening with more than one game so I'd definitely be checking your video driver settings for sure. You mention one was fixed by using OpenGL. Was it video playback that was dark, or the whole game? Video playback is normally done using the video overlay, but a lot of software these days can render video using OpenGL/DirectX instead of video overlay. There are graphic card settings for the video overlay surface that do not apply to OpenGL/DX video for example, so in theory one could have misconfigured video overlay in their control panel that causes dark or off colour video, but if they choose OpenGL/DX video it will bypass that and work properly. There could be a number of other cases like this as well.

One further thing I could suggest is to save a backup copy of your video driver configuration if possible, then restore it to factory defaults as if you just installed the driver brand new and have not reconfigured anything, see if the games still have problems or not. If not, then possibly some setting that was previously changed to a non-default may be the cause of the problems. That can be due to bugs in games too, but they're generally something that either can not or wont likely be fixed if they are older games that no longer get development and patching. Sometimes the only fix is a workaround.

Anyhow, hope this helps.
Posted June 21, 2016
avatar
misscrabtree456: The games were working fine on the same machine, the only thing I can think of is my graphics card is always updating. Which I don't like, if it isn't broke don't fix it type of thing.
From the description in the OP and the screenshot, it seems likely to me that it's a driver issue. Graphics drivers are, unfortunately, very much a hit and miss thing. Like you, I tend to prefer not to touch them if nothing's broken, but I think this is a case where I would be looking at them as suspect.

A quick google brought up this thread on steam which might be worth checking to see if it gives a solution for you.
Posted June 21, 2016
avatar
misscrabtree456: The reason I went off like that was I updated Colonization and it went dark, making it the 3rd game from Gog to this recently.
What update? You mean this game? There isn't one. Try running the game without Galaxy running at all (not just in the tray). GOG's support is all right. If a bit slower than ideal sometimes.
Someone else had a similar issue with one of those screen darkening utilities for using the computer at night. Forget what it's called. Shutting it down "fixed" it.
Have you tried just rebooting the PC yet?
Posted June 21, 2016
avatar
misscrabtree456: The reason I went off like that was I updated Colonization and it went dark, making it the 3rd game from Gog to this recently.
avatar
Gydion: What update? You mean this game? There isn't one. Try running the game without Galaxy running at all (not just in the tray). GOG's support is all right. If a bit slower than ideal sometimes.
Someone else had a similar issue with one of those screen darkening utilities for using the computer at night. Forget what it's called. Shutting it down "fixed" it.
Have you tried just rebooting the PC yet?
That was one of the ones that I fixed using a different graphics mode. But it was the one that set off the post since I didn't find the graphic mode file and thought it was not in the update package. I am not running Galaxy, I think Master of Magic is just a lost cause at this point, it has no setting of it's own and the graphics card settings don't do much to change things.
avatar
misscrabtree456: I did contact Gog and sent them a screen shot and file of my computer stats. I figured forums are your best shot. As you noted good luck getting tech support. I know all about Steam, their idea of support is "we got your money, sucks to be you." There is a game (No Mans Sky) coming out on both Gog and Steam, I plan on buying it on Gog. We'll see how this works out. The games were working fine on the same machine, the only thing I can think of is my graphics card is always updating. Which I don't like, if it isn't broke don't fix it type of thing.
avatar
skeletonbow: It's probably overly obvious, but a game being on the extreme dark side of things would have me suspecting that the gamma correction is misconfigured in the game's graphics settings or in the video driver control panel (although that's less likely if it only occurs with one game). There could potentially be other video driver settings that could cause malfunction with some video games but not others also. I learned that the hard way, as I had morphological filtering enabled in the AMD control center by default and it ended up causing the problems in the games I mentioned in my last post. I've had driver level anti-aliasing cause problems in some games as well as other driver level settings causing issues too. I've also had things that dynamically change the CPU frequency such as AMD's Turbocore and Cool n Quiet technologies cause some games to malfunction. Some of these things are extremely difficult to figure out the root cause, either as an end user, or even as tech support at a game company or retailer. In my cases, they were all caused ultimately due to user error in turning those settings on by default if I'm not mistaken. :)

Definitely check the gamma correction setting on the game even if you've never touched it personally (assuming it has such a setting). I just reread your original post and you're saying it's happening with more than one game so I'd definitely be checking your video driver settings for sure. You mention one was fixed by using OpenGL. Was it video playback that was dark, or the whole game? Video playback is normally done using the video overlay, but a lot of software these days can render video using OpenGL/DirectX instead of video overlay. There are graphic card settings for the video overlay surface that do not apply to OpenGL/DX video for example, so in theory one could have misconfigured video overlay in their control panel that causes dark or off colour video, but if they choose OpenGL/DX video it will bypass that and work properly. There could be a number of other cases like this as well.

One further thing I could suggest is to save a backup copy of your video driver configuration if possible, then restore it to factory defaults as if you just installed the driver brand new and have not reconfigured anything, see if the games still have problems or not. If not, then possibly some setting that was previously changed to a non-default may be the cause of the problems. That can be due to bugs in games too, but they're generally something that either can not or wont likely be fixed if they are older games that no longer get development and patching. Sometimes the only fix is a workaround.

Anyhow, hope this helps.
Thanks, at this point I have tried just about everything. The game doesn't have any options itself, and the graphics card changes made big changes to everything but the game. The idea of going back the driver 1.00 sounds like it may work though.
Post edited June 21, 2016 by misscrabtree456
Posted June 21, 2016
avatar
misscrabtree456: The reason I went off like that was I updated Colonization and it went dark, making it the 3rd game from Gog to this recently.
avatar
Gydion: What update? You mean this game? There isn't one. Try running the game without Galaxy running at all (not just in the tray). GOG's support is all right. If a bit slower than ideal sometimes.
Someone else had a similar issue with one of those screen darkening utilities for using the computer at night. Forget what it's called. Shutting it down "fixed" it.
Have you tried just rebooting the PC yet?
Ah yes, good call. I use one called "F.lux" which I often have to disable for games and movies and similar.
Pages:
1
2
3
This is my favourite topic
Community
General discussionUpdate, run dark(45 posts)(45 posts)
(45 posts)