BManx2000 Posted September 11, 2016 Posted September 11, 2016 (edited) https://www.digitalcombatsimulator.com/en/files/2080541/ Based on tutorial from Boris: https://forums.eagle.ru/showthread.php?t=124711 This mod adds to the briefing screen, wind data suitable for input into the A-10C CDU. The wind data is in the following format: (thousands of feet) (wind direction in degrees)/(wind speed in knots) (degrees celsius) It also adds QNH in hPa for the Viggen. Installation: Copy the "CDU Wind Briefing" folder into your JSGME mods folder and enable it. Edited February 11, 2017 by BManx2000
Gliptal Posted September 11, 2016 Posted September 11, 2016 https://www.digitalcombatsimulator.com/en/files/2080541/ Based on tutorial from Boris: https://forums.eagle.ru/showthread.php?t=124711 This mod adds to the briefing screen, wind data suitable for input into the A-10C CDU. The wind data is in the following format: (thousands of feet) (wind direction in degrees)/(wind speed in knots) (degrees celsius) Installation: Copy the "CDU Wind Briefing" folder into your JSGME mods folder and enable it.Excellent work!
Beeroshima Posted September 13, 2016 Posted September 13, 2016 Does this pass integrity check? Sent while I should be working instead.
Gliptal Posted December 13, 2016 Posted December 13, 2016 On the latest versions, this mods hangs DCS when loading the briefing screen.
gospadin Posted December 13, 2016 Posted December 13, 2016 Are CDU winds magnetic or true? Written wind notation is typically true, while spoken wind information is magnetic. My liveries, mods, and missions for DCS:World M-2000C English Cockpit | Extra Beacons Mod | Nav Kneeboard | Community A-4E
BManx2000 Posted December 23, 2016 Author Posted December 23, 2016 I uploaded a new version compatible with DCS 1.5.5.60503. This version also fixes a crash that would happen with "simple" briefings.
docWilly Posted February 4, 2017 Posted February 4, 2017 I just found after updating 2.0 to the latest release that CDU wind briefing mod leads to not loading your modules on NTTR. Latest 1.5.6 version plus fix from yesterday works fine. [sIGPIC][/sIGPIC]my rig specs: i7-4790K CPU 4.50GHz, 32GB RAM, 64bit WIN10, NVidia GeForce GTX 980 Ti, SSD+ A10C, UH-1H, M2C, F5E, Gazelle, KA 50, F18C, DCS 2.5x OB
aemvee Posted February 6, 2017 Posted February 6, 2017 Do you think you could add hPa value on the QNH line. See the attachment.
BManx2000 Posted February 11, 2017 Author Posted February 11, 2017 I updated the mod to work with the latest DCS versions and added QNH for the Viggen. 1
tintifaxl Posted February 22, 2017 Posted February 22, 2017 Fantastic mod! Windows 10 64bit, Intel i9-9900@5Ghz, 32 Gig RAM, MSI RTX 3080 TI, 2 TB SSD, 43" 2160p@1440p monitor.
docWilly Posted July 7, 2017 Posted July 7, 2017 And once again...after relase of Caucasus 1.5.7 CDU briefing mod leads DCS to hang with 10% on loading screen. If you are willing to have a look into that issue....functionality of this awsome mod is sadly missed .... :-) [sIGPIC][/sIGPIC]my rig specs: i7-4790K CPU 4.50GHz, 32GB RAM, 64bit WIN10, NVidia GeForce GTX 980 Ti, SSD+ A10C, UH-1H, M2C, F5E, Gazelle, KA 50, F18C, DCS 2.5x OB
Frederf Posted July 7, 2017 Posted July 7, 2017 Are CDU winds magnetic or true? Written wind notation is typically true, while spoken wind information is magnetic. It matches the setting in the IFFCC which defaults to magnetic in DCS. If the wind is blowing south to north in editor then A-10 LASTE would say 194° in Nevada and 185° in Georgia. For direct entry to CDU directions must be reversed by 180° (wind-to wind-from) and corrected for magnetic variation (~5°E or ~14°E).
RuskyV Posted July 13, 2017 Posted July 13, 2017 Hi all, Any news on whether this mod is now working with the latest DCS update? it was an excellent tool that i miss quite a bit.
Meisha Posted August 11, 2017 Posted August 11, 2017 update please!! this app is really important to A10C Pilots!
BManx2000 Posted August 12, 2017 Author Posted August 12, 2017 I finally got around to updating this, works in 1.5 and 2.1.
mastersetter Posted September 12, 2017 Posted September 12, 2017 Is this broken again in the latest update? I have not re enabled my mods since the update so may try that but it didn't show in the last mission i did recently.. i5-7600K @ 4.8 | 32GB | 1080 | Rift S | TM MFD & WH HOTAS-10mm ext + TFRP
Oscar Juliet Posted September 19, 2017 Posted September 19, 2017 This mod works and is IC compatible but the calculations are WRONG for 2.1. It gives you wrong LASTE data It uses MagVar -7 which is great for 1.5. I've read we should use a +12 in Nevada but I have no idea. Either way it drastically changes the way LASTE is calculated. This mod can't be used on 2.1 effectively. https://docs.google.com/spreadsheets/d/1xYATEyeH3hHkkaDqcFj-__mZWIin5u2HEFdonp-0k_w/edit#gid=1491611486 This spreadsheet was imported from one that was given out on the forums. My Youtube Channel
BManx2000 Posted September 20, 2017 Author Posted September 20, 2017 That's wrong, magnetic declination in both areas is positive. https://upload.wikimedia.org/wikipedia/commons/1/11/World_Magnetic_Declination_2015.pdf
Oscar Juliet Posted September 20, 2017 Posted September 20, 2017 (edited) That's wrong, magnetic declination in both areas is positive. https://upload.wikimedia.org/wikipedia/commons/1/11/World_Magnetic_Declination_2015.pdf The calculations from this mod and our spreadsheet at -7 are the same. So it is correct. +12 for Nevada which is on charts for the Nellis area gives almost accurate results. So this mod will not work for 2.1 calculations. NOTE: Using plus 12 on our spreadsheet and in high winds on Nevada we still will miss targets with guided weapons. If targeting a tank it will land next to it. This isn't noob error either. It happens with all of us. We don't know what the perfect laste calculation is on Nevada. Edited September 21, 2017 by Oscar Juliet My Youtube Channel
tintifaxl Posted October 26, 2017 Posted October 26, 2017 +1 Windows 10 64bit, Intel i9-9900@5Ghz, 32 Gig RAM, MSI RTX 3080 TI, 2 TB SSD, 43" 2160p@1440p monitor.
Jace11 Posted November 28, 2017 Posted November 28, 2017 Also keen to see this working! Had a look at the files and the scripts seem ok. If as people say, its a problem with subtracting the correct number from the wind heading to compensate for magnetic north bearing then I think the file that needs correcting is cdu_wind.lua and probably at line 44 which reads as@ local angle = wind.dir + 173 this is 173 (i.e 180 - 7) it looks like he coded it here at the start before the wind conversions and this should probably be the only thing that needs fixing for NTTR. So maybe 168 should be used instead? I'm fuzzy on the "should it be +12 or -12 thing" after reading these posts.
Ramsay Posted November 28, 2017 Posted November 28, 2017 (edited) I'm fuzzy on the "should it be +12 or -12 thing" after reading these posts. Both the Caucasus and Nevada theaters have +ve Magnetic Declination, +7° and +12° respectively. In Nevada • a map reading of 0° True = -12° Magnetic or converting a magnetic compass reading in the cockpit to a map bearing. • 0° Magnetic = +12° True on a map Convention is to describe how 0° Magnetic varies with respect to true north, as that is how regular maps and charts are marked. Hence the positive +12° sign. Note: The equation to convert between True and Magnetic bearings in Nevada is: • Magnetic = True - Declination = True - (+12) = True - 12 with the subtraction sometimes causing confusion in the +/- of the declination. Magnetic Declination Chart: https://upload.wikimedia.org/wikipedia/commons/thumb/1/11/World_Magnetic_Declination_2015.pdf/page1-800px-World_Magnetic_Declination_2015.pdf.jpg Edited November 28, 2017 by Ramsay i9 9900K @4.8GHz, 64GB DDR4, RTX4070 12GB, 1+2TB NVMe, 6+4TB HD, 4+1TB SSD, Winwing Orion 2 F-15EX Throttle + F-16EX Stick, TPR Pedals, TIR5, Win 11 Pro x64, Odyssey G93SC 5120X1440
Recommended Posts