Matrix Games Forums

Forums  Register  Login  Photo Gallery  Member List  Search  Calendars  FAQ 

My Profile  Inbox  Address Book  My Subscription  My Forums  Log Out

Scenario#3 Typo

 
View related threads: (in this forum | in all forums)

Logged in as: Guest
Users viewing this topic: none
  Printable Version
All Forums >> [New Releases from Matrix Games] >> Command: Modern Operations series >> Command: DLCs >> Command: Desert Storm >> Scenario#3 Typo Page: [1]
Login
Message << Older Topic   Newer Topic >>
Scenario#3 Typo - 4/1/2019 5:48:38 PM   
Andrea G


Posts: 325
Joined: 10/9/2017
From: Genoa, Italy
Status: offline
Just a typo in the:

PROVISIONAL HQ SITREP 08-001 170000Z AUG 90

The first one.

Al Banteen is listed as located in Oman while it's in the UAE

_____________________________

Post #: 1
RE: Scenario#3 Typo - 4/1/2019 8:07:34 PM   
stilesw


Posts: 1497
Joined: 6/26/2014
From: Hansville, WA, USA
Status: offline
Andrea,

Thanks, fixed in next update.

-Wayne

(in reply to Andrea G)
Post #: 2
RE: Scenario#3 Typo - 4/3/2019 7:14:07 PM   
bns130

 

Posts: 18
Joined: 7/20/2013
Status: offline
Just saw this post …

Here is my post Mod … feel free to read and delete.

https://www.matrixgames.com/forums/tm.asp?m=4614575

(in reply to stilesw)
Post #: 3
RE: Scenario#3 Typo - 4/3/2019 9:52:21 PM   
stilesw


Posts: 1497
Joined: 6/26/2014
From: Hansville, WA, USA
Status: offline
Brad,

quote:

Al Bateen AB UAE in the wrong location. It appears that Abu Dhabi airport is also misplaced. Typo on spelling of Bateen AB as well. Really glad to see you guys create this historical content!


You are correct that Al Banteen should be spelled Al Bateen and be closer to Abu Dhabi City which is represented by an airport. According to Google Maps though, the City of Abu Dhabi is pretty much located where it should be. This misplacement/spelling is in many of the campaign's scenarios and will not likely be immediately changed. After months of testing and evaluation you are the first to catch (or at least comment on) this discrepancy.

Thanks for the input,

-Wayne Stiles

(in reply to bns130)
Post #: 4
RE: Scenario#3 Typo - 4/4/2019 1:43:20 AM   
bns130

 

Posts: 18
Joined: 7/20/2013
Status: offline
No problem Wayne. I thought the Abu Dhabi icon was for the International Airport. I did not Beta Test this one or I would have caught the Bateen issue months ago. The initial OOB for Bateen AB should be 16 C-130E of 50th TAS Little Rock and 5 EC-130 of 43rd ECS from Davis Monthan. I was one of many deployed Little Rock C-130 Navigators. What are you guys using for an OOB source document for your scenario development? I would love to read it!

(in reply to stilesw)
Post #: 5
RE: Scenario#3 Typo - 4/4/2019 2:19:27 PM   
stilesw


Posts: 1497
Joined: 6/26/2014
From: Hansville, WA, USA
Status: offline
Morning Brad,

quote:

No problem Wayne. I thought the Abu Dhabi icon was for the International Airport. I did not Beta Test this one or I would have caught the Bateen issue months ago. The initial OOB for Bateen AB should be 16 C-130E of 50th TAS Little Rock and 5 EC-130 of 43rd ECS from Davis Monthan. I was one of many deployed Little Rock C-130 Navigators. What are you guys using for an OOB source document for your scenario development? I would love to read it!


Well, my main source, especially early on, was the internet. One reference was https://en.wikipedia.org/wiki/Organization_of_United_States_Air_Force_Units_in_the_Gulf_War which interestingly shows the base in question as Headquarters: Al Banteen Air Base, Abu Dhabi, United Arab Emirates hence my incorrect spelling. There is a lot of "high level" information about the conflict in general but not so much when drilling down to unit details. This was one of the more informative ones. Actual callsign information is practically non-existent unless I could find someone who was actually there. This resulted in me using real callsigns for the aircraft types but not necessarily ones actually used in theater.

Initially, I had tried to include the complete Coalition complement of units and bases but quickly found that the resulting scenarios would be huge at 5+ Mb each, way too big for a campaign. So, I made a design decisions to populate bases, carriers and other things with a representative sample of appropriate aircraft. So, there are EC-130's at Banteen (Bateen). It is not 100% correct and there have to be many veterans of the conflict who will think, "Hey, this or that is not right". But, if players accept the fact that the campaign was created using Desert Shield/Storm as a foundation to build on then I think (hope) they will enjoy it.

BTW, at the time all this happened I was at Red Flag, Nellis AFB, supporting the training operations for USAF, USN, USMC and foreign fighter and support crews. I recall many of the Air Force guys stridently complaining about being stuck in the desert and missing the war!

Again, thanks for the comments,

-Wayne

(in reply to bns130)
Post #: 6
RE: Scenario#3 Typo - 4/4/2019 3:12:06 PM   
Sniper31


Posts: 132
Joined: 9/15/2015
Status: offline

quote:

ORIGINAL: stilesw

Morning Brad,

quote:

No problem Wayne. I thought the Abu Dhabi icon was for the International Airport. I did not Beta Test this one or I would have caught the Bateen issue months ago. The initial OOB for Bateen AB should be 16 C-130E of 50th TAS Little Rock and 5 EC-130 of 43rd ECS from Davis Monthan. I was one of many deployed Little Rock C-130 Navigators. What are you guys using for an OOB source document for your scenario development? I would love to read it!


Well, my main source, especially early on, was the internet. One reference was https://en.wikipedia.org/wiki/Organization_of_United_States_Air_Force_Units_in_the_Gulf_War which interestingly shows the base in question as Headquarters: Al Banteen Air Base, Abu Dhabi, United Arab Emirates hence my incorrect spelling. There is a lot of "high level" information about the conflict in general but not so much when drilling down to unit details. This was one of the more informative ones. Actual callsign information is practically non-existent unless I could find someone who was actually there. This resulted in me using real callsigns for the aircraft types but not necessarily ones actually used in theater.

Initially, I had tried to include the complete Coalition complement of units and bases but quickly found that the resulting scenarios would be huge at 5+ Mb each, way too big for a campaign. So, I made a design decisions to populate bases, carriers and other things with a representative sample of appropriate aircraft. So, there are EC-130's at Banteen (Bateen). It is not 100% correct and there have to be many veterans of the conflict who will think, "Hey, this or that is not right". But, if players accept the fact that the campaign was created using Desert Shield/Storm as a foundation to build on then I think (hope) they will enjoy it.

BTW, at the time all this happened I was at Red Flag, Nellis AFB, supporting the training operations for USAF, USN, USMC and foreign fighter and support crews. I recall many of the Air Force guys stridently complaining about being stuck in the desert and missing the war!

Again, thanks for the comments,

-Wayne



Greetings Wayne,

Well, as a Desert Shield/Storm Veteran myself, on a LRS Team (in the 101st Airborne, Air Assault, LRSD) do very much appreciate the work you have done on this DLC. I was on the ground, behind enemy lines, having crossed the FLOT with my team the night before the ground war started. Granted, a ground pounding Army Infantry guy, but being on a LRS Team, our mission profile(s) have us interacting with LOTS of U.S. and allied aircraft. For Desert Storm, our insertion was on UH-60 Blackhawks with AH-64 Apaches for escort, and once on the ground and in our surveillance position, we called in several A-10 Strikes as well as some work with an AC-130 Spectre gunship. To this day, as much excitement and adrenaline that were flowing through my 19 year old self back then, I for the life of me could not tell you one call sign from those days. After 28 years on Active service, there are so many possible call signs bouncing around in my head, it's ridiculous. So, at least for this Desert Storm Veteran, some small inaccuracies and flexible story freedom in your DLC does not bother me at all. At the end of the day, I am simply happy to read and play these scenarios, and enjoy the fact that they help me refresh some of my memories from those younger days in my life. That Sir, is more than I could ever expect to ask from a game or simulation.

Cheers!

-Landon

_____________________________

"I say again, expend ALL remaining in my perimeter!" - Platoon

"This is JB27, on target...fire for effect.." - Me

(in reply to stilesw)
Post #: 7
RE: Scenario#3 Typo - 4/4/2019 7:47:17 PM   
bns130

 

Posts: 18
Joined: 7/20/2013
Status: offline
Wayne,

I know what you mean trying to recreate the entire ATO for the Gulf War ... it has to be a labor of love. I understand the playability vs. realism constraints that you live under and don't want to appear critical. :-) As for Nellis, when it's your generation's time to join the fight; no worthy crew dawg wants to be sitting on the sidelines!

Cheers,

Brad

(in reply to Sniper31)
Post #: 8
RE: Scenario#3 Typo - 4/4/2019 11:00:44 PM   
stilesw


Posts: 1497
Joined: 6/26/2014
From: Hansville, WA, USA
Status: offline
Landon,

quote:

Well, as a Desert Shield/Storm Veteran myself, on a LRS Team (in the 101st Airborne, Air Assault, LRSD) do very much appreciate the work you have done on this DLC. I was on the ground, behind enemy lines, having crossed the FLOT with my team the night before the ground war started. Granted, a ground pounding Army Infantry guy, but being on a LRS Team, our mission profile(s) have us interacting with LOTS of U.S. and allied aircraft. For Desert Storm (Hey, IMHO, any troop on the ground - D-Day, Market Garden, Battle of the Bulge, Korea, Nam or anywhere in the Middle East deserves an absolutely tremendous level of credit and respect - AIN'T NO EASY JOB!, our insertion was on UH-60 Blackhawks with AH-64 Apaches for escort, and once on the ground and in our surveillance position, we called in several A-10 Strikes as well as some work with an AC-130 Spectre gunship. To this day, as much excitement and adrenaline that were flowing through my 19 year old self back then, I for the life of me could not tell you one call sign from those days. After 28 years on Active service, there are so many possible call signs bouncing around in my head, it's ridiculous. So, at least for this Desert Storm Veteran, some small inaccuracies and flexible story freedom in your DLC does not bother me at all. At the end of the day, I am simply happy to read and play these scenarios, and enjoy the fact that they help me refresh some of my memories from those younger days in my life. That Sir, is more than I could ever expect to ask from a game or simulation. (Thank you very much for the praise. For me to do it was a perfect storm of things - 20 year USAF, skill set (software) and interest. I loved doing it. Although, if I do another DLC it has to be somewhere else - pretty burned out on the Middle East :)


Thanks for the comments,

-Wayne Stiles

< Message edited by stilesw -- 4/4/2019 11:01:25 PM >

(in reply to Sniper31)
Post #: 9
Page:   [1]
All Forums >> [New Releases from Matrix Games] >> Command: Modern Operations series >> Command: DLCs >> Command: Desert Storm >> Scenario#3 Typo Page: [1]
Jump to:





New Messages No New Messages
Hot Topic w/ New Messages Hot Topic w/o New Messages
Locked w/ New Messages Locked w/o New Messages
 Post New Thread
 Reply to Message
 Post New Poll
 Submit Vote
 Delete My Own Post
 Delete My Own Thread
 Rate Posts


Forum Software © ASPPlayground.NET Advanced Edition 2.4.5 ANSI

1.594