DCS: Black Shark - Dev Updates - 09 July 2008

[silverod]

black shark

 

recieved e-mail,yesterday,from ed.after enquires.made.about release date of blk shark.release date was given as april / may.2008.

[Peyoteros]

recieved e-mail,yesterday,from ed.after enquires.made.about release date of blk shark.release date was given as april / may.2008.

 

 

He he, nice try mon :lol:

[thereminqblank]

Yeah, I think we should be taking that with a very large pinch of salt! :P

[VMFA117_Poko]

A pinch or a punch? ;)

[Captain R]

Excellent.

[Guest Frenchy702]

lol, cant help it now, hopes have been raised... must... stop.... s..s..smiling....

[EvilBivol-1]

This was posted a few weeks a go here:

http://forums.eagle.ru/showthread.php?t=29282

 

DCS: Black Shark Target Detection Model for AI Aircraft

 

DCS: Black Shark features new target assignment functionality in the mission editor and a complex target detection model for AI fixed and rotary wing aircraft. The model accounts for specific onboard sensors and environmental conditions. It is primarily designed to provide more realistic AI air-to-ground operations and includes the following variables:

• Unit onboard sensors
  • air-to-air radar
    
  • air-to-surface radar
    
  • multimode radar
    
  • radar warning receiver
    
  • television optics
    
  • low-light television optics
    
  • imaging infrared optics
    
  • infrared search and track system

  [*]Unit skill

  [*]Unit speed

  [*]Unit cockpit view limits

  [*]Time of day

  [*]Target background (open terrain, forest, water, road, etc.)

  [*]Atmospheric conditions

  • fog
    
  • overcast
    
  • precipitation

  [*]Line of sight obstruction (terrain, structures)

  [*]Target size (including dust tail when moving over unpaved surfaces)

  [*]Single vs. group targets

  [*]Clutter (buildings/structures)

  [*]Weapon firing

  [*]Artificial illumination (flare, ground fire, etc.)

  [*]Target light source (lights, beacons, etc.)

When assigning an attack waypoint, the mission designer designates a specific user-defined area on the map and target type(s) for the attacking aircraft to target (vehicles, buildings, aircraft, etc.). Upon reaching the attack waypoint, the AI begins to search for the desired target type(s) in the designated area until it either finds a target or reaches the next waypoint. The designated area can be minimized to strike a single coordinate (‘point’) on the map. The mission designer can assign the AI to conduct level (“carpet”) bombing by targeting two map points under the same name and identifying the initial and final target ‘points’.

 

The various radars and optical sights used by AI aircraft are defined individually for each unit according to their characteristics. This provides modeling of a wide range of combat capabilities of the modeled aircraft, depending on time of day and weather conditions.

 

Aircraft with no optical sensors or radar, such as the Su-25, will detect targets only when visual contact is possible. Detection depends on the horizontal and vertical cockpit view limits and on various environmental conditions, including time of day, weather, line of sight and other variables. At night, visual detection can be aided with artificial illumination or target firing activity. In bad weather, visual detection may be impossible.

 

Aircraft with television or low-light television optics will rely on natural or artificial illumination to detect targets. Reduction of natural light, fog, cloud cover, and heavy precipitation will reduce and ultimately eliminate the effectiveness of such systems.

 

Imaging infrared devices will allow aircraft to detect targets at night and in bad weather.

 

Aircraft equipped with radar are able to detect air and ground targets in any time of day and weather conditions. For air-to-surface radars, targets masked in ground clutter, such as city blocks, may be difficult or impossible to detect. However, unit movement, large units groups, and unit location on roads or runways will enhance radar detection. Certain radar models are restricted to detect only static structures or maritime targets (bombers and naval reconnaissance aircraft, respectively).

 

The unit skill and airspeed also affect the likelihood, range and time required for detection. In general, higher skill settings, lower airspeed and greater cockpit visibility increase the chances and range of both visual and sensor-based detection.

 

Numerous target characteristics are also calculated in the model. The target’s general size will determine maximum detection range for visual and sensor contact. A target in a group of units is more likely to be detected further than a target that is isolated. A moving target’s dust tail, including that of low flying aircraft, increases detection range (the dust tail is not present during heavy precipitation). Finally, any weapon firing contributes to fast detection. In general, more visible weapon types, such as MLRS barrages, will be detected further than less visible types, such as machine gun fire. Weapon fire can be detected either when the firing source is in the AI field of view or if the weapon trajectory enters the AI field of view. For example, the AI can detect and react to a SAM launch from the opposite side of a mountain, if the missile enters the AI’s field of view in flight.

 

All infantry units, including MANPAD troops, can be detected only after firing their weapons.

 

When engaging with cannon, TV, IR or SAL-guided weapons, the AI will commit to an attack only when visual or optical detection is possible. Target contact is required for weapon release. If target contact is lost before weapon release, the attack can continue only with unguided munitions. For example, if a target is detected due to weapon firing or under artificial illumination, but illumination or fire ceases before the attacked is complete, the AI can continue the engagement of a single target for up to 10 seconds with unguided rockets or bombs, aiming for the last visible target location.

 

Anti-ship cruise missiles can only be employed against targets detected with attack sensors, while surface attack cruise missiles can be employed either against detected targets or any map coordinate (‘point’).

 

When set to attack a ‘point’, as opposed to an object, any weapon can be used in any time of day and weather conditions.

 

When engaging air-to-air, sensor or visual contact must be possible for the AI to commit to an attack with cannon and IR-guided missiles. Target contact is required for weapon release. Radar contact is required for use of SARH and ARH missiles.

 

The DCS player can adjust the maximum detection ranges of the various units and individual sensor parameters in the program configuration files outside the simulation.

[Avimimus]

Thats nice to see again. Its five times more impressive then it was the first (several) times I saw it. Why isn't it on the website proper?

 

S!

[BBQ]

Good question Avimimus--I almost missed it as well.

[VMFA117_Poko]

? :huh:

[VMFA117_Poko]

Ah yes. I missunderstood it.

 

The detection system is the best I have ever seen in any production. Really impressing.

[Wags]

May 16, 2008 Update

 

May 16 DCS Update

 

Since the last update, not much has scientifically changed from a new task point of view. This is primarily because we are in feature freeze and are focused on content iteration and debugging. Most of the work on DCS: Black Shark (now on build 46) has been focusing on the following areas:

 

1- Campaign generation

2- Training mission generation

3- Bug testing with a focus on multiplayer (lots of work to still do)

4- Editing and tweaking of Ka-50 the flight manual (currently 533 pages)

5- Writing of the DCS GUI manual (will be around 200 pages when complete)

6- FPS and RAM usage testing

7- General bug fixing (yes, there are still quite a few)

 

While we realize that many would just wish for us to release it now (particularly after some of the recent videos), we simply cannot do that given all the items listed above. It's too easy to release a buggy and incomplete product when being pressured by consumers and publishers to "just release it". Please be patient. Given that this will be our first self-published product, we want to do it right.

 

With the creation of larger missions in a near-complete mission environment, we are also now tuning and adjusting the simulation for increased frame rates and minimize RAM usage. Mostly given the 6 DOF cockpit, the higher population density or ground objects (buildings, trees, etc.) and the higher elevation mesh detail, DCS will require more system resources to run smoothly. However, we are taking steps to minimize this as much as possible. When complete, we should have a good idea of minimum and recommended system specs that will be realistic and not low-balled.

 

The GUI is just about done with the integration of the Options screen that allows you to set up separate Input options configurations for multiple types of aircraft. So, as we start to add more aircraft to DCS, each aircraft can have its own unique of input command profiles (keys, axis, etc.). Personally, I do all input controller programming now within the DCS Options GUI and I no longer use external profile programs (although that is still an option).

 

Select members of the Sim-Mod team are still working on some terrain enhancements and we hope to have final versions of the Spring and Fall textures soon. Additionally we hope to be updating additional airbase before release. Once complete we can integrate into the DCS code base.

 

The Mission Editor is just about final and just being debugged now. Two nice additions added near the end was the ability to set rules and actions for not just groups but each individual unit within a group and the ability to assign a mobile area trigger that is attached to a moving unit/group. Also, when creating multiplayer missions, each side will now have their own unique text and image briefings. Also, each side can be assigned unique goals. While this will not be a significant feature for Black Shark, which will likely focus on cooperative missions, this will be a welcome feature as we add additional aircraft to the DCS mix.

 

As for what happens after Black Shark, the team has several aircraft modules currently in development (this could include development of 6 DOF cockpits, avionics or flight dynamics). While the A-10A Suite 2 module will still likely follow the Black Shark, the following aircraft are also now planned for DCS in development at one stage or another:

 

1- A-10A Suite 2 (latest version of A-10A in active use)

2- A-10C Suite 3 (we now have permission from the USAF to develop an entertainment version of the simulation we developed for them. We are very happy and excited about this).

3- AH-64A Blk. 49A

4- Su-27

5- F-15C

6- Mi-24V

7- F-16C

8- MiG-29A

 

Naturally, release of aircraft like the Su-27 and F-15C would coincide with integration of advanced flight model for missiles, advanced seeker logic and advanced air-to-air radar logic and modeling.

 

Attached at the beginning of this thread are a few very early images of the 6 DOF cockpits for the Flanker and Eagle. http://forums.eagle.ru/showpost.php?p=422862&postcount=1

 

The actual order of release is still up in the air. For all of these aircraft, we now have all the needed data to model them properly to DCS standards (very important a big factor of what does and does not go into DCS as a flyable). It is important to remember that all of these aircraft will be modeled to the same level of detail as the Black Shark in DCS. As I hope many of you realize after reading and seeing more about Black Shark, this will be a daunting task but will provide the most comprehensive and realistic simulation of flying these aircraft within a combat environment on the PC.

 

Thanks,

Matt

[mvsgas]

Thanks for the update. Thank you very much.

[Smith]

Wow, that is a great Update, thank you very much!!! :thumbup:

[RvETito]

....

1- A-10A Suite 2 (latest version of A-10A in active use)

2- A-10C Suite 3 (we now have permission from the USAF to develop an entertainment version of the simulation we developed for them. We are very happy and excited about this).

3- AH-64A Blk. 49A

4- Su-27

5- F-15C

6- Mi-24V

7- F-16C

8- MiG-29A

 

A huge smile appears on my face....

[Esac_mirmidon]

May 16 DCS Update

 

 

1- A-10A Suite 2 (latest version of A-10A in active use)

2- A-10C Suite 3 (we now have permission from the USAF to develop an entertainment version of the simulation we developed for them. We are very happy and excited about this).

3- AH-64A Blk. 49A

4- Su-27

5- F-15C

6- Mi-24V

7- F-16C

8- MiG-29A

 

 

This is absolutely AMAZING ЎЎЎ

 

Tito, you are really fast, and mind reader XD

[GGTharos]

WOOOOO! DCS EAGLE! WOOOO! :D

 

Any chance we can get 2-seat versions (such as F-15D, Su-27UB) to use for training?

[VMFA117_Poko]

The GUI is just about done with the integration of the Options screen that allows you to set up separate Input options configurations for multiple types of aircraft. So, as we start to add more aircraft to DCS, each aircraft can have its own unique of input command profiles (keys, axis, etc.). Personally, I do all input controller programming now within the DCS Options GUI and I no longer use external profile programs (although that is still an option).

Does it mean we'll no longer have to change axis curves for different units as now changing between Su-25 and other aircrafts to get proper responses?

[Scart]

1- A-10A Suite 2 (latest version of A-10A in active use)

2- A-10C Suite 3 (we now have permission from the USAF to develop an entertainment version of the simulation we developed for them. We are very happy and excited about this).

3- AH-64A Blk. 49A

4- Su-27

5- F-15C

6- Mi-24V

7- F-16C

8- MiG-29A

a very huge smile appears on my face

[Glowing_Amraam]

Now there's an update!:D

[Wags]

Does it mean we'll no longer have to change axis curves for different units as now changing between Su-25 and other aircrafts to get proper responses?

 

Correct

[Wags]

WOOOOO! DCS EAGLE! WOOOO! :D

 

Any chance we can get 2-seat versions (such as F-15D, Su-27UB) to use for training?

 

Perhaps down the road, but as you see, we already have quite a work load in the pipe.

[VMFA117_Poko]

As for what happens after Black Shark, the team has several aircraft modules currently in development (this could include development of 6 DOF cockpits, avionics or flight dynamics). While the A-10A Suite 2 module will still likely follow the Black Shark, the following aircraft are also now planned for DCS in development at one stage or another:

 

1- A-10A Suite 2 (latest version of A-10A in active use)

2- A-10C Suite 3 (we now have permission from the USAF to develop an entertainment version of the simulation we developed for them. We are very happy and excited about this).

3- AH-64A Blk. 49A

4- Su-27

5- F-15C

6- Mi-24V

7- F-16C

8- MiG-29A

Can't not love You for this part!!! Huuge thanx! :D

[GGTharos]

Yeah, that was a pretty big update. Good job on getting permission from the USAF for the A-10C, too. Major props :)

[Boberro]

 

1- A-10A Suite 2 (latest version of A-10A in active use)

2- A-10C Suite 3 (we now have permission from the USAF to develop an entertainment version of the simulation we developed for them. We are very happy and excited about this).

3- AH-64A Blk. 49A

4- Su-27 :D

5- F-15C

6- Mi-24V

7- F-16C :)

8- MiG-29A

 

Yooohoi :D:D:D You can't be un-loved by this update :D

 

But... next to every plane is version.... except Su-27, so what version of 27 could be implemented ?