CrashO

It is, I used it months ago to test if it worked. Works just fine. How it works is (on all planes), the receiving party, has to select a channel +63 from the one transmitting. So if the flight lead is at for example Y11, the wingman has to select 11+63 = Y74.

Your friend is GCI, so no. My case was about people using a dedicated GCI client on the same connection they are playing with. So probably something like a laptop sitting on there desk, next to their game monitor. Showing the map en enemy popup positions. I am sure there a plenty of small groups using one of themselfs as GCI. Personally, I don't have any problems with that. But to basically recreate the (disabled..) F10 view by sticking a second computer on your desk.. is something very different.

What are the rules regarding private GCI? For a while there has been someone on the red team (i am sure everyone knows who it is) who has been using a second pc always connected to gci, as his own private radar map. But now, there is more then one. Today at one point I even saw 5 guys on red, of which 2 where in the GCI slot with the exact same ping as two of the fighters. Who connected at the same time, and disconnected at the same time. Not even trying to hide it with their nicknames (using a exclamation mark for one account, a decimal point for the other..).

Nope.. It just toggles between STT and TWS.

Not really. Pushing the lock button again switches to STT. (and alarms your target your locking him). Unless you want him to know (I use it sometimes in order to scare someone in going defensive and bleeding speed), there is not really a need to use it. Since the system switches automatically to STT after firing a 530.

I have been flying the Mirage for almost 13 months. And I have yet to find a second unlock key. I use the same one for STT unlock, TWS unlock and CCM unlock. My first post mentioned this one (backspace) And so did my other post: So please, elaborate on that second key. :D

It's s a manual for a highly detailed simulator. You can't expect them to repeat all information at every sub chapter. If you start flying a plane, the first thing you can expect the pilot to familiarize himself with is the buttons on his stick and throttle. (notice the line in the manual that says. "Integral HOTAS system". I am pretty sure at the landing section, it also doesn't mention "to prepare for landing, move the stick forward to point the nose down, and move the throttle backwards to reduce speed..". The information is all there, you just didn't read it. (or searched for it). It is a manual, not a Flying the mirage for Dummies guide. (that is what Chuck's guides are for). So you might want to try Chuck's Mirage Guide. It is not a manual, but a guide. Repeating all information in steps. It might be more to your likings.

Or you could just read the manual..

It is in the manual you where bashing in another thread...

Kijk eens op combatflight.nl . Zitten een hoop Nederlandse (en Belgische) vliegers bij elkaar. Het forum is redelijk uitgestorven, maar de Slack (soort moderne IRC) is erg actief (invite daarvan krijgt iedereen na forum registratie). We spelen vrijwel dagelijks op Buddyspike met A-10's, Hueys en Mirages.

5 weeks ago... :huh:

So you are saying you can still sustain flight in the mirage at 32kts? (60km/h). Goodluckwithdat. She might not "stall" in the classic way of pulling to high of a AoA, because of the FBW trying to create lift with the surfaces and controlling max AoA. But down, you will most certainly go. Which is basically what stalling boils down to (losing all lift).

PlaysTV and DCS don't like each-other because DCS does not run in "real" fullscreen by default. It runs in a borderless-maximized window, so most of the time it does not get detected as a running game. Try using Alt-Enter to go to fullscreen if playstv won't record. (although I have switched from PlaysTV because it crashed to often and now use Radeon ReLive, I still have to ALT+Enter for it to enable the playback mode)

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 :)

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

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

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

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)