Smashy

Serious question: why do people like you take the time and energy to look for problems and then make snarky comments in a way that is clearly non-constructive when there are so many things about this game to learn and enjoy? It's not as if you're conducting methodical tests to provide useful feedback to ED. Instead, it's almost as if you make a conscious effort to find faults and not have any fun. Life's too short for that and I truly wonder what motivates posts like this.

One possibility is you have a modifier+axis bound to UHF volume. Did you check your axis bindings?

Brilliant list, thanks for sharing these @wilbur81! I'm adding these to my podcast playlist. I'm always excited to fly the Hornet and listening to these kinds of interviews just feed that stoke. The way internet gladiators bash on one module or another in that "my dad can beat up your dad" fashion strikes me as extremely immature. It's boring to hear Viper guys bash the Hornet or vice versa. It's a video game and meant to be fun. Sure I have my favorites (Hornet, Huey, Mustang and now the Apache is growing on me) but all the modules I own have something to offer.

Will the ability to have multiple versions still be supported once the unified release hits? I use OB (with minor mods and add-ons) as my primary but keep a clean stable install to troubleshoot and test things if I run into problems to help determine if the problem is on my end or not. It would be nice to be able to do this going forward, if not with stable at least with a previous version.

I played with this last night and you are correct. My mistake!

I'm not sure if this is the optimal solution but this fixed it for me: Edit <DCS base dir>/Mods/aircraft/Uh-1H/Cockpit/Scripts/AI/ControlPanel/g_panel_page.lua Find the following line (appx line 42): local shift_X = -0.65 Experiment with the value to position the AI crew panel to where you like. My multi-monitor configuration has a horizontal resolution of 6144 and changing this value to "-2.80" put the AI panel where I wanted it. It will get overwritten when you update/repair DCS so save it in a safe place or look for it in <DCS base dir>/_backup.### to find it again. Hope this helps.

Right on, I'm doing something very similar as well. It's an acceptable workaround but can sometimes get clumsy switching between RWS/TWS to get the bar setting changed.

Can bar scan values be cursor-bumped like range and azimuth values?

Is it easier to accurately simulate older aircraft, avionics, sensors and weapons when compared to a newer platform? For modules like the Hornet, F-15E, and Apache I imagine a lot of details are fudged over either intentionally or because reliable unclassified data sources simply aren't available. Would this be the case with the F-4E? As awesome as the Phantom looks, it's even more exciting to think HB would be delivering as accurate a sim experience as possible. Do unclassified data sources exist for a platform as old as the F-4E?

adding dxdiag.txt and dcs.log per @BIGNEWY's request. My primary problem is a constant flickering like a bad fluorescent bulb. This happens in the 2D GUI as well as in-game. Often, a faint ghost image of a previous screen can be seen while in game(i.e., grid lines from F10 map, briefing window, options page). This doesn't happen on any other games I've tried, including an older stable version of DCS. dcs.log DxDiag.txt

I'm seeing the exact same issue. The flickering is so fast and so severe, I'm grateful I don't have epilepsy. It's apparent on various 2D screens in the GUI. In game, it's also noticeable at points of high contrast (i.e., horizon line). It does not happen in an older stable version that I happened to have installed. I've also tried experimenting with various settings but nothing has helped so far. RX 6800XT (23.10.1 drivers)

Did a cleanup and slow repair but did not remove mods listed above. The pipper was still behaving erratically. Instead of trying to troubleshoot my current install piece-by-piece, I decided to go with a fresh download of the stable release and test on that. Got a freshly-downloaded stable install done, installed the Hornet and Syria, and setup a simple test against a Flanker. The pipper starts jumping around once the Flanker starts maneuvering. It's especially noticeable when the Flanker is rolling side-to-side. No mods, no changes to default except importing my HOTAS binds from my beta install. Here's the track from this test. The random guns shots were just me trying to see what the BATR cue was doing. Hornet pipper test.trk

I appreciate the look. Sorry I forgot to include version and mod info in my previous post. For anyone curious: OpenBeta 2.8.6.41363, testing in single-threaded Following files have been modified: ./Mods/aircraft/F-16C/Cockpit/Scripts/EWS/CMDS/device/CMDS_ALE47.lua ./Mods/aircraft/F-16C/Input/F-16C/joystick/default.lua ./Mods/aircraft/F-16C/Input/F-16C/keyboard/default.lua ./Mods/aircraft/FA-18C/Cockpit/Scripts/TEWS/device/CMDS_ALE47.lua ./Mods/aircraft/FA-18C/Input/FA-18C/joystick/default.lua ./Mods/aircraft/FA-18C/Input/FA-18C/keyboard/default.lua ./Mods/aircraft/Ka-50/Cockpit/Scripts/Devices_specs/UV_26.lua ./Mods/aircraft/Mi-8MTV2/Cockpit/Scripts/CargoIndicator/CargoIndicator_page.lua ./Mods/aircraft/Mi-8MTV2/Cockpit/Scripts/ControlsIndicator/ControlsIndicator_page.lua ./Mods/aircraft/P-51D/Input/P-51D/joystick/default.lua ./Mods/aircraft/P-51D/Input/P-51D/keyboard/default.lua ./Mods/aircraft/Uh-1H/Cockpit/Scripts/AI/ControlPanel/g_panel_page.lua ./Mods/aircraft/Uh-1H/Cockpit/Scripts/CargoIndicator/CargoIndicator_page.lua ./Mods/aircraft/Uh-1H/Input/UH-1H/joystick/default.lua ./Mods/aircraft/Uh-1H/Input/UH-1H/keyboard/default.lua ./Scripts/Aircrafts/_Common/Cockpit/ViewportHandling.lua ./Scripts/Speech/common_events.lua third-party mods: SRS DCS Scratchpad TacView DCS-ExportScript Helios I'll try the repair and systematically remove mods for testing. I'll report back when that's all done. Thanks again!

Is this still fixed for you? For me, the pipper still appears to follow the behavior of the foresight cue. With a lock on a maneuvering and jinking target, the pipper still jumps around like crazy. Here's a short track where I'm saddled up behind a F1. Notice how the pipper starts moving erratically as soon as the F1 starts maneuvering. Even the BATR (bullet impact) cue is affected even though I'm still straight and level. Additionally, if the radar is in SIL mode switching to guns will take the radar out of SIL mode. I'm not sure if that's working as intended or not. @BIGNEWY can you please take a look at the track? Hopefully this clearly illustrates the problem I'm seeing. If more examples are needed, lmk and I can try to provide more tracks. Thanks. Hornet pipper.trk

You can add the relevant pages to [DCS rootdir]/Mods/terrains/[mapname]/Kneeboard This works great for all maps I have except Syria. I think there's a long-standing bug that affects Syria-specific custom kneeboard pages.

@Minsky - your module and aerodrome kneeboards really are works of art. Thanks for creating and sharing these!

Resurrecting a necrothread but I was just going to dig into this file tonight to do the same thing. I'm glad I found this post before I wasted my time. The first clue was that the default values for the AIM120 in this file aren't applied to a hot or cold started Hornet. Has anyone found a way to do what OP was trying to do in the last year? I'm also hoping for a data transfer cart. Hopefully we'll see something somewhere down the road.

In some of the joystick device diff LUA files, I noticed some interesting names in the name-value pairs found there: ["hardwareDetent"] = false, ["hardwareDetentAB"] = 0, ["hardwareDetentMax"] = 0, These are in the axis section for my new rudder pedals (which don't have detents). Are these old or are they something new for upcoming device support features? Maybe VKB TECS :D?

...it sends you to the E-Shop instead of the free-to-play page. FYI.

Hey @Dscross - I'm looking at upgrading my CH Pro Pedals and the Crosswinds and Ace Collection pedals are leading the race, with Slaw a close third. Would you mind posting an update on your thoughts on these? Which one ended up being your main set? Thanks!

Found the fix. The problem was caused by differences in the default.lua files in the following locations: [DCS basedir]/Mods/aircraft/Uh-1H/Input/UH-1H/joystick [DCS basedir]/Mods/aircraft/Uh-1H/Input/UH-1H/keyboard I made some changes to [DCS basedir]/Mods/aircraft/Uh-1H/Input/UH-1H/joystick/default.lua and can now switch seats via HOTAS button assignments. Make a backup copy of this file first just in case. Find the following lines and comment them out (prepend '--' to the line). It should look like this: --{down = device_commands.Button_1, cockpit_device_id = devices.HEAD_WRAPPER, value_down = 0.0, name = _('Set Pilot Seat'), category = _('View Cockpit')}, --{down = device_commands.Button_2, cockpit_device_id = devices.HEAD_WRAPPER, value_down = 0.0, name = _('Set Operator Seat'), category = _('View Cockpit')}, --{down = device_commands.Button_3, cockpit_device_id = devices.HEAD_WRAPPER, value_down = 0.0, name = _('Set Right Gunner Seat'), category = _('View Cockpit')}, --{down = device_commands.Button_4, cockpit_device_id = devices.HEAD_WRAPPER, value_down = 0.0, name = _('Set Left Gunner Seat'), category = _('View Cockpit')}, Add the following lines: {down = iCommandViewCockpitChangeSeat, value_down = 1, name = _('Set Pilot Seat'), category = _('View Cockpit')}, {down = iCommandViewCockpitChangeSeat, value_down = 2, name = _('Set Operator Seat'), category = _('View Cockpit')}, {down = iCommandViewCockpitChangeSeat, value_down = 3, name = _('Set Left Gunner Seat'), category = _('View Cockpit')}, {down = iCommandViewCockpitChangeSeat, value_down = 4, name = _('Set Right Gunner Seat'), category = _('View Cockpit')}, The orange warnings and duplicates are also gone from the control binding page. This appears to work so far but I'm not sure if it'll break anything else or violate IC. If it works for you, save the modified files in safe place or the next update will clobber them. Alternatively, you should be able to recover them from the most recent [DCS basedir]/_backup* that gets created after an update.

Did you go with the Cosmo or Avia cams?

With the latest OB patch 2.7.18.30765, it seems I'm unable to change seats with any joystick/throttle binds. The keyboard binds work just fine. I also notice that there are now duplicate control entries for these binds. Note that the keyboard column is grayed out for one pair of duplicates and the joystick column is grayed out for the other pair. Anyone else running into the same problem?

I'm curious about this too. I've tried various things - encoder rate, virtual axis on the encoder dial but nothing really worked the way I wanted. I'm currently using one of the hats to control radar antenna elevation. You might want to post this question over at the Virpil forums. I've asked a few questions there and have had good success in getting helpful answers.

I went with the Alpha Prime and CM3 base. The only thing I liked about the MCG over the Alpha Prime was the swappable ministick and hats. I would like to have 4 hats on the stick. I did try configuring the ministick on my CM3 throttle to send button presses and that will conceivably be a suitable workaround on the Alpha. The Alpha's ergonomics did look better to me and that's important since I have medium-ish hands. I also envision the scroll wheel encoder being pretty useful in a videogame context. Finally, while it's a generalization and personal preference, I like Western HOTAS designs over their Russian counterparts and the fictional but Western-looking (IMO) Alpha did speak to me louder than the MCG or T50CM2 grips. Oh, also finally, since I already have a Virpil throttle it'll be simpler for me to learn a single management software tool vs two tools. And lastly finally, Virpil might be a better option for the US guys in terms of support with the opening of their physical store here. At least that's the hope.