Homeworld Remastered Collection

Homeworld Remastered Collection

Zobacz statystyki:
ArxCA 25 lutego 2015 o 16:37
Homeworld 2 Classic crash to desktop atioglxx.dll fix AMD
If like me you have an AMD card and keep crashing to desktop upon launch of Homeworld 2 classic, simply go to this link and download this zip file.
http://www.thegameengine.org/wp-content/uploads/2012/11/atioglxx_fix.zip
It just involves putting the dll into the bin/release folder where the Homeworld 2 exe is and hopefully it should be fixed for you.
Ostatnio edytowany przez: ArxCA; 25 lutego 2015 o 16:57
< >
Wyświetlanie 31-45 z 60 komentarzy
Sammi79 27 października 2015 o 9:21 
OK found a simple fix that may work for you folks (it works for me, without using an old dll override on Win 10x64 with an AMD R9-285x). I take no credit as someone else found this one.

You need to create a shortcut to the Homeworld2.exe first, then right click it and select properties. In the target box (where the directory path and file name are listed inside quotes) after the end quote add a space then:

-nopbuffer

then click apply to save it. Run from the shortcut and report back here if you still have issues.

[edit]

Make sure to remove any atioglxx.dll file from the game directory.
Ostatnio edytowany przez: Sammi79; 8 listopada 2015 o 12:05
UnseenOni 8 listopada 2015 o 11:42 
I did this and I just get a black screen, but the intro sounds are there, however nothing happens.
Sammi79 8 listopada 2015 o 12:04 
Początkowo opublikowane przez Unseen Oni:
I did this and I just get a black screen, but the intro sounds are there, however nothing happens.

What did you just do?

If you used the atioglxx.dll from a legacy driver, delete it and try the -nopbuffer command.
UnseenOni 14 listopada 2015 o 8:02 
Thanks that worked, I didn't read the part about deleting the .dll file, now to make a shortcut for each of my mods lol.
tronix 21 listopada 2015 o 23:43 
Macbooks with AMD m370x

-nopbuffer

It is required to disable the DPI scaling for the game too if youre using a macbook pro with a m370x.

homworld2.exe -> right click -> properies -> compatibility -> check "Disable display scaling on high DPI setting"
Shermanator 27 listopada 2015 o 21:33 
Początkowo opublikowane przez Unseen Oni:
Thanks that worked, I didn't read the part about deleting the .dll file, now to make a shortcut for each of my mods lol.
.
How did you make your shortcuts for the mods? Did it work?


jur89 1 grudnia 2015 o 2:58 
Początkowo opublikowane przez Shermanator:
Początkowo opublikowane przez Unseen Oni:
Thanks that worked, I didn't read the part about deleting the .dll file, now to make a shortcut for each of my mods lol.
.
How did you make your shortcuts for the mods? Did it work?
Any progres on this? I can start HW2 but not the mod.
Ostatnio edytowany przez: jur89; 1 grudnia 2015 o 2:58
Shermanator 1 grudnia 2015 o 10:24 
Turns out it doesn't work :/. Wish gearbox could fix this already!
Początkowo opublikowane przez Sammi79:
OK found a simple fix that may work for you folks (it works for me, without using an old dll override on Win 10x64 with an AMD R9-285x). I take no credit as someone else found this one.

You need to create a shortcut to the Homeworld2.exe first, then right click it and select properties. In the target box (where the directory path and file name are listed inside quotes) after the end quote add a space then:

-nopbuffer

then click apply to save it. Run from the shortcut and report back here if you still have issues.

[edit]

Make sure to remove any atioglxx.dll file from the game directory.
This fixed it for me. Thank you!

If you want to play with a mod, just add -nopbuffer to the command line field before you start from the launcher.
Ostatnio edytowany przez: Mr. Bones' Wild Ride; 6 grudnia 2015 o 13:53
seym56 27 stycznia 2016 o 16:21 
If you have the Steam Remastered Collection you just need to subscribe to the mod on steam.

Tell Steam to put an icon on your desktop like for all games.

Launch the game

In the launcher on the bottom right - select mods (Under Multiplayer Beta).

Select HW2 Classic

Select Star Wars Warlords

Press select

In the Commandline Arguments: Paste: "-nopbuffer" (Without the quotes)

And finally select Launch
Ostatnio edytowany przez: seym56; 27 stycznia 2016 o 16:21
Shermanator 31 stycznia 2016 o 15:55 
Początkowo opublikowane przez Mr. Bones' Wild Ride:
Początkowo opublikowane przez Sammi79:
OK found a simple fix that may work for you folks (it works for me, without using an old dll override on Win 10x64 with an AMD R9-285x). I take no credit as someone else found this one.

You need to create a shortcut to the Homeworld2.exe first, then right click it and select properties. In the target box (where the directory path and file name are listed inside quotes) after the end quote add a space then:

-nopbuffer

then click apply to save it. Run from the shortcut and report back here if you still have issues.

[edit]

Make sure to remove any atioglxx.dll file from the game directory.
This fixed it for me. Thank you!

If you want to play with a mod, just add -nopbuffer to the command line field before you start from the launcher.

This Works!
tom147 1 lutego 2016 o 13:25 
atioglxx-fix saved my game! I have AMD R9380 with crimson drivers. Tried all the other fixes including the -nopbuffrer with no sucess. Downloaded the fix, dropped it into homeworld2 exe bin ,then opened bin dropped into release. made an easy shortcut bt sending the launcher file to desktop. Works perfectly after days of fustration. Thanx Big!
tom147 1 lutego 2016 o 13:31 
forgot to mention if you get black screen wait a bit as I found took almost 30 sec to load
i am about to pull my hair right out! ive done everything on here and then some and still no luck.
here is the error report from the release folder. please someone msg me wth a solution. PLEASE

Homeworld2.exe caused an Access Violation in module atioglxx.dll at 0023:6aa263be.
Error occurred at 2/1/2016 17:15:12.
Homeworld2.exe, run by John.
Microsoft Windows XP?.
4 processor(s), type 586.
2048 MBytes physical memory.
Read from location 0000001c caused an access violation.
< >
Wyświetlanie 31-45 z 60 komentarzy
Na stronę: 1530 50

Data napisania: 25 lutego 2015 o 16:37
Posty: 60