Scott-S6

If there's no adapter then modify the mount for the base - angle the grip and base forward. That's much easier to do.

That's fair but you said "materials" rather than "components".

I got it for max versatility but the alpha would be a close second. Increasing the glass mix by 10% would absolutely not double the price. I think they are just being overly cautious about mould life.

OP wants to have all audio go to his headset and all audio to go to the buttkicker. There is no combination of options you can select to do that.

I do find it a bit annoying that they don't function without the app though. For what they cost they ought to be smart enough to have a config pushed to them and then operate autonomously (like virpil or realsimulator controls do).

We're definitely on the same page there - physical controls, no keyboard and no clicking the virtual cockpit. In my pic above you can (just) see 3x streamdeck XLs. Between that and all of the physical switches/buttons in my pit I can run everthing and rapidly switch between aircraft. This is what my Viper profile looks like.

There's a right way and way that routinely breaks itself... But seriously, a lot of the people needing help with exports are using helios or simapp (especially simapp, it's rubbish) and that's what's causing the problem. It's an okay stop gap if you're not comfortable with the lua edits but there's really nothing difficult about lua edits or working out viewport locations. You'll very likely end up doing that sooner or later anyway so, personally, I'd say learn how to do viewport exports natively and just use Helios for drawing gauges. Then when Helios gets abandoned (again) or you get fed up of the odd performance issues it causes you can ditch it and your viewports will still work just fine.

The two MFDs and the EHSI have viewports configured already (if you want to display the EHSI then go straight to step two and add a viewport called "EHSI" to your monitor file). For any others, you need to add a viewport export to the instrument and then add that viewport to your monitor file. Here's how you do it (and the same method works on lots of other instruments that are a 2D display - doesn't work on 3D stuff like gauges). Remember to backup these files before you edit them in case you screw up and can't figure out what you've done wrong. First you find the indicator file for the instrument. In this case it is: DCS World\Mods\aircraft\F-16C\Cockpit\Scripts\EWS\RWR\indicator\RWR_ALR56_init.lua You need to add two lines to create a viewport. You can name it whatever you want but mine is called F16_RWR dofile(LockOn_Options.common_script_path.."ViewportHandling.lua") try_find_assigned_viewport("F16_RWR") Keep a note of these details as you'll need to do this again if you install an update. If you play multiplayer then be aware that this will cause you to fail an integrity check, no way around that. Then you go to your monitor file in DCS World\Config\MonitorSetup\whatever_yours_is_called.lua (in the DCS config menu you can see the name of your monitor config file) and define where you want this viewport to be displayed. Use the same name you used in the previous step and adjust the XY position (remember the top left corner of a box drawn around all of your monitors is 0,0 and the point you define is the top left corner of the viewport) and size. These are my numbers and name, yours might be completely different. --F16 RWR on center screen - working F16_RWR = { x = 2710; y = 890; width = 500; height = 500; } The first line which starts "--" is a comment - this is me reminding myself what it is, which screen it's on and whether I've finished adjusting it. Once it's where I want it I add the "working" suffix. You don't need to have this comment line at all but it's a useful thing to have when you come back to it later and can't remember what you were doing, especially if you get part way through setting something up. Do note, the RWR export is just the stuff that's drawn on the screen in green - it does not include the fixed lines and circles which are part of the 3D model. If you want those you'll need to have something draw them (helios can do this, for example). Because of this, it's blank if the RWR is turned off or not detecting anything. Therefore, be sure to find a mission where you immediately have a bunch of radar sources around you to jump into to test the size and position. The other one you might want is the DED. That's in DCS World\Mods\aircraft\F-16C\Cockpit\Scripts\Displays\DED\indicator\DED_init.lua And remember to share a pic of your setup!

Re IC issues - exporting any of the displays that don't have a viewport configured by default will cause an IC error regardless of whether it's done manually, by Helios or by simapp since they all do exactly the same thing in regards to viewports. In the viper the two MFDs and the EHSI have pre-configured viewports and you simply need to add them to the monitor file - no IC implications. The RWR, DED and other indicators exportable as a viewport require you to edit the indicator to create a viewport and this will cause an IC fail no matter how you do it (since all three methods involve editing that indicator file) unless ED change the IC at some point in the future. While I find Helios to be troublesome in a variety of ways and avoid using it wherever possible, IC check fails are not a Helios (or simapp) failing, they are unavoidable if you create a viewport for an instrument that doesn't have one configured by default.

A few things. First, you don't need an application to export MFDs. Both Helios and Simapp cause more problems than they solve for MFD exporting, imo. Setup your viewport file properly and stop using them for that. Helios has nothing to do with the exported MFDs, EHSI or DED in the pic - all done simply by configuring the viewport file properly. You can't export a piece of the cockpit like you're asking to do. What you can do is use an app like Helios to draw the gauges you want in the arrangement you want. It's not difficult at all. (the gauges aren't working in my pic because I no longer use them and have removed the helios interface, I still had the profile around though) I would suggest considering if those gauges are actually useful to export. If they're strictly for eyecandy then fine but I have found that a large RWR is much more useful in the Viper and that's how I use the center screen in that aircraft.

It's a standard joystick device, it'll work with anything. The build quality isn't great, especially considering the cost.

Quick update to say that this solution is still working great two years on. No issues with the longevity of the 555 board, relay or mag switch. Also, updated handle pic.

My guess would be that he's talking about cheat software which grabs memory and exports it to another PC for processing (this is how people get a map showing other players in FPS games, for example). This software can also send input device activations (to automatically fire as your sights align, for example) Something like this could potentially be a solution to our cockpit offload problem. I have no idea which ones offer a devkit so that you can create your own integrations. We also definitely don't want people using them to cheat in multiplayer so we end up with some terrible anti-cheat getting implemented.

I have pedals that use rails with linear bearing skates and have been using them for several years. No problems whatever with sticktion due to dust, etc - linear bearing skates have wipers built in. If I disengage the springs I can make them run end to end with a tap of a finger. If this was a problem they wouldn't be ubiquitous in machine tools. Also, consider that they don't run on the upper surface of the rail - they run on the v-grooves in the side - so debris on the top of the rail doesn't affect anything. If it did become a problem (unlikely) all he would have to do is add some brushes to the opening in the top of the case. My case is completely open and has no issues.

You should ask in the home cockpit forum, this one is for products from the RealSimulator company. You can get fairly inexpensive 25" ultra wide screens. They're approximately 24x11. Not touchscreens and not curved though. With a quick look I don't see any 22-23" ultra wide touch screens, yet alone curved ones. I notice that the the viperwing F35 pit doesn't haven't a curved display... Iiyama have a 20x10 touchscreen. A little pricey. TF2215MC-B2

Yes and no. If you just rotate it 180 then the down position will be well below horizontal and the up position will be approximately horizontal. It needs to be rotated less than 180. Also, if you have the version with throttle then you have additional issues.

I mean, you can reverse it but then it it'll be moving from angled down up to horizontal. You'll have to build an angle into your mount and if you could do that you'd have just made a mount.

Yep, Falcon Matters were very clear on this recently. They've also made their CAD files available.

Fun! This should help.

In which aircraft?

I had the correct screw but incorrect nut...

Where is your camera relative to you? Can we get a side shot of your setup with seat and camera visible?

Just tried locking to 60 and 70 fps. Each was tested with gsync, screen set to 60hz and screen set to 144hz. Saw no difference in head tracking. Trackir 5 (real one, not a Chinese clone) with trackclip pro.

This is the correct solution. It will work lose again though so I went ahead and epoxy bedded the tailpipe (a replacement steel one) into the grip.

No, slide switches slide, not rock like a hat switch. These are under trim switches. There are two ways in there as well.