Other Means

This guy doesn't know what he's on about. That only does 3 pages at a time and it seems to save as one big image. Wanker.

This tool, with a free no-registration 7 day trial, converts PDF's to Word. http://www.investintech.com/prod_downloadsa2e.htm

You can save a TXT version from the "File" menu. Loses all the images but what the hey, it only takes a second. And this manual is FUGLY.

Streamlined? One key is quicker to press than 2. I mean, the clue's in the question really Can I refer you to: *Can be remembered through repetition. Still faster than pressing 2 keys 2 key presses etc. Eyes must go to key display to check what is active. I disagree, as it takes 2 key presses. 2 Key presses is a key press more than one key press. One key...I'm boring myself here. I've never played an FPS that doubles key usage. Nah, just give a command to a key. Crazy I know, but it just might work.

I think it's just to get everything on the number pad, which means I'd be playing with my hands about 3cm apart - not comfy. Not a bad idea, as far as it goes. But I'd like to remove the need to do so. How? Navigating a web page, using a program, any HCI really, all done by muscle memory (past a certain level of experience). Also, if you're playing like I do, you give a unit orders, move and target, or set arc, then go on to the next. So with a 2 click/press system you're doubling your hands workload, as well as breaking concentration on tactics to use the UI (check current usage of button group) and it's that bit that really annoys. You shouldn't have any difficulty with 27 separate button usages on a kbd, I've got that many on my phone.

The main problem is the multiple use of a single key. There's enough keys to not do this on a full sized PC kbd so I think that's what should be done. I'm not too concerned with having them under easily remembered keys - that will come. Just spread them out on the kbd. Even if it was top (or possibly F) row movement, 2nd row combat etc. That way you're never 2 presses from anything. Flight sims have managed it for years, it shouldn't be an issue here.

The re-grouping is definitely broken. I've had a whole squad want to "quick" 200m back to one casualty, under fire the whole way, while fatigued. So annoying. A lot of little things like that need fixing. On the whole though, having a blast.

It struck me last night that with 1 - 1 you can't get the squad size increasing like it used to, so you're getting a lot of your info from the icons. If it even went so far as to have a "standing", "pinned" icon for the squad we could see how it was going.

I'd like it. I love the icons and use them all the time (now I've got the SF working, finally) and I think it'd be a great idea if there was some more information given in them, like casualties etc. I remember CC used to have this and it was a great help. Last on the list, I'm sure, but I'd find it useful.

No this is fine, you capture the unit and interrogate...and no, no, you're right - terrible bug.

Don't you know that you're my heeeeroooooh you are the wing beneath my wiiiingsss.

I think Matt's got it in his sig, I'll check it out, cheers.

Thing is, Kwazydog recommended it to me, now I in no way hold him responsible or feel BFC owes me anything for this, and I'm equally sure that it'll get fixed - I just think it's a little ironic.

Unless it doesn't have a weapon, in which case, no targeting.

I had it working on a P4 2G, 500M RAM and a GF4600. Amazingly.

Implying something sport?

Intel® Core2 Duo CPU E6850 @ 3.00GHz, 2.00GB DDR2 Conroe RAM Gf 8800GTS

My old 2G P4 ran SF. Very badly, but it ran it. So I ordered a new one last week - got it - built it tue & wed night. Got my uber geek mate to come find out what I did wrong tonight - now it's working. Brilliantly. Half Life 2 looks amazing. SF crashes when I finish the order phase. So I've spent ~£550 ($1100) on a machine that runs a game I'm bored of, but not what I wanted. *sigh* HL really does look amazing though.

No talk of features there. I'd expect the announcement to be a release date and feature list, the release date will be unclear unless you're really close because sometimes it's impossible to say how long something will take. But they will already have a feature list because they'll have gone through and proritised what to do. So I was asking if they felt like sharing.

And if so, can you share it? Even if not final, can you give us an idea of what you're looking at. No assumptions to be made that it will actually fix the bugs listed.

BTW I'm loving the unit indicators.

In affect, it's just turning the game into a memory test. Click on the map, see all the unit markers, memorise where you need to fire, click on your unit, fire at the area. So I think the ordering of area fire should go through C&C, if possible, to simulate the fact that a unit calls for it, but that call needs to go through the commander and back down to the support units. It may look a little funky, but here's what I mean (bear in mind I've not had a real chance to play the game yet because my machine is stone age - I'm building my new one currently). Unit A sees a unit marker in some cover. You as the player know there's a unit there. Currently you order your MG's to fire on this area and suppress whatever is in there. You are Queen Borg. What would be good is you order support fire, but there is a delay based on the shortest C&C time of all the units spotting any enemy unit marker in the area to HQ, to support unit. Unit A sees a unit marker. You as Queen Borg order area fire on the area. The game simulates the delay of getting an order to HQ and from HQ to the support units. A possible outcome being if Unit A has no CoC to HQ, it can't ask for area fire. I think this is a good result. Prep fire wouldn't suffer from this - so in effect it's quicker to area fire before there's a marker there. But I think this is a reasonable trade off, prep fire would be planned, while covering fire is reactive. I'd like to see CoC indicated a bit better too. So you can have movement, target and CoC indicators, showing where units are going, what they're shooting at, and who's telling them to do so. Just my half a shekel.

Yes. Your eyes would be tired if they were in a drawer somewhere, next to the gobstoppers.

Having been a dev, and under immense pressure at times, I know what it's like to be dreaming in code, then waking up and all your beautiful fixes evaporate. And rushing - whoa, not that I'm implying anything, I'm talking about myself here - rushing code out the door when I knew better than the users the problems they'd face but being forced to do it anyway. So. I've a cheeky red here that I'll raise and toast "Le Patch, Le fiole, Le Roi!". And may god have mercy on his poor tired eyes.

I think it's an excellent approach and the beloved blue bar will be forgotten quicker than you think. I'd like the option of not watching the replay though. It throws me going into it straight away.