Compulse

Quick fix - Go to \Eagle Dynamics\DCS World\Mods\aircraft\AJS37\Input\joystick\default.lua, open with something like notepad++ Under the weapons section (around line 130), paste the following Save the file and start DCS. You should have 2 new things you can bind under the weapons section, one of which will open the cover, one which will press the button.

First: 56 MiG, 24 Tiggen Second: 61 MiG, 28 Tiggen.

The problem with doing that is that preventing modification of the file will stop you from getting any new additions to the file. You could try to make the file read only, but I haven't tested that and have no idea if it would work. I just have my extra lines saved in a separate file, and add them after an update; it only takes 30 seconds.

The latest FM patch seems.. strange. The Mirage will fly ~250kn with hardly any throttle, and as soon as you think about turning you lose 50+ knots instantly. I'm not sure how realistic it is, as I have very little experience flying planes in real life (and no experience flying a delta wing), but it seems a little off. I understand that people were complaining about the Mirage performance being overpowered before this patch, but this seems like a large swing in the opposite direction.

Zeus, is there any information you can give us about the vertical angle below/behind the plane that this will cover? Anything about the range?

Works perfectly, thank you. Another question - the Neopixel library doesn't work with the normal servo library, so they include their own library. It should be as simple as swapping the "#include <Servo.h>" to "#include <Adafruit_TiCoServo.h>" and using "Adafruit_TiCoServo servo_;" instead of "Servo servo_;" according to their documentation. I did this in Servos.h in the DCS bios arduino library, however it gives an error on compiling - flaps:12: error: 'ServoOutput' in namespace 'DcsBios' does not name a type DcsBios::ServoOutput flapPos(0x10a0, 9, 1100, 500); ^ exit status 1 'ServoOutput' in namespace 'DcsBios' does not name a typeDocumentation for the TiCoServo library - https://learn.adafruit.com/neopixels-and-servos/the-ticoservo-library I found this - Which I'm guessing might be the cause of this - any idea on how to correct it? EDIT: I removed the #ifdef check for the Servo.h include. I now have this error - cciLTvkl.ltrans0.o:(.text+0x790): undefined reference to `Adafruit_TiCoServo::writeMicroseconds(unsigned int)' collect2.exe: error: ld returned 1 exit status exit status 1 Error compiling for board Arduino/Genuino Uno.I've checked the Adafruit TiCoServo library and it supports writeMicroseconds (and I've edited the library too to ensure that it's not confusing my board for one that doesn't support it. I know this is pretty far outside the scope of DCS Bios, but any help would be appreciated. FINAL EDIT: I've changed some library code for the TicoServo and it appears to now be working.

Hi Ian, Is there any way to detect when a plane (A-10c) has crashed/the player has disconnected? I'm using a Neopixel as a Handle Gear Warning Light, but it's often left turned on indefinitely if the plane crashes while the light is on. Is there a place I can add a call to turn it off should the plane explode/the player disconnect?

The Master Arm button clickbox is not over the switch when the switch is in the up position, resulting in a large area of the switch that is unclickable. I'm not sure if this is a new bug as I always have the Master Arm bound, but I'm running the latest update on the beta version of 1.5. I'm not sure if the resolution of the game is causing this issue, as I'm running at 3440x1440. Video of problem -

28/11 is a Monday, all DCS news/updates are on Fridays. I was expecting a 28th October announcement and a 11th November launch. Hype train derailed :(

Zeus, if you decide to not change the aerodynamics, would it be possible to make the drag chute reloadable through the weapons/fuel menu, rather than the repair menu?

My HOTAS Warthog setup - not perfect yet, I still need to adjust a few things, but it's getting there. I also have a small box I made myself for a few extra switches/toggles. Running off an Arduino with MMJoy2.

QUESTION 1, Would you buy an AV-8B Harrier Module A = Yes - after the quality of the Mirage, I have faith in RAZBAM delivering something great. QUESTION 2, How long do you honestly believe before the Harrier will be introduced?(No disrespects to RAZBAAM you guys are great!) B = 12 Months - Honestly, I would rather have something great released later than something not-so-great released earlier. QUESTION 3, Are you more excited for the AT-27 Tucano that is supposed to be released by the end of this year, or waiting some more time for the AV-8B? B = AV-8B - I might buy the Tucano, but it won't be a preorder. I don't see it being anywhere near as fun as a Harrier, but if it's a quality module it'll end up in my collection eventually. Question 4, Do you see the AV-8B having a place in DCS World? A = Yes, it will add some very interesting gameplay features to DCS - It's going to fit in very well I think. It might not be the best at any one role, but it's very versatile. RAZBAM have a guaranteed preorder from me with any fast jet they make, after the quality of the Mirage. I just hope that the Harrier is as good.

It's currently impossible to do it perfectly - moving the switch only with a keybind doesn't actually do the function. You can kind of do what you're looking for, but it's not perfect. Using iCommandSwitchMasterArm bound to a 3-Pos abstraction, you can toggle the function, but you have to make sure that the switch is in the right position to start with.

Ok, that's useful. Thanks very much.

The Radar being at an angle to the left instead of straight. Apologies if that wasn't clear.

I've been watching youtube videos of the Mirage, and I've seen people doing this with the radar quite often. I can see the obvious advantage of it, but I can't for the life of me work out how to do it - I've looked through all the keybinds and done some light googling, but haven't had any luck. Is this something that was removed from the Radar, or if it's still possible, how do you do it?

Is this wrong then? Are we not getting the PCM mode, or is the guide wrong?

That post is from 2015, but it explains RAZBAMs view on it I believe. I can't speak for how it compares to the real plane. To add on to my last post - I found this list of missing features - The IFF is enabled now, although I'm not sure if there's more work to be done on it. Right now it works fine for me. Air to Air refueling works too I believe, although it may be bugged as to how much fuel you can take on board, which should be fixed soon if it is.

I would say the plane is pretty close to being functionality complete. I believe that the radar has a bit of work that needs doing on it (ground display?), the jammer has some implementation things that need to be done (high power mode I believe), and the IR launch detection needs to be done I believe (although it's a subject of debate as to if the plane should have it). I'm not sure of anything else that needs implementing, but most of the functionality is there. There's a few things that need fixing (magic missiles are currently very bugged, radar isn't great with locks and switching stores), but I believe a lot of patches are coming on Friday. The devs are great at patching as well as providing updates on progress. Apart from a few bugs that really should have been picked up before patches went live (Magics again, do I sound salty?), the devs have been brilliant. Many people, myself included, would list RAZBAM as the best 3rd party devs for DCS, and as someone who hates preorders, I will be preordering their next plane release. The flight model is exceptional. The mirage will outturn anything it comes up against, and it's a joy to fly. There's a few things that I believe need small tweaks, but overall it's an incredible FM. The mirage is currently my favourite module, and I can't see that changing for quite a while. It's definitely worth picking up.

I just tested the Gun Arm, and it works fine with that code. Master Arm doesn't :( Can you explain how you find the enumerations and panel IDs of the switches?

Master Arm doesn't work (not even the switch moves), Gun Arm switch moves but haven't tested shooting yet. Thanks for the help so far, I'll play around some more and try to get something working. How do you find the switch enumeration and cockpit_device_id? I googled for a while to find a method but resorted to just checking current bindings. I can see those, but that's only a toggle - The switch only has an On position and an Off position, to I have to flip it to On twice to toggle. I'm trying to make it work for Switch on - Arm on, Switch off - Arm off. Thanks. I guess we'll have to wait for a iCommandSwitchMasterArmOn method to be added before it works though.

I'm trying to bind two position switches on my Hotas Warthog to the Master Arm and Gun Arm switches. Currently they only have toggle functionality, meaning I have to flip the switch twice to change on/off. Unfortunately I can't find a cockpit_device_id and enumeration of the switch, but I have added a line to the 3-Pos switch abstractions to toggle them - {down = iCommandPlaneAHCPGUNArm, up = iCommandPlaneAHCPGUNArm, name = _('Gun Arm TOGGLE ME'), category = _('3-Pos. Switch Abstractions')}, However, this doesn't account for the position of the switch to start with. Is there a way to do this better? I've also tried blindly using "iCommandPlaneAHCPGUNArmOff" following the landing gears principal - "iCommandPlaneGearUp" and "iCommandPlaneGearDown", but that didn't work. Does anyone know the switch enumeration for the master arm/gun arm?