Bay 12 Games Forum

Huh, I somehow missed adding the dev diary videos to the first post before. Still they are all linked there now.

One thing I noticed is that they are developing for both PC and SteamOS, the first interesting game I've noticed specifying that they are developing for it.

I could use a key if someone is still giving those away, thank you very much.

Sending you one now.

That would be nice.

Also if you get SR4, don't forget to check the Store Page, there's 2 DLC that are free.

Also, also if you get SR4 through this bundle, It may be worth picking up the sr4 upgrade pack on the humble store giving you all the DLC for far less than individually.

Quote from: Metalax on November 10, 2014, 04:29:54 am

Quote from: Noel.se on November 09, 2014, 02:17:03 pm

I searched for COMCTL32.ocx on my computer, I have it and it is in the right folder. My computer knowledge is insufficient to detect the problem.

Instructions for win 7. Haven't messed around with win 8, but it should use the same general procedure.

Verify if comctl32.ocx is in C:\windows\system32 folder. If it is, you may try re-registering the file.

1. Go to start and type cmd.
2. Right-Click on cmd in the results list and select “Run as Administrator”.
3. Type regsvr32 comctl32.ocx /u and press Enter. <- this unregisters the file in case the registration got corrupted
4. Type regsvr32 comctl32.ocx and press Enter.

If successful you should get a response saying "DllregisterServer in comscl32.ocx succeeded"

Hm, it gives me an error at step 3. Something about an error occurring while loading comctl.ocx. Not sure about the exact translation, since it is German. I checked and the file in my system32 folder is actually called "COMCTL.OCX" . I'm not sure if that matters, typing regsvr32 COMCTL.OCX /u gives a similar error (could not load COMCTL.OCX).

Ah, I wasn't fully awake when I last posted, so I missed a couple of things out, sorry.

Firstly, if a file is named something different then it is not the same file.
Note, that if you are using a 64bit version of windows, the file should be located in a different location, in the SysWOW64 directory, rather than in system32.

Second you need to change directory after opening the command prompt, that is likely what is causing the error you saw.

for a 32 bit version of windows make sure comctl32.ocx is located in the windows\system32 directory then
1. Go to start and type cmd.
2. Right-Click on cmd in the results list and select “Run as Administrator”.
3. Type, without quotes, "cd %systemroot%\system32" and press Enter.
4. Type, without quotes, "regsvr32 comctl32.ocx /u" and press Enter. <- this unregisters the file in case the registration got corrupted
5. Type, without quotes, "regsvr32 comctl32.ocx" and press Enter. <- this registers the file
If successful you should get a response saying "DllregisterServer in comscl32.ocx succeeded"

for a 64 bit version of windows make sure comctl32.ocx is located in the windows\SysWOW64 directory then
1. Go to start and type cmd.
2. Right-Click on cmd in the results list and select “Run as Administrator”.
3. Type, without quotes, "cd %systemroot%\SysWOW64" and press Enter.
4. Type, without quotes, "regsvr32 comctl32.ocx /u" and press Enter. <- this unregisters the file in case the registration got corrupted
5. Type, without quotes, "regsvr32 comctl32.ocx" and press Enter. <- this registers the file
If successful you should get a response saying "DllregisterServer in comscl32.ocx succeeded"

First thing to check would be if you have all of your drivers, chipset, graphics, etc, installed correctly.

Did you follow the process for moving a steam installation? Google it if you don't know the procedure. Obviously, as you have reinstalled windows all of the registry keys will no longer exist, so each game should need to run it's first run procedure again.

If you have a small game on your account that wasn't previously installed, download it and see if that runs.

I want to play TF2 so bad, but there is something terminally wrong with my computer where I can't find or connect to ANY servers whatsoever. I've tried everything I can think of, it's no use!

*Genuinely upset*

You've probably tried most of these, but worth going through the list.

If you open the server browser in steam(view->servers) and have team fortress 2 selected in the filters, do you still see nothing?

Ports are forwarded correctly? This site gives instructions on how to forward ports for TF2 for most if not all routers.

Try with any software/hardware firewalls temporarily disabled?

Try with any anti-viruses temporarily disabled?

Try a safemode with networking boot?

Try lugging the computer to somewhere with a different connection and trying from there? Or bringing a computer/laptop that it works on from somewhere else and trying on your connection?

Before I put it into production, is there anything fundamentally wrong with this design?

Code: [Select]

Farseer class Scout    9,000 tons     215 Crew     1608.4 BP      TCS 180  TH 720  EM 0
4000 km/s     Armour 1-38     Shields 0-0     Sensors 1/180/0/0     Damage Control Rating 9     PPV 0
Maint Life 3.01 Years     MSP 1005    AFR 72%    IFR 1%    1YR 167    5YR 2499    Max Repair 630 MSP
Intended Deployment Time: 12 months    Spare Berths 3   

DU-LC-01 (1)    Power 720    Fuel Use 38.5%    Signature 720    Exp 10%
Fuel Capacity 2,500,000 Litres    Range 129.9 billion km   (375 days at full power)

SR-SC-01 (1)     GPS 63000     Range 378.0m km    Resolution 100
EM-SC-01  (1)     Sensitivity 180     Detect Sig Strength 1000:  180m km

This design is classed as a Military Vessel for maintenance purposes
The intended purpose is to either be paired with an armed jumpship for investigating unexplored jump points (to find out if there's any colonies or warships in the system) or later on to provide long-range sensor support as part of a larger fleet.

Looks generally ok, although it will have difficulty spotting fighters/gunboats/swarm, and will miss missiles entirely. Still if it is only intended to pick up full size ships and colonies it should serve well. I tend to prefer thermal over EM sensors if I'm only installing one, on the basis that in almost every situation something has to be mobile, and hence have a thermal signature, in order to be a threat.

Only minor quibble would be that you generally want to have supplies carried be at least twice the max repair cost so that in-field repairs can be made. Still, as the ship has no active defences, if it is taking damage it is likely going to be destroyed outright rather than have the chance to repair.