98abaile

Because it's that third party's prerogative of when to announce their next project.

The problem with that is that if they update the default file, you lose any of the new bindings when you put your modded one back. I've already tried that, it didn't work. I know it's supposed to, but it didn't.

As the update says, I have to modify the default.lua file in "E:\Program Files\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\FA-18C\Input\FA-18C\joystick" after it gets overwritten every update. I want to add these lines: { down = iCommandPlaneGearUp, up = iCommandPlaneGearDown, name = _('Landing Gear Control Handle - 2Pswitch'), category = {_('Special For Joystick'), _('Left Vertical Panel')}}, { down = SMS_commands.MasterArmSw, up = SMS_commands.MasterArmSw, cockpit_device_id = devices.SMS, value_down = 1.0, value_up = 0.0, name = _('Master Arm Switch - 2Pswitch'), category = {_('Special For Joystick'), _('Master Arm Panel')}}, { down = gear_commands.HookHandle, up = gear_commands.HookHandle, cockpit_device_id = devices.GEAR_INTERFACE, value_down = 1.0, value_up = 0.0, name = _('Arresting Hook Handle - 2P switch'), category = {_('Special For Joystick'),_('Right Vertical Panel')}}, { down = hotas_commands.THROTTLE_EXTERIOR_LIGTHS_EXT, up = hotas_commands.THROTTLE_EXTERIOR_LIGTHS_EXT, cockpit_device_id = devices.HOTAS, value_down = 1.0, value_up = 0.0, name = _('Exterior Lights Switch - 2Pswitch'), category = {_('Special For Joystick'),_('Throttle Grip'), _('HOTAS')}},Can I create a diff file in my saved games and how do I do that (actually it doesn't matter if it'll work or not, how do I create a diff.lua? everything on google is gobbledygook)? EDIT: Guys, mod managers are not the solution since the modded file will overwrite the latest official file and remove any official updates to the file.

Say an individual wanted to bolt the modules onto some hardboard or ply. I take it there's a standard bolt pattern?

Yeah, what kaltokiri said. I have no idea how to use the script page.

Yep would rather have the W model.

There's probably no reason why they couldn't model it (like they did with the hornet LEX vapors), but I'd wait for them to finish their atmospheric model first.

200 euro for just the grip? Hard pass. I didn't even want it made of metal.

I think the main thing that was putting me off was actually the PR disaster that was splitting up multiplayer with the carrier DLC (jury's still out on the one; over to ED), only to then get negative news about the F-16. Basically a bad time for more bad news. The lack of the sniper pod is the only thing I'm a bit sad about now, but I understand the reason. TERs weren't a big issue for me, but I'm grateful they'll be in since it's an opportunity for fun. I'm very happy that JSOW is back in since I like the idea of using exotic weapons. I think I'll be preordering it on Friday.

I'm not convinced. LODs are a thing..

Number 3 is fine, just make it so they get no ATC response, can't spawn on it and bolter every time.

The upcoming Nimitz DLC will prevent players who don't have it from joining servers that use it. It's basically the assets pack debacle all over again and ED hasn't learned their lesson of "don't split the community". Some people are also complaining about the new carrier comms and LSO grading (which will be part of the DLC) being stuck behind a paywall, but that's a negligible issue.

Would it be possible to allow us to disable certain instruments entirely for certain aircraft? For example, I only need the UFC for the harrier and the hornet, and I only need the CDU for the A10C. The other exports for those aircraft are just an unnecessary burden on my computer and wifi. Also, would it be possible to have the rotatable instruments auto rotate to match the device's orientation? Having to select it each time in the PC app (and reselect it if it messes up) is an annoyance.

This is exactly my issue as well. The thing is it should be simple for ED to work around and I can't believe they haven't already thought of it. Allow me to spell it out: 1. If a player doesn't own the module, they will be unable to select any slots that spawn on the DLC carrier. Similarly, if they somehow do make it aboard, they will be unable to hook up to the cat. 2. If a player doesn't own the module, they will not get a response if they try to contact it (whether they can even hear it if they tune in is up for debate, I believe they should if only as an advertisement on what they're missing). 3. If a player doesn't own the module and they try to land on the DLC carrier, they bolter every time. Whether they can see any of the animated deck crew (or perhaps low detail facsimiles) is up for debate. The key here is to simple deny any interaction to players who don't own the module; not the ham fisted way of denying people access to servers. Remember the golden rule: Do not split the community!

The problem I face is finding one at a reasonable price in the UK.

Save different profiles?

Is it still not possible to export mfds to monitors to the left of my primary screen (i.e. negative coordinates)? I really don't want Windows to treat my left monitor as the primary

Nice, just the thing I needed. Now if only there were a way to positively locate it with correct alignment on a Virpil mongoose.

Niiiiice!!! For warthog users, it'll likely be compatible too without any specialist connector.

Cheap: https://www.amazon.co.uk/Thrustmaster-T-Flight-Hotas-Joystick-PS3/dp/B007TL3GP4/ref=sr_1_2?keywords=tflight%2Bhotas&qid=1555616175&s=gateway&sr=8-2&th=1 Mid range: https://www.amazon.co.uk/Thrustmaster-T-16000M-FCS-Hotas-PC/dp/B01H6KXGDY/ref=sr_1_2?keywords=thrustmaster&qid=1555410448&s=gateway&sr=8-2 The warthog is high range (although it's really showing its age and design flaws now) but requires you to buy pedals. VKB and Virpil are very high end boutique pieces. If money is no object, get the Virpil CM2 base with the T50CM2 grip and either get the Virpil throttle or try and get a warthog throttle and mod it with the replacement slew control (https://deltasimelectronics.com/). You'll then need to get pedals, either the new thrustmaster ones, preorder the virpil ones or order some from from MFG or Slaw. If money is an issue however, my advice for new starters however is get the Tflight first (you never know, you may not like the hobby after a few weeks) and if you're not doing VR, your very next upgrade should be some sort of head tracking! Fancy joysticks beyond your first HOTAS won't make nearly as much of a difference as head tracking; it cannot be understated how much of a game changer it is to be able to look around (after you get used to it at least). You can but trackIR5 if you want an off the shelf solution, but for something cheaper, try trackhat or delanclip. You can also make your own if you want.

With clickable switches and instruments? I thought of making such a thing myself, but as I was learning Java I realised that the android environment would be like learning a completely new coding language, then to top it off, I found out that since DCSbios doesn't report switch positions, I'd have to learn lua and how to interact with DCS and presumably how to make and run a server; not to mention I'd have to create all the art assets for it. At that point I just gave up.

Would it be possible to be able to switch between different things by rotating the tablet? It'd be cool if there was an option to be able to view the CDU/ UFC in portrait mode and then instantly switch to the MFCDs by rotating the tablet to landscape. I have a portable simpit setup that I can mount to my desk and it's be cool to print a rotating mount for my tablet that I could just have in front of me.

Most likely to be whatever you use as your TDC. Before I replaced it, I had a similar issue with the mouse nipple on my TMWH. Not only was it biased to one side, it would never return fully to center.

Congrats.

This should be the rest of the stuff. I've already resized it all. EDIT: I forgot to include the license so I've reuploaded the zip. Unfortunately because the knobs file are so large I had to remove the one with the sprue. FA-18_UFC_v001.zip