U-2 Discussion / Use of U-2 in scenarios

[TheOttoman]

That's kinda sorta brilliant!

[TheOttoman]

I've submitted the first database request, for the U-2G in the Cold War thread.

It's fairly straightforward and there aren't too many changes. Mainly cleaning up service dates, take-off / landing data, some properties and coms.


This is easy because there were only three made, they all had the same basic camera package. Two were used for testing (#56-6681/6682),and a third was used in Operation Fish Hawk, which took pictures of French preparations for a nuclear weapons test in Tahiti on 19 May 1964 (#56-6718).


While it's possible for the U-2G to operate from a carrier. It's impractical. All other carrier operations must be halted while the plane is onboard because it must remain on the deck of the ship. IT had no folding wings, so it could not be stored on the hanger deck. But I guess if you want to really have a U-2 operate off of a carrier, or win at stupid bar trivia, I present the U-2G.

I mean, I didn't believe it until I actually saw it... so here:
https://www.youtube.com/watch?v=L8HMPMYL19E

[SeaQueen]

ORIGINAL: TheOttoman
The completely modularity / one off builds is what turned me on to the platform. It's staggering at the amount of uniqueness found throughout the fleet, especially during the mid-80's. To be able to manage that effectively, on a global level is insane.

Given that it's fairly well documented in many books, I'm surprised that nobody has made a project of identifying different configurations of U-2, and estimating the capabilities of the sensors for the database.

One of the things I found was that the pilots need to take up to two hours prior to the flight to take in essentially pure oxygen, and that after the flight, they're required to be down for 24-48 hours.

I've heard that the suits are claustrophobic and annoying because you can't scratch your nose in them.

[TheOttoman]

The next question I have is more along the specific entry for the U-2

Due to the modularity of the platform, does it make sense to have a U-2 entry with each of the different sensors and combinations, or can the sensors themselves be introduced as mounts (and then continue to act as a sensor, and not necessarily a weapon).

I'm ignorant into whether or not sensors can be added/loaded in this way. What would be the recommendation?


To give a sense as to what we're talking about, there are at least 8 sensors that can be put into the Q-Bay of the U-2

[Rory Noonan]

Sensors can be added as loadouts (e.g. FLIR pods and the like); it also allows the flexibility to change sensor loadouts on particular aircraft on the ground with a time penalty rather than having multiple different versions of an aircraft.

Just bear in mind adding a sensor on its own is trivial, but creating new sensors is an involved process. Because they influence so much in the sim, sensors need high quality data in order for them to work as intended. An overpowered sensor will very quickly put an otherwise realistic scenario into the realms of fantasy.

[TheOttoman]

So as much verifiable data as possible... gotcha.

In looking at entries for the current sensors, it looks like the criteria are max range, notes and the aforementioned abilities. This last part seems sort of "generic". Is there a listing of all of the possible "abilities" to choose from to make that portion easier?

Also, for the max range, is that radius or diameter?

[SeaQueen]

ORIGINAL: TheOttoman
Due to the modularity of the platform, does it make sense to have a U-2 entry with each of the different sensors and combinations, or can the sensors themselves be introduced as mounts (and then continue to act as a sensor, and not necessarily a weapon).

I'd prefer to see the different configurations as loadouts, the reason is that if you're starting a scenario with the U-2 on the ground, it's more convenient than having to start a U-2 in the air, mount a bunch of sensors on it, and then land it, THEN start designing the scenario. The other thing is that it forces people to document configurations with pictures.

There actually exist manuals documenting every possible flightworthy configuration for every aircraft in the US inventory. Those manuals are huge, and in practice only a few of the possible configurations ever get used regularly. In the case of the U-2, many configurations might be possible, but are unlikely. Would it make sense to mix a photographic recce configuration with an ELINT configuration? Maybe in the right circumstance, but in practice you'll most likely see it be one or the other. The air sampler is probably it's own thing, since that's a very specialized sort of mission.

[TheOttoman]

ORIGINAL: SeaQueen

I'd prefer to see the different configurations as loadouts, the reason is that if you're starting a scenario with the U-2 on the ground, it's more convenient than having to start a U-2 in the air, mount a bunch of sensors on it, and then land it, THEN start designing the scenario. The other thing is that it forces people to document configurations with pictures.

There actually exist manuals documenting every possible flightworthy configuration for every aircraft in the US inventory. Those manuals are huge, and in practice only a few of the possible configurations ever get used regularly. In the case of the U-2, many configurations might be possible, but are unlikely. Would it make sense to mix a photographic recce configuration with an ELINT configuration? Maybe in the right circumstance, but in practice you'll most likely see it be one or the other. The air sampler is probably it's own thing, since that's a very specialized sort of mission.

I think loadouts are the best way to go as well. The good news is that apache85 seems to think so too.


Also, side note, I've got pictures of just about every configuration of the U-2

[Rory Noonan]

ORIGINAL: TheOttoman

So as much verifiable data as possible... gotcha.

In looking at entries for the current sensors, it looks like the criteria are max range, notes and the aforementioned abilities. This last part seems sort of "generic". Is there a listing of all of the possible "abilities" to choose from to make that portion easier?

Also, for the max range, is that radius or diameter?

Okay. Sorry for the delay in getting back to you, IRL strikes again.

That's correct, as much verifiable data as possible. I've attached two screenshots that list all the fields for sensors in the database, which should give you a good idea of what I need. Don't worry about getting every single data point, but the more the better.

The max range is a radius, so a sensor with a max range of 50nm will be able to detect contacts 50nm from its host, which makes a circle with a diameter of 100nm centred on the host of the sensor.

As for sensor abilities, they are:
Air Search
Surface Search
Submarine Search
Land Search - Fixed Facility
Land Search - Mobile Unit
Periscope Search
C-RAM (Counter-Rocket, Artillery and Mortar)
Space Search - ABM
Mine & Obstacle Search
Torpedo Warning
Missile Approach Warning
Range Information
Altitude Information
Speed Information
Heading Information
Navigation Only
Ground Mapping Only
Terrain Avoidance / Following Only
Weather Only
Weather and Navigation Only
OTH-B (Backscatter)
OTH-SW (Surface Wave)

I'm not able to elaborate on what these do specifically but they're pretty self-explanatory.

Like I mentioned earlier DB updates are my focus at the moment so once you provide the data I can get the ball rolling.

[Rory Noonan]

Bump. Any further developments here?

[Nikel]

Resurrecting this interesting thread to post the scenarios I could find, in which the U-2 is featured:


2918 - U-2S (United States - 2013)

Bear Island, 2022

NFZ Med, 2022

NFZ Pacific, 2022

Operation Lightning Strike, 2014

Operation Reclaimed Might, 2015

Sudan Strike, 2025

Chains of War 5. Nightmares



821 - U-2S (United States - 1995)

Northern Fury 27 and 35

Operation Allied Force, 1999

First night over Kosovo (1999). This scenario is not in the CSP yet.

https://forums.matrixgames.com/viewtopi ... 5#p5164905




1076 - TR-1A Dragon Lady (United States - 1987-1991)

Northern Fury 18, 19, 20, 21, 24 and 25

Desert Storm 1. Invasion



817 - U-2R (United States - 1987)

The Silent Service 2. Ground Pounder. Controlled by the USAF side.

[Kushan04]

Operation Lightning Strike also should go on the list.

Technically TSS 2. Ground Pounders has a U-2, but it's not under players direct control.