Leaderboard

You can omit the update if you want and do it on Monday or whenever you want .. just click on that "Later" button ... let the rest of us have the update as soon as its available

@jejsus First of all, you didn't bother to exlain / justify your request in your original half-a$$ed post, so Rudel's advice was valid. Second - what about all people who actually can and want to update and run their servers on Friday, just in time for the weekend when most playing takes place? Why should they all have to wait for you, who clearly are selfish and ignorant here? Yes, some people with slower connections will have to wait longer, just like people with Stable version will probably have to wait for new content until January. It is what it is.

What is the DCS: Ka-50 Black Shark 3 update? This is a paid update to the existing DCS: Ka-50 Black Shark 2 to add new systems, features and fixes to usher in another 10 years of the most advanced simulation of the Ka-50 on the market. How much will it be? The full version will be available for only $69.99 on our Shop and Steam. For owners of the Black Shark 3, you may take advantage of the Black Shark 3 Upgrade Program. This offer grants you the brand new version for only $10.99. Please note that this offer is only available for 3 months. After that, the upgrade cost will increase to $19.99. **Please note** Users who received BS2 as a gift or event prize will not be eligible for the update, the full version must be purchased. I already own the DCS: Ka-50 Black Shark 2, do I need to buy this? No, if you do not want to buy the upgrade, it will not be required. You will have everything the current Black Shark 2 module has currently, you will not receive the new systems and updated 3D model and textures. **NOTE** If you are upgrading for an older version still using Starforce and are experiencing issues, please contact support and we will get it sorted for you. Thanks! I only own the DCS: Ka-50 Black Shark 1, can I upgrade? You can only upgrade the DCS: Ka-50 Black Shark 2. You will most likely be better off to by the full version of the DCS: Ka-50 Black Shark 3. Will Ka-50 Black Shark 3 and the upgrade option be available on Steam? Yes, we plan for both. **Please Note** Those who purchased BS2 on Steam and migrated to Standalone will have to purchase BS3 upgrade on Steam and migrate once again. We cannot provide an upgrade option on Standalone to them. Why do I have to pay for this, shouldn't it be free? The paid version is for weapons and systems that required extra research, development and implementation to add." What happens to my original Ka-50 Black Shark 2 if I buy the upgrade? It will still be available to use as you remember it today. You will still be able to use all the content and such you had before, you will simply have another module called the Ka-50 III in the game to use. Alternatively, in the Mission editor, you will be able to remove the MWS sensors and Igla missiles, returning the helicopter to the original version but with the brand new 3D External model. What new features will come with the upgrade? Main features: A Missile Warning System for warning about the launch of missiles at a helicopter has been developed. The possibility of using Air-to-Air Igla missiles has been implemented. A realistic model of an Inertial Navigation System has been developed, which has the properties of a real one: it requires alignment before the flight and accumulates an error. The error of INS coordinates can be fixed in flight by previously assigned landmarks as fixpoints. New, more accurate and detailed 3D helicopter model using modern technologies and materials. The Black Shark 3 project fixed a number of old bugs and made some improvements from the users wish list and builders of home cockpits. (Also fixed for BS2) Changes in the flight dynamics model include the implementation of the engine gas-dynamic instability during the rockets launch from the inboard launchers, from hover and at low speeds. This is due to the sake of hot rocket gases into the air intakes, which can lead to a drop in thrust, surgeon and shutdown of the engines. (Also fixed for BS2) Added vibration during the transition from hovering to flight and vice versa. (Also fixed for BS2) Will there be a new Manual for DCS: Ka-50 Black Shark 3? Yes, you can find it on the doc folder for the module or you can download it here: https://www.digitalcombatsimulator.com/en/downloads/documentation/. Will there be any missions for the DCS: Ka-50 Black Shark 3? Yes, we will have a mix of new, and updated instant action and missions for the the Ka-50 Black Shark 3. Will my campaigns work with the new module? This will be up to content creators if they choose to update their campaigns to the new module, other wise they will work as normal. Why are you doing this, shouldn't you be working on the Mi-24, AH-64D and other core issues? The DCS: Ka-50 Black Shark is an important module to DCS World, keeping it updated and relevant is very important to us, and to our users. This project is only being worked on by a few devs that were instrumental in the original Ka-50 Black Shark, it has not affected any other project or core issues being addressed. Known Issues as of release Release Video: Feature and How-to Videos:

A version compatible with 2.8.1 has been added to the OP. Enjoy!

sent 9L and Newy a PM with all the documents needed. fingers crossed...

I mean, the whole helicopter will hardly be found in the world with an english cockpit at all so when selecting english for those whose russian is a little rusty the WHOLE cockpit should actually be in english It makes little sense to leave the HUD out.

Happy Holidays Everyone !!!!!!!

Guys, thanks all for the feedback. f4l0 as SimShaker for Aviators developer is informed and will look into this issue as soon as he can. Probably tomorrow. We are tryiing to get in contact with the ED team as well. You are not alone in front of the issue. Stay in touch and calm down a little.

Hi Joe, We have an internal fix for it, it should be available in the Open Beta with the next update.

Another thing to mention with cold contacts, which friends who fly 4th gen fighters have explained to me, is that the whole issue of "closure speed is near zero, so it falls into a Doppler gate" isn't a problem in real life, because in real life, 4th gen radars are also looking at their own jet's closure with the ground. If you are flying at 400 knots ground speed, and your radar is painting (and filtering out) ground returns that are closing at 400 knots, then that range hit (aircraft )with zero knots closure looks mighty suspicious to the Doppler side of the radar. Radar systems are highly dependent on knowing your own aircraft's ground speed to make the filtering work -- not sure if ED has considered that. Also explained to me was that the look down penalty isn't a thing; the altitude problem is when your own jet is down below a certain altitude (let's say 5K as a nice general number), then you get more false returns. The issue isn't that you can't detect down low, or that there's a look down penalty, but rather that you get more false returns because of the extra noise. Razbam radars do this now. Apparently, the look down penalty that ED has modeled is specific to an early version of the flanker/fulcrum slotback radar. I'm guessing ED has that documentation, and applied that to all 4th gen aircraft.

Yep as i said makes no sense to me either. I thought the same thing that's why i made the post because i believed that the fix was intended to make the 88 rack to be able to fire in ripple as it didn't work before. That's the logical thing to assume from the changelog. But reading on bignewys response made me wonder if that's really the case. I also hope they 'll take a look on this and not let it linger forever like other bugs, like the one with VIS mode for example.

So I've gone and taken your second run with the updated driver, and ran another test with the track file I sent you to allow for a frame by frame comparison. Considering that our system are slightly different in terms of motherboard, ram, storage, and the fact that the track will have slight variation between runs, it's important to try and average the results and not take the values at face value. Looking at them side by side, I'd say they perform on par with one another. I believe the slightly higher FPS on the RX 7900 XTX is due to my ram/storage configuration being slightly faster than yours, especially since both our system's aren't maxing out the GPU's to 100%. There's a couple of frames where we are at the same FPS and both cards are showing the same GPU percentage. We might have to run another test where the GPU's are being maxed out, instead of being limited to our CPU's. It might also be worthwhile to come back to this test after ED's implementation of multithreading. On the RX 7900 XTX side of things, there's glitchy smoke as seen in the clips. I'm not sure if it's a driver, game setting or issue with the game that may be causing it, but I've only noticed the effect in the benchmark. I also think the RX 7900 XTX uses quite a lot more power compared to the RTX 4080. My card will pull up to 400W on 100% usage in other games, and I don't think the RTX 4080 will pull that high, so may be something to consider if you're in a region with expensive electricity. My card is also pulling a consistent 126W while writing this post, but I believe it'll be fixed with a driver update in the future. Also for VR, it's been mentioned before that the RX 7900 XTX will lose to the RTX 4080 at the moment, due to driver issues. I don't have a VR headset to test with, so I can't say at the moment how the card will perform and it'll be up to someone else to test that scenario. For my conclusion, I'd say if you're not a VR gamer then both cards perform the same and you'd be happy with either but the deciding factor on which to get will depend on price, which card are in stock and if you're willing to deal with the AMD driver problems until they're sorted.

Not trying to be a smartass here, but the easiest way around this would be a squadron policy that there are to be no updates on fridays, so all members have a chance to load the update in time. I don't see a reason why taking everybody else hostage should be the best possible solution.

The wheelchocks are a small bug that unfortunately did not receive the last minute fix anymore that we uploaded, as we hoped. It will be fixed in the patch.

Ми-26

If you bought BS1 in ~2008 and upgraded to BS2 a while ago, you can merge the BS1+BS2 into a proper BS2 license and then the discount to BS3 will show up. There is a menu in the bottom left of the license page to convert a BS1+BS2 upgrade to BS2. https://www.digitalcombatsimulator.com/en/personal/licensing/

Radio communication and discipline totally different from each other.However in DCS its kinda mix of both.Also we should have different frequencies like marshall,tower,approach etc I would like to switch between those channels instead of magic trick.Thanks

If of interest it is now available from the DCS E Shop. As staccato shafts of burning light flashed by the canopy, Lieutenant Scott Rivers, call sign ‘Ford’, squeezed the release button. He felt the expected “kick in the pants” as the Hornet surged when a ton of self-guiding ordinance dropped away intent on finding its mark. Below, seconds later, there was a massive shock wave as the area where the I.R.G.C. meeting was being held, exploded into ‘Hell on earth’ lighting up the entire City. As the two Hornets disappeared into the dark Bandar Abbas night, chased by the flailing neon arms of the triple A they both new they had just changed the face of the conflict. For once things were going their way. With the Iranian IRGC command including ‘Asad’ now gone and the USS Truman relief fleet just a day away, ‘Matrix’ could taste that well deserved R&R. What could possibly go wrong? This campaign follows on from Ford and Matrix’s exploits in the Straits of Hormuz on board the USS Abraham Lincoln in the “Rise of the Persian Lion Campaign.” The campaign ethos, as before, is not to capture full reality but create an imaginative, immersive, and engaging set of missions linked together with a developing narrative. Even though the story line continues from the last campaign, “Rise of the Persian Lion II” can be fully enjoyed as a standalone. Key Features · 13 Detailed missions linked by an ongoing story line. (Mission 9 in two parts). · ‘Ford’ and his wing ‘Matrix’ are now joined with a second flight of Hornets, led by Lieutenant James Cook, ‘Chef’ and his number two Lieutenant Steve Miller, ‘Grinder’. · As before the campaign has been developed in VR so there will be no requirement to physically write down disappearing coordinates and break immersion. · Over one and a half thousand voice overs performed by voice actors. · Detailed briefs for each of the missions including PDF versions. · Kneeboards for each mission plus PDF versions. · Personalised aircraft skins. · Alternate optional campaign version included with ‘Easy Air to Air Refuel’ for those who have yet to master the art of catching the basket. BADGER633 Youtube.com/@badger633 Discord.gg/MAeMQ97 forums.eagle.ru/forum/275-badger-633

I think you are about 10+ years too late to complain about the Black Shark validity. I would welcome more what-ifs and testbeds into DCS, as with the Black Shark it makes for a very enjoyable flight sim experience as well as gives us some aircraft where we might not be able to do them otherwise.

We have nothing new on this. The task is more complex than other radios. We are currently working on integration into the HUD and COMM page.

I don't think the phantom had a HUD. More like a gun sight similar to the F-5. The alignment time should be in line with all the other INS equipped aircraft, so around 8 minutes. I don't have answers for the rest.

I've updated to Open Beta 2.8.1.34437 and my performance is much worse in VR than it was in the previous open beta

ditto and to be fair there wasn't anything in the patch notes to say they had fixed it

Yeah how is this correct as it is lol

Except that I feel that you are a) forcing everyone to conform to the lowest common denominator (which happens to coincide with yours, what about that), and even worse b) you assume that everyone is like you and plays on week-ends. I work on week-ends, and your proposal seems selfish to anyone who isn't observing some arcane occidental custom where Sundays are non-working days. In short, your proposal sounds to me that you feel inconvenienced by a Friday release and think it's fine that that everyone else should put off their updates so you can play on week-ends. Please forgive me when I say that the word "selfish" does come to my mind when I look at it that way.

16 hours of work but the hull is now done...

It was announced recently for a later release in 2023, but not in 2022 or even this actual OB.

from our perspective we have met the memory requirements that ED set out for terrains, we have seen an overall performance increase across the map. also with that in mind we are also reviewing all of our models and reducing unneeded geometry to get more performance. as it stands today I can run the map in the Varjo at the highest settings (39ppd) with a 4090 and get a solid 60+ fps across the map no matter where i am looking. but as I said we are redoing some of the models to simplify the geo, example the new containers (Specter Studio) ones lod0 960 polys lod1 5 lod2 5 this will be in the next update, however as you can imagine there are a lot of models to go through in conjunction with the other works that is required so this will take time. Thanks Specter

Correct, aerodyn cover for the TCS, and eventually - maybe - have the entire TCS pod removable. The fuel pylons will not become removable, as it would include reworking large parts of the fuselage entirely (which is out of scope time and ressource wise). Whether or not that may change in the more distant future, ofc remains to be seen, but it should neither be expected, nor do we want to promise anything. Until then, the best answer thus is simply no, unfortunately. Thank you all for your kind understanding.

This. The no target size functionality with the AIM54C, the omniscient AI, and the strange AIM54 guidance when notched (the pitch up and seemingly inability to reacquire even when out of notch) has all really put this missile in a bad place. I hope that both HB and ED will get this stuff fixed so that it can renew my interest in flying the F14...

Dear all, as always we would like to ask for your kind feedback regarding the last patch. Our apologies that Reforger II. is not included today yet, some minor issues are currently holding back release which we hope to iron out over the weekend, and bring it to you next week, in time before the Holidays. A new addition to the F-14 - finally! - comes in the form of wheel chocks, which will primarily help holding the Tomcat in place during turns by the carrier. They are set to be on by default for all cold starts, so do not forget to remove them, or taxiing will be difficult. Taxiing over them is not possible. Please also note: when requested to be set by the player, they appear instantly. This is on purpose, to provide immediate fixation on air craft carriers, should a player get surprised by the carrier turning. The ground crew call will follow a bit later and somewhat desynced, unfortunately this is a small, but necessary trade off. All other fixes please take from the changelog below. Thank you for your great feedback thus far, we are always looking forward to more! The Heatblur Team DCS F-14 Tomcat by Heatblur Simulations NEW: Added wheel chocks. By default on for cold starts. Fixed aircraft in place when chocks are active, avoiding deck sliding on carriers. Fixed LANTIRN CTD with 2.8. Added FPS-117 to the RWR threat library. Fixed not all masses contributing correctly to the total mass and balance on each respawn; causing discrepancies in aircraft performance on subsequent flights. Fixed shader definition for far LoD - aircraft will now sample a small part of main aircraft textures for the right colour. Fixed Op Reforger Mission 5 TALDs not working for Pontiac. Updated Quickstart F-14A_IA_NTTR_Zone5 by Reflected Simulations. Added VX-9 XF240 White Whale livery by Isaac. (Thank you!) EDIT: Our apologies, the mission fixes have not been pulled in time anymore (like the wheelchocks fix), please download them here. F-14B_Campaign_Mission5.miz F-14B_Campaign_Mission5_SC.miz

After some other testing, I notice two things whichn in conjunction make the Mirage F1 currently very hard to control: The Well known pitch sensitivity problem, which makes the aircraft to reach the max AOA very quickly with huge "elasticity" (the nose go back down once we release the stick). The pitch is so sensitive that we currently can properly fly with only the half of the joystick Y axis amplitude, we still reach max AOA. The roll in the other hand, seem to have huge latency and inertia, making the aircraft long to make it roll and still rolls pretty long time after joystick returned to center. The result is that we have sensation to fly a nervous jumbo jet. This is hardest module to control I have tested ever, even the Mig-29 still more controllable. I really doubt the real Mirage F1 is as hard to control as in the module.

I just test-flew the F-14 mission "Bone Strike," which has so far frozen 100% of the time for me at some point between the RTB call and the carrier. Here's my report on the fix:

Yep, work this stuff out with squadron buddies / your server admin and all will be well

Nope and I won't wait 20 minutes for an INS system to align when all I want is a nice Ka50 evening session with a couple of other people. I have a family xD Turn on the BS and go for a walk with the dog or what xD

Here is a short multiplayer track from Hoggit's PGAW with only a couple of players online. Quick and dirty startup and heading towards the Pyotr. It's the beginning of the first phase, so a lot of enemy SAM emitters are present. TRACK DOWNLOAD (Google Drive folder) Video 1 shows situation pre-lock/launch, switching the SEARCH button on and off Video 2 during lock/launch In default mode (Search off) you don't see what is locking you or launching at you.

The XMT option on the HSD is only relevant for transmitting data across the selected network (e.g. sending a steerpoint with Comm Switch IFF IN Long). It doesn't control anything regarding receiving datalink info. As far as I've seen, the main issues that crop up regarding non-functional DL info is the MIDS LVT knob not being on, or an incorrect/interrupted alignment.

Thanks so much for the performance fixes, it feels absolutely great now!

Yes. Here's a comparison made by another member of manual data versus the old performance in DCS, with his caption. All credit to @rossmum for the work, I'm just quoting. To keep it short, Heatblur did a great job making your product a better simulation of reality, so pop open a beer and let's drink to that!

More work. Quite happy with the exhaust residue. Not so with the ejectionport residue etc... not found good examples of how it should look like in RL (halp plz). Added some more masks to have a library on possible finish combinations. Re done the wing mask. Re did the leading edge and made it so to be more compatible with further variations. Also partially "resprayed" the pattern in an uneven fashion to redo the "hasty late war slave labor" finish. Redid the spinner. Pixel density seems lower in that area. Pity. Added a fabric overlay over the control surfaces and some stand in generic red primer chipping on these. Fixed the marbling overlay layer and that led to less visible seams. They´re still pita, especially around the wheelbays and adding mud spatter around them will be pure masochism.. Some wonky stuff still going on on the left hand wing filet... not tracked down the culprit yet. Still have to fix some seams and paint fill errors here and there. However, gonna continue on workin on the panels and rivets tomorrow, before i can continue working on the diffuse. The new panel and rivet mask is needed for correct dust/grime masking and essential for doing some good chipping. Anyway,Pics:

We do, and it's still over performing a lot at high altitudes with full burner. The performance charts can be found in "SFI AJ37 Del 3". It should be available in a thread here on the forum if searched for if you want to dive deeper. If something is changed, and mentioned in the changelog, it's most likely for more accuracy. Even if that means performance gets worse in some way.

Not worth it if it was not faithful to the real aircraft.

Black Shark 3 Screenshots. https://www.digitalcombatsimulator.com/upload/iblock/09a/43hq50yxxon9xy2ep9tjr4ma6egi4dvq/dcs-world-flight-simulator-02-black-shark-3.jpg https://www.digitalcombatsimulator.com/upload/iblock/ece/zgrmlsimylf99w1n0iafoy33brh42a1j/dcs-world-flight-simulator-01-black-shark-3.jpg DCS: F/A-18C Rise of the Persian Lion II Campaign Screenshots

To clarify, I am not sure if there will be a hotfix patch, the campaign, if released next week, will be released as separate download first, not necessarily in a patch, or unlikely.

I have included both variants (RA64519 and RF64525) in version 1.1.1215 I also included covers for the cameras that will open/close depending on airborne state. However, these are highly speculative - very few public photos available. If you don't like the implementation, let me know. I have added RA-64529 (as well as your request for RF-64514 Ty-214R) in version 1.1.1215 Tu-214/Tu-214R has been updated to version 1.1.1215 - now available for download

Probability of detection is definitely a huge thing we are lacking in DCS. As another example of how it drastically changed how things should be: A dragging (cold) contact will have a lower probability of detection per hit, however because of the much lower closure rate compared to a hot target you actually have a higher probability of detection at any specific range, because you get more hits. This is talked about specially in a 1983 paper by Ringel on the APG-66. This is in contrast to DCS where a cold contact has a lower detection range.

Tried the 7900xt last night and was very disappointed. Frames were about the same or worse then my 6800xt. BAR had a noticeable negative impact on frames. Overall about 30-40% less fps then the 4080 I returned. 6800xt=50fps sitting on the ramp in F5 on Caucus however frames seemed to drop more during flight then the 7900 (relatively speaking, frames didn’t seem to drop in flight as much with the 7900 but they were still lower overall in flight as well with the 7900xt) to about 40-45. 7900xt = 42fps dipped into the high 30’s in flight saw high gpu utilization throughout (high 90's with 99% most of the time I was looking at it). 4080 = 60fps rock solid 60 or more in flight, gpu utilization was often below 90%, down to as low as 75% I’m currently running a 5800x3d with 32 go ram at 3400 with g2 in open xr. Cleaned up drivers with ddu after every gpu swap. Also probably worth mentioning that my 6800xt is overclocked/undervolted. I did not change anything for the 7900xt except BAR. On a sub note, the low gpu utilization of the 4080 is weird because if I turned on FRS with my 6800xt in VR and ran a low resolution I could easily get 90fps, which seems to indicate on this map (same for all comparisons) that I am not CPU limited.