Jump to content

Gibsonm

Members
  • Content Count

    16,200
  • Joined

  • Last visited

About Gibsonm

Personal Information

  • Location
    Canberra, Australia

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. I tried opening it in 4.023 and received an error about "It maybe incompatible or its artwork (map) resources may be missing". The log provided: [13:45:49,738] WARN : ------------------------------- [13:45:49,738] WARN : Steel Beasts Log File v4.023 [13:45:49,739] WARN : Sun Oct 13 13:45:49 201 / 21484 [13:45:49,739] WARN : ------------------------------- [13:45:49,739] WARN : +--+ MEMORY USAGE INFO (SteelBeasts START): [13:45:49,739] WARN : | | Process: 4.3 GB (0 % of 128.0 TB total, 128.0 TB free) 4.3 GB min/4.2 GB max [13:45:49,739] WARN : | | Physical: 11.6 GB (24 % of 48.0 GB total, 36.3 GB free) 11.6 GB min/11.6 GB max [13:45:49,739] WARN : +--+ Pagefile: 15.6 GB (25 % of 62.0 GB total, 46.3 GB free) 15.5 GB min/15.6 GB max [13:46:00,543] WARN : +--+ MEMORY USAGE INFO (LoadFileInScenarioEditor start): [13:46:00,543] WARN : | | Process: 5.3 GB (0 % of 128.0 TB total, 128.0 TB free) 4.3 GB min/5.3 GB max [13:46:00,543] WARN : | | Physical: 12.3 GB (26 % of 48.0 GB total, 35.6 GB free) 11.6 GB min/12.3 GB max [13:46:00,543] WARN : +--+ Pagefile: 16.6 GB (27 % of 62.0 GB total, 45.4 GB free) 15.5 GB min/16.6 GB max [13:46:09,480] WARN : +--+ MEMORY USAGE INFO (LoadFileInScenarioEditor end): [13:46:09,480] WARN : | | Process: 5.7 GB (0 % of 128.0 TB total, 128.0 TB free) 4.3 GB min/5.7 GB max [13:46:09,480] WARN : | | Physical: 12.8 GB (27 % of 48.0 GB total, 35.2 GB free) 11.6 GB min/12.8 GB max [13:46:09,480] WARN : +--+ Pagefile: 17.0 GB (27 % of 62.0 GB total, 45.0 GB free) 15.5 GB min/17.0 GB max [13:46:46,584] WARN : +--+ MEMORY USAGE INFO (LoadFileInScenarioEditor start): [13:46:46,584] WARN : | | Process: 5.7 GB (0 % of 128.0 TB total, 128.0 TB free) 4.3 GB min/5.7 GB max [13:46:46,584] WARN : | | Physical: 12.8 GB (27 % of 48.0 GB total, 35.2 GB free) 11.6 GB min/12.8 GB max [13:46:46,584] WARN : +--+ Pagefile: 17.0 GB (27 % of 62.0 GB total, 45.0 GB free) 15.5 GB min/17.0 GB max [13:46:50,305] ERROR: Unknown type (0x24). Cannot create unit! [13:46:50,305] ERROR: Invalid formation size 'Size: 1; 0x80024, '! [13:47:04,548] WARN : +--+ MEMORY USAGE INFO (LoadFileInScenarioEditor end): [13:47:04,548] WARN : | | Process: 6.0 GB (0 % of 128.0 TB total, 128.0 TB free) 4.3 GB min/6.0 GB max [13:47:04,548] WARN : | | Physical: 13.0 GB (27 % of 48.0 GB total, 35.0 GB free) 11.6 GB min/13.0 GB max [13:47:04,548] WARN : +--+ Pagefile: 17.2 GB (28 % of 62.0 GB total, 44.8 GB free) 15.5 GB min/17.2 GB max [13:47:39,166] WARN : +--+ MEMORY USAGE INFO (LoadFileToPlay start): [13:47:39,166] WARN : | | Process: 5.9 GB (0 % of 128.0 TB total, 128.0 TB free) 4.3 GB min/6.0 GB max [13:47:39,166] WARN : | | Physical: 12.7 GB (26 % of 48.0 GB total, 35.3 GB free) 11.6 GB min/13.0 GB max [13:47:39,166] WARN : +--+ Pagefile: 16.9 GB (27 % of 62.0 GB total, 45.1 GB free) 15.5 GB min/17.2 GB max [13:47:43,241] ERROR: Unknown type (0x24). Cannot create unit! [13:47:43,241] ERROR: Invalid formation size 'Size: 1; 0x80024, '! [13:47:43,242] ERROR: CGame::ReadScenarioFromFile failed [13:47:43,242] ERROR: Error setting up new game! [13:47:51,487] WARN : +--+ MEMORY USAGE INFO (SteelBeasts END): [13:47:51,487] WARN : | | Process: 5.7 GB (0 % of 128.0 TB total, 128.0 TB free) 4.3 GB min/6.0 GB max [13:47:51,487] WARN : | | Physical: 12.3 GB (26 % of 48.0 GB total, 35.7 GB free) 11.6 GB min/13.0 GB max [13:47:51,487] WARN : +--+ Pagefile: 16.4 GB (26 % of 62.0 GB total, 45.5 GB free) 15.5 GB min/17.2 GB max [13:47:51,552] WARN : Done My guess is that is uses a unit that perhaps no longer exists. Trying to open in it SB Pro 3.3X had the same outcome. I'm afraid my copies of 2.654 and earlier have been archived.
  2. Gibsonm

    We love photos

    Its called the roof. We have become adept over time with "external stowage". Although it got to the point that we needed to add a vehicle to some organisations to support extended patrolling (e.g. a Cav Troop) where the 1 x APC has been replaced with 2 x APC (each carrying half a section) but also carrying the additional "stuff" required.
  3. Australia has moved to Daylight Savings and accordingly out Time Zones have bomb burst into Daylight Saving time (since not all states adopt it). 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 the 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 0800 GMT, but so that the Kiwi's aren't after Midnight, the Mission will commence promptly at 0830 GMT. Agenda: If you did not attend last week, arrive a little early so we can get you the required map package. 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 Thursday: 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 Thursday sent to regular attendees. 2nd Thursday: 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 Thursday: We play the same scenario with a different CO (each able to improve / adjust their plan based on their predecessor). 4th Thursday: We play the same scenario with a different CO (each able to improve / adjust their plan based on their predecessor). 5th Thursday (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.161 (either download from scratch or download and install 4.156, then patch to 4.161) 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. Next meeting: 0830 GMT on Thursday, October 10th. 0930 in London 1630 in Perth 1800 in Darwin 1900 in Adelaide 1830 in Brisbane 1930 in Sydney, Melbourne, Canberra 2130 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 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 web site https://www.bganzac.org and sign up.
  4. @Striker I'm sorry but I'm finding this map very problematic esp. where the bridges are concerned. Admittedly the scenario I'm working on has some snow but I don't believe it should impact routes crossing bridges. For example (there about six bridges that exhibit similar behaviour) 1. Route: Between waypoints 135 and 136 I used "Shift click" to lock the route to the road and have used a March command in column formation. Yet the BRDM consistently swerves off the road, fords the river and then spends the rest of the time trying to get back onto the road "through" the side of the bridge. The spawned civilian traffic is even worse since I can't give it routes. 2. End result 3D world: I've even had to resort to re-routing road traffic across railway links to ensure that they actually work: I'm unsure what has gone astray compared to the old map? I hate to say it but I'll take a working map over a pretty one every time.
  5. Ah ok. My issue is slightly different and happens during the conversion / update process: 4.023: 4.157: But as Ssnake mentioned, they are looking into it (as well as towns that disappear).
  6. Gibsonm

    We love photos

    They probably need more than nine rounds.
  7. Thank you @Lumituisku, I was starting to think I was the only one.
  8. until

    DELAYED! Standby for revised date / timing.
  9. I'm going with COA 2 "Delay". Once the package approaches completion I'll start a new poll to select the "least worse" dates / times. Again sorry for those who re-worked their schedule around this.
  10. Gibsonm

    BURBS Spotted

    Do they need more than one? I thought the RAC was now time sharing vehicles between the Regts?
  11. An update of sorts. For a variety of reasons (one person with numerous competing tasks [work, family, personal, SB, ...]) the series of scenarios planned for Rolling Thunder '19 will not be finished in time, let alone the supporting documents, OPORDs, etc. Even if I rushed through some half baked work (not my preference) we still need to fill manning slots and allow time for potential commanders to develop plans etc. There are therefore two COAs available. COA 1: Proceed. Recycle some earlier Rolling Thunder product, with patching to ensure it at least runs in 4.161. Pros: Something will happen this weekend. I appreciate the effort made by those to re-arrange work shifts, etc. There is supporting product (OPORDs, etc.) ready. Updating the scenarios should be straight forward (update map links, etc.). Cons: Recycled product, no suprises, potentially doesn't take advantage of new features, may lead to "templating" by previous participants. Impact of new modelling unknown (scenarios maybe broken by new maps, AI behaviours, etc.) and wont be discovered prior due to lack of testing time. COA 2: Delay. Continue to develop Rolling Thunder '19 product, and present a properly finished series of scenarios with briefings, etc. Pros: Avoids the time crunch. Better experience. New scenarios (challenges, etc.) and takes advantage of 4.1xx features. Depending on the date selected may allow some who couldn't make this weekend to attend. Cons: Disappointment. Some people have made sacrifices / arrangements for something not happening. Need to determine a new date *. * Previous RTs have taken advantage of long weekends here in Australia. The logic being that getting up at 0200 to run them (so that the GMT time was "nice") was offset by not having to go to work on the Monday. Unfortunately the next Public Holiday here in Australia is the Christmas Break. I'm assuming most here will be away / unavailable based on past attempts to run "ad hoc" events and / or Q& A Tutorial sessions over the Christmas / New Year's break. After that its Australia Day on the 26th of January. I maybe able to run it earlier but I'd rather not consume 50% of a normal weekend. Questions: 1. COA 1 or COA 2? 2. If COA 2, are people happy to wait for late Jan '20? The sweetner would be we'd be running RT'19 in Jan and RT'20 in June or October. Depending on the response, I'll post something here on Thursday 03 OCT 19 my time advising which COA will be adopted. If COA 1 proceeds, people should be prepared for rushed planning and uncertain scenario performance.
  12. Gibsonm

    BG ANZAC

    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.
  13. Gibsonm

    BG ANZAC

    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. Gibsonm

    BG ANZAC

    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.
×
×
  • Create New...