Gibsonm

Pretty much a trade off. M1 family, turret remains facing the frontal arc (mostly) but not fast. Leo 2s, turret traverses off but faster. Ideally for both you pull back into dead ground if you can, before you start the process.

1. Dare I say the AI's spotting ability is well known. Where possible use terrain (hills, etc.) rather than vegetation as detecting one pixel can result in target acquisition by the AI. 2. Yes, don't use time acceleration.

Two points if I can: 1. The "loading process" on the range or under combat conditions is the same. Modern, Cellulose cased ammunition, is not designed to be "lap loaded". It risks tearing (as oppose to older Brass cased). 2. A tank is not designed as an anti helicopter platform. If you have to, fire once or twice, then move, then engage again. If you don't have to, passive air defence is better.

Yes its on the vehicle: Then you can specify, if in region X and repair vehicle Y is too and elapsed time is Z and not under direct or Indirect fire, ...:

Pretty sure if can be as long as the scenario designer has ticked the relevant boxes in the "Repair if ..." condition.

Daylight Saving now in effect and AS time zones have fractured. Good news is this is the last one before we go back to "normal". By now most readers will already know who BG ANZAC is, so I'll put the information relevant to this week in first, then background, etc. If you are new to the Forum, feel free to read the entire post. IMPORTANT: As a serving Officer, I am not allowed to make "public comment" about topics without clearance. This is why my signature block says what it says to cover written comment. Recorded audio on YouTube = "Public Comment", especially if I were to express a personal opinion (without knowing someone was recording). In addition recording people's voices in Australia is illegal without their permission or a Warrant. If you want to record a session, ASK! We maybe about fit you in (I maybe able to play the OPFOR, etc.). If you don't ask: a. Expect me to ask you to remove the YouTube (or other media). b. Don't be too surprised if you aren't welcomed back. BLUF (Bottom Line Up Front): Your Local time: Click on this link for Local time in your part of the world Count down: Time remaining until Meeting start Mission will start promptly at 0830 GMT. If you want a pre game "chat" then by all means come on line at say 0830 GMT, but so that the Kiwi's aren't after Midnight, the Mission will commence promptly at 0830 GMT. Agenda: Based on the recent sustained good attendance, we are embarking on a more structured approach (only sustainable if the attendance is maintained). Planned Agenda: 1st meeting: Teach / Discuss a topic (Attack, Defence, Convoy Escort, Reserve Demolition, OPs, ...) using a scenario / map as the basis for discussion. As to what we cover, that will be will be determined by the response to the related email "newsletter" for this Wednesday sent to regular attendees. 2nd meeting: First volunteer develops a plan for the tactical problem and we see how they go. There will be a brief debrief at the end looking at strengths / weaknesses of their solution, which the person COing the next week is free to incorporate into their solution. 3rd meeting: We play the same scenario with a different CO (each able to improve / adjust their plan based on their predecessor). 4th meeting: We play the same scenario with a different CO (each able to improve / adjust their plan based on their predecessor). 5th meeting (if there is one in a given month): Q & A - You need to supply the questions or a "player's choice" determined by responses here / to email. As always, visitors (apart from one individual) / first timers / spectators are welcome. Current Standard: 4.379 Refer here: Please use the new Calendar RSVP function or post here to facilitate planning. Background: Who is BG ANZAC? https://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: Timings: Thursday evenings, Australian East Coast time. Daylight Saving has started and the number of time zones has increased. Next meeting: 0830 GMT on Thursday, April 4th. 0830 in London (GMT / Zulu) 1630 in Perth 1800 in Darwin 1900 in Adelaide 1830 in Brisbane 1930 in Sydney, Melbourne, Canberra 2130 NZST in Auckland In game chat / Communications: You'll need access to "Teamspeak" to communicate with us. The Teamspeak software is available here: Download Teamspeak client software How to connect and use it is detailed here: Steel Beasts Wiki Entry - Starter Pack Primary = eSim Teamspeak. 216.22.24.158 Alternate = BG ANZAC Teamspeak. 144.130.10.25 Contingency = BG ANZAC Discord. Emergency = Perhaps Teamviewer? Remote Access / Screen Sharing / Whiteboard Sessions: 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). Team Viewer available here This maybe a suitable vehicle for people to see what the software is all about (you can even use it on a Mac), without having to invest in even a short time limited copy. Anyway we'll see how it goes. So if you are interested, visit our Discord site https://discord.gg/YyrUtH3 and sign up.

In real life, yes. A scenario designer can emulate it if they wish - refer above.

You as the tactical commander (i.e SB Pro PE Player) do not have "all the resources". Usually repairs are addressed by time / resources. Things you can influence: Simple repairs - crew tasks like fixing track that can be done within X time is done by the crew. If they can't do it they call for support. Slightly more complex repairs - that can be done by a recovery vehicle helping the crew. These are limited by time. Its better to have a recovery vehicle spend 2 hours fixing 4 different vehicles than spend 2 hours on one. If a vehicle can not be made "battleworthy" (not perfect, just "good enough") the vehicle is towed back for field repair. Assuming the scenario designer has added suitable units, setup Repair zones, etc. and the duration of the scenario is long enough: More complex repairs - The vehicle is recovered back to the next level of repair (say 5 - 10km behind the shooting) where dedicated mechanics work on it with white light, hard standing, overhead cover, etc. If they can't repair it in the time allocated, again its recovered further back. Things you can not influence: Yet more complex repairs - The vehicle is recovered still further back and things like turret lifts are undertaken (for other readers I know you could do this forward, but I'm trying to provide a simple overview). Again, if they can't repair it in the time allocated, again its recovered still further back. At this point the crew is usually given a replacement vehicle, if available, and get back into the fight. Very complex repairs - The vehicle is recovered still further back to a major repair facility. Still not fixed - likely to be cannibalised (working parts taken off the vehicle and used to repair others). This assessment is made throughout the process. This triage approach is similar to that used in the medical system.

As to the first question, sure, but .... 1. Recovery to base workshops (usually a reasonable distance behind the front lines) 2. Repair (assuming they have parts). 3. Bringing back forward. 4. Re-crewing ... 5. Re-ammunitioning ... Tend to be beyond the time scale of the average mission. Not many magic wands here.

So to be clear: 1800 GMT.

Do I need to repeat my availability here, or are you just going to use the entries already posted in the other thread? Also is it actually "World clock 1900 GMT"? Clicking on that link displays:

I don't care if its open source, its the country of origin. Why would I bloat my computer with steam? So the Mission Editor doesn't work, the map transfer tool doesn't work - basically it doesn't work.

I'm unsure when your cut off for responses is, but I suspect its looking unlikely at this stage?

Glad you got it to work. I have no intention of putting Russian or Chinese software on my computer though.

I can make it.

If mine has somehow been changed - that's fine, I'll change it back. I just wanted to confirm the process for the scenario's briefing. Thanks for clearing it up.

Grenny, This is a rare Monday I can join. Unfortunately it appears the Bluefor has no CSS. Hope no one stubs a toe. Sorry - Disregard I didn't realise you skipped a week.

Oooh a "sleep in Saturday" for me. Enjoy your break!

Except of course people would probably want to be able to deploy infantry in the building, which implies access points, floors, windows to shoot from, roof, etc. not just a blob that you could "stretch to fit".

Thanks I'll let him know.