Welcome to Steelbeasts.com

Register now to gain access to all of our features. Once registered and logged in, you will be able to contribute to this site by submitting your own content or replying to existing content. You'll be able to customize your profile, receive reputation points as a reward for submitting content, while also communicating with other members via your own private inbox, plus much more! This message will be removed once you have signed in.


  • Content count

  • Joined

  • Last visited

About Gibsonm

  • Rank
    Senior Member
  • Birthday

Personal Information

  • Location
    Sydney, Australia
  1. I think this could be included in the time a unit spends at a given location and for infantry be linked to the level of defensive positions. So if they are there for say over an hour (or as a start state for a unit) they could be under a shelter, then after maybe another hour be in some diggings, 12 hours more advanced diggings, 24 hours well developed postions. Its unlikely that a given scenario would run for that entire 24hour period with a unit static throughout but I guess it may have some application. You could do something similar with vehicle cam nets but then as well as allocating time to put the net up you need to allocate time (say 30mins) to pull it down and stow it. That is you might give a unit a route at say game time 2min, but it wouldn't actually move until game time 32min. I guess you could get it to go straight away (some dire situation) but then you couldn't put the net up in the new location as you had left it behind at the old one.
  2. Is there a chance that you inadvertantly copied say a downloaded woodland pattern for these vehicles (M1 and Bradley) into the desert folder?
  3. Well the scenario was set in 1991 and all my comments have been about that issue as it related to the scenario and the OP's comment. The only time I've strayed from that time frame was in response "Wilso845"s comment. I assume when you say "1991" above you mean OP GRANBY? That's not relevant to the scenario that started this discussion which is set in Germany in 1991 and has those same assets deployed throughout BOAR, not the one armoured division sent to the Gulf. The UK "emptied the shop" to ensure they had everything in theatre for GRANBY, even cannibalising vehicles in Germany for spares. So of course there are more AD weapons per fighting units. Just like in other smaller recent conflicts Bn units have Div sized allocations of ISR resources, etc. because only Bns were deployed. But that's another topic. If you want a tracked rapier with your tank troop, then SB lets you do that (albeit using a proxy for the Rapier). If you want manpads, place a bunch of RBS-70s in some APCs and have them move with the Infantry Platoon. But: 1. It's not accurate for 1991 - in Europe with a Cold War gone hot. 2. It's not how they operate in real life, where "scarce resources are controlled at the highest level". I suspect further comment on this from me is a waste of time.
  4. I'm sure you'll be welcome at BG ANZAC, Kanium, etc. if you want to "get some time up" in the meantime (and its a convenient time for you).
  5. Who is BG ANZAC? http://www.bganzac.org Described here: http://www.steelbeasts.com/sbforums/showthread.php?t=21753 A couple of examples of the BattleGroup at work: Multi Player session: Training session: So if you are interested, visit our web site http://www.bganzac.org and sign up. Timings: Thursday evenings, Australian time. So Daylight Saving has kicked in here and for the next 6 months the country is broken up into yet more time zones. Next meeting: 0830 GMT on Thursday, January 19th 0830 in London 1630 in Perth 1800 in Darwin 1900 in Adelaide 1930 in Sydney, Melbourne and Canberra 1830 in Brisbane 2130 in Auckland http://www.timeanddate.com/worldclock/fixedtime.html?iso=20170119T0830 This may need to be adjusted given the late start in NZ, perhaps moving to 0800 GMT? So a work around: Mission will start promptly at 0830 GMT. If you want a pre game "chat" then by all means come on line at say 0800 GMT, but so that the Kiwi's aren't after Midnight the Mission will commence promptly at 0830 GMT. Count down: http://www.timeanddate.com/countdown/generic?iso=20170119T0830 We continue the use of TeamViewer so people without the Steel Beasts software can connect and see and hear what we see and hear (looking over our shoulder if you like). http://www.teamviewer.com/en/index.aspx?pid=google.tv.s.au&gclid=CPLOveOGlcECFVgkvQodqk0A4g This maybe a suitable vehicle for people to see what the software is all about, without having to invest in even a short time limited copy. Anyway we'll see how it goes. Agenda: As always depends on sign ups but: 1. Possible re-run of a recent Kanium mission to see if we can get it to crash (or if its something to do with Kanium's setup). 2. Moving on to look at some sort of Offensive Ops scenario for the next planning cycle. 3. Discussion about Australia Day - Falls on a Thursday so will we have a night off? 4. Discussions regarding Rolling Thunder '17. As always, visitors / first timers / spectators are welcome. Current Standard: 4.010 Please use the new Calendar RSVP function to facilitate planning.
  6. Sure, the key word is "integral" in my quote. That means under command of the supported unit. I suspect you are confusing that with "integrated" where the radar, fire control system and missile are all on the one vehicle? How many tracked Rapier batteries under command (i.e owned by) CO 2 RTR or Royal Scots Dragoon Guards, or QDG? Zero. Sure the Brigade commander might allocate some of what he receives to a given BG, but the BG CO can't rely on having them 100% of the time.
  7. I think we covered this recently in another post (or maybe earlier in this one). Certainly many of the users of "professional" don't need it as they use products like "CNR-Sim" (or similar) or real radios to achieve comms. Teamspeak is fine with perhaps the only improvement being the ability to create sub channels on the fly but they used to have that (each VU had their own area) and had to remove it, I think due to abuse of the feature by some. All it really needs (IMHO) is: 1. People not to waffle (take 5 mins to say something that only needs 30 sec) or bang on about AI issues as opposed to the war at hand. 2. People to use their call signs and address comments to the relevant callsign. 3. People to listen out for their call sign and answer it.
  8. I suspect he was being polite or his request was lost in the mass of teamspeak traffic. The CO was a little overwhelmed with both managing the current battle and handing off reinforcements as they arrived. P.S.: MDF, there's a PM in your IN Box.
  9. I'm afraid there just isn't enough to go around for every Battlegroup to get their own "slice". If you look here (yes I know its open source): https://en.wikipedia.org/wiki/NORTHAG_wartime_structure_in_1989#7th_Panzer_Division You'll see that 7th Panzer Division has 36 Gepards between some 12 Pz or PzGdr Battalions and a mass of soft targets. Those rare AD assets go to protect large high value targets like Logistic hubs, HQs, key routes, defiles, etc. even if your Battalion got say 2 (say 6% of the Division's allocation), the CO is going to use it to protect the same stuff, his CSS and HQ. Your Tank Company has bu**er all chance of getting its own. Across NATO its a similar story: 1 British Corps (4 x Divisions) gets 2 Regts of Air defense - 24 Tracked Rapier (suitable for non static roles) and 72 Towed (key point defence). Fighting units, by and large, need to fend for themselves.
  10. When you compare say a Mark IV (of logo fame) - designed to cross wire and obstacles, with a low speed (6kph or so) and little/no suspension (resulting in few snag points / weaknesses) and most of the running gear covered in the hull, to a newer AFV designed to go a lot quicker, not optimised for wire and trench crossing and with a whole bunch of exposed shock absorbers, support arms, and other suspension components and sure you'll have issues. Just hitting a roll of wire at 40 kph vs 6 kph is going to be different.
  11. OK, so now all we need is: 1. The scenario file. 2. Where that unit tried to dismount its passengers (i.e. the grid reference). 3. When it tried to dismount (mission time).
  12. Unsure if it helps, but happy to run it at next BG ANZAC meeting (will need a copy of course). If someone can tell me which unit seems to cause the crash when it dismounts ATGMs (as well as where and when) we can focus on that. Would be a "clean" comparison (same Server exe but different machine, different participants, etc.)
  13. Chris, Did you look in your "downloads" folder area within the SB folder? If not I can send you a link tonight via TS (I know you wont be staying but perhaps you can drop in, get it and go)?
  14. Also the main heat source (jet exhaust) tends to reveal itself as the plane is flying away.