Leaderboard

Dear all, A little update on DCS: AH-64D development. We understand that some of you are concerned about the lack of new features. No resources have been taken off the AH-64D, and work continues ahead steadily. Much of this work has focused on bug fixes and tunning. Before we add too many new features, it is very important that we first have a solid foundation to build upon. Additionally, a big push on bug fixes and tuning has been required to avoid player confusion and frustration. Some of the larger bug fixes and tuning that have been underway include: Tuning how George calculates target range. Corrected TEDAC video errors. Adjusted HUD only views. Tuning damage model like flying sans-tail. Adjusted gun fire shake. Fix multi-crew ASE sync. Removed HDU glare. Fix some engine start issues. Tuning LMC. Further improvements to the PERF page. Better IR texture maps. Lesson, input, and tool tip improvements. Fixes to the CMWS flare system. Tuning of SAS collective channel issues and altitude/attitude holds. Fix SAS tones and hold behaviors. Tuning yaw offset. Fix PNVS stutter. More accurate weight calculations. Trim tuning. Multi-crew hold modes sync. Fix hold modes disengagement logic. SAS fixes. Better SAS Collective altitude hold. More realistic slip ball behavior. APU not requiring fuel fix. Fixed various warnings and advisories. Fixed standby indicators. Tuning TADS and NVS relationship. This is to name a few. A great deal of work on this front is ongoing. Although bug fixing and tuning has been our priority, we have certainly been working on new features that are not gated by existing bugs. Some of these include: Option to remove the auxiliary fuel tank for more cannon rounds. Adding the AGM-114L radar-guided Hellfire. Adding the Improved Datalink Modem (IDM) and LB Net. Adding the Fire Control Radar (FCR). Adding the Laser Spot Tracker (LST). Adding animated engine nacelle cooling doors. Wipers removing rain drops. Many of these items are rather complex and take time. Please be patient. Kind regards, Wags

Hi all. We finished the second phase and are already testing it. We fixed a lot of remarks from ED and made a little more than we wanted. I will make a report a little later about what we have in second phase (airfields, unique objects, SAM places (120 +), helipads (400+)), etc ... Several screenshots:

As someone who has spent their life writing software and managing and leading software development teams, I always find this thread amusing. While schedule is important the old adage "people will remember it was wrong long after they forget it was late", still applies. We'll get it when it's ready:)

Jedes mal, wenn man sieht, das hier neue Beitrage kamen, habe ich die Hoffnung, das endlich wieder jemand was verkauft und ich mein wohl verdientes Schnäppchen machen kann. Das ich jedes mal enttäuscht werde, nervt langsam....

Не шумите, мы не можем физически отвечать всем сразу. Касаемо мода Суфы - самолёт интересный (впрочем, как и любой самолёт), но выдавать SDK каждому создателю мода мы, разумеется, не можем. Для этого существуют определённые процедуры (официальное обращение к руководству, предоставление информации о себе, показ своих наработок и доказывание перспективности сотрудничества, согласование типа ЛА для моделирования). С другой стороны, мы намеренно сделали DCS открытой платформой с возможностью несложных модификаций как скриптами, так и новыми ЛА. Любой достаточно грамотный пользователь может попробовать свои силы, но если речь идёт о включении ЛА на полноценной основе - это совсем другой уровень ответственности и другой разговор. По мультитредингу - все аналогии идут мимо, их легко можно вывернуть наизнанку и запутаться в схоластике. Обещали - сделаем, будет вам мультитрединг - сами всё увидите и оцените. Работа программистов по МТ исключительно сложна.

AviaStorm Tornado little update. https://discord.com/channels/1020277498363269120/1020303137145368627/1080914474283835412

Kürzliche Diskussion der Preise hierhin verschoben: Diskussionen sollten hier nicht stattfinden! Angebot reinstellen, alles andere per persönl. Nachricht an den Verkäufer.

Leute, ihr seid gerade dabei einen Thread, der bisher tadellos funktioniert hat, kaputt zu machen. Ich hab' hier schon ganz stressfrei gekauft und auch verkauft und würde das gerne weiter tun. Macht doch bitte einen separaten Thread auf, wenn ihr über Etikette und/oder Verkaufsethik diskutieren wollt? Ja? Bitte, bitte? Gibt es einen deutsch-sprachigen Moderator, der hier mal aufräumen kann?

Purchased a 7950X3D that will be arriving sometime next week, and will do the transplant/build next weekend. I plan on posting few benchmarks for you guys to see the performance gains compared to 5800X, as well as look at how multithreading improves things when it gets released.

Nachdem Eagle-Eye den Thread ausgelagert hat, kommentiere ich dann doch mal, was mir auf der Seele brennt. Es wurde eigentlich schon erwähnt, ist auch eigentlich selbstverständlich, aber scheint heutzutage nicht mehr üblich zu sein: ein Verkauf findet statt, indem ein Verkäufer seine Ware anbietet und ein Käufer diese kauft. Dazu kann(!) der Verkäufer seine Preisvorstellung angeben und der Käufer hat die Möglichkeit der Preisverhandlung (im Volksmund "Feilschen" genannt). Weder haben Preisvorstellungen anderer Anbieter direkt etwas mit dem Angebot zu tun, noch muss der Verkäufer den Käufer akzeptieren, oder umgekehrt. Selbst das Argument "ist den Preis nicht Wert" ist vollkommen sinnbefreit, da auch der UVP nicht den "Wert" (Material, Produktions und Transport/Lagerkosten) widerspiegelt, sondern den erwarteten Gewinn des Herstellers. Wert ist am Ende, was ein Käufer bereit ist dafür zu bezahlen. Einzig der Verkäufer muss das entscheiden.

My vote is for the C-141 Starlifter which earned the nickname 'Hanoi Taxi' for sending troops to Vietnam and bringing them back once their service was done. It had a much longer service life compared to the likes of the C-17 and C-5, I am pretty sure they were run way past their life expectancy, basically until they were about to fall apart before we developed new planes in-category. The A model was used during Vietnam and the longer B model was used after. Pretty much paved the way historically for the US modern transports and is rather unsung.

Ich lese in der deutschen Community schon erheblich länger mit als ich schreibe (so ca. 4 Jahre). Und tendentiell reagieren hier erheblich mehr Nutzer angepisst auf Beiträge anderer oder werden gleich persönlich als in den kompletten englischsprachigen DCS-Foren. Und Deine Reaktion war das Paradebeispiel. Tut mir leid, Kittie. Du hast recht. Es wäre gut, wenn ein Moderator die komplette Off-Topic-Diskussion inkl. der Preisdiskussion löschen würde.

Excelent work, tx a lot !!! One thing, the naming of your mods - would be great to have thomething like "[sam] " or "[cHill] " at the beginning of ALL Displaynames - to identify your mods and packages - and perhaps also file names?

Finished DK296 https://www.digitalcombatsimulator.com/en/files/3319689/

At the end of the day if ED implements what Tim is pointing out, IT IS going to be "for more enjoy". Flying the Huey will be the same, you will just have more power to spare, you will be able to fly faster, higher and with heavier loads... Nothing else should change.

So, Total Controls is going to produce a Apache Keyboard Unit. We would lovey your thoughts and inputs on this hardware. Release date and price is not set yet. We might do a Kickstarter on it.

When your opinion is proven to be false, and you proudly state that you will hang on to it regardless - that is a core issue that speaks to something that has nothing at all to do with the game. No development team, bug with a game, or fix that could come out is going to address the underlying unrest inherent in that statement, nor is it the responsibility of any person other than that individual, to address that kind of deeper emotional/maturity dissonance.

Please add a sun visor toggle to your modules.

Just got back from a business trip late last night and had the new 7950X3D waiting on me. Hope to do the build today. Going to pair with a Crosshair Hero X670E, 64GB of Trident Z DDR5 CL30 6000 EXPO kit, and a RTX4090FE...

Hi Developers, The newly added compass rose is a great addon on the F10 MAP. However, the CR is ONLY visible and movable AFTER loading the mission. So in short; we can only use it when the mission is loaded, and place the CR into the correct location (for example on top of the bulls eye) it would be great if it would be visible and usable too in the mission editor and put it in place BEFORE flying the mission. When receiving the 'Bulls' information from the AWACS, the CP needs to be placed on top of the Bullseye to get the correct heading. Kind regards, RWC.

For YOUR situation it doesn't work. There are likely a relatively small number of users that are running multiple monitors and your original reply suggested it just doesn't work at all. On single monitor with TIR it's no problem to look out your side window with it. Next time it would be useful if you qualified your reply with the fact that using multiple monitors and your experience may not apply.

They are kept private to save them from harassment from people like you.

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

Yes, that's what I imagined ... so, to me this fact confirms that all these assets are actually assets provided by the 3rd party Module, irrespective if they decided to allow free use by everyone or not.

A C-141C SOLL II bird would fit in nicely ... let the green lizard legacy live forever in DCS World!

We now have a magnetic and true heading readout on the taskbar. Could we have a MSL/AGL altitude readout as well?

I just died in the c101 online...love the light jets...I just want some flares

Отвечу коротко. E-ядра в логике распределения рабочей нагрузки и работы МТ принимаются во внимание.

We've added a tighter model of the illuminating radar systems lobewidths so you'll get much less spurious warnings from systems that are not actually targeting yourself. But as for systems that are actually targeting you it shouldn't be that much of a difference.

Yes, "Two weeks". Sorry.

Looking at the screenshots again we need buffalo, camels, donkeys, sheep, and goats DCS Beef (cows) won't cut it

Great skin, I loved it, wish you good luck with the contest:

Eben doch, die Nitro+ 7900XT ist neu für 999€ zu haben. Demnach würdest Du für die 7900XT gebraucht auch keine oder maximal 900€ bekommen. Jetzt erklär was die 6900XT Nitro+ soviel wertvoller (in Bezug auf Nutzen von Leistung/Qualität) gegenüber der Nitro+ 7900XT macht? Naja wenn wer Interesse hat und mir 800€ für meine Referenz 6900XT bietet werde ich die auch abgeben, zu normalen Handelspreisen behalte ich die dann doch

Nur weil bei Restbeständen Mondpreise aufgerufen werden, ist der aufgerufene Preis für die gebrauchte, gerechtfertig ? Oder weil auf Ebay manche "Ihr Glück versuchen" ? Unten mal ein interessanter Chart über die Karte....bis 09.02 lag die Karte NEU bei 800-900 Euro ! Und jetzt komm mir bitte nicht mit den Scalper Tagen um die Ecke. Zudem kommt noch, schaut man sich die Preise zu bestimmen Sales von 7900XT/XTX sowie der 4080 an, ist eine gebrauchte 6900 auch mit XTXH Chip für 900,00 Euro ein Mondpreis ! Du bekommst für 900 Euro ne Suprim X als 3090. ach egal... Kauft mal....

Just happened across this little gem today. Seems relevant. Do check it out. (And I do hope that this gets fixed too). https://forum.dcs.world/topic/170264-article-when-abuse-becomes-the-cost-of-doing-business/#comment-170279

Honestly, as nice as it would have been to get the domestic kit, this odd off shoot is appealing to me more and more. It's going to be very interesting to use, I think.

I just want to point out that this entire thread is a perfect example of why I love older jets in DCS. People at throwing up EM graghs. Finding small errors at certain flight regimes. It's awesome to be able to actually compare the modules data to the real things data. Unlike some other modules. That and the jets are just interesting. The Cold War is heating up in DCS, and the Tomcat already has a huge head start. I can wait to see the improvements that are coming to the old bird.

this is not about adding, this is a bug the a10 of yore used to have these working 11 years ago but hey haven't been fixed check the radar altimeter after the bomb when he banks

I very much like the A10, was my 2nd purchase after the Blackshark2. I still go back to it every couple months even after “flying” it for over a decade.

That's how it's supposed to sound

It uncouples the stick from the autopilot / pre-servo control and switches to the back up direct control. used in case of partial hydraulics failure or autopilot system failure I believe. Source is F1ED flight manual

Hi. I really thank @Rudel_chwfor the outstanding contributions he has been doing to the A-29B mod. Just a quick update: I'm currently working on a EFM version of the mod and plan to release it this month. The mod is compatible with 2.8 openbeta and can be obtained like it is explained above, using "Download Latest Release" on the readme. Sorry if the development speed is not up to some of you guys, but feel free to offer help and contribute like many have done. We don't need to create a different branch of this mod. After the EFM we will do the backseat 3d model and enable it. New features coming are Datalink, VOR, ADB, GPS/INS weapons, new FLIR with lasing capability, new autopilot and more. For other features, please post on github the wishlist because it is easier for me to keep track. Also a completely new cockpit and external 3d model is on the way. Sorry for not answering here before, but i changed my email address and forgot to update it here, so i wasn't getting any notifications.

@FalcoGer, here is what you don't seem to understand. BigNewy, NineLine, or other ED staff are not coming down on you for posting bugs. They are coming down on you for your incessant attitude and disrespect towards others in your conduct within the bug report threads. You post quite a few bug reports that are regarding "fringe" behaviors or conditions. Yes, if bug reports are valid, they will be addressed in due time (and those are appreciated). However, it is a higher priority to ensure the "mainstream" behavior or condtions of the module are working first. This is what BigNewy was referring to when he said you were intentionally exceeding laser limits. Development is prioritized to those behaviors that are within the usable range of the laser. You demand that your bug reports be handled within a schedule that fits within what you think is acceptable, regardless of the larger picture; and when it is not, you resort to your usual attitude as a way of lashing out for some reason. Your disrespectful and immature attitude towards the ED community managers is quite tiresome, and this is why you have been given multiple warnings and some of your posts removed. Your other posts had nothing to do with reporting bugs, they were disrespectful rants.

What is it with people and moving to subscription model?

Yes, and 80-90% of added things are just "fixed" something broken.

We do not need a perfect solution; there are a few "Good enough" things that can be done quickly and easily which will benefit thousands of players. DICE for countermeasures DICE provides countermeasure programming and has been downloaded over 5,000 times. It is providing a valuable service to players. ED obviously have the ability to whitelist these particular files and exclude them from IC but they do not wish to do so. So lets look at another easy alternative. Instead of having the values inside the .lua files themselves lets put them somewhere else and then read from that somewhere else in the lua files. For extra security and anti-cheat lets make that somewhere else a data file instead of a source-code file. In the C:\Users\$user\Saved Games\DCS.openbeta path ED can create a folder called "Countermeasures" and then inside can add a JSON file called "F-18.json" (These locations and filrenames are obviously just examples) with the following format which is just a JSON representation of the existing lua table: { "MAN_1" : { "chaff": 1, "flare": 1, "intv": 1.0, "cycle": 10 }, "MAN_2" : { "chaff": 1, "flare": 1, "intv": 0.5, "cycle": 10 } } ED then modifies the lua file to instead read the program values from the JSON file and then DICE, or other programs. or just people not afraid of JSON, can modify the JSON file values without breaking IC. There are obviously some other considerations to take into account such as JSON error handling, default values and the like etc. but a competent developer should be able to make and test this change in an afternoon per aircraft (since different aircraft will require different JSON structures). This is something that can be done now as an intermediate solution while we wait for a full-fledged DTC. Helios for instrument exports Helios literally has a list of patches that they apply to ED files to enable cockpit instrument exports that are currently missing. https://github.com/HeliosVirtualCockpit/Helios/tree/1.6.5600.0/Patching/Patches/DCS/002_008_00000_33006_00000/Viewports/Mods/aircraft ED can look at those, validate that they are safe, and then upstream them into DCS itself so that Helios no longer needs to do any patching. Most of them are literaly one-liners. ED can then invite the Helios devs to the Beta Test team so that they can validate changes work with Helios and contribute fixes before new versions go to open beta. Helios has also been downloaded thousands of times. With a minimal amount of work, ED has now catered to those users. These patches will also fix IC for people who just want to export displays by manually by providing the screens that they can reference in their moitor lua setups. VIACOM for voice commands Viacom has also been downloaded thousands of times. This one I am not sure can be fixed or not by upstreaming changes that VIACOM makes; I haven't looked into it in enough detail. However an alternative is to implement some APIs that allow access to the code that sits beneath the F10 radio menus to reduce the chances of breaking in the future. A request that has been outstanding for many many years. e.g. With these two simple, and one potentially less simple, changes. ED makes life easier for thousands (Close to 10,000 than 1,000 I reckon) of its customers which were impacted by EDs breaking changes.