@nonithu wrote:

I had a Code for the closed Beta can I play also now ?

Posts: 3

Participants: 3

Read full topic

@t.thoron wrote:

Like i said in post i have horrible lags when i press F or Middle mouse button (wheel) to focus viewport on selection. Only in remastered collection ! I tried to change button but nothing change. I have the latest drivers (Radeon software 16.3.1) and a very good machine running all games smooth. AMD R9 m395x 16go of DDR4 and a skylake I7 6820hk. I also tried all drivers i can for my GPU and i have the same result. I hope somebody can help me and other guys with this problem !

Posts: 2

Participants: 2

Read full topic

@Migz_DH wrote:

In the Steam forum, there have been a few threads lately 1 2 3 from people complaining that using the WASD keys or other pre-assigned keys to move the camera doesn't work. As rebinding keys always worked for me previously, I was curious and tried it out today. Indeed, directly swapping WASD for Up, Left, Down, and Right arrows doesn't work. (Edit: Presumably, the same thing happens with Pan Up and Pan Down as well. Edit2: Nope, not true. As Hell_Diguner mentioned below, the Pan Up and Pan Down work as expected after swapping.)

The problem is that the PLAYERCFG.LUA file's "ControlOptions" section doesn't fill in correctly when swapping the camera movement keys for keys which are already assigned to functions (such as WASD). This doesn't happen when moving the pre-assigned functions to keys which don't already have assignments such as the Number Pad keys first, then assigning the WASD keys (or similar) to the camera movement.

Inside of the PLAYERCFG.LUA file, entries should appear like this (example for W as Pan Forward):

{
151,
"Camera_PanCmd(INKE_KeyDown,PS_Up)",
0,
0,
"Pan Forward",
{
87,
},
},
{
152,
"Camera_PanCmd(INKE_KeyUp,PS_Up)",
1,
0,
"Pan Forward",
{
87,
},
},

However, it doesn't. Instead, it's missing the key entry for W ("87,") in the second part and it looks like this:

{
151,
"Camera_PanCmd(INKE_KeyDown,PS_Up)",
0,
0,
"Pan Forward",
{
87,
},
},
{
152,
"Camera_PanCmd(INKE_KeyUp,PS_Up)",
1,
0,
"Pan Forward",
{
},
},

All four camera movement entries miss that second key causing the camera to fail to move correctly.

Of course, by entering the correct key values to PLAYERCFG.LUA, the camera works as intended with WASD, but these players don't know that, and they shouldn't have to do that anyway.

As mentioned above, this entry problem can be bypassed by first assigning the functions to other keys first. Then, assigning the camera movement to the new keys. So, for example, if I move Waypoints, Military Selection, Stop, and Dock to NumPad 4, 5, 6, and 7 respectively, then assign Pan Forward, Pan Left, Pan Backward, and Pan Right to W, A, S, and D respectively, the PLAYERCFG.LUA file fills out correctly, and the camera moves as expected.

So, here are the instructions for two workarounds I've begun writing to players who have this problem:

1. 
   A. Change Waypoints, Military Selection, Stop, and Dock (WASD currently) to Number Pad numbers.
   B. Change the camera movement keys to WASD.
   C. Change Waypoints, Military Selection, Stop, and Dock to whichever other keys you want them to actually be.
   D. Check the PLAYERCFG.LUA file to ensure all of the entries are filled correctly.

2.
A. Change the camera movement keys to WASD while moving the Waypoints, Military Selection, Stop, and Dock functions to where you want them to be.
B. Check the PLAYERCFG.LUA file to ensure all of the entries are filled correctly and correct whatever problems occur.

I hope a solution to this can be included in the patch the GBX team has been working on.

(Oh, swapping the camera movement keys while in a match does nothing until exiting out of it btw. Did you know that?)

---

How to reproduce this problem:

1. While in the Main Menu, go to the Options Menu, then the Controls Menu.
2. Assign Military Selection to Left.
3. Assign Waypoints to Up.
4. Assign Stop to Down.
5. Assign Dock to Right.
6. Assign Pan Forward to W.
7. Assign Pan Backward to S.
8. Assign Pan Left to A.
9. Assign Pan Right to D.
10. Try to play a match in either the campaign or Player vs. CPU; it doesn't matter which.
11. You should find that pressing either W or A results in the camera moving forward and not stopping when the key is released. Hit the key again to stop the camera from moving.
12. You should find that hitting any of the WASD keys afterwards results in no movement at all.
13. Exit the game.
14. Enter the PLAYERCFG.LUA file and scroll down to the "ControlsOptions" section.
15. You should find the key number entries missing for the four camera pan stop functions.
16. You should find that the key number entries are there for Military Selection, Waypoints, Stop, and Dock.
17. Add the appropriate key entry to the four broken sections, and save the file.
    A. Pan Forward - "87,"
    B. Pan Backward - "83,"
    C. Pan Left - "65,"
    D. Pan Right - "68,"
18. Repeat steps 10 through 12 to see if the camera works as expected... it should.
19. Exit the match, and go to the Main Menu.
20. While in the Main Menu, go to the Options Menu, then the Controls Menu.
21. Set all of the controls to the default.
22. Exit to Desktop.
23. Boot up the game.
24. While in the Main Menu, go to the Options Menu, then the Controls Menu.
25. Assign Military Selection to Num 6.
26. Assign Waypoints to Num 7.
27. Assign Stop to Num 8.
28. Assign Dock to Num 9.
29. Assign Pan Forward to W.
30. Assign Pan Backward to S.
31. Assign Pan Left to A.
32. Assign Pan Right to D.
33. Repeat steps 10 through 12 to see if the camera works as expected... it should.
34. Exit to Desktop.

Posts: 5

Participants: 3

Read full topic

@BigTuna117 wrote:

My problem is that cannot actually get into the multiplayer beta. It's curious, to say the least. All of the Intel based machines I've tried it on run fine, however all of the AMD based machines, regardless of chipset, GPU brand, and CPU model, absolutely will not connect in. They just stick at "you need a shift account to proceed." After buying the game I promptly requested assistance from Gearbox support (REQUEST #93202 for any support personnel reading this), who tried quite valiantly to assist, however things got a bit confusing when the tech started sending me Linux support pages from Steam (I was on Win 8.1 at the time, now on Win 10). It was also around this time my motherboard failed, however since rebuilding my machine, I retraced my steps and still haven't gotten it to connect in, and the support page has been closed because of how long it took to get the machine back up and running. I also have a "test bench" machine which is also an AMD based machine, and it too will not connect. I've tried it on both machines to no avail.

Frustrated and unsure of where to go, I figured i'd take a break and enjoy the single player campaigns. Now, nearly a year later, I seek to get it working. I'm not really sure where to start, though. I'll post specs for both machines, I guess we'll go from there.

Primary machine (actually codenamed Sajuuk when I built it 3+ years ago)

CPU: AMD FX-6100
MOBO: ASUS TUF 990FX R2.0 (the one that died was a Gigabyte 970A-D3 REV 1.1)
RAM: Corsair Vengeance 16GB @ 1600mhz
GPU: Gigabyte GTX 960 2.0GB
Sandisk 120GB SSD primary
2.0TB + 2.0TB RAID 0 Secondary
Windows 10

Secondary machine

CPU: AMD Phenom II X4 910
MoBo: MSI 760GM-P34 (FX)
RAM: Kingston HyperX DDR3, 8GB @1600mhz
GPU: AMD Radeon HD 6770 1GB (Note: this motherboard includes integrated graphics, but is disabled)
750GB 7200RPM drive primary
Windows 10

As I said, these two machines won't get past "You need a SHiFT account to proceed." I am curious to hear your guys' thoughts.

Posts: 2

Participants: 2

Read full topic

@myrandakrose wrote:

No error messages are displayed. None.

Launcher runs fine, all the buttons seem to work, but when I click on any there's the usual "beep" and then nothing.

I have verified the files, and am now in the process of re-installing completely.

My hardware btw

3770K
GTX 980Ti
16GB RAM
Plenty of disk space...

Ran fine previously with an AMD GPU, but with horrid graphical glitches - all the units were partially transparent - now I've upgraded... nothing works

Posts: 6

Participants: 2

Read full topic

@kkface477 wrote:

A quick run down.
first off I know that the a bunch of stuff doesn't like the game, however my first step is simply getting the launcher to not instantly crash. I have done everything from updating redistributables, making the game file an exception. I can launch everything but HW2 manually, but I fail to see why that is impacting the launcher.

I have error messages from HW2 but if I launch the launcher it will not give me these errors, simply crash:

"Homeworld2.exe caused an Access Violation in module atioglxx.dll at 0023:5f461a05.
Error occurred at 5/22/2016 22:36:06.
Homeworld2.exe, run by kkfac.
Microsoft Windows XP?.
4 processor(s), type 586.
2048 MBytes physical memory.
Read from location 00000020 caused an access violation.

MiniDump failed to save."

Now, I remember reading about the atioglxx.dll file where I need to make the .dll into a .dl or something, but that file does not exist, nor does adding that file (from the people on steam who try and help)

I would really like to run it on my nice computer as I'm trying to help a modder and it always crashes after a while on my laptop.

Thnx

Posts: 6

Participants: 3

Read full topic

@jnaymie wrote:

When i launch the MP Beta, most of the time the Steam option is greyed out and I can only select Local Network. The only way to fix it is to keep relaunching the game until the option to play over Steam is no longer disabled. Sometimes this take 15 or more relaunches. Any idea what the problem is or what I can do to fix it?

Posts: 4

Participants: 3

Read full topic

@StigmA wrote:

Tue Jun 07 18:00:20 2016
Version 2.0, Build Number 25, Changelist Number 1230194
Loaded Archive: 'Homeworld2.big'
Failed to Load Archive '....\DATAUPDATES\UpdateHomeworld2.big'
Loaded Archive: 'HW1Ships.big'
Failed to Load Archive '....\DATAUPDATES\UpdateHW1Ships.big'
Loaded Archive: 'HW2Ships.big'
Failed to Load Archive '....\DATAUPDATES\UpdateHW2Ships.big'
Loaded Archive: 'HWBackgrounds.big'
Failed to Load Archive '....\DATAUPDATES\UpdateHWBackgrounds.big'
UTIL -- filepath failure, path doesn't exists 'D:\Program Files (x86)\Steam\steamapps\common\Homeworld\HomeworldRM\data\locale\English'
Loaded Archive: 'English.big'
Failed to Load Archive '....\DATAUPDATES\UpdateEnglish.big'
Failed to Load Archive '....\DATAUPDATES\Compatibility.big'
Loaded Archive: 'D:\PROGRAM FILES (X86)\STEAM\STEAMAPPS\COMMON\HOMEWORLD\HOMEWORLDRM\DATA\HW1Campaign.big'
Loaded DLC Campaign Archive: 'D:\PROGRAM FILES (X86)\STEAM\STEAMAPPS\COMMON\HOMEWORLD\HOMEWORLDRM\DATA\HW1Campaign.big'
Failed to Load Archive '....\DATAUPDATES\UpdateHW1Campaign.big'
Loaded Archive: 'D:\PROGRAM FILES (X86)\STEAM\STEAMAPPS\COMMON\HOMEWORLD\HOMEWORLDRM\DATA\EnglishHW1Campaign.big'
Loaded DLC Campaign Localized Data Archive: 'D:\PROGRAM FILES (X86)\STEAM\STEAMAPPS\COMMON\HOMEWORLD\HOMEWORLDRM\DATA\EnglishHW1Campaign.big'
Failed to Load Archive '....\DATAUPDATES\UpdateEnglishHW1Campaign.big'
Loaded Archive: 'D:\PROGRAM FILES (X86)\STEAM\STEAMAPPS\COMMON\HOMEWORLD\HOMEWORLDRM\DATA\EnglishSpeechHW1Campaign.big'
Loaded DLC Campaign Speech Archive: 'D:\PROGRAM FILES (X86)\STEAM\STEAMAPPS\COMMON\HOMEWORLD\HOMEWORLDRM\DATA\EnglishSpeechHW1Campaign.big'
Failed to Load Archive '....\DATAUPDATES\UpdateEnglishSpeechHW1Campaign.big'
Loaded Archive: 'D:\PROGRAM FILES (X86)\STEAM\STEAMAPPS\COMMON\HOMEWORLD\HOMEWORLDRM\DATA\MusicHW1Campaign.big'
Loaded DLC Campaign Music Archive: 'D:\PROGRAM FILES (X86)\STEAM\STEAMAPPS\COMMON\HOMEWORLD\HOMEWORLDRM\DATA\MusicHW1Campaign.big'
Failed to Load Archive '....\DATAUPDATES\UpdateMusicHW1Campaign.big'
Uing ..profiles\ for profiles folder
GAME -- Using player profile mysteamnick
Changing from a 32 bit colour depth in winNT (6.2 build 9200),
Display: (0, 0, 1920, 1080) - (0, 0)
Switching to a 1920x1080 32bit mode
GL Info: 3.3 - 3.3.12874 Compatibility Profile Context 16.200.1013.0
GL Vendor: ATI Technologies Inc.
GL Renderer: AMD Radeon R9 200 Series
GL Part ID: 200
Loaded Archive: 'EnglishSpeech.big'
Failed to Load Archive '....\DATAUPDATES\UpdateEnglishSpeech.big'
Loaded Archive: 'Music.big'
Failed to Load Archive '....\DATAUPDATES\UpdateMusic.big'
SOUND -- created destination [ fdaudio ], handle [ 4 ] with [ 48 ] channels created
SOUND -- created destination [ fda streamer ], handle [ 5 ] with [ 8 ] channels created
SOUND -- created destination [ dxa streamer ], handle [ 0 ] with [ 8 ] channels created
SOUND -- created destination [ dxaudio ], handle [ 1 ] with [ 48 ] channels created
Build name:
Data path : D:\Program Files (x86)\Steam\steamapps\common\Homeworld\HomeworldRM\data
Font Load: data:UI\Font\Blender.rcf, 1920,1080
Font Attr: 14, Biu
No mapping for font 'Blender' - using 'default'
Resetting fp PC control word.
CmdLine: -dlccampaign HW1Campaign.big -campaign HomeworldClassic -moviepath DataHW1Campaign
Race Filtering: SINGLEPLAYER rules - @SinglePlayer
12 Races Discovered
Starting Level: Data:\LevelData\Campaign\homeworldclassic\Mission13\Mission13.level
EngineTrailStatic::getTweaks requesing index(0) that doesn't exist.
EngineTrailStatic::getTweaks requesing index(0) that doesn't exist.
EngineTrailStatic::getTweaks requesing index(1) that doesn't exist.
EngineTrailStatic::getTweaks requesing index(2) that doesn't exist.
Font Load: data:UI\Font\SmallFonts7.rcf, 1920,1080
Font Attr: 14, Biu
EngineTrailStatic::getTweaks requesing index(0) that doesn't exist.
EngineTrailStatic::getTweaks requesing index(1) that doesn't exist.
EngineTrailStatic::getTweaks requesing index(0) that doesn't exist.
EngineTrailStatic::getTweaks requesing index(1) that doesn't exist.
Unable to retrieve UI (animated) texture ()
Error, LoadScreen failed to screen of type GameBalanceScreen when loading section GameBalanceScreen from file DATA:\UI\NewUI\Developer\GameBalanceScreen.lua
Error, LoadScreen failed to screen of type DeveloperScreen when loading section DeveloperScreen from file DATA:\UI\NewUI\Developer\DeveloperScreen.lua
Restoring video mode
Display: (0, 0, 100, 100) - (8, 31)

Still crashing on loading mission 13 of HWR1

Posts: 12

Participants: 5

Read full topic

@Migz_DH wrote:

In the Advanced Commands tutorial, the player is asked to select a Strikegroup on the Strikegroup Roll Out bar. While clicking the Delta, Broad, X, Claw, Wall, and Sphere Strikegroup buttons forces the ships to move into those formations, they don't complete the step. Only using the Capital Phalanx, Frigate Line, and Fighter Screen options will complete the step.

Additionally, earlier in that tutorial, the player is instructed to order 3 squadrons of bombers to attack a frigate. The bombers don't attempt to maneuver away from the exploding frigate and sometimes take damage. In two of the four runs I did today, 3 bombers in the central squadron were destroyed. I know the damage due to exploding ships was increased, but I also read that other ships are supposed to try to move away from the exploding ones, so I'm mentioning this as an example where that doesn't seem to occur.

Screenshot showing the bombers being blown up after destroying the frigate:
http://images.akamai.steamusercontent.com/ugc/271719542646104927/99019BF48F4AB6ADEC877A745BC8E883E11D4058/

Posts: 1

Participants: 1

Read full topic

@BiohazardBG wrote:

Hello i find some problems wit the texture in the interior of the mothership

the second screen is with patch 2.0 I turn off all of the HDR lighting and bloom to show the problem.

Best regards, Andrew!

Mother ship texture bug.jpg1920x2312 1.85 MB

Posts: 4

Participants: 2

Read full topic

@Migz_DH wrote:

I saw in another thread that there's a texture problem with some of the motherships, and I thought I'd seen something similar with the carriers, so I looked. Unfortunately, I don't have enough screenshots of the old carriers to compare, but while looking for that, I discovered a problem with the Taiidan carrier.

Along the upper edge of the Taiidan carrier's U-shaped hull, there are black artifacts which didn't seem to exist previous to 2.0. You can see the artifacts on one edge in the two following screenshots. They're just forward (screen left) of the upper yellow lighted surface.

When changing the camera angle though, the black artifacts mostly disappear like in this screenshot.

Before 2.0, the black artifacts didn't appear on the Taiidan carrier at that angle. The following is a screenshot taken a little over three weeks ago.

I quickly checked the other carriers and all of the motherships, and none of them showed anything quite like this.

All of the video settings are the same from before 2.0 to now... unless some were changed by the patch, and I didn't notice them. (Edit: I looked at an old screenshot of the video settings, and the ones used now are the same as were used previously.)

To ensure that the problem wasn't driver related, the first and third screenshots above are using the newest NVIDIA driver which was released today. The second and fourth screenshots above used the April 2016 driver package.

Also, the issue exists with SLI both on and off.

System Information:
OS - Windows 7 Home Premium (x64), SP1
Processor - Intel i7-2600K 3.4GHz (OC @ 4.2GHz)
RAM - 8GB G-Skill @2133MHz (F3-17000CL9D-8GBXM); CL9-11-10-28; 1.65 Volt
Motherboard - ASUS P8P67 WS REVOLUTION Rev 3.0
BIOS - Ver 2105, May 2012
GPU - 2x SLI NVIDIA Geforce GTX 570 (EVGA) OC @ 797 MHz Core Clock, 1950 MHz Memory Clock, 1.013V
Video Driver - 368.39 - WHQL, 7 June 2016 (10.18.13.6839)
Monitor - Samsung S27B550V @ 1920x1080
System Drive - Samsung 830 SSD, 256GB, F/W CXM03B1Q
Sound Card - Creative Sound Blaster X-Fi Titanium
Sound Driver - 2.17.0008, July 2010
Speakers - Logitech G51 5.1 Surround

Posts: 4

Participants: 3

Read full topic

@Thalaron86 wrote:

Played the 1st 2 missions in HW1RM, how ever during mission 2 just after the 1st triggered Raider attack I began to get massive FPS drops and stuttering, made its pretty much unplayable, had to restart the game to get it to go away. Yes that fixed it temporarily.

My system is well above the Required system spec for this game.

AMD FX 8370 @ 4GHz
8GB DDR3 @ 1600MHz
Samsung 850 Pro 512GB SSD
Sapphire R9-390X Tri-X OC 8GB
Corsair HX1200I PSU

This setup has no issues playing every other game I play maxed out, including Skyrim with 200+ mods, ESO, Star Trek Online, PlanetSide 2, Warframe, Star Citizen, BattleFront etc.

My current ingame settings.
http://sta.sh/2qrw5jommvs?edit=1

As of posting this I have disabled Raptr, which is known to cause issues in some games from its overlay, how ever the overlay was disabled manually before I started getting this issue.

Anyone else having similar issues ? Post your specs and ingame settings and when it happens, Would be appreciated :).

Posts: 15

Participants: 3

Read full topic

@isned2000 wrote:

Homeworld Remastered Collection does not seem be updating to the latest patch on my Mac. I have tried tinkering with the update priority and even reinstalling entirely. But I still seem to be running the older version of the game. Does anybody know the cause of this or a fix?

My specs:
11 inch macbook air, mid 2012
running os 10.11.5
1.7 GHz intel core i5
4 GB 1600 MHz DDR3 ram
Intel HD 4000 1536 mb graphics card

I am playing the steam version.

Posts: 2

Participants: 2

Read full topic

@BiohazardBG wrote:

Hello I find another issue with the engines of the Higaran capital ships. This issue effect the destroyer and all of the frigates. The problem is that they dont glow when in formation like the carrier and the battlecruser or even if glow they dont have this whit temperature but very dark blue like are idle. All other ships dont look like have this issue.

Here is the engine of the frigate from the classic HW2 in flight

2015-02-28_00007.jpg1920x1200 270 KB

the current engine

20160608113329_1.jpg1920x1200 144 KB

as you can see only the battlecruser and the carrier in the front have the right engine light. The destroyer engine still have glow when in formation but the frigates dont. When they glow the also have this dark blue glow.

20160608113725_1.jpg1920x1200 104 KB

Some of the engines glow other not when in formation. Here I select all of the ships with this problem and the afected are The destroyer and all of the frigates.

20160608113323_1.jpg1920x1200 183 KB

The frigate compare to the carrier

20160608113734_1.jpg1920x1200 140 KB

Here you can see that the mothership and the shipyard have proper engine light.

20160608113203_1.jpg1920x1200 172 KB

I hope this can be fixed.

Best regards, Andrew!

Posts: 5

Participants: 3

Read full topic

@Migz_DH wrote:

While in the 5th HW1 mission, I was experimenting with using strike craft in sphere formation when I found a group of Taiidan Interceptors in X formation wobbling oddly just a short distance away from my frigates. Since screenshots would be useless to show that, I recorded the behavior in video. I apologize that the camera moves a bit much at the beginning; I was trying to see what else was going on as well.

In the video, after identifying the wobbling craft as Taiidan Interceptors, I tried to attack them with Group 1 (Interceptors) which were previously assigned to guard frigates in conjunction with Groups 2 and 3 (also Interceptors). As soon as I sent that command, the Taiidan Interceptors moved and briefly attacked one of my frigates (btw, having all ships set to passive by default is rather inconvenient) before wobbling again, but Group 1 remained in guard position.

I then commanded Group 2 to attack. Neither the Taiidan ships nor Group 2 moved.

So, I sent Group 3 to attack as well. Finally, all three of my Interceptor Groups moved, and the Taiidan squadron moved as well after being attacked... to attack a collector ship far away. I suspect that the first two Interceptor groups didn't leave their Guard duty to attack like I expected they would, because the other Interceptors were still Guarding, and breaking the formation wasn't allowed. But, once all of the Interceptors were relieved from Guard duty, they all left.

After recording that video, I reloaded my latest save to see what would happen, and one of the Taiidan Interceptor squadrons did the same thing but that time near my collectors rather than my frigates.

In case it's useful, I uploaded my most recent save file. It should be from just shortly before this video takes place. https://www.sendspace.com/file/0r3vtn

Posts: 2

Participants: 2

Read full topic

@nickgod89 wrote:

As seen in the description I cannot load and of my saved games.

I just played a few days ago and went to play again today and the files were missing. I tried starting from one of the autosave points and the menu will pop up only allowing me to either exit to main menu or to Windows. This is really frusterating! Is anyone out there experiencing the same issue?

Thanks.

-Nick

Posts: 1

Participants: 1

Read full topic

@kremblin89 wrote:

Ok, so both heavy and light corvettes do not move when fighting, they get into range and then just sit there until whatever they are are shooting at is dead, or moves out of range in which case the corvettes move very slowly to try and get in range this can result in them attempt to chase fighters but never actually do anything. The same thing happens to the Turanic Corvettes on mission 2 they just sit there and trade fire with my own corvettes, or move a tiny bit and repeat to try and stay in range of fighters.. This makes Mission 3 impossible as interceptors are unable to kill the 7 assault frigates before they blow up the stasis pods, and corvettes sit there and get 2-3 shot by the frigates.

As for fighters, they seem to miss 99% of shots, 21 interceptors can take upwards of 5 min to kill one Turanic fighter since they not only miss pretty much every shot, they move to do a strafing run, but don't actually shoot half the time before peeling off to take another run. This also applies to Corvettes, they can be in range of a target and will just sit there without shooting sometimes.

Posts: 1

Participants: 1

Read full topic

@Lost_Cow wrote:

Hi guys and girls sorry if this post isn't in the right spot but I am not sure were to post. As the title says the game isn't working after I downloaded the mega patch, I access the game on steam and I get to the screen where you select which game you want to play (Homeworld 1 remastered, Homeworld 2 Remastered, Multiplayer, Homeworld 1 classic, and Homeworld 2 classic) but when I click on remastered Homeworld 1 or 2 or Homeworld 2 classic the screen goes away and nothing happens, I should note that when I click on classic Homeworld 1 it goes to game. I tried uninstalling and deleting local content through Steam and reinstalling it but the game still follows the same behaviour. I should also note that before the patch the game was working fine. I tried following the “HW 1 Remastered Campaign:"C:\Program Files (x86)\Steam\steamapps\common\Homeworld\HomeworldRM\Bin\Release\HomeworldRM.exe" path I get a message that says “The program can’t start because MSVCP110.dll is missing from your computer” I am unsure what to do I need your help bringing Sajuuk to bear! Thank you all.

Posts: 4

Participants: 2

Read full topic

@slinger1410 wrote:

I posted this over at the steam forums, but everyone kept telling me to post here, so here it goes:

HW2RM mission 2 is really buggy. First of all, there is a group of fighters that spawn over by transport 4 and 5, which normally these don't spawn unless you has less then 2 squadrons of fighters, but now they spawn no matter how many fighters you start the mission with. Second, transport 1 apparently has 80 speed to start with and after saving it, the speed buff will jump to 120, which isn't correct. However, the other transport are at 40 to start, but after you save them, they won't get their speed buff and will remain at 40, which also isn't correct. They are suppose to have 40 speed, then jump to like 100 or something like that after saving them, but they don't. It wouldn't be so bad, but some of them now try to dock at the sametime, which results in them trying to push each other out of the way and none of them end up docking at all. Third, Captain Soban is now apparently just an ordinary marine frigate. He doesn't have his increase ROF or increase damage like he did in the original.

Posts: 3

Participants: 3

Read full topic

@BiohazardBG wrote:

Hello i just find a little glitch with the texture of the mothership looks like sym problem to me and is not affected by the shaders and the texture just glow

20160611151834_1.jpg1920x1200 279 KB

20160611151927_1.jpg1920x1200 290 KB

20160611152034_1.jpg1920x1200 400 KB

Here is problem with the shadows looks like the shadow map is inverted

20160611154836_1.jpg1920x1200 245 KB

20160611155001_1.jpg1920x1200 319 KB

Posts: 8

Participants: 4

Read full topic