RT

Open the RTM in the VID and press 9 to display MISC targets in the TRS, I think by default they are filtered out.

Unluckily no, and there's no evidence whatsoever that anyone is going to ever make it :/

Please give the exact size of the AAW.exe file, eg: Size : 3.79 MB (3,976,704 bytes).

First of all, I need to know what version you're using, IE where you bought it from. There are several versions, and they all work slightly differently, so this error message may pop up for different reasons if you bought it from Steam or from other online distributors.

Magnus and I used to meet on IRC, but I haven't gone there in a month at least.

The AI ships travelling to a specific destination will always continue with their mission, regardless of what you do. Once their task is done however, they'll likely return to SAD stance, which then means they'll engage close by hostiles (that is, unless they were on a DOCK or FLEE order in which case they'll dock to a station/planetfall, removing them from the game world). Of course AI ships ESCORTing or DEFENDing another ship will engage you if you target that ship, PATROLing ships will most likely come after you too. And as you noticed, PTAs will fire at ennemy targets in range, regardless of the ship's target or mission, since PTA turrets have their own targets matrix and engagement rules.

I guess this wasn't quite clear. Actually this is only usefull to owners of a Thrustmaster HOTAS cougar joystick. This is basically a file which explains this quite advanced joystick how to behave. If you don't own such a joystick, these files wont be of any use to you though.

These are some great color schemes! Nice work. Will you release some texture packs whe nyou got some more?

Nice! Btw, have the shield FX been removed completely, or will they be back in the later games?

I've no idea what is causing this graphical error. However, you can set your joystick as your primary controller by opening the ucconfig.ini file, and looking for the Controller entry. Setting it to 1 will make the joystick your controller IIRC. You can even change your key mapping there, but you will have to experiment a bit as to what joystick button is which. Most of the time, the trigger is button1, which should be a good start! Now, I'd rather recommend you buy UCCE, which is supported and works just fine

I spent a couple hours creating an AAW/AOA profile for my hotas cougar. If any of you are interested, here's the MediaFire link. You can check the layout directly here. This archive contains: AAW.tmj AAW.tmm AAW.jpg If you have a cougar, chances are you already know how to use them. If not, drop me a PM. Those files are of course free of any virus. NB: You may notice that some (3 actually) buttons aren't used: my Cougar is getting old, and those 3 keys aren't working anymore. I'll eventually fix it, but feel free to alter the files according to your own cougar.

Very good news that you'll indeed resume work on KB! Guess that will bring back a lot of all those old timers!

Oh, the countless times I bought games on Steam, feeling a bit ashamed of myself for spending hard-earned money on video games I most likely wont play for more than a dozen hours

I uninstalled the beta build (you invalidated all the beta keys, right?), and as I was wanting to test and reproduce some annoyances I noticed some times ago during MP, I downloaded the demo, since it's obviously what everybody's currently running. This is no problem, I'll wait untill the demo is updated. I haven't contacted Sho yet to schedule a mp session anyway.

So I downloaded the demo today from the AAW media page, installed it and ran it to play a bit of MP. Unluckily, whenever I try to join one of the 5 servers, I get a version mismatch error: " client version:'demo' server version:'1.00.17 demo' ". I'm pretty sure I got the latest, full demo from that page, tried getting it from 3 mirrors already, but none of them seem to have the correct version number. Am I missing something obvious or... ?

Actually I turned them off, as they were spinning too fast for my taste. I'm just fine without them (though I sometimes feel the need to run the game with default settings, just to get that feeling once in a while...The same need that sometimes makes me fire up again BC millenium gold D:)

Capturing stations is tricky at first, but you wil lget the hang of it. There are lots of topics covering this matter on this forum, but here's what I do: Fire 100% IOD at the station untill armor gets down to 4-300, then switch IOD to 10% power. Gently bring it down to <30 armor, and carefully watch the numbers right below the target's name and classification in the VDD in VID mode, these are the target's sub-systems status; hangar, engines, weapons, reactor. If any of those is down to 0, the station blows up.

Thanks guys! I had a very nice day, and it's a real pleasure to see people on this board care too! 22y-o, I now feel a bit closer to you dinosau...err, veterans

Best when you capture a station is to stay around for a while untill it gets back to full strength.

Maybe if you posted your config we could help you. Also, you can run the game in fullscreen in a lower resolution instead of windowed. Windowed tends to impact your FPS in most games.

What game does this exactly happen with, and what version? I think I experienced such a CTD when resizing the perscan window a while ago, but it only happened once (most likely I didn't bothered trying to reproduce it). This is strange as the perscan log is often split into two tables and I'm positive expanding it doesn't crash as I do it often. I'll investigate once you give more info.

Confirmed, you can't launch probes using the Engstrom.

Happy one Wolferz!

Star wars, when I was like 6 or 7. My father was a big 2001 fan too, so that helped I guess.

Starbases were ALREADY in the game, several scenarios request that you either protect or destroy one. They're not starstations, and the difference has always been crystal clear in all the 3000ad games; ground (big) building.