Jump to content

Gibsonm

Members
  • Posts

    19,455
  • Joined

  • Last visited

  • Days Won

    60

Everything posted by Gibsonm

  1. That sounds great! Much between that counting boxes in the Debugger and trying to work out the order for the sub task after the first one: 1 2 3 4 5 or 1 2 4 3 5 etc. And then having worked that out, closing it and then opening the event / condition to work on say the fourth sub task. This plus the "reverse look up" option would be a great outcome.
  2. Sorry I was unclear. I understand they are sub tasks / events/ ... all of which need to be satisfied before the overall item is satisfied. What I'm hoping for is something like: Event 16 has 5 sub-conditions something like (doubtful due to space constraints): In the Debugger you have an indication of: - Trigger 2 - Event 5 - Red Condition 2 - Condition 3 - Event 25 As a result, if the 4th check box is not checked you know that "Condition 3" hasn't been satisfied.
  3. I may have posted this previously and it maybe part of the Ver 5.x "rebuild", but .... Is there a possibility that we will be able to "audit" Triggers, Events and Conditions and find out where they are used? I'm currently revising / rebuilding someone else's work and unfortunately there are Triggers, Events and Conditions that may or may not be redundant. Is it possible to add a "Used by ..." button somewhere on here (or the new format), for Events Conditions and Triggers? The Debugger is great for telling me if an Event or Condition is satisfied, but I have no idea what the small sub check boxes relate to: And of course there are similar "full" screens for the other parties too.
  4. Or maybe not. The guy said "I don't know".
  5. You can do this via a work around: - Place IEDs. - Set to detonate at H>0. - Run the Mission. - Wait for explosions. - Do a "In progress save". Use that In progress save file as your new scenario baseline. Using that approach you can drop bridges, demolish / damage buildings, etc. The bigger the IED, the bigger the crater / damage:
  6. Daylight Saving now in effect and AS time zones have fractured. 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, March 14th. 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.
  7. In RL sure, but this isn't intended to be a "tank driving sim". I'm not aware of any "first parade" or "halt parade" mod or similar (in part because this would vary between vehicles).
  8. Thanks for the summary.
  9. AFAIK, the license you bought is limited to the version you had. That is, your license allows you to run the version you had in 2012, not the current 4.379. Given the 2012 time frame, before the introduction of time based licenses, then yes you need the dongle as the dongle contains your licensing information. If you want to use 4.379: - Then "yes" you need to buy a new license. - If you want a permanent license that you can move from machine to machine, yes you need the dongle. - If you want a time based license linked to a specific machine, there is no need for a dongle, but the license is not enduring (duration depends on which one you purchase). Details here: https://www.esimgames.com/3165-2/ I can't help with that one.
  10. Will be there. Happy to fill a role in whichever is the "non German" Platoon.
  11. Can you perhaps not use civilians but achieve a "civilian like" effect using using Infantry? This is an FO Team but with options to: Discard weapons if H>0 and "set look of Infantry" changed: Pretty sure they aren't "blind". 240311 Test of FO party.sce
  12. Hi, You may have tried this already, but assuming the civilians are "GREENFOR" (or a non Blue or Red colour) you could have them trigger events when (disregard the "engine off bit"): or Where "anywhere" is replaced by the NAI the spotters are looking at / operating in. You can add some dynamics to this too with say GREENFOR initially allied to Blue but becoming "enemy if ..." Blue does something silly - shoots at a location of cultural significance, indirect fire into an urban area, etc. This will also mean that while GREENFOR wont show up on the map, you'll have background "pattern of life" in the 3D world (that is Blue will need to report it).
  13. until
    Usual weekly meeting Refer relevant post in Multiplayer Engagements section for details. Global equivalent times: Your Local time Please use the RSVP function to facilitate planning.
  14. until
    Usual weekly meeting Refer relevant post in Multiplayer Engagements section for details. Global equivalent times: Your Local time Please use the RSVP function to facilitate planning.
  15. until
    Usual weekly meeting Refer relevant post in Multiplayer Engagements section for details. Global equivalent times: Your Local time Please use the RSVP function to facilitate planning.
  16. until
    Usual weekly meeting Refer relevant post in Multiplayer Engagements section for details. Global equivalent times: Your Local time Please use the RSVP function to facilitate planning.
  17. Daylight Saving now in effect and AS time zones have fractured. 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, February 29th. 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.
  18. Perhaps take a small sliver of that €100 billion special fund and get a Puma, Lynx, and Fennek?
  19. You might want to have a look here:
  20. Thanks for the option. Perhaps I'm doing it incorrectly but "reducing the colour saturation" requires me to adjust 19 icons, each of which has 3 sliders?
  21. Yes you could but as its a night mission, the contours at least give me a rough idea of the topography (slope, where is uphill?, etc.). In the last screenshot, the more Southern route requires the vehicles to go uphill, prior to WP593 and depending on the slope this is a "no go" for 4x4. 593 - 591 is at least traversing at the same height so all I need to worry about there are the trees and various bumps in the ground (lots of "a think I can" moments as the wheels spin and the vehicle inches forward). 591 - 592 - 132 is back down the slope.
  22. Thanks for the suggestion, how if I do that I now need to "squint harder" just to see the routes. Theme colours "on": Theme colours "off": We'll get there.
  23. Well you can do this: Using one of these (this is the Diamond option):
  24. Perhaps a Ver 5 thing: Is there anyway to include some sort on Terrain Analysis into the Mission Editor? I've spent months almost now on a project where I there is no simple way to see if a proposed route is viable. On first glance this looks like its viable, threading the needle between the swamp on the map and a similar one under the blue line: However after running it, it becomes clear that the "lillipads of death" extend well beyond the darker indicated area: This unit followed the designated route, its just that the impassable terrain was larger than the map graphic depicted. I'll now attempt a bypass, well to the South: I'm not after the full "not suitable for tracked vehicles, "not suitable for wheeled vehicles" type hatching, but a nice clear, accurate, red zone would be a great help though.
×
×
  • Create New...