Osric

I was hoping to access the weapon damage (etc.) values as well. Unfortunately all the db folder contains at the moment is an .h file (script?) and a 300kb binary file (not much at all). I would certainly like to know if the ability to do this is coming soon, or if we're just looking in the wrong place, or whatever the issue might be.

Authentic. Like Brie...

It could be a Czech word. ...Or you could just be over-thinking things. Simple test: what happened on September 11 2001?

I initially thought the scanner would let the equipped unit detect enemy units from further away (and display them on the mini-map). Blundering into an AT turret at full speed quickly dispelled THAT illusion! TBH I think giving it that exact function would be enough to make it viable rather than its current function of...umm...yeah. If it were to be moved to the No. 2 slot on the Walrus you would then only be able to equip the light weapons (GL, MG, Laser) since the heavy guns use slot 2. I'd like to keep the option of a scout Howitzer thanks.

The FPS sections would be fine bar BI's fetish with mouse acceleration that you can't turn off. Oh, and the cheesy voice acting, SO MUCH CHEESE!

What are your victory conditions set to? That might have something to do with it.Regards to the enemy Carrier running away: That's a problem I've had occurring in my current (Strategy) game a lot lately. The strangest thing is that when you arrive at a friendly island where the enemy carrier is present it runs away from the ISLAND not the your carrier. This difference was rather spectacularly demonstrated to me as he proceeded to go leave via the way I came; right through my Carrier and the two Walrus I had deployed (and I mean smash bash through me, not magical clipping)!

Something needs to be done about the mouse acceleration NOW. While I can normally deal with a little bit of mouse acceleration (e.g. Far Cry 2, BF3 etc.) there is so much in CC I cannot play the campaign because the disconnect between relative mouse movement and what actually happens on the screen is enough to make me motion sick. Not even the beta trick of switching off post-processing makes it bearable any more. Ugh.

On that note; I'm having trouble accessing the feedback area so who should I contact about that?

Currently Mantas can only refuel and rearm on the carrier. I'm guessing that may change given they're already programmed to '"land" once they get close enough to the ground but where and how is another story. That's what the beta's for I guess! Also what helipad are you landing on? Those spawn [enemy] Mantas! That must have been hell to pull off lol.

I look at the front end of a Walrus and immediately think of a Range Rover.

You guys tried re-downloading the beta file as well as re-installing? You could have just got a partially corrupt file (that was still good enough to install but the contents were totally borked).

To all those experiencing crashes there is a crash log in C:/Documents/CarrierCommand/Crash.txt. I'd advise shooting that to the feedback people so they can work on fixing it for the next build.

The small number of islands is only for the beta. Needless to say that's probably what's making production seem so slow as well.

Except the Walrus a re-purposed civilian vehicle. How many Vauxhalls have you seen win a fight with a tree? Besides the trees sway so damn nicely in the weather why would you want to knock them over?

The carrier running over Walruses I can understand (see HMAS Melbourne) however dropping things into the collision model is a problem. I just dropped a Walrus on the deck of my carrier and drove it around for a bit so that seems solid so how'd you drop a Walrus into the model? Perhaps the best solution is that units executing a docking command don't take collision damage with their own carrier?