Comrade Doge

Hello, great ideas. At the moment I am not too familiar with the helicopter's systems, and these advanced features would probably require a new user interface to be designed... I'll keep this in mind for the future.

Hello! As some of you know, I've built a software capable of automatically entering waypoints into the aircraft by choosing them visually from the F10 map. This post is meant to announce the support for the AH-64. If this sounds cool, you can check out the forum post here: https://forum.dcs.world/topic/272110-transfer-steerpoints-from-the-f10-map-into-the-aircraft-dcs-the-way/ Happy flying!

Thanks to the wonderful contribution of @jonsky7, the AH-64 Apache is now supported! I have tested it with both Pilot and CP/G seats, and everything appears to be in order, but as always, waiting for everyone's feedback as well! (as a note, the copilot seat appears to take a bit longer to enter the waypoints as opposed to the pilot seat). For multiplayer I'd advise letting the Pilot enter the waypoints, due to potential issues with multircrew synchronization at the moment... If you are upgrading from an older version, simply extract the new 'The Way' folder contained in the .zip file into your existing folder, overriding any files, and replace your old 'TheWay.lua' file in your Saved Games with the new one. Download from here: https://github.com/aronCiucu/DCSTheWay/releases/tag/v1.5.0

Correct me if I am wrong, but doesn't the Viggen already have the capability to add steerpoints from the F10 map? Same for the JF-17 and the F-14, hence why I didn't add them in...

Update: I got the Apache, TheWay for it coming soon!

Hello, I hope to get my hands on the Longbow soon-ish, and try it out as well, thanks for the involvement!

You use it as normally, as with any other plane. It will transfer them fast to the A10 so it might appear as nothing happened, but if you check the waypoints are there.

No it does not currently. Might consider it at a later date

We have base game liveries for multiple other countries as well... Would be a shame not to have it for ROAF.

3rd parties may have made them, but are they in the base game?

Hello everyone, found an interesting behaviour in the F-16, namely when using the ACM RADAR modes, in that they become stuck at a 5 mile range, from the usual 10 mile range they should scan and lock targets at. Since this is a relatively small bug, I will not go into many details apart from offering the procedure to replicate the bug: Acquire an ACM lock in DGFT submode, with the scan mode of your choice (BORE, 20, 60, SLEW) Wait for the target to close and the FCR screen to autoscale to a 5 mile range (shown on the MFD) Drop the lock by TMS Down Enter the same ACM mode you previously used to lock, and you would notice it's scan range is now 5 miles instead of 10. Note: The 5 mile range bug, when triggered, persists only in the ACM submode that it was triggered in initially (BORE, 20, 60, SLEW). For example, if you trigger the bug in BORE acquisition mode, and the range becomes stuck at 5 miles, the rest of the modes still scan at the regular 10 miles, until the bug is triggered using each one of them as well. Below I attach the trackfile where you can see me triggering the bug in the BORE, 20 and 60 submodes, one by one. Have a great week everyone! F16ACMbug.trk

Hello, check if you installed the .lua files in the right place, and also show me the Export.lua file to see if it had been edited correctly

Alright, message me directly via private message and we'll try to fix it there

Hello, can you check if the server you are playing on has exports turned on? Try using the program offline and see if it works

That would be the plan indeed. I am looking at Electron + Vue.js for a rebuild, will be quite the task but when I find the free time I will look forward to finalizing it (I still need to learn some extra JS knowledge to make it work). I enjoy working on it when I can, and the project has taught me a good number of things so far.

I used the DCS-BIOS repo as a reference for all the device and command codes corresponding to all the switches. About the UI, I recently posted a demo about how the new interface would look like, and that I would like to rebuild it someday in another language...

These are all great features to implement, and people have indeed requested them a great deal. However at the moment it appears that my free time to develop them has become scarce (exams, study, things of that nature)... hopefully the situation will improve and I might find more occasions to work on those features in the future...

Hello, yes it has! Check out the latest release.

Splendid summary! I am most pleased to find that this thread has become packed with useful information like the above.

Hello, that is a splendid suggestion, and would definitely make the life easier for FC3 pilots. It would require quite the bit of work to implement, and I'm not sure my expertise is sufficient to materialize it... I will remember the request however, not sure if it would come to fruition though... Cheers!

Hello all, I finally got to publishing the hotfix version, download it from here: https://github.com/aronCiucu/DCSTheWay/releases/tag/v1.4.1

Hello, good work there! I will test it as soon as I can as well. I see some other changes as well, like the NAV master mode input being removed. Is that not required anymore?

Hello, indeed I got some reports for it not working anymore, I will work on a fix as soon as I can

Thank you for taking the time to read through this and reach out to Wags. I'm glad it's correct, it seemed like an exploit to me at first. Have a fantastic new year!

Hello everyone, I am sure many players have been most pleased with the addition of a substantial depth to our beloved F-16 Electronic Warfare capabilities, opening up a new field to explore. This post is intended to seek some extra details and clear up some confusion about the ALQ-184 ECM pod, namely it's effect on the onboard sensors. Let us begin. As we have been informed by Matt Wagner's recent videos and Mini Updates, the ALQ-184 has 2 main modes of transmission: Self Protection Jammer (SPJ) mode Barrage Noise Jammer mode One of Wags' videos explains what they mean, SPJ mode attempting to break a radar lock on the aircraft, and Noise Jammer mode denies radar range information from hostiles. In terms of the ECM's interference with the onboard sensors such as the FCR, HTS and HARM, the 184 seems to have another 2 modes of operation, as explained by Matt: Radar Priority mode ECM Priority mode To explain how these modes work, here is a quote from one of Wags' Mini Updates: When in ECM Priority, the FCR and HARM/HTS are silenced; When in Radar Priority and the jammer is transmitting and ownship radar and HARM/HTS performance is reduced by 40%. Currently in DCS it seems that the Noise Jammer mode, in Position 3 on the ECM panel, functions in ECM Priority, turning off the FCR. The other SPJ mode can function in both Radar Priority or ECM Priority, using switches 1 and 2 respectively. The interesting behaviour arises when selecting Position 3 Noise Jammer, beginning transmission, then switching to Position 1, which now allows the FCR to operate. Position 1 seems to now work as the Radar Priority mode toggle instead of enabling the SPJ mode, when ECM is still transmitting in Noise Jammer mode. I am uncertain if this is correct behaviour. On one hand it would make sense to have the Position switches be multi purpose, and make them double as toggling the Radar Priority mode when transmitting Noise, as there is no Position 4 to enable Radar Priority in Noise Jammer mode. I also have my concerns that the Noise Jammer mode should function in Radar Priority in the first place, it being in ECM Priority and disabling the FCR, HTS and HARM is not mentioned anywhere by Wags, quite the contrary, he has told us that Barrage Noise Jammer mode is intended to be turned on, and left on as a preemptive measure, which would be unwise to do if it would turn off all the sensors, as it does in DCS. As a summary, the main question is: is it correct that switching from Position 3 to Position 1, while ECM still transmits in Noise Mode, enables the FCR to function? I am aware that things may still be work in progress, this post is intended to clarify some details about the workings of the ALQ-184, as it is a complex system that I am sure required a lot of development time. Best of luck with the module moving forwards, and happy holidays! ECM.trk