Jump to content

Collingwood

Members
  • Posts

    344
  • Joined

  • Last visited

Posts posted by Collingwood

  1. On the subject of AFVs ramming each other: having in the past sustained various injuries in APCs from sudden lurches, barging into gullies un-announced (thanks driver) etc I would dread the result of crashing into a tank and coming to a sudden stop. Being inside with zero visibility it's hard enough surviving driving over terrain at speed, it's actually quite disorienting. I agree with the assessment of unacceptable risk to crew.

  2. Kind of strange that they have taken the pre-order announcement down....don't know whether that means a release is soon or there is a delay?

    Go to the front page http://battlefront.com

    Scroll down.

    The link to pre-order is still there.

    Or, click on "store" in the navigation bar, then click on CMRT. You can then "order now" and your only choice is pre-order.

    Meanwhile, this is the second "false alarm" thread already - only to be expected I guess.

  3. Thank you for the tantalizing look at what's coming up Steve. I've got a long term interest in Ukraine, Russian, Soviet history and although it's sad about current events, as your own plans for a game show, they're not a complete surprise to observers.

    It's completely understandable you're worried about cheap shots being levelled at BF (what's the military equivalent of ambulance chasing?) but given we knew about the upcoming game long before these events, as you say it's easy to prove you've simply been good at identifying a realistic scenario for a modern conflict. While most or all of us don't rejoice at recent events - I've actually been pretty upset by it all - it reflects well on BF's understanding of conflicts and what drives them, in other words you don't just go around making s41t up.

    With the imminent release of CMRT and with Black Sea hot on its heels, I tell you I'm in wargamer heaven. However and I don't say this just to be PC, I sincerely hope the closest I come to seeing the type of conflict we're discussing remains confined to my screen when I purchase the game.

  4. Here is a link to a great tutorial. It is for the earliest version, I believe, so some things may change in version 2+ (and maybe 1.10).

    Welcome to the best game there is!

    I was going to post the same link. It's an excellent tutorial for beginners to CMBN and it got me over the initial hurdle. It would be worth BF putting a link to it in their "thanks for your purchase" email, and/or as a link in a readme file in the demo download.

  5. Don't underestimate yourself. Your last sally left a gaping hole in my upper left breast. I calculate that it arrived from a N/E/E direction and was satirical in nature. ;)

    :D Placing puns wholly aside, in relation to the question: I play only wego, so my observations only apply to that. I will admit there are times when playing I will "rewind" the action several times because I am mystified as to where a shot came from.

    But I quite seriously can't imagine I am going to try to work out by zooming in on a decal, the precise angle etc the shot came from. More likely if I am being 'gamey' I will do it similar to what we see Chris (normal dude) doing in his showcasing of CMRT. Several times he rewinds to see "who did that" - admittedly most of the time he's trying to verify which one of his tanks got a hit, not where he was hit from. We were all marvelling over the hit decals, one tiger looked like it had a bad case of metallic measles.

    Very often we know if we've been hit from a particular side. Rewinding will usually confirm something like "from that tree-line over there". I could be wrong, but I sincerely doubt that close examination of the hit decal will reveal "it was a 76mm, it must have been entrenched because I estimate the trajectory to have originated no more than 18 inches from the ground, 2 inches to the right of the elderberry by that shrubbery 784.5 metres away".**

    Basically, were I to play h2h against someone and they wanted to use hit decals to try to triangulate my position, good luck to them and it wouldn't concern me. But I can understand why concerns have been raised.

    ** I am willing to run some tests if I can be sent the latest beta build (thanks)

  6. This is why I'm fascinated by the emergence of new financial technology like online crypto-currencies such as Bitcoin. They basically can't be frozen, and with proper security measures can be made anonymous.

    What I also find fascinating is that if you don't make proper security measures, you can lose close on half a billion dollars worth of Bitcoins a-la Mt Gox. No force required, just good hacking skills. I can imagine some very powerful players (and I don't mean banks) will be interested in that kind of power if someone over-exposes their assets - or even if they don't.

  7. Boy, am I ready for this game.

    It's a terrific way to showcase the game. Seeing CMRT actually being played is way more satisfying than screen grabs.

    I really appreciate Chris' effort to spend so much time with us the last 3 weeks, it's a great step forward in BF's communication with us. Not that they don't already listen and make themselves available on the forum - but this takes it to a new level.

    And, Chris has the right personality to pull this off. There are some people out there presenting other games that I can't take more than five minutes of, yet I think I've easily watched more than five hours of ND and look forward to next week.

  8. I can accept that the QB is what it is, in terms of AI plans etc, but the inability to get an interesting - surprising - small battle out of it kills it for me. The auto selector is never going to buy the AI a Pzgr company supported by a PzIV and 2 half tracks, you have to do it for it, which makes the scenario a grind against a known force composition where, once you have dealt with the known highest threats, you barely have to play properly anymore.

    Agreed. Which is one reason why I dream of the scenario file being xml format - or at least the force composition. This way I could define a set of acceptable and realistic forces to fight against, then script their (random) insertion into a battle.

  9. Part of the problem with AI plans in the QB was illustrated to me in the example I tried. I used a "Suggestion" for the AI side, and that included some Flak pieces (immobile).

    I confess, I often choose the AI forces for it.

    I have a suggestion for those of you with a circle of friends who like to play QBs: play each other HvH! :) But if you can't be doing with that, how about you set up QB opfors for each other?

    Great suggestion, which reminds me - There's something I've been working on for a while now: I set up a QB and choose all the forces. I then duplicate this, and vary the AI forces slightly. After I've got 3 or 4 QBs I put them into a folder, and have a script which randomly plucks one, and copies it with a new name into my scenarios folder/directory.

    End result: I still get a sensible AI force to play against - but I'm never sure exactly what it will be. No matter which scenario was chosen by the script it copies it to the same generic name so I don't tip myself off, so to speak.

    I have also been working on a similar idea to provide greater surprise value for scenarios.

×
×
  • Create New...