CrashO

Surely you aren't trying to stick a track file on youtube right? What is the file type (and what did you record it with) ?

How is the feeling on those? I have some cheap "heavy duty" switches laying around here (with the same style of red name shield on them). And they don't feel smooth at all. They work, but when flipping them it just feels forced. If you flip them not far enough, they just stay between 2 positions. I also have some Apem switches and they feel butter smooth, pretty similar to the ones on the Trustmaster Warthog throttle base. But at $5 a pop I would prefer to go for ebay ones :D

So if I understand you correctly, you just want 2 joystick buttons (ingame) using a normal off-on toggle switch? Not sure on how to do it with MMJoy (I don't use it). But to do so with ArduinoJoystickLibrary is pretty easy. I imagine MMJoy allows you to do it pretty much the same way. Just keep track of the buttonState (is it on or off) and set a joy button to 1 while the other one is 0. When the state changes, flip it. I do it like this (to use on-off-on switches as 3 joybuttons, but you can just rip out the stuff for the second pin to use for on-off) // toggleIndex = location inside the array where all info about this switch is stored // rowIndex = pin for the row (common of the switch) // col_1 = first pin for switch // col_2 = second pin for the switch // button_1 = joy number for 1st position // button_2 = joy number for 2nd position // button_3 = joy number for 3rd position void readThreewayToggle(int toggleIndex, int rowIndex, int col_1, int col_2, int button_1, int button_2, int button_3) { pinMode(row[rowIndex], OUTPUT); // Set row to output digitalWrite(row[rowIndex], LOW); // Set row to GND int currentButtonState = 0; //column currentButtonState = !digitalRead(col_1); if (currentButtonState != lastButtonStateToggle[toggleIndex][0]) { Joystick.setButton(button_1, currentButtonState); lastButtonStateToggle[toggleIndex][0] = currentButtonState; Joystick.setButton(button_3, 0); lastButtonStateToggle[toggleIndex][2] = 0; } currentButtonState = !digitalRead(col_2); if (currentButtonState != lastButtonStateToggle[toggleIndex][1]) { Joystick.setButton(button_2, currentButtonState); lastButtonStateToggle[toggleIndex][1] = currentButtonState; Joystick.setButton(button_3, 0); lastButtonStateToggle[toggleIndex][2] = 0; } if (lastButtonStateToggle[toggleIndex][0] == lastButtonStateToggle[toggleIndex][1] && lastButtonStateToggle[toggleIndex][2] == 0) { Joystick.setButton(button_3, 1); lastButtonStateToggle[toggleIndex][2] = 1; } pinMode(row[rowIndex], INPUT); // Set row to float again } So to use it, I would just call this from inside void loop(): readThreewayToggle(0, 1, column[3], column[4], 1, 2, 3); for the following hardware wiring: *Note, values in the call are -1 from the hardware schematic because of zero based arrays :)

Has been doing this since 3 updates ago.

ED's list is never complete for the Mirage. Just wait for the list from Razbam.

Try turning the radio on .. :huh: AR = Arret = Off Pal = Principal = Main

Possibly related bug: Today I jumped in a Mirage that already had a waypoint (1) set per mission settings. Changed it to something else, flew the sortie and then landed. After (hot) re-arming, I noticed the way-point (1) had changed back to the default coordinates it had on entering the plane.

Works fine here on today's OpenBeta release. Tried it with a new mission and one from last week. If it is older then last week, try re-saving the mission you are using.

Or here (this is Matbog's main thread) :D https://forums.eagle.ru/showthread.php?t=170097

I have seen this too, but only in a "dirty" plane. Seems there is some data being left in the memory. -> enter new game session, pick mirage startup, enter a couple of waypoints, no problems # get shot, pick the same mirage again startup, and look at waypoint 1, and data from the last time still seems present (it is showing the old entered coordinates, so are 2 and 3 etc. However, I can only select them in PREP, not use them in DEST. When I try to change them, sometimes the fluke from the OP happens. However, It is possible to enter a new waypoint over it, you just have to do it "blind". After entering, the screen is normal again.

Use the [ YOUTUBE ] tags ànd enter the video ID between them, don't use the entire url. so [ youtube ]4-Rd4ixccok[ / youtube ] for example (without spaces, ofcourse)

I deserve it because I am to cheap to fork out the money to buy it myself :D

I have been throwing dozens of them for the last few days and on all of them I use RET. No problems whatsoever :thumbup: From an hour ago:

The manual has a nice diagram about it

The gauges show fuel in the feeder tanks (590kg max per tank). So they will only drop when your fuel level gets below 1180kg.

Longitude needs a extra digit (range 000 - 180).. so start with zero (unless you are in Nevada, which lies west of 099 degrees :D ). So 422845 -> 0422845

Just store your stick settings in a seperate file, in case of the Trustmaster Warthog, the names DCS automatically recognizes are: (in \Mods\aircraft\M-2000C\Input\M-2000C\joystick) It allows DCS to update default.lua and not break anything because DCS doesn't touch any files other then default.lua. The only downside is, when using those files, you can't use the settings panel in DCS anymore to assign that device. (you can still view the controls, but the entire column of example the throttle, becomes un-assignable, the files overrule it). So all your bindings will have to be done in those lua's. But, as long as you keep all of your hog bindings in those files. It works great. *edit* For an example, see the files posted here: https://forums.eagle.ru/showpost.php?p=2921551&postcount=9

S turns work great in the Mirage. Try placing the missile at 90 degrees from you (use the RWR) en deploy chaff.

Why not just set the Coordinate display of the map to Lat Long Decimal and get rid of all conversion hassle? Only thing you have to do to the coordinates after that is round up the last digit. So 42'39.883 becomes 42'39.88 and 041'24.166 becomes 041'24.17. (the minor deviation in the screenshot above is due to "mouse precision" on the map)

Page 116 of the manual. (make sure you always check the latest revision in: DCS World\Mods\aircraft\M-2000C\Doc). It (ussually) gets updated after large system changes, such as new jammer functionality :D

RTM :smartass:

Pretty sure this is it: source

I tested it again and again and eventually found the problem. PEBKAC (as always) :D The culprit was a mod I was running (Werewolf's M-2000C Nightvision mod). It missed the changes made to devices and devices_init.lua (DDM_IND) what caused it remove them, and thus removing their functionality. All is good now :thumbup:

Ç'est cool ! :notworthy: