Leaderboard

Yep, before every new DCS update I save and archive all the LUAs of the current version. I then run a compare on all the scheme files and check what kind of changes they have implemented. Sometimes it's necessary to change my assets for them to function, and sometimes I find new features to put into my assets. But this one is different. The scheme used for the mentioned cruise missiles (including the DCS core Burke) hasn't been changed since July. That's why I suspect the change is somewhere else in the core.

DCS 2.9 Graphic Options FAQ The introduction of DCS 2.9 into the Open Beta provides users many new options to tune and improve performance and visuals. Please note that you must be running the Multithreading version of the game to use these options. DLSS 3.5 for Nvdia Users DLSS, or Deep Learning Super Sampling, has been introduced for DCS users that own a Nvidia 20xx, 30xx, or 40xx series graphics card. With DLSS you can run DCS at a lower resolution that is upsampled to a higher resolution to provide better visuals without a performance hit. Why is the option greyed out? As stated above, you need to be running in Multithreading and have an Nvidia 20xx, 30xx or 40xx series Nvidia card. These options are not available for the Single Thread version of DCS. Why is it blurry? With DLSS you have a number of options; Quality, Balanced, Performance and Ultra Performance. These along with the Sharpening slider, described below, allow you to adjust the upscaling between visual fidelity and performance. There is no one answer for all players, so we suggest that you experiment to find the best balance for you in combination with the Sharpening slider. Is Frame Generation supported? Because DCS 2.9 is a DirectX 11 title and DLSS 3.0 Frame Generation requires DirectX 12, it is not possible at this time. Why do I see little to no performance increase with DLSS? If you are CPU-limited, meaning that CPU computations and not your graphics card are limiting performance, you may see little to no improvement. Further, if the scene is not very graphically demanding, you may not see much change. You will see the most change over high-density scenes like large cities. FSR 2 for AMD Users FSR 2, or FidelityFX Super Resolution 2, is a similar solution to Nvidia’s DLSS. One main difference is that Nvidia users can also enable FSR 2, which opens up options for other Nvidia cards like the 16xx series. As with DLSS, your results may vary; try out different settings to find the ones that work best for you. What is Scaling? FSR 2 Scaling controls how much the image is scaled up; adjust this to control your FSR 2 upsampling results. What is Sharpening? As an image is scaled up, it may become more blurry or fuzzy. This may be particularly true for a Heads Up Display and Multi-Function Displays. Use this to adjust how much sharpening is added to the image to try and smooth it out. The more sharpening, the greater the impact on performance. NIS (Nvidia Image Scaling) NIS is a cross-platform alternative to Nvidia’s DLSS. It does not require RTX cards and can be used on other brands such as AMD. Like FSR you can control the scaling and Sharpening. TAA (Temporal Anti-Aliasing) TAA is an anti-aliasing option that uses current and past frames to smooth out the jaggedness of the current frame. It will also result in better performance but with some loss of visuals compared to MSAA. Does Sharpening work with TAA? Yes, you can use sharpening to try to improve the image if it's still too fuzzy or is jagged. Again though, increased sharpening can impact performance. Like much of the graphics settings, it’s about finding the balance that best meets your needs. SSS (Screen Space Shadows) This is a new option that allows for better shadow rendering, specifically in environments with many objects such as grass, bushes, and forest. It gives these areas a more realistic look and feel without any performance hits from standard shadow maps. Color Grading Color Grading was generally added for you to easily add different color effects to your images and videos. You may also find a color grading that you prefer to fly with. You should see no difference in performance using this. LOD Switch Factor As we work to improve the LOD (Level of Detail) system in DCS, this option allows you to control when the LOD system changes from a more detailed model to a less detailed model at greater distances. The current default is 1. Lowering this lowers the details on closer objects/units, and this will increase performance. Conversely, increasing the slider value will allow for more detailed models to be seen at greater distances, and it will reduce performance.

Hello. I came across this on reddit and confirmed it in game. The B-1B model seems to have been cut down in resolution compared to the newsletter picture. Is this intended or a mis-export of the model? null

I think I'm going to hold off making any changes to my assets until ED have released a couple of 2.9 hotfixes. Otherwise I'll just be chasing my own tail. Edit: It looks like ED decommissioned and replaced the scheme I used for the JDAM-ER. That's why we have this on the 2.9 changelog: DCS: JF-17 by Deka Ironwork Simulations Fixed: LS-6 and GB-6 do not fly to target So I have updated the JDAM-ER accordingly, and it works fine now. I will release the updated MiG-29MU2 since it doesn't seem to have anything to do with the other strange missile stuff going on.

Hey I just wanted to share my thoughts on the newly dropped OB 2.9 and DCS in general. The last year has been a big, big one for DCS. We got Multithreading, DLSS and voice comms is getting up there to SRS level (not quite yet, but it will, making the whole game more and more enjoyable). I got into DCS as I was starting my pilot training about 10 years ago, because I was searching for a decent helicopter simulation and the options were kind of limited at the time. I bought the Huey in early access and from there on the whole thing has crept on me like those additional tasks at work, only I enjoy this one. Of course DCS has problems, issues, annoying bugs, stuff that could be done better. AND it costs an arm and a leg. Not just the software itself (which is free, the modules are kind of expensive - the huey was 49.99 in 2013 when I first got it in beta) but in terms of the rabbit hole it made me go down with peripherals, I must have consumed about 10k on sticks, throttles, collectives alone, not counting the PC hardware and recently the VR related stuff. AND the time sinkhole this whole hobby tends to be. But it makes me happy. This thing makes me want to play since 10 years and it is something no other game has been able to do, to date (and I am fast approaching 50y.o.). The other game with a high enough hours count to be comparable is Elite Dangerous, which I played from 2016 until about 2019 and where I have a measly 1800hrs played... DCS hasn't got a reliable way of counting the hours I have spent in the virtual cockpits, but I would venture to say I have might have accrued some 8-10K hours to date. It's just that good, to me. So here's my thanks to ED for making, keeping up in supporting and developing such a piece of software.

I'm using a G2 and I thought spotting in VR was perfect previously. The best it has ever been. It was a sharp dot at a distance and now it is totally immersion breaking with a big black square. It's akin to playing with labels on.

ERJ-145, 135BJ is updated to version 0.0.2 . Added: LODs, collision models, night lighting. DL link is kept from ver 0.0.1 in 1st post / User Files area. --- DC-9 and MD-83 need more weeks to finish.

comparing the cbu_97.lua from dcs 2.8 and 2.9 for that weapon, it looks like the explosive mass value of the warhead changed from 3.0 to 0.3 that‘s a pretty large difference same applies to cbu-105 maybe that’s a typo @BIGNEWY/ @NineLine

It's to enable communications scrolling. It's now possible to scroll through the radio menu instead of using hotkeys

Good news! Thanks for confirming no explosions! Inviato dal mio ASUS_I005D utilizzando Tapatalk Thanks for reporting no explosions! This is a little success [emoji3] Inviato dal mio ASUS_I005D utilizzando Tapatalk

Marder 1A5 IFV (Germany) version 1.0.0 released! Changelog Version 1.0.0 Release version

Good technical breakdown of the new features.

Hello there! I would like to submit a potential issue with the search & identify function of the Peterovich AI for Mi-24 Hind. Yesterday during a multiplayer session I noticed that Peterovich had significant difficulty in locating targets on open fields, even in very close range. In this case the target is a AI BMP-2 and a T-55, both stationary, with a handful of destroyed wrecks, and one friendly AI M-60 nearby. Time of the in-game session was mid-day and weather condition was clear. Aircraft was being flown without any aggressive maneuver at reasonable altitude and no battle damage had been sustained. Peterovich failed to locate the targets even after the BMP and T-55 had fired upon my aircraft, but he did warn me about the in-coming ground fire from 12 o’clock as usual. I do notice the newly implemented changes in 2.9 for Peterovich AI to act according to target density and possible obscurity of the targets. In this case however, both targets were located in open fields, and no bush or tree or building could obscure Peterovich’s view. It was also not likely for Peterovich to be overloaded as there weren’t too many targets for Peterovich to process. Swapping a fresh aircraft and flew to the same target area did not fix the issue, neither did re-entering the server provide any help. The issue was repetitive during the whole game session. I am therefore confused by the behavior of Peterovich and I would like to ask if you could kindly provide any assistance? Or it maybe it is a potential bug? You can find my track file as attached to this post. Thank you! 001.trk

Reinstalled them this afternoon and it's dropped the VRAM usage a fair amount so still on my ovgme list for now

In the Open beta TEST build they should be identified before release, but they need to be fixed for the release. Depending on the root cause it is absolutely viable to simply deactivate stuff or ignore bugs until the rest of the development build is in a state that supports a fix. E.g. instead of fixing bugs in the AH-64D EUFC radio operations, the devs decided to deactivate the functionality, until the DataLink and radio presets have been developed to a state where the bugfix made sense. It took quite some time but at no point in time the Apache was "broken" leave alone DCS unplayable. Same for the "missing town of Afrin" that took years to be added. Still nothing that prevented players to enjoy the Syria map in the last years... I am not saying everything is perfectly ok with the Sinai map, but it is absolutely ok for a developer to have a roadmap that differs from customer expectations.

Hmm, no mention of the cruise missiles issue, or am I blind?

Hm, I have no issues with it.

threads merged, we are working on a fix thank you

We are looking into the DotRendererExperiment = False as it does not seem to be working correctly. the team are aware.

This update is creating a lot of problems with mods.

Please dont apologise Urbi, your workmanship and help is always very much appreciated. I can see what the problem is now, and have started to fix my liveries. Many thanks again my friend, you have saved the day.

The glare shields are fiberglass. They delaminate like that due to the sun exposure, and physical abuse they get. The Heatblur F-4E cockpit looks very much like what I remember from my time working on them in the 70's and 80's.

Вот теперя вас люблю я, вот теперя вас хвалю я (это разработчикам по поводу производительности и оптимизации). Вот только одна мааааленькая, но большая просьба: НЕ СЛОМАЙТЕ НИЧЕГО в последующих обновлениях! Вот как только увидели, что ваши кодеры лезут в оптимизацию, сразу бейте им по рукам! Можно тяпками.

This is the OPEN Beta version. You and some others might wish to consider it as the stable version, but it’s not. There are some implications of effectively being a beta tester

They changed the format, I have seen it said because people were stealing their models. This is understandable. They have advertised these 3D models for a very long time, all the time obviously better then the ones they deliver. Very nice, last part less so, still explainable. They gave us the wrong versions of all 3 of the highlighted upgrades, delivering worse versions and somehow did not catch this despite testing the update for weeks. This is a bit suspicious. Nineline and everyone else in the channel refuse to simply say 'it's a bug'. Instead insist that there is more information coming later. Are they not at liberty to say if things are a bug? It is not in the Known issues list: Despite being reported no less than 4 times in the object bugs section alone, 5 times if you count this post, At least 2 of which times where reported back to ED, roughly a full day prior to the known issues list being published. Finally, there is only one livery available and every texture within it is prefixed with 'low'. I wish I could be as casually dismissive as you are and I would be glad to be proven an idiot in this case. I don't like to speculate about ED and I don't like to hate on them either. I have more reason than most to hope for the best from ED as well as their continued success. At the same time this is hard to be dismissive about. They have quietly delivered models noticeably worse than what they have been advertising since at least the beginning of this year, models that are below the standards of what they were putting out at least 2 years ago. We know that the models aren't the same, and now I have shown you all of this. Take it as you will.

Could you name a single bug on this map that breaks the game and render DCS unplayable?

Change Log for Version 2.0.0.37 *(In order fixes were committed): ** Note: the Preset Editor will not add missing lines to the options.lua, it’s recommended to launch DCS to populate missing lines. ** - Fixed Mislink for Avionics Language in Saving Preset Function. - Condensed Parsing for v1.1 Scan Functions. (From 18 Lines and 3 Functions to 4 Lines and 1 Function) - Added Checkbox on App Settings Page and Synced with External Apps Launch Switch on Adv. Launch Page. - Adjusted layout of External Apps block in App Settings. - Adjusted Size/Position of Preset Profile Radar Graph. - Added Missing Cockpit Tooltips to Camera / Views Menu. (Uses v1.1 Parser) - Restructured Log Readouts for Scan/Import and Update/Save Functions in LUA Parsing For v1.1 Parser Items. - Cleansed Rem'd Lines and Notes from Scan/Import Update/Save Functions. - Added Difficulty Controls (All use v1.1 Parser). - Added Exception Catch on Generate Default Options.lua Function. - Fixed Mis-link in Preset Switching / Saving When using Status Bar Button to Change Preset. - Removed Duplicate Preset Scan Function Call when Using System Tray Menu to Change Preset. - Rem'd ""shadowTree"" from parser (Value hasn’t been used since Pre-1.5 iirc). - Added User Setting String for Compare.Lua Enabled Option. - Added Changed Values List to Changed Settings Preset Prompt. - Removed Single Instance Limit (Resolves some loading issues if the previous instance is still in memory). - Fixed Tooltips for the Difficulty Menu Controls. - Corrected Mislink in Module Scanner for Flaming Sunrise Panel and Information. - Added Color Grading LUT to Parser and UI Under Shader Options. - Audio Settings Page Completed (Uses v1.1 Parser). - Misc Settings Page Completed (Uses v1.1 Parser). - Added Mi-24P The Border Campaign Assets. - Added Mi-24P to Campaign Aircraft Filter. - Adjusted a few Campaign's Eras. - Added Exception Catch on Preset On Copy Function if file already exists in destination. - Adjusted Enable Preset Editor Logging. - Adjusted Preset Saving/Comparing And Loading/Importing Functions for Slider Values. - Renamed Graphics Preset Editor to Options Preset Editor. - Renamed Misc / Plugins Page to Miscellaneous. - Converted Logbook Scan to v1.1 Parser. - Adjusted Logbook Parser Logging. - Converted ServerSettings Scan to v1.1 Parser. - Adjusted ServerSettings Parser Logging. - Adjusted ServerSettings Panel Layout. - Adjusted Upscaling TrackBar Visibility when Selecting DLSS. - Adjusted DLSS Quality Drop Down Location and labels. - Removed DLAA from DLSS Quality Drop down - Adjusted TacView User Path from Browse to File to Browse to Folder. - Adjusted TacView Check to Scan for 32 and 64 Bit Executables. - Added Tacview Checkbox to Force 32-Bit Executable Use. - Corrected Typos on Render/Shader Pages. - Adjusted Parsing Values for CivTraffic, Adjusted Save/Load Function to Match. - Options Pages for Render, Shader, Terrain, VR, Views all Converted to Parser v1.1. - Activated SZ Cinema Preset, ED Sim / Game Presets, and Updated SZ Ultra Preset. - Minor Position shift for the Preset Radar Graph. - Converted Import Preset Function to Parser v1.1. - Rem'd Old Parser v1.0 Code, to be cleansed. - Adjusted App Settings Layout (Sorted Items). - Added Enable Compare/Prompt Option for Preset Editor. - Updater Server Settings Compare Function to Match Preset Compare. - Corrected Various ToolTips. - Cleansed All Rem'd and Depreciated Code/Controls. - Fixed Thread Exception Crash when using DXDiag Generator Function more than once. - Rewrote Theme XML Writer, Unified all Themes to Single XML Template w/ Switching Data. - Precoding for User Custom Color Themes. (Not Activated). - Fixed / Adjusted Parsing and Filtering for Anti-Aliasing Values. (Same Adjustment for Import Function). - Fixed Mis-Link in VR Confine Mouse Setting. - Added Renaming Function to Preset On, if an Old Options.lua was left in /Preset/Default/ App will rename and Load Preset. - Corrected Math Error in DLSS Ultra Performance Resolution Calculator. - Added Dynamic Resolution calculator and linked to Upscaling Scale Slider. - Adjusted NIS / FSR to use the same Input/Output Resolution Display Label. - Adjusted Startup Procedure. (Re-ordered functions, moved App Minimized/Show to Last command). - Adjusted Sim Scan and Module Scan Engines for separate parameters when running during app startup ( Scan Engines will run on thread 00 during startup, and their own new threads after startup. ) - Preset 1-4 Renaming Moved to Context Menu, Buttons Hidden (If Needed for Revert), and Background Graphic Removed. - Slots 1-6 Configuration Items Moved to Context Menu, Buttons Hidden (If Needed for Revert), Background Graphic and Update Graphic Updated Repositioned. - Added "Update This build now" option to each Slot's Drop Down Menu. (Update Specific Builds without having to change slots.) - Added Ability to Rename VR Headset Preset. - Fixed Mis-Link in Head Movement, Mute While Minimized, Control Stick. - Added Loaded Preset Values for Scanned/Skipped/Loaded/Failed/Exception Count to Preset Screen. - Added Saved Preset Values for Scanned/Skipped/Loaded/Failed/Exception Count to Preset Screen. - Added Upscaling AA Rules for NIS/DLSS/FSR. - Button for "Custom Theme" testing Hidden. - Removed Some Controls that were hidden and no longer used. - Correct Su-33 Release Date Value. - Added Module Info Panel. - Adjusted Module Info Parsing for FC3 Aircraft. - Added External App / Scripts Function to Dedicated Server Launch. - Adjusted Custom Scripts Function, Moved .Bat Save from App's SG Folder to Selected Build's SG Folder, Now Build Specific. - Added Path debug line in log when No Options.lua or ServerSettings.lua file is found. - Adjusted FC3 UI Elements & Modules to read "FCS" ("Flaming Cliffs Series") - Removed Web Browser Control for Embedded Youtube Videos from Module Info Panel., - Adjusted module info panel layout (entirely WIP / experimental). - Module Info Panel Activated for A-10A -> C-101, and Asset Pack Modules (as Test). - Removed Button Disable Function for Slots If no build is Set.. - Removed Local Source Backup Renaming if Local Source Switch is set to off. - Added Screen Space Shadows to Preset Scan / Editor - Adjusted Preset Load, If No Preset is Selected it will attempt to scan default options.lua - Added Falklands and China Asset Pack Module Panel - Added Campaigns (F-16 First In Weasels of Syria and Black Shark MAD) - Adjusted Shadow Dropdown Rules for Screen Space Shadows - Fixed Tooltip for Screen Space Shadows. - Adjusted Layout of Rendering Tab. - Moved LoD Multiplier from Scenery Tab to Rendering, Renamed to Match DCS. - Tooltip Corrections.

Hello! I have a problem with the AJS 37 after the DCS Open Beta 2.9 update. I use multi thread exe. The aircraft is sunken into ground when on ground. No problem with AI AJS 37, only when I am player. I have no problem with the F-18C module either. The same problem occurs on Caucasus map, Syria map and Sinai map. I own The South Atlantic map and the persian gulf map but have not installed and tested on them. Other than that the AJS 37 module works fine as far as I know. Best regards: Otulf AJS 37 GEORG AI mt 2.9.trk AJS 37 GEORG mt 2.9.trk AJS 37 Incirlik mt 2.9.trk AJS 37 SINAI mt 2.9.trk

ALCMs and Tomahawks are orbiting after launch, especially if enemy SAM installation is present nearby.

I really like all Taz1004 mods, they all make complete sense to me and improve the game. It's not like I'm a fan and blindly download, it's just I've tried them all and I have them all ever since. I seriously don't understand why they are still not in the base game.

I am looking into it, I might not get a response until Monday.

I regulary see commercial airplanes in the hold at biggen hill which is approximatly 8nm from my position, they then fly the holding pattern that takes them further away from my position, the only time i have trouble seeing them is because of cloud or ground objects. my eye sight is worse than 20 20

Yeah, that gives me hope, that this is just a bug and the internal build does have the showcased models. Strangely, if you check the 2.9 Launch trailer, it is using the downgraded model, which is currently available in the game. The loss of files was just a hypothetical scenario I made up. What I'm trying to get at, is ED should be more transparent, even if the explanation is something embarrassing. Giving us the silent treatment, or being vague just sparks suspicion, speculation and mistrust.

Hi , I see the same problem, Maybe is it needed to post it in the bug section ?

As a very enthusiastic adopter of the dot fix mod when it passed IC, I've got to say this is a large step in the right direction. 3440x1440, I am able to visually pick up a Fencer at just under 20nm if I know where to look. This is probably a bit too far away to be seen, IMO and I don't think the original dot mod would have rendered an aircraft at that distance. At ranges under 8nm, the scaling seems pretty reasonable. I still have a hard time spotting aircraft, but when I'm able to visually track one, I feel like I haven't had any of those moments where a LOD change renders them invisible. I also have a G2 but I haven't yet tested that properly. I'll report back when I get a chance to do so. Good job so far, ED. Options.lua

It's all of the models in the new format, under CoreMods\HeavyMetalCore and those models alone. B-1B, B-52H, LPWS, S-3B and all the new S-300PS models - they all look as though they're LOD1 models (i.e the next step down from full-quality) as opposed to LOD0. I mean, the B-1B lancer appears in full-quality (as does LPWS, the S-3B and the new Big Bird radar) in the recently released short cinematic: You can also see higher-quality elements on LPWS (higher-poly EOSS and rungs present) and on the Big Bird radar (antenna elements present in 3D as opposed to just a texture). My guess is that it's probably just a bug with the new format, though said new format makes me a bit worried because they seem to be containers (possibly encrypted) and cannot be read in the modelviewer. There are some files that cannot be accessed which are necessary for modders looking to make liveries (as right now, there's only one for each, even though the same short showed a camouflage livery for LPWS and we've seen a 69th Bomb Squadron for the B-52H in a screenshot in a newsletter).

Alright, I have no idea how I did it but it works now. I have installed even more of your assets and it started working.

You are not thanked enough, so ......THX for your hard work and outstanding quality which leads to an unmatched immersion

@Hiob (Sorry, I was away at work) yes, I eventually got it thanks! Using MT version and DLSS, my performance in VR increased tremendously!!!

Devs are working to find out what causes this issue.

We are working on it. Txs!

This is what happens when community pushes for something they feel should be correct. No offense, but these look like "Independence Day" alien mother ships.

Замечательно, что пусковые С-300ПС теперь могут быть в походном положении и вполне хорошо передвигаются! А также сделан нормальный реалистичный старт ракет из них, как по звуку так и по визуалу

It's one of those things best done in a tool that does it all at once, namely the whole Substance 3D suite, as you can "paint" with PBR materials and then layer in the weathering, scratches, scuffs, stains, etc. There's been some comments around that something like that *could* happen, but it will be time intensive and not a quickly delivered thing. As I understand the F-14's cockpit (or really its whole model/texturing) was done differently than the upcoming F-4, where the F-14 took the photo scans and then cleaned them up by hand, the F-4 was all done by hand. With Substance you can dynamically create various levels of wear and tear as desired, without losing that base "depth" and feel of the painted metal panels. And yes, they had validated in the past that the existing cockpit was not just straight up scanned from a museum jet and dropped in, it was cleaned up significantly and adjusted to SME input of what a jet typically looked like on cruise.

Hey all, this is currently being investigated by the team, we hope to figure out the issue soon. Thanks!

It's in the changelog, a known issue. Known Issues - Hotfix planned Objects moving at speed may begin to jitter after some time in mission

Since the 2.9 update now external graphics have a shaking / shuddering effect going on. RTX 4070 with ver 537.13 first, then updated to latest 545.84 GRD. Getting the same result.

Thank you all. I have reported this internally.

It literally took you longer to type this and original post out than it would take you to upload the track file (which is honestly not needed in this case). Real nice attitude you have there