Gibsonm

OK so that clashes with the "let's get this done and out the door" requirement. I only have so much "free" time in the day to devote to this project and my focus for the last X months on this one particular scenario has been fixing things to make it work. If I now divert time to look at this, we may get an answer but at the cost of this scenario not being ready for another X months and there are then 3 more to do after this one is "done".

It also may not reveal the issue if its something like computer resource usage. That is, simpler version doesn't tax the machine, therefore everything works as it should. Actual version imposes load on machine and generates erroneous behaviour. However the scenario is being run approx 3 times per day as we check fixes put in place for other errors, and clean up (trim) the current code so I'll try and keep my eye out for it. I've also put in mitigation by adding "reports of" and "will investigate" to the text so the Blue player isn't asking themselves "How are we getting this information when the helicopters are on the ground in the FARP?".

Sure. Sub-condition 1 (the region is empty of any Blue forces, let alone helicopters): Sub-condition 2: The US Stragglers event (the region is empty of friendly any forces):

I suspect "unusable" is a bit of an exaggeration. Yes its not powered (electric or hydraulic) but nor is the real thing.

I'm in the midst of shaping operations with GOC Home Command to invest around $2,000 Australian micro-pesos on a Tamiya 1:16 scale RC kit and a bit more on some after market steel components. I also have concerns re airbrushing (i.e. spend $ lots and then ruin kit with paint job). I may buy a sacrificial 1/16 scale kit to get my skills up to speed before doing the real thing.

Hi, I continue to receive messages from a True "event" though the preconditions are not satisfed. To the best of my knowledge the event "2. AVN spots US Nth" with an AND statement needs both check boxes ticked before its true. However I do receive the associated message and the Mission Debugger tells me Event 2 is "True" with no check boxes ticked?

There's nothing new about "suppressing the firer."

Perhaps I was unclear. I'm using the Mission Editor to test. 13/10 Spec is following a series of routes (yellow arrows "1"). It has the Pathfinding set to "Cross-country (vehicles)". My drawing is not the best but the route actually taken matches the plotted route. 15/10 Spec is meant to be following the route I've clicked on (magenta line highlighted with the purple oval "2") ending at WP818 (labelled in yellow - "OP Bridge 3"), using "Cross-country (personnel)" pathfinding. The actual route 15/10 Spec is taking is the black route (orange oval "3"), which is the same shape as the magenta one but offset by 10m or so. The rolling text at the bottom of the screen tells me it is heading for WP818, however on the ground (3D world) the soldiers actually end up at WP819 (at the T junction), not near the largish building. Its not copy and paste, more a comparison of "planned" vs "actual". It seems: If you use "Cross-country (vehicles)" for dismounts, "planned" = "actual". If you use "Cross-country (personnel)" for dismounts, "actual" is offset from "planned" by several metres.

I usually use "Cross-country (personnel)" for dismounts. However I've just noticed that sometimes they seem to be displaced: 13/10 Spec (near arrow) is using "Cross-country (vehicles)" and the unit is moving exactly in line with the plotted route. 15/10 Spec (near blue dashed line) appears offset: Route is the highlighted purple. Actual path being taken by the unit is the black line. The route is identical just offset. The report indicates that 15/10 Spec is moving to WP818, but in reality it will end up near WP819.

Daylight Saving now over and AS time zones have re-aligned. 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 0900 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 0900 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: 0900 GMT on Thursday, April 11th. 1000 in London (BST) 1700 in Perth 1830 in Darwin 1830 in Adelaide 1900 in Brisbane 1900 in Sydney, Melbourne, Canberra 2100 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.

Another great session. Well worth getting up at 0430 for here. Next week it gets even better with a 0330 kick off.

Fixed.

Thank you. Glad I asked.

Can I confirm its still "1900 GMT" for you post Daylight Savings?

I'm not overly worried if you agree or not. As for the helicopter, I can't help you if that's what the scenario designer built. Perhaps instead of a "tree line" use a forest, or put in a review or comment, or give it less than "5 stars" ...

Economy of effort 1 x DM11 round: 1 x Tank destroyed, 1 x BMP damaged: What are "Friends" for:

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.