notproplayer3 Posted July 6, 2020 Posted July 6, 2020 No, this is the intended behavior, I really don't know the details but I think the cooling fluid for the IR seeker only keeps it cool for about 30 minutes, after that the seeker overheats (?), so basically you should prep those missiles only a certain time before a possible engagement. They explain this in the training missions, and I probably got lots of details wrong anyway, but I just know that if the missile is prepped for too long, it'll stop working Full fidelity su27/mig29 ?
Murdock_01 Posted July 6, 2020 Posted July 6, 2020 So you mean by preping the missile is turning the master arm on? Is this information in the Manual? M2000c Pilot :pilotfly:
nanucq Posted July 6, 2020 Posted July 6, 2020 Take a look at page 229 in manual : 4. MAGIC II P REPARATION . This button is used to trigger On or Off all MAGIC II missiles Preparation (BIT & cooling of the seeker) and thus allowing/preventing their use. The preparation is triggered by either powering up the aircraft, clicking on the button or by selecting the missile related-mode on the PCA or using the HOTAS selector. Switching the preparation Off is used to save the MAGIC II seeker coolant supply (nitrogen). There is enough supply to keep the seeker heads active for 90 minutes, after that time the seekers become warm rendering the missiles useless. The missile will take 30 seconds before becoming fully operational. NOTE Each time the preparation is reactivated (switched On) will shorten the coolant supply by 10 minutes. Plan its use carefully. Page 22915 - 2 SECTION 15 W EAPONS M ANAGEMENT COMBAT The button has two lights: P: Short for “Prêt” (Ready). Turns on when the MAGIC IIs are ready to use. Blinking when they are undergoing the preparation process and Dark when the missiles are in safe mode or no missiles are onboard MAG: Turns on when there are MAGIC II missiles aboard the aircraft. i7 8700k @ 4.7, 32GB 2666Mhz, GTX 2070 Super, SSD 1To, TrackIR 5, TM16000M HOTAS
Murdock_01 Posted July 6, 2020 Posted July 6, 2020 Great... that explains it. So this is not a bug. Thanks for Clarifying guys. M2000c Pilot :pilotfly:
hlfritz Posted July 8, 2020 Posted July 8, 2020 further issue in the 1.1.1 manual. page 270, the caution statement says "In the M-2000C, the bomb release mode is determined by the bomb type. MK-82s, GBU-12, GBU-16 and GBU-24 all use CCRP through the BL (Bombes Lisses, Free fall bombs) master mode. MK-82SE, BLG-66 use CCIP through the BF (Bombes Freinées, High drag bombs) master mode" then on page 272 in the CCRP section, para. 3 states "This bombing mode is exclusive to Mk-82, BGL-66 and GBU series bombs." I believe the statement on page 272 regarding BGL-66 is the incorrect statement.
narq Posted July 9, 2020 Posted July 9, 2020 Hi There, I've noticed there is no way to bind the UHF and U/VHF channel selector knobs in the Mirage. I have rotaries on my HOTAS which are perfect for this function but can't bind them. I found an older post which stated they were planned, but it was some time ago (Feb 2019): https://forums.eagle.ru/showthread.php?t=232906 These binds would be very useful - as well as some additional ones like Master Arm On/ Master Arm off (to bind to switches). Thanks
Golfwingzero Posted July 20, 2020 Posted July 20, 2020 I was also looking for those channel selectors and was surprised it wasn't possible to bind them. I hope they add this, but I don't think this is the right place to ask.
Charly314159 Posted July 24, 2020 Posted July 24, 2020 Hello, With the last open beta update, and possibly before that, it is not possible to tune flood lights intensity. Knobs act like a on/off switch. This makes night flying highly uncomfortable. Please fix ASAP. Moreover flood lights tank the performance...
Madone Posted July 26, 2020 Posted July 26, 2020 +1 it's always been like on/off Strike Posture Set CAS Center of Excellence Intel Core i5 4690k @4,6Ghz, Gigabyte GTX 970 OC, Gigabyte Z97-X, 16GB G Skill Sniper @2400, Samsung 860/850 EVO , Win 10 64 bits, Dual monitors 27"@144"Opentrack + TM Warthog + Saitek pro flight combat
Balzarog Posted July 27, 2020 Posted July 27, 2020 (edited) I just updated to the latest open beta. With the exception of the “kneeboard on/off,” and one other kneeboard selection, ALL of the kneeboard commands are in orange, and I con’t assign a Warthog H.O.T.A.S binding to them. I’ve restarted the sim about five times with no change. I even loaded my old H.O.T.A.S. bindings from 2017 with no luck. I have checked my bindings. The bindings aren’t the issue. The issue is that you can’t even assign bindings to the kneeboard commands. I will try to run a repair to see if that works. I’ll edit this post with my results after I do. Admittedly, I haven’t gone into the M2000 for a few years. Edit: After I performed a repair on the Open Beta, it turns out that the issue is related to the controls bindings, but it was an obscure problem. After much searching, and deleting the common ED binding duplicates, I noticed that all of the affected commands shared a common factor. I use my Warthog “pinkey” switch as a modifier. I deleted the modifier, and assigned the “pinkey” switch as a modifier again. That solved the issue. Edited July 28, 2020 by Balzarog When all else fails, READ THE INSTRUCTIONS! i-7 8700K Coffee Lake 5 GHz OC CPU, 32GB Corsair 3200 RAM, GTX1080 Ti 11Gb VRAM. Controls - Thrustmaster Warthog H.O.T.A.S., Saitek Pro rudder pedals, TrackIR 5, Oculus Rift S, Rift CV1
Mr_sukebe Posted July 27, 2020 Posted July 27, 2020 Try a repair, mine is fine 7800x3d, 5080, 64GB, PCIE5 SSD - Oculus Pro - Moza (AB9), Virpil (Alpha, CM3, CM1 and CM2), WW (TOP and CP), TM (MFDs, Pendular Rudder), Tek Creations (F18 panel), Total Controls (Apache MFD), Jetseat
Ramsay Posted July 28, 2020 Posted July 28, 2020 I just updated to the latest open beta. With the exception of the “kneeboard on/off,” and one other kneeboard selection, ALL of the kneeboard commands are in orange, and I con’t assign a Warthog H.O.T.A.S binding to them. Sometimes the input config file(s) can become corrupt i.e. have conflicting, redundant or duplicate assignments. AFAIK the only* reliable way to fix it is to delete your old input profile for the effected module i.e. • "Saved Games\DCS\Config\Input\M-2000C" ... and redo your keyboard and joystick assignments. In my case, I take a backup of the old profile and open the .diff.lua's in Notepad++ for reference when redoing the assignments. *you can open the "DCS World" default profile(s) and compare them to the "Saved Games" .diff.lua's to find the problem(s) but it's faster and easier to delete the old profile(s) and do them afresh. 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
RAZBAM_ELMO Posted October 29, 2020 Author Posted October 29, 2020 Testrandom tests 2.mizdcs.log-20180204-102638.zipFailureTest.trkWheelChocksToHigh.trkTacview-20190806-215616-DCS-Caucasus M-2000C Guns, guns, guns.ziptest_m2000.mizHUDbug.trkM2000-CAS-AGmode-bug.trkMirage_Radio_CLR_Display.trkm2000aispot.trkf18aispot.trkM2000C Crash.trkM-2000.trkVTB PPI lock bug.trkVTB_RWS_behavior.trkVTB_Scan_alt_behavior.trkRDR_Vert_Scan.trkHUD_TD_box.trkRWR_lock_bug.trkPCN_FPS_Bug.trkCCPL-PI_Bug.trkHUD_IDN_Bug.trkPID_Bug.trkCCPI PI.trkCCPL PI INS update.trkJF17 RWR.trklightKnobEmptyScroll.trklightKnobEmptyScroll.txtdcs.log-20200404-183526.zipMk2CStrangeRadarBehaviour.trkm2000c-LLnav-bug.trk Know and use all the capabilities in your airplane. If you don't, sooner or later, some guy who does use them all will kick your ass. — Dave 'Preacher' Pace, USN.
Recommended Posts