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 discussionGOG GALAXY BETA(6179 posts) (6179 posts) 
(6179 posts) 
Pages:
1
100
108
109
110
111
112
300
400
412
This is my favourite topic
Posted May 06, 2015
high rated
!!! PLEASE READ BEFORE POSTING !!!

== BUG REPORTING ==

Please use: http://mantis.gog.com and include
1. steps to reproduce the bug (if possible)
2. screenshot or movie showing the bug (if possible)
3. Galaxy Client logs (see below)

Where can I find Galaxy logs on my computer?
On Windows 7 or later: C:\ProgramData\GOG.com\Galaxy\Logs
On Mac OS X: /Users/Shared/GOG.com/Galaxy/Logs

== FEATURE SUGGESTIONS ==

Please use: http://www.gog.com/wishlist/galaxy. For feature suggestions and votes on them please try do explain how Galaxy and its users will really benefit from it.

== IMPORT ALREADY INSTALLED GAMES TO GALAXY ==

1. For GOG games installed using installers from the last few months (so called Galaxy-compatible installers)
Click the Galaxy logo button on top of the sidebar and select "scan and import folders" - it will find all compatible games within that folder and add them to the Client.

2. For remaining GOG game INSTALLATIONS
Find the game in the Library (click on the image of the game), then click the More button and select "Manage Installation" -> "Import folder" and point the folder selector into the folder where that game is installed.

== KNOWN ISSUES ==
- throttling max download speed is not yet possible
- notifications related to incoming chat messages and friend requests does not always disappear instantly when consumed and may require reloading Store page
- games imported from existing installations will auto-update once, even if updating is disabled
- Moving Galaxy from /Applications on Mac OS X will stop the app from working
- Galaxy cannot be launched by other users on the same computer
Post edited October 03, 2016 by Liosan
Posted July 03, 2015
high rated
Hi Everyone,

Below you can find the changelog of GOG Galaxy.

Changelog 1.1.15 (September 7th, 2016):
Changes / Improvements:
• Added Wallet button in dropdown menu under user's avatar
• Performance improvements on UI speed and a little on CPU usage
• Enabled copying text in Galaxy forums
• History will now remember only the 100 most recent pages in history
Bugfixes:
• Fix for "Disk access problem" bug, which broke installation and updates of games. (Bug happened on Windows only, but general mechanism is better on OS X as well)
• Fix for Verify/Repair, which did not work in some scenarios (The above bug for example)
• Fix for "Server problem" while downloading backup installers or other goodies. They will now work, even if temporary download folder is same as destination folder
• Fixed situations in which Store page sometimes did not load properly after waking up computer

Changelog 1.1.16 (September 19th, 2016):
Improvements:
• Galaxy now supports H.264 codecs
• Much better handling of paying using third party processors (PayPal, paysafecard etc.)
• Friends and chat window now scale with the system scaling factor
• New and prettier GOG Eula will be used in games
• Better handling of loading timeouts

Bugfixes:
• "INSTALLED" label will appear all pages of the library now
• Fixed a bug with game time tracking for some games. Galaxy will now register more than one minute:)
• Fixed a bug in which Galaxy in rare cases could not be able to update the game (bug rather existed in rollbacks)
• Galaxy will no longer show a little bit of bare code upon launching
• Fixed blurred images in sidebar expanded list mode

Changelog 1.1.17(hotfix September 20th, 2016):
• Fixed crashes and 'Disk Access Problem' caused by updating Galaxy from 1.1.12 (and earlier versions) to 1.1.16

Changelog 1.1.18 (October 19th, 2016):
Improvements:
• More accurate game time tracking mechanism
• Improved mechanism showing current online status between friends

Bugfixes:
• Fixed a bug which caused Galaxy to stop tracking game time

Changelog 1.1.19 (October 25th, 2016):
Improvements:
• We have removed download size from Galaxy updater. It showed faulty data, as Galaxy Updater doesn't download > 100mb each time and only downloads differences. It will come back in nearest future, when it will show correct data:)
• The first check for game updates will be done 15s after Galaxy starts, instead of 5 minutes.
• OSX: Improved mechanism responsible for removing old files left by Galaxy updates
• OSX: Improved the way Galaxy handles installing games into protected locations like /Applications; you will receive a password prompt about a "Helper tool" installation

Bugfixes:
• Fixed "Essential components missing" error which sometimes appeared after fresh installation
• Fixed a situation where failure in Updater could lead to Galaxy not being able to launch
• Fixed self-update on OSX to properly delete leftover files
• Fixed friends window losing functionality after network loss and reconnect
• Fixed blurry Windows 10 Galaxy tray icon
• Galaxy will remember maximised window status

Changelog 1.1.20(November 2nd, 2016)
Bugfixes:
• Fixed installing XNA4 and other msi-based dependencies.
• Store page won't be reloaded twice upon logging in

Changelog: 1.1.21 (November 17th, 2016)
Improvements / changes:
• Added "with preview updates" suffix to Galaxy window title
• Small optimizations with memory and Galaxy loading time
• Small improvements with updater, it should fail less

Bugfixes:
• Fixed a bug with Galaxy refreshing pages
• Fixed occasional crashes

Changelog 1.1.22 (November 22nd, 2016)
Bugfixes:
• Galaxy will no longer freeze when downloading a game update and checking another game in library
• Galaxy should crash even less now:)

Changelog 1.1.23 (November 28th, 2016)
Bugfixes:
• Galaxy will be now able to reconnect to internet correctly, if computer was put to sleep and then woken up without (initially) Internet connection
• Downloading of games/updates should have less impact on starting other installations

Changelog 1.1.24(December 6th, 2016)
Bugfixes:
• Downloading an installer with Galaxy and using it to install the game should not result in redownloading the whole game again
• Updater should no longer report over 100% progress on download

Adjustments:
• Increased timeout for failures during sign in
• Increased timeout for "Loading Timeout"

Changelog 1.1.25 (December 20th, 2016)
Bugfixes:
• Fixed a crash when trying to install certain games (Game affected was 1979 Revolution: Black Friday).

Changelog 1.1.26 (December 23rd, 2016, Preview only)
Changes:
• Introduced new downloading mechanism

Changelog 1.1.27 (January 26th, 2017, Preview)
Bugfixes:
• Aborting or pausing downloads will be smoother (They will stop faster)
• Pausing downloads will no longer cause memory usage to go super high

Changelog 1.1.27 (January 31th, 2017)
Changes:
• Introduced new downloading mechanism
Bugfixes:
• Aborting or pausing downloads will be smoother (They will stop faster)
• Pausing downloads will no longer cause memory usage to go super high

Changelog 1.1.28 (March 10th, 2017)
Changes / Improvements:
- Better support for differential patches. They are now seperate depending on game's language and system bitness
- Italian & Japanese partial support + more Spanish translations
- Improved checking for new available updates of the games
- We'll sort available DLCs alphabetically
Bugfixes:
- Fixed a crash when Galaxy doesn't have permissions to the logs directory
- Fixed showing empty grey page after a while of inactivity
- Fixed infinite spinner after going to support page
- Fixed displaying of prices in cart when they were over 999 (Bug caused by a comma in the price)
- MacOS: Popup windows (for example chat) will no longer open as a tab but as a separate window instead
- MacOS: Fixed memory leak (~30MB upon GOG Galaxy launch)
- MacOS: Fixed memory leak while playing a game

Changelog 1.1.29 (March 14nd, 2017)
Changes:
- Changes in downloading mechanism, which allows for better control over download's flow
Bugfixes:
- Fixed displaying progress of differential patches (It did not display the "Extracting" status)

Changelog 1.1.30 (March 16th, 2017)
Bugfixes:
- Fixed a crash within games downloading mechanism

== PREVIEW UPDATES* ===

HOW TO ENABLE PREVIEWS?
Go to your Galaxy settings and check the option to receive preview updates.

HOW TO DISABLE PREVIEW?
- Uninstall Galaxy
- Download current installer from gog.com/galaxy
- Install Galaxy
- Import your games

Changelog 1.2.0 (March 22nd, 2017)
Changes and improvements:
- Cloud saves backup and syncing (supported games only)
- Screenshot capture with F12 (supported games only)
- In-game overlay with FPS counter and notifications (supported games only)
- Greatly improved chat, also in overlay
- Ability to enable or disable achievements, game time tracking, auto-updating games and more
- Desktop and in-game notifications system
- Ability to set bandwidth limit and scheduler
- New settings window
- Rarity information in achievements
- Abort button next to installation status
- Only one Galaxy Updater window will be shown in most cases
- GOG Galaxy updates will be downloaded in the background
- Games are now downloaded directly to their install directory, instead of a temporary location
- Galaxy changelog is displayed in Galaxy

Bugfixes:
- Fixed game time tracking issues
- Initial size of Galaxy Client window will respect Windows scaling
- Improved Windows 10 Galaxy tray icon
- Fixed a bug which caused Galaxy to redownload whole data in case of a failure of installation/update
- Thumbnail highlighting in media gallery now works properly
- Decreased client's network and CPU usage (especially for a lot of games)
- MacOS: Fixed situation when Galaxy Client could downloading due to App Nap
- MacOS: Fixed crash when logging out with "New post" popup open
- MacOS: Fixed game processes not being properly cleaned up after exiting
Post edited March 22, 2017 by TheTomasz
Posted March 26, 2016
high rated
For everyone who has a problem with missing api-ms-crt dlls in Client's versions post 1.1.5:
Please install one of those windows update: https://support.microsoft.com/en-us/kb/2999226 https://support.microsoft.com/en-us/kb/3118401
You may need to update Windows to meet the requirements for these:
For Windows 8.1 and for Windows Server 2012: https://support.microsoft.com/en-us/kb/2919355
For Windows 7 and for Windows Server 2008 R2: https://support.microsoft.com/en-us/kb/976932

You can also try reinstalling Microsoft Visual C++ Redistributables 2015 (x86) if you meet above requirements.
Available here: https://www.microsoft.com/en-us/download/details.aspx?id=48145

If above instructions doesn't work for you, create a separate issue on mantis.gog.com and we'll try to help you individually.

Please note that this solution only helps with the missing api-ms-crt dlls.


========================================================================================


Answering this question: Why 1.1 doesn't work after updating to 1.2?

This is happening probably due to incompatible database from version 1.2, please delete this folder:
%ALLUSERSPROFILE%\GOG.com\Galaxy\storage
usually
C:\ProgramData\GOG.com\storage\

Then you'll have to use scan&import (menu under the top Galaxy logo) function to see your games back in Galaxy Client.
Attachments:
programsandfeatu.png (143 Kb)
Post edited March 27, 2017 by TheTomasz
Posted June 10, 2015
avatar
MorningStar33: How can issue #1984 (reported May 6th) be duplicate of issue #2822 (reported May 22nd)? Back to the future?
Seriously, what the fuck GOG?
The two bug reports do indeed seem to describe the same issue. But i did not look into Galaxy's code, so i don't know. You seem to know much better. So, how exactly do you know it is not the same bug causing the trouble in both cases?
Post edited June 10, 2015 by elgonzo
Posted June 10, 2015
avatar
MorningStar33: How can issue #1984 (reported May 6th) be duplicate of issue #2822 (reported May 22nd)? Back to the future?
Seriously, what the fuck GOG?
avatar
elgonzo: The two bug reports do indeed seem to describe the same issue. But i did not look into Galaxy's code, so i don't know. You seem to know much better. So, how exactly do you know it is not the same bug causing the trouble in both cases?
He is not disputing that. He is pointing out that if anything #2822 is the duplicate.
Posted June 10, 2015
avatar
elgonzo: The two bug reports do indeed seem to describe the same issue. But i did not look into Galaxy's code, so i don't know. You seem to know much better. So, how exactly do you know it is not the same bug causing the trouble in both cases?
avatar
Kristian: He is not disputing that. He is pointing out that if anything #2822 is the duplicate.
Seriously i am not getting what you or supposedly MorningStar33 try to say here. Not at all... :)

What is the purpose of marking a bug as a duplicate? To answer that you have to know that eventually a bug report (i.e. issue ID) is assigned to a developer who will be responsible for fixing that particular bug. If you have two or more reports describing the same issue or which have been identified to be caused by the same underlying bug, then it makes sense to treat these two reports as the same identical issue, assigning it only once to a developer to fix.

If you have two bug reports A and B which are duplicate, it does not matter whether A is marked a duplicate of B, or whether B is marked a duplicate of A. Whether a developer gets issue A assigned (with B being a duplicate of A), or whether the developer gets B assigned (with A being duplicate of B) is irrelevant, because the result is the same: The developer would in both cases work on exactly the same bug and hopefully fix it. In the concrete case brought up here, the developer would get issue 2822 assigned. Looking up issue 2822, the developer is presented with a list with all other bug reports about the same issue (and which also allows him to easily access the specific information, comments and attachments of each of these reports).

Knowing this, it beggars belief that one would make an argument such as there being a relevant distinction between "issue A is duplicate of B" and "issue B is duplicate of A"...
Post edited June 10, 2015 by elgonzo
Posted June 10, 2015
I wasn't trying to claim any practical importance to the "issue" only explain what it is.
Posted June 10, 2015
avatar
Kristian: I wasn't trying to claim any practical importance to the "issue" only explain what it is.
Okay, well. I guess i interpreted too much into your comment then.
If you will excuse me, i need some hot coffee... ;)
Post edited June 10, 2015 by elgonzo
Posted June 10, 2015
avatar
elgonzo: If you have two bug reports A and B which are duplicate, it does not matter whether A is marked a duplicate of B, or whether B is marked a duplicate of A.
Maybe in a situation when reports haven't been checked yet, altough it still wouldn't make much sense. But that's not the case here; both bugs were confirmed and a person was assigned for them.
Posted June 10, 2015
avatar
lostanddamned: 4th times i ask. not asking for help anymore. just gets ignored again jsut want to know
ALL I GET IS A BLANK WHITE WINDOW WHEN STARTING GALAXY. KNOWN PROBLEM OR NOT?
avatar
BKGaming: Known issue:

http://www.gog.com/support/support_view/bgog_galaxy_troubleshooting_and_useful_informationb
thank you a lot.
didn't help, already tried that by myself. but at leadt i know it's known
Post edited June 10, 2015 by lostanddamned
Posted June 10, 2015
avatar
Blackdrazon: Sometimes this fixes if you click on the game and wait for its page to fully load (the icon seems to load at the same time as the background image on the game's page). But it doesn't fix all the time, so if that doesn't work for you, hey, same here.
That could be it. Clicked on the Ys I game and waited several minutes but the background image isn't loading.

Flynn
Posted June 10, 2015
avatar
elgonzo: If you have two bug reports A and B which are duplicate, it does not matter whether A is marked a duplicate of B, or whether B is marked a duplicate of A.
avatar
MorningStar33: Maybe in a situation when reports haven't been checked yet, altough it still wouldn't make much sense. But that's not the case here; both bugs were confirmed and a person was assigned for them.
Okay, i guess i see now what you are referring to. It's the status being "assigned" and the meaning that is normally assigned (no pun intended) to it, right? If that's the case, i can understand your frustration.

I noticed already some time ago that GOG does not use the "assigned" status indication as intended, so i stopped paying attention to it. GOG's Mantis auto-assigns a GOG member to any newly created bug report and automatically sets the status to "assigned" - pretty obvious from this fact alone that GOG uses the "assigned" status not in the normal sense of indicating "this bug is being worked on by the assigned person".
Post edited June 10, 2015 by elgonzo
Posted June 10, 2015
avatar
MorningStar33: Maybe in a situation when reports haven't been checked yet, altough it still wouldn't make much sense. But that's not the case here; both bugs were confirmed and a person was assigned for them.
avatar
elgonzo: Okay, i guess i see now what you are referring to. It's the status being "assigned" and the meaning that is normally assigned (no pun intended) to it, right? If that's the case, i can understand your frustration.

I noticed already some time ago that GOG does not use the "assigned" status indication as intended, so i stopped paying attention to it. GOG's Mantis auto-assigns a GOG member to any newly created bug report and automatically sets the status to "assigned" - pretty obvious from this fact alone that GOG uses the "assigned" status not in the normal sense of indicating "this bug is being worked on by the assigned person".
It is probable all bugs are immediately assigned to an individual just to triage them. Somebody does need to triage them as they come in, probably in batches at a time as they accumulate. At this point they would be reassigned to the appropriate engineer. One cannot assume that assigning a bug means it is verified. It could be initially assigned to somebody to verify it and also try to reproduce it reliably if the end user did not or could not. Then it would go to someone else most likely to actually fix it.

When marking one of two bug reports a duplicate it does not matter which was reported first. I can only imagine someone felt slighted when their bug was marked a duplicate but they reported it before somebody else. This isn't a contest to note who found it first. It doesn't matter. They know about the bug now, good enough.

I think people would do well to not worry about thier process of managing bugs and bug reports. It's enough to just test the application and submit the reports. That's a big help. Becoming invested in one's own bug reports and then becoming upset when they are not handled the way one wants them to be or expects them to be isn't helpful and only produces unnecessary frustration. Just submit them and good enough would be my advice.
Posted June 10, 2015
avatar
dirtyharry50: It is probable all bugs are immediately assigned to an individual just to triage them. Somebody does need to triage them as they come in, probably in batches at a time as they accumulate.
I guess so too that the devs use the automatic assignment to "hand over" newly filed issue reports to a specific GOG team member who is in charge of triaging issues of a particular category. Although it would make more sense when those who manage bug triaging for a particular project would select the issues they are responsible for based on the particular content of the project and category field (i.e., filtering the issue list) -- it should not require automatic assignments as some kind of workaround for that. But then again, i know little about Mantis and its limitations, perhaps it is indeed more practical for the devs to use automatic assignments instead of filtering the issue list by project and category... But then again (again), i said i stopped paying attention to it, so i should better shut up now :)
Post edited June 10, 2015 by elgonzo
Posted June 10, 2015
just found out that the patch level varies between Galaxy and regular/offline game builds - Thief Gold and Thief2 are at 1.22 on Galaxy, but 1.21 on the regular build (with the latest offline patch), System Shock2 offline build with patch is at 2.42, and the Galaxy build seems to be only at 2.4 for some reason.

this is something that should be corrected, I believe.
Post edited June 10, 2015 by voodoo47
Posted June 11, 2015
avatar
BKGaming: Known issue:

http://www.gog.com/support/support_view/bgog_galaxy_troubleshooting_and_useful_informationb
avatar
lostanddamned: thank you a lot.
didn't help, already tried that by myself. but at leadt i know it's known
Yea other people have said the same, hopefully it is fixed soon.
Posted June 11, 2015
Hopefully this is the right forum.
Before I get some crap, as per usual, for having an outdated PC I'll just state I'm not complaining just merely asking out of curiosity.

Any particular reason why GOG Galaxy client requires Windows 7 or later? I'm still running Vista and it appears this is the only client I've come across where it isn't supported. Find it kind of weird and disappointing at the same time.
Posted June 11, 2015
avatar
voodoo47: just found out that the patch level varies between Galaxy and regular/offline game builds - Thief Gold and Thief2 are at 1.22 on Galaxy, but 1.21 on the regular build (with the latest offline patch), System Shock2 offline build with patch is at 2.42, and the Galaxy build seems to be only at 2.4 for some reason.

this is something that should be corrected, I believe.
Particularly annoying is when I installed Hand of Fate using the latest installer. When I imported the folder into Galaxy, even though the game was already at 1.03, Galaxy had to redownload the entire 3+ GB game.

Sense! Makes none!

Flynn
Pages:
1
100
108
109
110
111
112
300
400
412
This is my favourite topic
Community
General discussionGOG GALAXY BETA(6179 posts) (6179 posts) 
(6179 posts)