EvilBivol-1

For those who missed it, a comprehensive list of new and improved features in Black Shark 2 has been posted below the official announcement. http://forums.eagle.ru/showpost.php?p=1321328&postcount=2

Thanks, then it seems it isn't up yet. Apologies for the false alarm.

I can't confirm this now as staff is unavailable, but I believe the installer has already been replaced on the website and should readily except all previously installed versions of Black Shark. We are awaiting confirmation of a successful resolution to the Steam problem to be sure.

To help alleviate some of concerns raised here about the general direction of DCS development, I can say that ED understands that production of individual titles, which need to be continually updated separately in order maintain compatibility is not a sustainable system in the long term. It continues to be our goal to develop a truly modular system with a unified world into which individual products can be plugged into and maintained up to date. Creating a technological and financial infrastructure for such a system is challenging, time-consuming and expensive, in particular when the realism bar for player-controlled and AI units, as well as the rest of the virtual world are so high. We know this has been a vision for many simmers and sim developers for a long time, including ED, but there is a reason why it hasn't happened yet. We will continue to work to try and make it a reality.

Obviously I can't speak for either eSim or 777, but from what I understand eSim is far more focused on revenue from the military market, which is why they are able to adopt the kind of gaming marketing approach that they have. For ED, the gaming market contiues to be a critical interest. Worldwide retail is very important.

By retailers, I mean to include online retailers as well. I hope you understand that I cannot continue a discussion of company or product financial structruring. I hope, though, that it may be useful to provide an example of the kind of thing we mean when we talk about external limitations on our decision-making process.

Unfortunately that simple idea quickly breaks down in practice, unless we limit our sales to our own website. Retailers who carry our product have their own ideas and limits regarding price points. These are generally guided by normal costs of other games they carry.

A new installer is being tested and is so far successfully recognizing all versions, including Steam. We anticipate making this available shortly (I'll stick my neck out and say by tomorrow, but don't cut my head off if I'm wrong).

If I understand you correctly, you are referring to this entry in the Black Shark FAQ? If so, I do think it falls well within Wags' earlier comment that such language was carefully chosen to avoid the promise of free updates - despite the fact that it was indeed our hope to provide them. Such careful use of language was and is warranted, because product development plans on software projects of this scale, complexity and longevity are difficult to maintain and often require reassessment. This has happened in the past and will probably happen in the future, unfortunately. Having said that, as somebody who was officially sanctioned by ED at the time DCS: Black Shark was in development (as volunteer Community Manager), I can certainly extend my apology for any change in our plans that might have made users feel mislead. While it's true that in some cases we feel it isn't appropriate to discuss product plans prematurely (though sometimes things slip anyway), it was never ED's intention to mislead anyone. The company operates in an environment where development costs are very high, while revenue potential is not only limited, but also determined by outside factors (for example game cost ceilings for retail chains). With the added complexity of having to coordinate out gaming product development with military product development, product plans often suffer from significant changes in direction. This has proven to be a difficult, but thus far unavoidable part of the development process. This isn't the first time we are in a position to appeal to the users for understanding that product plans are subject to change. We understand that sometimes these changes may not be well liked, but hope that the opposite is true as well. For example, I would imagine that our change of plans to model the A-10C instead of the A-10A, which was already in development for DCS: Warthog at the time with cockpit screenshots published, was on balance a positive one. Once again, we understand that the decision to release Black Shark 2 as a payware upgrade may have taken many by surprise and is not to everyone's liking. As with all of our other products, we feel that it is a warranted decision based on the amount of resources invested in its development and is in general well worth the price as an upgrade package to the original Black Shark. It's your right to disagree with this decision, but please consider the manner in which such disagreement is voiced, as it is our right to develop our products and maintain the official forum in a manner we feel is most effective. Unfortunately I cannot comment much regarding future DCS integration plans, other than to say that it continues to be our goal to develop a unified electronic battlefield in which players can control a variety of realistically modeled platforms.

This feature was actually removed back in 1.02 due to some changes to the sound engine.

We've been pleased to see this thread stay on quite a level track, but it seems like it may be slipping, so I would like to take a second and note that while we respect everyone's right to voice their opinion, including a disapproving one as you can hopefully see by the number of them already posted, we expect posts to be made in a polite manner with respect to users, developers, and the product in general. Whether you are showing support or disagreement with our plans, please consider the tone and language of your post before hitting the Post button.

Я думаю стоит отметить и обновленный звуковой движок, который в оригинале оставлял желать лучшего.

This is not a guarantee of anything, but try to simply re-save the mission in the BS2 editor. Sometimes doing so updates the internal mechanics of the mission and fixes any left-over issues.

BS2 is not compatible with FC2.

A Russian version is being prepared, but not ready yet.

If you haven't already, please add to the Wish List thread.

Honest mistake.

Yes, you are correct and I suspected that was the issue. In that situation, the mission is actually looking for the A key press before it will proceed.

Ah, right, sorry, I should have mentioned this. You can save a track by running the mission out of the mission editor. You will then get a debriefing screen with the option to save the track file.

"July 19/10: Raytheon announces a $12.6 million USAF contract for Phase 1 integration and qualification of the Helmet Mounted Integrated Targeting (HMIT) system for USAF and Air National Guard A-10C and F-16C Block 30/32 aircraft. Raytheon Technical Services Company LLC (RTSC), the prime contractor, is teamed with Gentex Corp. in Simpson, PA to produce the system, based on Gentex’s Visionix Scorpion™ Helmet Mounted Cueing System. HMIT will be a night-vision compatible helmet-mounted display that shows crucial information in high-resolution color imagery directly in the pilot’s field of vision. The color imagery is a step forward, and information displayed will include weapons-cueing, targeting and situational data from on-board and remote sensors. Like other HMDs, the system will track helmet movement to display accurate imagery, regardless of the direction the pilot’s head is turned. The program includes 5 one-year production options, with a potential total value up to $50 million." http://www.defenseindustrydaily.com/a-highertech-hog-the-a10c-pe-program-03187/ http://www.gentexcorp.com/default.aspx?pageid=2602

Sorry, no Radio Item Add/Remove for MP. Added a note for this in the GUI manual.

Hi Spike. The mission should be working correctly, so you probably missed one of the triggers along the way. My guess it maybe it had to do with turning off the Autopilot, which is something the mission looks for around the time you need to line up behind the first target. We can diagnose better if you attach a track of your flight so we can see what happened.

Also, for those who haven't seen this, there is an additional official training mission dedicated to fundamental HOTAS understanding: http://files.digitalcombatsimulator.com/en/84730/

Of course, you can open the track file in the ME.

I'm not sure if I understood your request correctly, but here is a short mission track that shows the following elements: - at mission start, a group of ground vehicles is set to hold their position and be invisible for 1 minute - at mission start, a Predator is airborne and looking for targets, but is unable to detect them - after one minute, the ground group begins to move and is now visible - the Predator is able to detect the ground units and assigns them as targets to the player, including a datalink message on the TAD (not mobile). Predator-JTAC.trk