Leaderboard

It is disappointing yes, we are all excited for the patch, but the team were not happy with final checks, so best to delay and take the extra time needed. Patch now planned for the 28th. thank you all.

Ka-50-3

Get a grip fella

Dear friends, first of all, many thanks for having supported us during all these years! Your words have been a strong inspiration for us and have encouraged us to try and make the MB.339 as detailed as we could make it. However, we are conscious that this will not be perfect, and due to its complexity, there is the possibility that new bugs or defects will be spotted: rest assured that development has not stopped and we will continue working to improve the plane. We believe in a complete, honest and transparent communication with our customers, so here is the list of bugs and improvements which we are working on at the moment: Missing features: Flight Director Gun Camera Wheel chocks Known Issues: The gunsight MILS settings tumblers should be discreet, now it is possible to set in between steps. Breakes on controls indicator window always ON Repair does not replace used/overheated/broken battery Missing many key binds Easily flyable with one wing if the aircraft is fully loaded of weapons Flaps do not have a collision model MB-339 Rear canopy does not break from ejection When replaying the trackfile the view position in the rear pilot appears too backwards so that it is covered by the pilot model Wingtip damage missing It is possible to eject in either seat and still control the aircraft if you are not solo. You cannot swap to the other seat, but nonetheless control is still possible. Also, the other guy should probably eject too if you can't swap seats to control the aircraft. (Even though the seats aren't linked) AI - Damage model might be over performing Damage to flaps has no effect on maximum speed straightline or stall speed (clean) The release is now imminent and we are really excited for our debut on DCS World as a third party developers. We look forward to your feedback and encourage you to provide constructive criticism so that our product meets the highest quality standards. Thank you! IndiaFoxtEcho Visual Simulations

you have given your feedback, but we have no plans to change how we do patch days. When we plan a patch we like to keep you all informed, its that simple.

The patch is currently still planned for the 27th but we do not have a time. Please remain patient while we finalise the patch thank you

Open Beta Public testing build Current version number: DCS 2.7.18.30765 Next update: Planned 28th October 2022 ( subject to change ) Despite our best efforts to patch today the 27th we will be moving the patch to the 28th Thank you for your patience

'Twas the afternoon on patchday, when all through the board Not a user was posting, not even a mod; The harddrives were placed in their cases with care, In hopes that St. Wagner soon would be there;

We really need a thumbs down reaction icon ..

It amazes me grown up people acting like crying kid on christmas when didn't receive the christmas gift that they wanted. Things take time, learn to deal with it. Life don't give us what we want when we want.

Sorry for the late notice on this- 2.8 has been a very difficult patch cycle and was a huge iceberg in terms of making both modules compatible. We unfortunately had to split the two patches apart because of this and decided to prioritize the F-14. We endeavour instead to ship Viggen additions and changes in the follow-up patch in November, while tomorrow's update simply updates the Viggen to be compatible with 2.8. This is disappointing, but we're not superhuman and can only do so much with these unforeseen roadblocks. Shipping only a maintenance update for the initial release of 2.8 is rather bitter for us as well, but we simply had to focus away the game breaking issues. For that I do apologize. We are pressing and trying as hard as we can on all fronts and trying to navigate this year as best as we can considering circumstances. There are some major issues, e.g. with damage modeling that are impacting gameplay and we are aware of how annoying they are and how they impact the grander simulation, and I am trying to puzzle together our planning to ensure the Viggen is not the runt of the litter.

How can you react like this? ... you are an old user, surely you must known a better way to react

Showing disappointment is not the issue with your posts. Your behavior around it is…. Immediately switching in the victim role also is a certain pattern. Perhaps you should reconsider how you express disappointment. Plenty of good role models in this thread….

Even if we are disappointed it is not a reason to yell at them, they do what they can we will have the patch tomorrow it's not death, we will appreciate it even more. Let's be cool and shake hands, we're on the same side Thank you ED for your efforts good continuation

Lol unfortunately this is one of those cases where they are darned if they do and darned if they don't. It simply is what it is, and we can look forward to hopefully tomorrow.

We're patient, we promise.

True, the gods do not like to be tempted. I better put a few bucks in the food bank can at the store as a sign of contrition. That said, everyone should put a buck in the food bank can if there is one. If we have $60 for a plane, I'm sure we can find a dollar or two to help someone who's hungry.

Complains like yours are the ones that will force ED to not state dates at all, since it seems so many people are unable to understand the meaning of the word "planned" or "estimated" .. once ED realizes that providing dates is counter productive, they will for sure avoid giving them .. I know that that's the way I would act towards this kind of customers.

well 2.8 on 28th is karma kinda

I'd tell the team to hold off and release next Wednesday

Case I operations in effect....Go to the fridge, grab one out of the Case and watch

Sitting here… refresh… refresh….refresh… waiting anxiously… as soon as my truck warms up I have to go work. Oh the suspense just to read a change log!

Dear ed team, can we expect long lasting contrails in 2.8? brgds maks

except, a single pixel in 1080p is 4 times the size of a single pixel in 4K. As higher resolutions become more common, ED should take that into account. Spotting is an issue in DCS. Single pixels that may even be outwashed by anti aliasing (or other gfx) are not a proper real life equivalent.

So is sitting in a dark room with a Track IR on your head. "Unrealistic" is such a silly thing to say. IRL, you can SEE aircraft at large distances. In game, you cannot. So the GAME is already "Unrealistic."

Dear All, Another major F-14 update is about to drop! One of the biggest features we’ve developed since launch for the F-14 is coming with today’s patch; namely expanding and extending our radar simulation to encompass Jamming and associated EW effects and their impact on the AWG-9- but we’re also shipping more features such as new JESTER functionality for mission editors and the in-cockpit VR pilot with this patch. Lets kick things off with a deep-dive into the biggest feature to drop, namely Jamming and Jammer Tracking for the AWG-9 NEW FEATURE: Jammer Effects, Detection & Tracking in the AWG-9 This new feature will now enable accurate effects on the DDD and TID for jamming, tracking jamming targets and guiding missiles on these targets, as well as any associated ancillary effects that we feel make sense to model in the DCS environment. Here’s a breakdown of some of the things you should expect: In summary, noise jammers prevent the AWG-9 radar from ascertaining (and therefore displaying) range or range-rate information on a target, until burn-through is achieved (when the radar return signal is sufficiently strong to overcome the received jamming noise). The AWG-9 has several features which allow the aircraft to still be effective against such threats, which we can detail further below; The DDD will show noise returns over the range axis at the azimuth of a jammer in pulse search mode, which looks something like this: In Pulse Doppler modes, the DDD shows a jamming intensity trace overlaid on the lower one-third of the display. This is essentially a graph of received wideband power vs. azimuth, and thus also shows smaller normal radar returns. Where a noise exceeds a predetermined threshold, a JET (Jam Exceeds Threshold) vertical strobe is also displayed on the DDD at the jammer azimuth. Note that due to what we feel are justifiable DCS limitations in jamming fidelity, the JET (Jam Exceeds Threshold) settable knob is not implemented at present. Here’s what this kind of intensity trace can look like on the DDD: Jammers will show up with a jamming strobe (straight line in the direction of the detected jamming signal) on the TID in TWS and RWS modes, these can be toggled with the Jam Strobe button beneath the TID. If range/range-rate is not available for the jammer (beyond burn through), an angle symbol (<) is displayed on the strobe at 50NM from your aircraft. The jam strobes are also shared over Link-4C fighter-to-fighter datalink, allowing for eyeballed triangulation of actual jammer position, an example of which looks like this: The TID angle symbol is hookable, to allow the RIO to try to get an STT lock via the PD-STT or P-STT buttons. The HCU radar cursor can also be used in the normal fashion on the DDD to try to acquire jamming targets in PD search or P search. We’ve extended JESTER functionality to also allow him to lock jammers ahead. Practically speaking, when a jammer is locked in any of these scenarios, it leads to a special STT submode named Jam Angle Track (JAT). In JAT, the range/range-rate of the jammer is unknown, but the angles are known and can be tracked as such. Instead of the RDROT (Radar On Target) light above the DDD, the JAT light is displayed in this case. On the TID, the angle symbol (<) is displayed along the jam strobe at 1 inch from own aircraft position in STT-JAT modes. When burn-through is achieved, the angle symbol will disappear and be replaced with the normal target symbol at the correct position. Conversely, if an STT target starts jamming (and is beyond burn-through), it will automatically transition to STT-JAT submode. In STT-JAT sub-modes, both AIM-7 and AIM-54 can be employed in Home On Jam (HOJ) modes. Since range is unknown, lofting is disabled, and the missile guidance is similarly limited to only using angle information to intercept the target. HOJ launches are therefore limited compared to normal STT launches, but in the end, better than nothing. With this update, we hope to take another large step forward in our simulation of the AWG-9 radar and associated systems, and bring us far closer to a fully realised picture of what utilising and operating this radar system was like in a live combat environment. The effects described above and the associated functionality in the AWG-9 will have to be accounted for by all RIOs and JESTER, and significant changes in how you approach various situations may be required. We’re proud of our work on simulating this aspect of the AWG-9 and greatly hope you will enjoy flying and fighting not only enemy bandits but also their emissions. New & Expanded Feature: JESTER Custom Commands We love supporting all the wonderful and talented mission and campaign-builders out there in the community. One of the great things about multi-crewed aircraft is that it can bring a sense of immersion that single-seat aircraft can’t- and JESTER is a big part of that for the F-14. Over the past few months, we’ve invested significant time in extending JESTER’s functionality but also giving mission makers deep hooks into JESTER to enable you to control the RIO at a granular level and make this a key part of your narrative toolset. Succinctly, we’ve added a large number of commands which let JESTER perform actions on his own, at the behest of the mission designer, without the player’s input, which can help drive a scripted narrative or create the illusion of him being an autonomous RIO who both thinks and acts on his own in the context of pre-planned situations. These set commands can be triggered in the mission editor as actions, following the entire range of conditions provided to the mission creator in DCS, from unit inside zone, to flags being true, etc. The first major addition to these were the LANTIRN set commands, which we demonstrated in the mission “Training Day” - they let JESTER scan zones, track targets, designate and undesignate whatever is in the crosshairs, and thus help create the impression of the RIO pro-actively searching an area and fulfilling his mission to locate, track and engage a target. Additionally we gave mission creators the ability to make him go silent or talkative again, so that mission-based voice acting does not cross over with the normal JESTER comments that are situation-based and can conflict with scripted dialogue at any given time. We’ve also added the ability to make JESTER change channel presets for the AN/ARC-182, tune TACAN channels on his own, change steerpoints, create steer points from coordinates belonging to a trigger zone, to set the WCS to on, off or standby, manipulate the TID range knob, perform an RWR test and even have him eject on the command of the mission creator. With this latest update, we are introducing even more set commands to further the mission creator’s abilities. He will now be able to select weapon stations, set the weapon selector wheel to a preselect and desired weapon for air to ground missions, set ripple quantity and interval as well as all additional delivery modes, he can set attack modes like computer target, computer pilot and manual. Furthermore he can now manipulate the radar scan zone in elevation and azimuth, he can STT a specified target (and break lock again), and also perform a missile launch if the mission creator so desires. To give you some insight into a “on the ground” usage of these tools; here’s what the wonderful Reflected had to say about using this new functionality in the upcoming “Speed & Angels” campaign! To guide you through using these tools, here’s a tutorial video from Reflected himself running you through how to use these tools in your missions. We greatly hope you’ll enjoy using these new JESTER tools to craft immersive, guided and curated experiences for the Tomcat. Check out the full list of commands here: https://forum.dcs.world/topic/311033-jester-set-commands-full-list/ New Feature: In-Cockpit Pilot Last but not least; we’re finally implementing in-cockpit pilot bodies for both the Pilot and RIO positions. These new pilot models were sculpted for the purpose of not only serving as cockpit bodies, but will eventually replace the current lower detail bodies in exterior view and in the cockpit for the other crewmember. This will however be added at a later date. We’ll be adding more customization functionality as we go. null The non-exhaustive changelog for the F-14 in 2.8 looks as follows: DCS: F-14 Tomcat by Heatblur Simulations NEW: Introduced Pilot and RIO body for front and back cockpit. NEW: Added jammer detection and tracking functionality in the AWG-9, which adds amongst other features: Noise jammers will now prevent AWG-9 from ascertaining range or range-rate from a target. DDD will show noise returns over the range axis at jammer azimuth in pulse search. DDD will show jamming intensity trace overlay in pulse doppler modes. TID will display jamming strobe in TWS and RWS modes. TID jamming strobe can be toggled via Jam Strobe button below TID. Jam strobes can be shared over Link-4C fighter to fighter datalink, allowing for eyeballed triangulation of actual jammer position. TID angle symbol is hookable. PSTT or PDSTT on jamming target leads JAT (Jam Angle Track). STT-ed target transitioning to jamming outside of burnthrough automatically switches to JAT submode. In STT-JAT submodes both AIM-7 and AIM-54 can employed in HOJ (home on jam). Added jamming targets to JESTER STT options. NEW: Added new list of set commands for JESTER to be used in the Mission Editor. 10017 to 10033 are new. For a full list visit this post here. Reverted AIM-54 loft to state before looping hotfix to revert exceptionally poor performance (by ED). Fixed forward rendering for canopy sealant - will now not appear shadowed at odd angles anymore. Screens and other glass surfaces will now reflect sunlight again. Added non-gfx external args to check the status of JESTER tracking air targets (to be used with scripts): 1026: tracked predefined target; 0.01 - 0.99, same as command 10024; 0.0 - no predefined target tracked. 1027: range to predefined target (only when tracking); 0.xxx - three digits of distance to tracked predefined target in NM. Potential fix for mission freeze including F-14 AI. Made LANTIRN available as laser designator for the AI. Fixed ALT HOLD not working >36k AGL. Fixed flashbang-like sun glare on internal canopy glass. Fixed MiG-23s not taking off in PG Flogger Faceoff Mission. Adjusted all Quickstart BVR missions for new AIM-54s. Removed instances of “color” shader in cockpit due to deprecation Minor cockpit optimizations - fixed some visibility arguments not triggering LoD changes Thank you all for your support. We hope you’ll enjoy this update to the F-14 in 2.8; and we look forward to sharing more on the F-4, Eurofighter, Viggen and others very soon! Sincerely, Team Heatblur

Probably discussed to death already but, the current solution to rendering distant aircraft as a single black pixel doesn't scale for different resolutions (eg. high-res display pixels are significantly smaller than low res). It also pushes players away from using anti-aliasing (as those distant contacts get smoothed out of existence). I'd really like to see (hur hur) aircraft visibility improved, maybe using a combination of smart-scaling, resolution-independent standins (like use a small sprite instead of a pixel), and visual effects (eg sun glints) to catch the eye. Or whatever else the talented folks at ED can think up! Totally appreciate that maintaining visual contact is a real challenge that's hard to do in real life, but feel like we're fighting the graphics most of the time. I don't think anyone really wants to fly with labels on. I'd even take a highlight aid that you can toggle on with a keypress to subtly highlight contacts when they get lost in the pixel soup.

Thank god for ice cream. I can drown my sorrows in chocolatey goodness.

Quite.....We complain that we don't get given a timescale, then we moan when it's not met. Perhaps silence is the best way, mostly.

I'd much rather have a tested good quality release later than a buggy release earlier... said everyone... always

Dude.... delayed again? This is not serious, how can don´t realize there´s an error just hours prior to the release date, say you are goint to fix it on the next day, and delayed it again? Why do you state dates if you don´t know whats going on and have no idea when is is gonna be fixed?

patient /ˈpeɪʃ(ə)nt/ Learn to pronounce adjective able to accept or tolerate delays, problems, or suffering without becoming annoyed or anxious. "be patient, your time will come"

We have a poet here! I know, it's stupid, but the feeling on patch day is similar to the excitement on christmas eve as a kid.......

At last! ... today the Mirage F1 section was added to User Files https://www.digitalcombatsimulator.com/en/files/filter/unit-is-mirage/apply/ I will re-test my missions on DCS 2.8 and then share them on the new section

Thx a lot sniper for your work...I was confused, with the octopusG teasing on their FB page, and was wondering if you were keeping your project alive. May the force be with you man !

Hi Cobra, it’s a nice move (serious here, no irony!) of you to chime in here and explain. And while you and your team do have my sympathies for all the difficult additional issues you are facing this year, I can still only echo @Spirale‘s point: It is your decision what you prioritise and time and time again the Viggen gets the short straw. I very much get that you run a business and that other considerations influence your decisions. But still I can only repeat it and I’m sure I’m not the only one who feels that way, as a Viggen customer, this is a really disappointing trend and it’s been that way quite a while. It’s not like this happened only once or twice with the lopsided updates /development (from what is available to us customers, not your internal builds). It was many many update cycles. That plus the (by now ) very stale assurances from you and/or IronMike that this will change and that the Viggen will receive more development soonish leave a bad taste for a customer. Because, I’m really sorry to say, by this point I don’t believe them anymore and you have lost my trust in that regard. I do believe you have the intention and want to improve the Viggen, but in my personal opinion you would need a serious ,conscious and lasting change in priority and task assignment if you really want to stop disappointing Viggen customers and get this done . Of course you could also keep up with the current coffee drip drip strategy and the Viggen will only be done in a decade or two. But in this case I would advise against putting out further Viggen development assurances/update announcements, because it’s just making things much much worse from a trustworthiness perspective , even if I’m sure they’re not meant that way. But it’s your train set in the end. All that being said, I do you hope you personally and the Heatblur team is safe and ok because I know you and them were facing various different difficulties ! My best wishes for you all . regards, Snappy

To be clear, seeing dots at a distance isn't the only visibility issue. Objects get lost against the background far too easily imo. Sure, this happens in real life as well ("losing tally" wouldn't be a thing otherwise), but in the game we're also fighting against aliasing, texture filtering, and res/fov differences. Plus in real life, our eyes and brains are just that much better at focusing and picking out objects at different distances. All this means , that for me at least, I end up playing this game leaning forward squinting at the monitor trying to look for pixels (sometimes getting them confused with specks of dirt), and losing sight of my target the instant it dips in front of literally any other object. I've seen plenty of people using post-processing effects to increase sharpness and add subtle outline, to help combat this. Feel like.. there are obvious limitations with the graphics, and we can't perfectly recreate reality. That's fine. But I also think it's inaccurate to say it's more realistic/immersive without any visual assistance, because we have to deal with problems in the simulation that just aren't an issue in real life. I'd lean towards playability and accessibility anyday.

Even at a high level, jamming burn-through range should be dependent on the power/gain of the radar, the power/gain of the jammer, the RCS of the defended asset, and a signals processing factor. ED does none of this. Just like target detection requires sufficient Signal to Noise ratio, jamming requires sufficient Jamming to Signal ratio, with the 'sufficient' ratio depending on the type of jamming implemented. Without making things crazy classified the easiest way for ED to go about this would be to have each ECM system for an aircraft have a jamming effectiveness rating that reduces detection range by a fixed percentage, as RCS and Radar power already account for normal detection range. I get that HB is just trying to play ball. What we DO have is a BIG missile with HOJ capability and the ability to triangulate the range so that the user can fire it off at ~35nm then turn around before their own jamming is burned through.

DCS Patch status Current versions: https://updates.digitalcombatsimulator.com/ Change logs: https://www.digitalcombatsimulator.com/en/news/changelog/release/ Release Version Current version number: DCS 2.9.19.13478 Next planned update: To be announced

Hello, one of my biggest wishes for the Super Carrier would be a Recovery Tanker without the need for any Setup in Mission Editor. My thought is that this one can be called via the F10 Menu and will be launched from the Carrier, and takes Station like a Racetrack at 6000 feet in the close proximity of the Carrier. Greetings Sky

I am sorry to ear that, anyway I hope you enjoy it during the trial period. Have a good luck for everything Inviato dal mio ASUS_I005D utilizzando Tapatalk We are sorry that we have not finished this feature, probably we assigned wrongly some priorities. We know the importance of this system and we will focus all our effort to add it shortly. Inviato dal mio ASUS_I005D utilizzando Tapatalk

Permettimi di difendere la categoria: "dilettantesco" sarebbe stato rilasciare l'aggiornamento senza averlo testato a modo. Del resto, se hanno deciso di rimandare ancora il rilascio e' sicuramente a causa del fatto che il problema che hanno trovato non e' ne una pinzellacchera ne una quisquilia, ma qualcosa che poteva seriamente pregiudicare l'esperienza di gioco. Ben venga quindi il ritardo se questo significa meno problemi al rilascio. Quanto al "subject to change", piu' che una parata di fondoschiena a me sembra una onesta ammissione del fatto che nel caso spunti un problema all'ultimo minuto non affrettano il rilascio solo perche' oramai lo avevano programmato. In passato sono stati molto critcati proprio per questo e il fatto che hanno diradato i rilasci dell'OB e' stata la loro risposta al problema, a mio modo di vedere azzeccata.

Please keep this thread for patch notes discussion. off topic posts will be removed. thank you

Hi all, please play nice with each other.

Еще бы помимо 29-го изучили возможность создания Ил-2 и Су-25/27/27УБ/33/30.

Thx for your reply Cobra. That's being done you said " we are not superhuman"....True BUT you explain to us that you cannot take car of the two module à at the same time. while I also understand this, i know you are yourselves your own bosses and you are responsible about your decision. You are not superhuman but you choose to always prioritise the F14. That's the problem... Since not monthes but years now we, Viggen fans, pilots, enthousiasts, are waiting for a "balance of care" between Viggen and F14: nope only one side is treated....The Viggen receive crumbs...Look at updates history: hundreds of lines for the Tomcat, crumbs for the Viggen... So yes your are not superhuman but responsibto to not alternate the improvments . On my side , IRL i am not demanding but this time i am fed to always read the same things from HB about the Viggen and i fully agree with Snappy: the Viggen is without a doubt a black sheep...No wonders why the Viggen remains a non popular module... Regards ps: and who cares bout dynamic numbers on tail really? FM@high speed, flying without wings, drag indexes and so on are way more criticals..