Maulkin Posted March 4, 2017 Posted March 4, 2017 After patching to 2.0.1 I jump into a Mirage free flight instant action mission. Instantly the Mirage is pitching about and completely out of control. I can see the master warning is on and the warnings panel has left and right fuel pump lights lit up. I check the left and right fuel boost switches and confirm they are both on. Cycling them has no effect. I can see that I have fuel flow to the engines however. I dont have any of these problems with DCS 1.5. Does anyone know what is going on? --Maulkin Windows 10 64-bit - AMD Ryzen 9 5900X @ 3.7 GHz - 32 GB DDR4 3600MHz RAM - EVGA FTW3 RTX 3080 - Asus Crosshair VIII Hero motherboard - Samsung EVO Pro 1 TB SSD - TrackIR 4 Pro - Thrustmaster Warthog - Saitek rudder pedals - Lilliput UM-80/C with TM Cougars
Zeus67 Posted March 4, 2017 Posted March 4, 2017 I understand your predicament but we need a track file to see what is happening "Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning." "The three most dangerous things in the world are a programmer with a soldering iron, a hardware type with a program patch and a user with an idea."
wolle Posted March 4, 2017 Posted March 4, 2017 see attached trk file. This seems to be just one example of the fact that 2.0 has gone beserk for some users with the latest updates (see similar reports for other aircraft in other forums.m2k track.trk [sIGPIC][/sIGPIC] Intel Core I7 4820K @4.3 GHz, Asus P9X79 motherboard, 16 GB RAM @ 933 MHz, NVidia GTX 1070 with 8 GB VRAM, Windows 10 Pro
Maulkin Posted March 4, 2017 Author Posted March 4, 2017 (edited) Sorry I should have thought of that. Looking at the CTRL-ENTER, it appears the fly-by-wire system goes crazy. EDIT: I just reviewed the track and noticed something. Play the track the first time and the aircraft looses control the second you unpause. Stop the track and immediately replay it again (dont go back to the main menu) and you will see what I actually saw when I recorded it. You should see the aircraft pitching about, but not violently. Then you should see where I CTRL-ENTER to check the white diamond vs. the red diamond (red diamond remains centered indicating no control input but the white diamond is jumping up and down). I then start to give some control input and the FBW system goes nuts.M2K_FBW_insane.trk Edited March 4, 2017 by Maulkin --Maulkin Windows 10 64-bit - AMD Ryzen 9 5900X @ 3.7 GHz - 32 GB DDR4 3600MHz RAM - EVGA FTW3 RTX 3080 - Asus Crosshair VIII Hero motherboard - Samsung EVO Pro 1 TB SSD - TrackIR 4 Pro - Thrustmaster Warthog - Saitek rudder pedals - Lilliput UM-80/C with TM Cougars
antagonist Posted March 4, 2017 Posted March 4, 2017 This is almost certainly not a problem with the module itself, but the latest patch introducing some sort of error in lots of planes due to its copy protection. Links to follow. https://forums.eagle.ru/showthread.php?p=3069205#post3069205 https://forums.eagle.ru/showpost.php?p=3069070&postcount=51
Recommended Posts