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

×
Hey IronArcturus,

just asking if you are running Homeworld Remastered in compatibility mode?

Or did you install another Visual Basic Redist, that overwrote some files from the Redist which came with Homeworld remastered?
avatar
IronArcturus: Shukaku mentioned that the error logs are reporting the wrong OS. I'm wondering if that has something to do with it. Since I'm running Win7 and the error logs say WinXP for some reason.
Well, at least for me Win7 & no galaxy doesn't seem to be an issue so far. I've only tried both versions of Homeworld (1)
Well I think I may have found a temporary fix for this problem. After the 2.1 patch, the game will not load unless you give Homeworld Remastered access to "home" which is 127.0.0.1. This is required even if one is playing offline. Version 2.0 didn't have this issue.
avatar
IronArcturus: Well I think I may have found a temporary fix for this problem. After the 2.1 patch, the game will not load unless you give Homeworld Remastered access to "home" which is 127.0.0.1. This is required even if one is playing offline. Version 2.0 didn't have this issue.
That definitely sounds like a bug and should be reported to the GBX Staff over on their forums. :)
avatar
IronArcturus: I installed the new v2.1 patch and now I keep getting this error window every time I launch the game. It says "access violation" in multiple languages. Here is the screenshot. I'm running Windows 7 64-bit on an nVidia card.

Is there any way to fix this problem? Are the game devs aware of it?
This has happened to me a few times as well, and I am using Galaxy.
avatar
IronArcturus: Well I think I may have found a temporary fix for this problem. After the 2.1 patch, the game will not load unless you give Homeworld Remastered access to "home" which is 127.0.0.1. This is required even if one is playing offline. Version 2.0 didn't have this issue.
Are you saying this is required all the time? Because I just tried it without any internet access and the game ran fine. Using Win 10.
avatar
micktiegs_8: Are you saying this is required all the time? Because I just tried it without any internet access and the game ran fine. Using Win 10.
I'm running Win7 with no Galaxy installed. With v2.0 of HR, the game ran fine. But they apparently changed something in v2.1. Every time I tried to load it, it would show an error window saying "access violation" in multiple languages. The only way I can get around this error was to allow the game access to 127.0.0.1. This looks like a bug with the Galaxy implementation ("HomeworldRM.exe caused an Access Violation in module Galaxy.dll at 0023:61ce2067" in the logs) since there's no reason why an offline game should have access to this.
avatar
IronArcturus: Well I think I may have found a temporary fix for this problem. After the 2.1 patch, the game will not load unless you give Homeworld Remastered access to "home" which is 127.0.0.1. This is required even if one is playing offline. Version 2.0 didn't have this issue.
avatar
micktiegs_8: Are you saying this is required all the time? Because I just tried it without any internet access and the game ran fine. Using Win 10.
Localhost (127.0.0.1) traffic never leaves your computer. Internet access isn't involved. Presumably it's used for inter-process communication (time honored, common, cross-OS method) between the game and an attempted connection to the Galaxy service. GOG should improve their shitty error handling and not just crash if it is dropped.
No particular harm in allowing the game to access the local computer. Particularly when there isn't anything to talk to for those without the Galaxy client.
avatar
micktiegs_8: Are you saying this is required all the time? Because I just tried it without any internet access and the game ran fine. Using Win 10.
avatar
IronArcturus: I'm running Win7 with no Galaxy installed. With v2.0 of HR, the game ran fine. But they apparently changed something in v2.1. Every time I tried to load it, it would show an error window saying "access violation" in multiple languages. The only way I can get around this error was to allow the game access to 127.0.0.1. This looks like a bug with the Galaxy implementation ("HomeworldRM.exe caused an Access Violation in module Galaxy.dll at 0023:61ce2067" in the logs) since there's no reason why an offline game should have access to this.
Yep, no Galaxy here either. Did you download the entire 2.1 installer, or use the patch for 2.0? I've had past problems where games wouldn't work if I used the patch, but downloading the entire installer fixed it.

I've also had an issue with the DLC for Dungeons 2 where the DLC did not register unless you had Galaxy installed. Support rectified that a short time after more people than just myself had the problem (because I'm insane apparently).
Maybe GOG can fix the dependency issue themselves, in a similar fashion... probably after constant nagging of course.
avatar
micktiegs_8: Are you saying this is required all the time? Because I just tried it without any internet access and the game ran fine. Using Win 10.
avatar
Gydion: Localhost (127.0.0.1) traffic never leaves your computer.
I know that's probably something 'everyone who owns a computer' should know, but I didn't realise it was a local thing... sorry. Still doesn't change that I had no problem under 'no Galaxy' environments... which is the important part, no?
Post edited June 22, 2016 by micktiegs_8
avatar
micktiegs_8: Still doesn't change that I had no problem under 'no Galaxy' environments... which is the important part, no?
Sure. My response was also to the thread at large. I also was assuming no internet meant no network connection. Which is not necessarily the case. No network connection does effect some firewalls behavior. Do you even DROP traffic to localhost? If not I wouldn't expect you to have issues.
The dll itself seems buggy anyway.
Post edited June 22, 2016 by Gydion
avatar
micktiegs_8: Yep, no Galaxy here either. Did you download the entire 2.1 installer, or use the patch for 2.0? I've had past problems where games wouldn't work if I used the patch, but downloading the entire installer fixed it.

I've also had an issue with the DLC for Dungeons 2 where the DLC did not register unless you had Galaxy installed. Support rectified that a short time after more people than just myself had the problem (because I'm insane apparently).
Maybe GOG can fix the dependency issue themselves, in a similar fashion... probably after constant nagging of course.
avatar
Gydion: Localhost (127.0.0.1) traffic never leaves your computer.
avatar
micktiegs_8: I know that's probably something 'everyone who owns a computer' should know, but I didn't realise it was a local thing... sorry. Still doesn't change that I had no problem under 'no Galaxy' environments... which is the important part, no?
As of right now, GOG only has the v2.1 patch as a stand-alone to the installer. It looks like they haven't merged the two yet. Also, with localhost, that's still the game trying to access a network IP address and there's really no need for this at all. Users shouldn't have to mess with their firewalls to get a singleplayer game to work.
avatar
IronArcturus: As of right now, GOG only has the v2.1 patch as a stand-alone to the installer. It looks like they haven't merged the two yet.
Actually it is merged. Does your link say 2.1 (GOG-16) next to part 1,2,3? As well as the patch for 2.1?
That patch is just there for those who had 2.0 (which is GOG-15) and didn't want to download the entire thing again.
I can assure you that it is definitely merged.
avatar
micktiegs_8: Actually it is merged. Does your link say 2.1 (GOG-16) next to part 1,2,3? As well as the patch for 2.1?
That patch is just there for those who had 2.0 (which is GOG-15) and didn't want to download the entire thing again.
I can assure you that it is definitely merged.
I looked in my game shelf and HR installer finally updated. But since the filesize is so large, I think I'm going to wait for the next version to see if the issue has been fixed.
Hello!
If you don't want give access to 127.0.0.1 - you can:

1. run Homeworld Remastered (first tale) from launcher and wait (don't press any keys and do not touch or close error message!!!) until the application window will unfold/start to full screen and press alt+Enter (you can hear the standard sound of the Windows), you can see developer-logo (don't press any keys!!!).

Wait the game-menu. You can see circle instead of the cursor. Press any menu-tab. You can play in the game, but don't touch or close error message!!!

2. run Homeworld Remastered 2 from launcher and use first step.

But in Homeworld Remastered 2 i have problem with this method, after use alt+Enter (can turn into a non-fullscreen and window about error does not allow to play.). You should use first step (with alt+Enter - method) - many times before the game will work.
Post edited July 13, 2016 by Alachomor
avatar
IronArcturus: Well I think I may have found a temporary fix for this problem. After the 2.1 patch, the game will not load unless you give Homeworld Remastered access to "home" which is 127.0.0.1. This is required even if one is playing offline. Version 2.0 didn't have this issue.
Can anyone post how excactly can this be accomplished? I have no idea how to give access to "home".