Scofflaw

I think this might be the solution. I noticed yesterday if I had the right throttle a bit looser than the left, it would push into the afterburner detent a tiny bit more than the left. This problem is not catastrophic or anything, but it can get a bit annoying in some aircraft. It can cause a very slight but noticeable roll to the left in the hornet at certain throttle settings, and while flying the A320 in MSFS, the autothrust detents don't always line up. Again, not a big deal, but just a matter of convenience. I'm curious - do the throttles axes line up perfectly for everyone else while using the sync lock?

I had to remove & reinstall SimApp three times to get the vibrations working. I was playing with all the settings every time, so it's possible I only got the settings correct on the third try. As Zeufman mentioned, launch SimApp, then hit the cogwheel in the upper right next to the logout button. You want to make sure you have the correct version of DCS selected, with the correct folders set. Can't tell you which to select, since it'll depend on your setup. Here's mine, but I have DCS OpenBeta installed by itself on a separate drive:

Yeah, ran through the calibration several times. I did more testing, and I think the issue I'm having is that the right throttle is a tiny bit more forward when they're synced together. Admittedly, I was quite excited when I assembled it all, so I'll take it apart later today to see if I may have missed something, or over/under-tightened a fastener.

I'm not sure if anyone else has had to deal with this issue. I just received my Orion 2 throttle, finger lifts, and F15EX grips today. I noticed when I have the sync lock in place, the two throttles aren't at the same position. It's not a huge amount, but noticeable enough to cause issues with trying to maintain level flight in a few aircraft I've tested. I checked every fastener, and everything is tight with no play. I tried running through the calibration, but the issue seems to be more of a misalignment of the two throttles. I also noticed when I push both sticks to the AB detent, the right stick is a little further ahead than the left. Again, everything looks straight and kosher, but I think I may need to adjust something. I'm going to keep working on this, but has anyone had to deal with something similar? This is what I see when I have both throttles synced with the lock:

Are you talking about this site? https://winwingsim.com/view/simapppro.html I'm not having any issues with it.

It definitely takes a lot of practice though. I've probably done more damage to ground units with sling loads than bombs.

I've noticed oscillations during aerial refueling. I'm fairly certain in my case it's PIO - I'll be a bit low, adjust to come up a bit, then notice I'm coming up too fast, so I adjust down, and end up doing a sine-wave dance below the tanker. I fly the F14, 15, 16, and 18 regularly, and this is the only aircraft where I experience this. Not sure if this will help you, but sometimes to rule out control issues, I'll put some exaggerated curves to see if the issue goes away. If it does, I adjust the curve, if not, I look elsewhere.

My work schedule is way too unpredictable to commit to any multiplayer, so Jester it is. The only time I struggle with him is with A2A combat. I'm not proficient at controling him with the wheel at all, and it shows during combat.

This one is already in my top modules. I'm enjoying it way more than I thought I would. It's quite effective at every role I enjoy - the long legs & huge quantity of armaments it carries makes for enjoyable long missions. I think the devs need to be commended for releasing an EA product with most of the major features working. Small things like TACAN, ILS, lights, etc. really go a long way in helping us forget it's EA. Looking forward to seeing how this aircraft develops with future releases.

I really disliked the F14 when it first came out; it felt like the Wright Flyer after spending so much time in the FA18. After forcing myself to spend some time with the tomcat, it really grew on me. It's one of my favorite modules today, so I don't rely on my first impressions anymore. I do find we are reaching a point in DCS where modules are starting to overlap, but that's not complaint. I enjoy flying the same mission in different jets to see how it plays out differently. Aside from naval operations, the F14, F15, F16, and FA18 can mostly accomplish the same things, so it's a matter of taste at this point. Having more options is always a good thing.

I find the F15 to be the easiest of the non-carrier aircraft to land. Just have to avoid landing fully loaded, much like any other plane in DCS.

I noticed sometimes I can break the autopilot altitude functions. It tends to happen when I'm fighting with it, and at one point the autopilot will refuse to enable any kind of altitude hold function. I'll have to try to replicate it to see if I'm doing something wrong.

I understand what you mean - I find myself using the helmet visor (left shift + N) for every daytime mission in the F15. The F16 canopy seems to provide quite a lot of sun protection compared to the F15, and the FA18 seems to be somewhere between the two. I only tested the Syria and PG maps, but sometimes without the visor I can hardly see anything. I'll try to take screenshots later.

Can you include a picture/screenshot? What resolution are you running?

Salut, I just tested it, and had no issues. Are you sure you pressed the space bar to "start" the mission after entering the data?

Funny, I thought this was a bug. I personally hate it - I play DCS on a 43" 4k screen on my desk, and now this menu is about 2'x3'. I'm staring at a 6 square foot spreadsheet every time I try to change some controls. I'm probably in the minority with my setup, so I'll just deal with it.

Possible, but I doubt it. My water-cooled 10900k is overclocked to 5.2GHz on all 10 cores. Aside from benchmarks, I've never had any game or application push my CPU anywhere near 100%. I can do a stable 5.3ghz, but it'll start to hit gnarly temps when I do that. The only major improvement I could do on this setup is go from 32 to 64GB of RAM, but I was saving that for my next build.

I'm running an i9 10900k and went from a 3090 to a 4090, on a 4k 120hz panel. In DCS, there was no noticeable improvement so far. I tried a bunch of games, and went into the settings to try to max them out, but I noticed they were already maxed out. Some games did show improvements - RDR2 is much better, MSFS is hard to tell but seems better, the battlefield games already ran great on the 3090. One improvement I noticed for sure is noise. I was running an EVGA XC3 3090, and it used to get really loud. My MSI 4090 fans are set to auto, and they haven't gone over 30% yet. It pumps out a lot of heat, but the cooler is really efficient. I'd really hope so, given the insane size. I had to literally cut holes in my case and mount internal case fans on the outside to fit the thing in. It's gigantic.

In DCS, the initial pitch trim range is a bit sensitive but slows down. What this means is that pitching up/down from neutral trim will be pretty aggressive at first. The roll trim seems steady in its entire range. I'm not sure what you mean by "autotrim a little slow on approach", as far as I understand it, the aircraft tries to maintain 1G, but you can maintain 1G at all kinds of different AOAs. If you hit RCTRL+ENTER, you will see your trim settings, and the above statements will make more sense.

I managed to get an order in for a 4090 before they sold out - it's arriving next week. I'm already running DCS pretty maxed out on my 3090, so we'll see what difference this makes.

I have a 3090, and run 4k @ 120hz, and I probably wouldn't upgrade if DCS was the only game I played. That being said, if the leaked benchmarks are accurate, I'll probably pick one up. I spend at least 8-12 hours every day on my computer for both work and fun combined, so I don't mind spending money on my system.

Apologies, I never saw this reply. Nice find! I was trying to get it working again today, and reached the same conclusion as you, but I set "ExportScript.Config.Listener = false" in the main config.lua. This does exactly what you say - you get functional switch status from the sim, but the streamdeck cannot send data to the sim. This is probably oversimplified, but I originally thought maybe this script was pulling too much data from DCS, but this suggests the issue might be the streamdeck -> sim communication. I'm going to keep looking as well; I really want to get this plugin working. edit - In DCS-ExportScript\lib\Tools.lua, line 48, try changing the value from (.001) to (.000): ExportScript.socket.try(ExportScript.UDPListener:settimeout(.000)) So far, this has fixed my stuttering. Unfortunately, I only setup 1 switch on my streamdeck for testing purposes, so I'm not sure if this breaks anything. I'm going to do further testing tonight and see if this is an actual long term solution.

Quoting myself to eat my words. I read through the manual, and realized the SAS and CAS systems are trying to help me fly smoother, but I wasn't aware I was enabling/disabling different modes based on my application of the force trim button/cyclic/collective. Lesson learned - I shouldn't say I don't understand something if I haven't read the manual.

Speaking strictly for myself, I feel like I can get the hind to do what I want it to do, whereas I feel like I'm constantly fighting with the Apache to even get it to go in a straight line. I can complete a mission in either one, but if you were to watch my Apache replays, you would probably assume I'm flying drunk. I think the Apache is the only module where I don't really understand what the stability/AP systems are trying to accomplish. Sometimes while fighting with it I'll go hands off and just let the aircraft show me what it wants to do, and it'll always do something I can't explain. edit - to be clear, I'm criticizing my ability to understand the Apache, not the module itself.

When you say wobble, what do you mean? The reason I ask, is that almost no matter how I trim, I cannot establish a fixed heading. It almost always starts to bank to one side or the other. I use the attitude hold to work around this, but I was wondering if it was just a lack of practice on my end. In regard to the difficulty, I own all the helicopter modules, and this is the only one that hasn't clicked with me yet. When I crash any other helicopter, I usually know what I did wrong, but not with this one yet. I definitely need more practice, and enjoy the process, so I'm not complaining. It took me a long time to figure out the black shark, and the mi8 took even longer. They both feel easy to fly now, so I'm hoping the Apache will too one day.