Leaderboard

Unfortunately the downloads will be suspended until 21:00 UTC. This is because of all my updated assets and your downloads. There is a limit of 1 TB downloads per 24 hours. This happens only when I do these large updates and it's not much I can do about it. Edit: I had it confirmed with the Dropbox support, there is no way to display the current download amount. And also, my uploads doesn't count towards the download limit. The temporary download suspension is 24 hours from when I reach the limit, so it's not per calendar day.

Folks I have moderate the thread, please treat each other with respect when posting. Leute, ich habe den Thread moderiert, bitte geht beim Posten respektvoll miteinander um. thank you

Good afternoon CH! I love your work, and thoroughly enjoy watching the videos you do with the GR guys. With the Persian Gulf Map being very Iran/UAE focused, have you considered working on some of the newer Iranian indigenous systems like the 3rd Khordad? Reportedly it is the system that shot down the RQ4 a few years ago and I wanted to run a sim where a counter strike actually took place. Again, Outstanding work Toast

We are working on it. We are preparing an update along with phase 3 (bug fix and map extention). Work in progress. Later we will make a report on the future update.

It isn't schizophrenia (paranoia at worst) and I'm not convinced that you're qualified to judge people's fears for their safety in a situation that you aren't experiencing.

I have spoken to the team and they are aware, we do plan to revisit atmosphere in DCS in the future. thank you

This work is not mine, I copy paste what the dude (Maya on discord) wrote on the discord bug channel so his work attracts attention from ED. "Hi, has anyone thought that the sunrises & sunsets in DCS are a bit too purple? I'm a graphics programmer who's familiar with Eric Bruneton's (which is used in DCS) and Sebastien Hillaire's atmosphere models and I found a "bug" in their implementation which causes the sky to be too purple and developed a tool called ARPC which allows accurately calculating the atmosphere parameters. Basically both Bruneton's and Hillaire's models pick 3 primary wavelengths for red, green and blue to determine Rayleigh scattering and Ozone absorption coefficients, but this method simply doesn't have enough precision to take especially the Ozone absorption spectrum into account. ARPC on the other hand uses CIE 1931 XYZ color matching functions to take a weighted average of the coefficients for all wavelengths when calculating the coefficients for red, green and blue. This approach gets much closer the spectrally rendered path-traced reference, which has more blue-tinted sunrises / sunsets. It also calculates a few other parameters such as the scale height and ozone distribution more accurately, by using ISA instead of the constant temperature atmosphere used in Bruneton's and Hillaire's models. If anyone's from ED is interested, I can provide more technical details regarding how ARPC works. It's already open source (MIT licensed, so can be integrated to any commercial project without any royalties) and available on GitHub: https://github.com/FarukEroglu2048/ARPC Here's a quick comparison with the ARPC coefficients, I changed the coefficients in the shader code for it: Default Coefficients: ARPC Coefficients: Here's another comparison using a ShaderToy implementation of Hillaire's atmosphere model: Hillaire's Original Coefficients: ARPC Coefficients: To validate my approach with ARPC, I used a root finding algorithm which tried to find the scattering and absorption coefficients which minimized the error between the spectrally rendered reference and also converted a reference spectral light source and the transmitted light spectrum after it passes through the atmosphere into sRGB to solve for the coefficients. In both cases, the expected coefficients almost perfectly matched the coefficients calculated by my approach: Under the spectrum calculations section, the first line is Rayleigh scattering coefficients and the next line is Ozone absorption coefficients for red, green and blue, calculated using ARPC. And below them, the array shown by “x” contains the Rayleigh scattering and Ozone absorption coefficients that match the spectrally rendered reference the best, found by the root finding algorithm. You can see that they are in great agreement with the ARPC coefficients. Even without more rigorous tests like that, the results with the ARPC coefficients are visually very close to the spectrally rendered path-traced reference."

Just one for the next time the forum dev's decide to tinker with the forum a little more, but as someone who glances through the 'Latest activity', it would be nice to have the ability to choose to ignore individual topics/threads so they don't keep reshowing if that's not too difficult to add please.

Currently, the pilot's body's hands stay glued to the throttle and joystick. I understand it would take some effort regarding more dynamic animation (i.e. inverse kinematics etc), but it would be great if, when tracked hands are detected/enabled, that the pilots arms/wrists are connected to the tracked gloves.

COMING SOON In this DCS: AH-64D video, we’ll discuss how to datalink with other AH-64Ds in a mission. This is done over the AH-64D radios and will allow you to send TSD points, tactical reports, or text messages. This is a very powerful tool to coordinate actions. Let’s first start in the Mission Editor where we can pre-configure our datalink networks. From the Helicopter Group window, the top portion remains unchanged. The bottom portion has new information from the Additional Aircraft Properties and Datalinks tabs. Along the bottom portion of the Aircraft Additional Properties tab are two new entries for DATALINK. The first is the Datalink Originator ID that distinguishes data sent between networked members. Each AH-64D in mission should have a unique Originator ID. Below that is the Ownship Callsign, and like the Originator ID, this should be unique. We’ll see these later when setting up the network. Before we discuss the Datalink tab, let’s first look at the Radio Settings tab. This lists each radio in the AH-64D and the preset channel assignments for each. As you can see, each radio can have up to 10 presets. On the Datalinks tab we have two sub-tabs: Settings and Network. On the Settings sub-tab, we have 10 Presets, and each can have a unique Unit ID and Callsign. We’ll see these later in the cockpit. The primary frequency assigned to each Preset is defined in the drop down for each. Along the right side are check boxes to determine if the Preset takes part in the datalink network. The Network sub-tab allows us to view, add, or remove AH-64Ds that will participate in a Preset’s datalink network. As you can see, I currently only have myself, Chaos 11, and my wingman, Chaos 12 assigned to Preset 1, which is for “Gunslinger” battalion. I can assign Presets 1 to 10 from the top row. If I wish to add other AH-64Ds to Preset 1, I can select Preset 1 and add them as a Group or as individual Units. Note that this datalink is different from the ones used in aircraft like the F-16 and F/A-18, and they cannot exchange data. We’ll first discuss setting up and editing the datalink through the COM page. From the left MPD, I’ll select COM and we can see the Presets 1 to 10 listed along the right and left sides of the page with our ownship information in the center that includes the callsign CS11, for Chaos 11 and the datalink originator ID of 1 as we created in the Mission Editor. If I select ORIG ID, you can see that it displays the same information at the top left and top right. If wanted to edit this, I could select either one of these options and enter new designations for my own aircraft with the keyboard unit. Back on the main COM page, if I select the first Preset, it then displays additional information regarding the Preset in the center, in this case the radio frequencies used by “Gunslinger” battalion. If wanted to edit this though, I could select PRESET EDIT and select UNIT ID and CALLSIGN and enter new designations with the keyboard unit. I could also select V/UHF, FM, or HF along the top row to edit the frequency data that the Preset will use when tuned to the corresponding radios. Selecting NET from the bottom row, I can display the aircraft assigned to this Preset’s datalink network. As you can see, this matches what we set up in the Mission Editor, Chaos, and Bootleg flights. To add Saber flight, I simply select Member Directory, and select SR11 and press ADD and the same with SR12. We can now see that all six aircraft are assigned to Preset 1, Gunslinger’s datalink network. At the top you’ll notice other options. If you select a network member and select Delete, it will remove that aircraft from the selected Preset. Selecting a network member and setting them as a Team member will allow you to send messages from that member through the COM page. If you set them as a Primary member, or PRI, you can send reports over the TSD and FCR page. Note that they are not mutually exclusive. As mentioned, the Originator ID must be unique for each AH-64D. If you need to, you can edit you own by selecting Originator ID from the bottom of the main COM page as already demonstrated, or by selecting C/S, Callsign, or SUB at the top of the NET and entering a new designation for the network member that you have boxed in the network list. NOTE 1. Due to complications stemming from our other businesses, we had to adjust datalink terms. In this case, Secure Modem Datalink (SMDL). This is all I will say on the matter. NOTE 2. As always, these videos provide a preview of an upcoming feature to assist you in understanding a new feature. Later, it is quite possible that the feature will change, and the feature functionality has changed. As much as I’d like to, I lack the time re-record these videos. NOTE 3. The next AH-64D datalink video will instruct how to transmit and receive datalink text messages, tactical reports, and points.

Here's my 2cents based on experience with MSFS and Reverb G2: DLSS is the BEST visual quality in that sim in VR, period. The trick is that in VR you'll need quite a bit of supersampling for not only anti-aliasing but for correctly counter-distort the lenses. That's why the G2's 100% resolution set to around 3100x3100 pixels per eye in Steam, despite the headset having "only" 2160x2160 pixels per eye resolution. The best we can do is set the headset to 3500x3500 or even 4000x4000 resolution per eye (sounds silly, eh?), and turn on DLSS to have the game's rendering lower (like the native 2160x2160) and let DLSS do the proper upscaling. The result will be not only a MUCH sharper image, but a much larger hotspot (even edge to edge clarity). It's incredible. I have very high hopes in DLSS an DLAA in DCS with VR, I'm super excited!

you can bind your steam account to your dcs account at any time to use stand alone, there is no delay when linking the same steam account. you just can not use them together, and as you mentioned you never did before so no real change for you.

Awww, that's nice! Haha! Yes, a huge shout out and thanks to @Dangerzone I learned something even if I've been using 2FA for years for work. This forum is awesome! Sent from my MAR-LX1A using Tapatalk

@MAXsenna I followed Dangerzone's plan and got the 2FA through my PC. No phone involved. Burned a few brain cells trying to understand it, but it worked. So thanks to Dangerzone for the info, and to you for being such a bother and pointing me in the right direction.

Because you do very high quality work and there are a lot of downloads. Thanks a lot

У меня домашний "кокпит" вообще состоит из двух джойстиков, один из которых Логитек-3д про (уточнил, что бы было понимание всех "радостей" при моей работе с А-10с) и по началу я тоже не понимал зачем все эти долгие и короткие нажатия. Спустя полтора года я наконец то перестал бороться с системой HOTAS, приняв её за базу при работе с А-10с. Есть мысли, что всё из-за тонкостей работы с установленным оборудованием. (я про реальный самолёт). В игре же отлично передана историческая аутентичность в этом вопросе. И по моему так и должно быть во всех модулях, аутентичность и историческая достоверность. Поэтому желание сократить время на нажатие, это уже действительно из области аркадных хотелок. Не стоит упрощать то, что выполнено великолепно. Порой некоторые вещи стоит смаковать. А описанная ситуация с налётом на БУК мягко говоря не типична для подобного самолёта. Поправьте меня если я не прав, но насколько я помню, А-10С не выполняет SEAD миссии. Но если же его упорно стараться применять не по назначению, то наверное и станут возникать подобные желания по изменению HOTAS, а со временем захочется добавить ему скорости полёта и т.д. Так можно дойти и до сказочных эльфийских подвесов, по типу HARM. (эльфийских из-за того, что на данном самолёте подобное не применялось) Всем добра и понимания!

I spent a number of hours digging around ACL and this is what I've found. The 6 twisting-handle panel This one seems to have been introduced by the D-27 and per its own individual drawing (*which I have a feeling are being wrong, so I'm relying on the overall installation drawings more than the individual parts ones, where they overlap. I suspect this because sometimes the 47 versions listed on parts don't match up with the installation's specified utilized parts per version)* says it runs up to as far as the P47N-1. However a look at this pretty broad installation drawing (1) instead suggests it was last used on the P-47D-35 The 3 twisting-handle panel Source #6 Introduced per itself with the P-47N and up. However it's listed on the installation drawing(1) in its -4 iteration form since the P-47D-36 and up (or just -40 probably?). The -4 form of this panel doensn't include the extra nub for the 4th handle above the BELLY inscription. I haven't found what it was for, but it doesn't appear to be the panel we have in our DCS -40 so it shouldn't matter anyways. The horizontal arming panel Included with our DCS 47D-40, this one is listed to have started with the -36, and continues well into the P-47N. Source #5 The vertical arming panel Included with our DCS P47D-30 (regular), on the far side of the stick. The drawings (mini installation (source #2) and parts(source #3)) list this as having been introduced with the P-47D-30 and more or less up from there. I can't get a solid pin on in with an overall installation drawing because somehow it was missed or excluded from the parts list on the bottom right corner of each drawing. It's drawn on the installation page (1), but not listed. So I cannot get a better sourced reference on when this panel was introduced to the P-47. So, left with just the parts' listing, it says it was added on the P-47D-30. The red bomb release handle PANEL The panel for this is not included on the DCS D-30 early, but on the D-30 regular. This particular part(4) says it was introduced along with the D-28....and up. So, i don't have a good pin on this one either. However, this part has a similar case as the vertical arming panel...it's not listed on the overall installation drawing (1). So an installation reference seems to have escaped me. I'm still a bit muddy on it tbh, it wasn't quite as clear cut to read as the P-51's drawings are...or it seems that Republic didn't follow its own directions nearly as strictly as North American did. From what I can tell, our P-47D-30 (regular/late) should have the 6-handled arming panel. It sounds a bit absurd, because now additionally there would be three ways to drop bombs; via 6-handled panel, via red pull handles in front of the pilot, and electronically with the weapon release trigger. However, this appears to be how the stars are aligning for a P-47D-30 cockpit. P-47D-40 appears to be pretty solidly accurate for what I've found. P-47D-30Early is closer to a P-47D-27 in its arming and drop system layout. However, turning our P47D-30Early into a P47D-27 includes a potential stumbling block that ED might not be so keen on remaking if they wanted....a new propeller. The P47D-27 used the Hamilton Standard propeller, as opposed to our current 47s' improved Curtiss propeller. This would require an FM edit which I'm not sure how ED would feel about doing. Some other changes I noticed (didn't complete my D-27 investigation) were included but not limited to: different dashboard gauge layout, different fittings for wing drop tanks, no belly tank/bomb sway bolts(?), and extremely likely more that I haven't yet found. So, without the creation of a D-27, it looks more like the D-30Early should be removed and the D-30 (regular) get the 6-handled bomb arm/release system. For more info as well, here's the installation for the P-47D-27: https://app.aircorpslibrary.com/drawing/viewer/93f78227/p-47/p47-dwg-l?p=2 (1) https://app.aircorpslibrary.com/drawing/viewer/93f78300/p-47/p47-dwg-e?p=5 (2) https://app.aircorpslibrary.com/drawing/viewer/93f82214/p-47/p47-dwg-l (3) https://app.aircorpslibrary.com/drawing/viewer/93f82215/p-47/p47-dwg-l (4) https://app.aircorpslibrary.com/drawing/viewer/93f78301/p-47/p47-dwg-l (5) https://app.aircorpslibrary.com/drawing/viewer/93f82340/p-47/p47-dwg-e?p=2 (6) https://app.aircorpslibrary.com/drawing/viewer/96f78223/p-47/p47-dwg-e

Yes. And for those forum users out there (you know who you are) that have a penchant for posting documents that you should not, before any forum rules are violated regarding what can be posted here, AH-64D's talking to E-8's is open source information. However, how it is actually performed and what happens in each aircraft is not open source information.

Gotta be real, this feels like a really trashy way to treat your customers, by the ED leadership. First, we dont even get told about this change at first and had to learn it the hard way. Thats unacceptable from the get go and shows a blatant disregard for customers and community. And secondly, this is ED arbitrarily changing how we can access the game. This is some kind of "pray I dont alter the deal further" moment. We have no choice, we werent asked, not told. Just ED changing such a fundamental thing, a principle of access the game was sold on, and we have to suck it up. This is only made worse becasue we already put up with so much. We pay silly amounts of money for modules, we accept a deeply buggy game, and we crowdfund eternal early access modules with often questionable road maps. If anything, ED should give back more to the community, rather than treat us like this and take away features. I planned to purchase more modules, eg the F-4E instantly at release, but Im gonna put those on hold. Not just because Im treated badly, but because this makes clear that I cannot trust ED to not make changes against my interest. If they did a decision like this as if its nothing, what else will they do in the future?

This is my F-15E UFC — now available on GitHub! https://github.com/MilKris666 Video: Razbam at Tokyo Game Show 2024 — using my UFC!

If you played Steam recently and got a 403 error, Please go to your DCS profile page. If your Steam account state shows binded, it doesn't matter if you transferred or not; you have to click unbind, and then you can use Steam again. or Just use standalone client. In recent days, some users keep getting 403 steam authorization error. I thought it's a steam issue. A lot of people don't know what's wrong with their games. until someone mentioned there's changes in the ED profile page , now it displays: It seems only people who have bind their steam accounts before will get the error, and the problem remains until users unbind their steam accounts. But ED didn't make any announcement, and your FAQ and pined post still remain the same. It is mind boggling and disregard for the customers.

Glad to hear I could be of help and you've got a suitable solution. Enjoy your trials! (Which reminds me, it's about time I teased myself with something else).

The video is titled "Datalink Setup", and Wags says in the video that it is "how you set up the datalink", and then mentioned what will be in the following video.

Hand tracking, preferably with finger tracking, synchronized in MP will be necessary for efficient communication between crew when we get aircraft with side by side setup like A6

Yes! The eventual ability to give hand signals to wingmen would be amazing!

All Army aviators receive training in how to call artillery. I can't speak for how often the Lift or Assault communities practiced it, but Attack and Scout crews practiced it quite often. It's just as important as working with infantry, JTACs, fixed-wing CAS, etc.

Hi @currenthill, First of all I wanna say thanks for all the great assets you've made. Do you have any plans on making variants of the US logistic vehicles like HEMTT (other than the ones already created), FMTV, or Oshkosh M1070? or other nation's logistic vehicles too RMMV HX perhaps since Sweden is one of the operators

exaggerating a bit too much? ... I'm an honest user and I don't feel affected by this in the least, as I never use both DCS instances at the same time.

@dburne SteelSeries Nova 7 is awesome especially with the Varjo Aero. Lot of early discussions about the Nova 7 on that very long thread; Aero Beginners, you and I follow. Fits comfortable and very convenient mic that retracts into the headphones. I hard wire directly into the output jack in the Aero but there is the wireless/bluetooth options as well. I am extremely happy with it.

Beyer 990 pros

ИМХО звук так себе, переключение азсов вообще дичь какая-то. Какой-то скрежет в кабине. По поводу самой кабины, мультяшная, как нарисованная карандашами. И я, конечно, не знаток мигов, НО немного понимаю в оборотах. Такое движение стрелок немного странное. Если ТК двигателя, возможно, и способен так резко набрать обороты на 10%, что тоже странно, то потерять их так же резко он вряд ли сможет. Короче, MSFS и DCS несопоставимы. Позывной бомба: MILITARY MIG)))

ты не понимаешь, у Юры свое виденье А-10С не важно что это так на самом деле, ему медленно надо переделать, под его хотелку он резкий, как понос и по его мнению, там должно быть 0.3 а то и 0.2, иначе ММЕЕЕЕЕДДЛЕНННООООО !!!

Hi @FalcoGer This was reported internally for analysis. Thanks.

$bomber, instead of A or B (keys on controller) you can use Enter from keyboard for A and Esc from keyboard for B. The program gives clear instructions for the procedure but fails to explain this properly. No controllers needed.

Чтобы подтвердить или исключить проблемы с железом - можно загрузиться с какой ни будь загрузочной флешки (желательно с другой осью) и проверить там.

Some great research in this thread, well done. I think it pretty reasonable to sell Briggs body parts for a razorback too. Though it shouldn’t cost an arm and a leg. Very decent, taking one for the team.

I took the link down due to my limited google drive space. And since ED seemed to not be keen on the relevant liveries, I scrubbed it. However a handful of the liveries live on in the 4YA Project Overlord liveries pack. This is a mod that replaces some aircraft's default liveries with more historical ones for the 1944 Normandy invasion period. While ordinarily available through the 4YA PO discord here (https://discord.gg/rg8ytU2v), the link to the mod is here (https://drive.google.com/drive/folders/1_ckTm8VXPqJV2u5uuiNVMeARPvL8_0oU?usp=share_link) Remember though, this livery replaces the default liveries. This means that the names of such liveries will be identical as default in order to fit the 4YA PO server, but the paint itself will be different. I encourage taking a look into the readme provided in the drive link as well @Rudel_chw @Nealius @Slippa

Yes. Just unbind the licences from the standalone DCS. You're not forced to use standalone. You just have to choose between the two now. Your settings, missions, profiles, etc. are still in the \saved games\dcs - always good to make a backup.

My source is real world experience and hands-on use of what is actually possible, not a Google search of the internet. A lot of things change in the real world equipment from what is announced and what actually becomes reality. The A-10's SADL was supposed to be broadly fielded between the US Air Force and the US Army to enable direct communication with ground forces. It doesn't, because the Army decided not to field SADL after the fact. The Fire Support protocol was supposed to facilitate artillery fire missions via datalink, but it was depreciated and wasn't even functional, even though the option exists in the cockpit. Reality does not always conform to what can be searched for on the internet.

null

Hi all, Sorry for the late reply. If you want to use stand alone DCS version you can bind your Steam account to your DCS account and use stand alone, but you will no longer be able to use the steam version while the steam account is bound to stand alone. If you unbind your steam account your stand alone version will no longer fetch your steam modules, but you will be able to use steam version again. thank you we will get it added to the FAQ

Еще раз, задержка в 0.5 сек для долгого нажатия не старый косяк, а особенность реальной авионики. К этому пришли ее разработчики там, это скопировали разработчики тут и честно сказать Ваши претензии, Юрий, уникальны. Раньше подобных жалоб я не припомню от других пользователей. Все вышесказанное в совокупности дает основания считать предмет обсуждения не реальным косяком, а субъективными капризами. А капризы - бывают, штош поделаешь. Провоцировать пламенные обсуждения лучше в темах дискорда, предназначенных для флуда)

Проблемы можно разделить на две категории: несоответствие реальности и личные хотелки. За первое можно и нужно бороться, за второе - нет. С говномётчиками тоже можно и нужно бороться, согласно правил общения тут, главное, самому не понаписать чего. А так-то, если неудобен реальный аппарат чем-то, то только и остается, что приспосабливаться, тренироваться. Как и приспосабливаться к своему комнатному кокпиту, который редко бывает удобнее реального. Никто не будет снижать копийность каноничного DCS модуля.

Read that as you will but when pilots and aircrew with 2000+ hours in the real thing says we're good we're going to listen to them. And thank you for you praise for the module! And also, like I said, afaik an official cockpit with less wear will happen.

The current cockpit is intended to be representative of how the actual cockpits of the represented aircraft looked. This has also been verified by basically all of our SMEs.

Seems to work for ai! But player sinks into the ground a bit. A collision up-date is needed. Runway needs love. No trees added

And the new: