GregP

Sorry for the late reply. To turn off admin, just right click on the DCS.exe, go to properties, then compatibility tab, and make sure 'run this program as an administrator' is unchecked.

Just wanted to say thank you for such an amazingly simple tool. I've been a DCS fan since the early days and could never wrap my mind around how to properly set the user curve to get the afterburner detent working. Using your tool, I was able to get it done in just a few minutes. Really great work, thank you for making this available to us all!

Possibly not! I just came across that suggestion in Casmo's video about the AP too, and I don't recall whether I changed power, but I'll try that next flight.

I can get the AP alt hold to work, but not alt select; I've tried as many combinations and orders of options as I can think of and nothing will force the plane to climb or descent to my selected altitude. Hopefully AP functionality is still WIP?

I had a similar issue but slightly different solution recently: MT load times were very slow compared to non-MT, and then I remembered a while back I'd used the ParkControl utility to disable core parking on all my i9-12900k's cores. I set the cores back to default and my MT load times now are the same or faster than non-MT. Might be worth trying if anyone else is having issues with MT and have used an app to mess with core management before.

Six months later and I finally solved it! Actually I put DCS aside for several months and just came back to it, and this problem continued to bug me, so I kept at it. Initially the different folder structure of the F-15E compared to say, the F-16C and F/A-18C, which had known solutions to the same problem, confused me, as I was trawling through several LUA files trying to find the same parameters. But then finally today I found the very simple solution, which actually is the same fix that the F-16 and F-18 use - I hadn't realized the F-15E has the same file: you have to edit the Display_StrokeDefs.lua file in X:\DCS World OpenBeta\Mods\aircraft\F-15E\Cockpit\Displays\. Default vaules are: stroke_thickness = 0.6 stroke_fuziness = 0.4 Which I changed to 0.2 and 0.4, respectively, which looks good on my 7680x2160 resolution. Hope this helps somebody else too!

I too really like the idea of a more Cold War-esque setting for the Apache. Did you make any progress exploring the mission editor?

I run a 32:9 resolution (7680x2160) and the HUD font becomes way too thick and fuzzy when zoomed out a 'normal' distance - attached is a cropped image of what it looks like. In other modules like the F-16 and F-18, lua files can be modified to improve the look of the font and make it less thick, but I haven't yet been able to find something similar in the F-15E's files. Has anyone else had any luck if they've noticed the same issue?

Anyone figured out how to do same with the F-15E? Seems to depend on FOV and on my setup with a wide FOV the default font is so thick it's almost hard to read. I poked around the relevant lua files but they seem to be quite a bit different from those for the F-16 and F-18.

Lots of great input here, guys, so thank you for the replies. I've been flight simming for 35 years and I suppose the overwhelming majority of that has been in either FBW or civilian aircraft where you can generally trim things out quite easily and fly hands-off in level flight for more than a few seconds without things getting out of hand. But it makes sense that the Tomcat is simply a different kind of beast and trim doesn't serve the same purpose as in those other aircraft. Luckily the complexity of the flying is one of the things that I love about the F-14 so no problem there! The trim acting this way just didn't seem intuitive to me at first.

Well PIO may have been an exaggeration; but my point was I feel like I'm constantly chasing the trim around - I get nearly stable with, say, slight back stick pressure required, so I do a single trim up press. This then eventually puts me into a slight climb, so I try to cancel it out with a single trim down press - but this then puts me into a slight descent, so I try to cancel it out, and on and on and on. It seems like I never get perfectly level without constantly needing to correct. And so yes, I realize this isn't a FBW aircraft, but from experience with other simulated aircraft, I highly suspect that if the trim increment was about half what it currently is, that single trim press would likely get me right where I'd want to be.

The wings would move in this situation, why? That seems odd to me. Either way though, the specific situation I'm trying to solve here is a constant airspeed level flight, so the wings most definitely would not be moving during that time and should not upset the balance at all. This is exactly my point. I would imagine that in the real plane, the pitch trim has adequate sensitivity per press of the trim hat switch button, that it would be a fairly simple matter to completely trim out the stick forces during a constant air speed level flight situation. But what I'm seeing on my end, across several different joysticks over the years, is that each press of the trim hat switch changes the trim position an amount that is larger than what I generally need, thus inducing a PIO type of situation. On other aircraft, lua file changes have allowed us to, say, reduce the pitch trim increment by 50%, and It's been a great improvement. But it doesn't seem like such a change is possible with the F 14, at least upon my cursory look through some of the lua files.

Also, we should acknowledge that level flight is only one condition in which a pilot may want to use trim. The point of a trim system is to allow the pilot to eliminate stick forces while holding any attitude they desire, obviously assuming that airspeed etc. remains constant. So the pitch trim system should allow me to hold a climb, descent, or level flight. I think it's confusing the issue to simply say that trim is not supposed to be autopilot; it's two different situations.

No, I'm not saying it should allow perfect hands off flight for a long period, I'm saying that it should at least allow a degree of control that does let you trim out stick forces such that you can take your hands off the controls for a few seconds, and have the plane maintain level flight during that time. Are you suggesting that on the real aircraft, the trim function is not supposed to do this? Its function is to simply reduce stick forces without being able to easily eliminate them? If so, this operates different to pretty much every other aircraft in the world, I would think.

Sure, but presumably the designers of the Tomcat came up with a system that actually works as opposed to what we have in the sim at the moment. Why have a trim system if it doesn't actually allow you to trim out the stick force?

Coming back to the Tomcat after quite a bit of time away, I was reminded of how frustrating it is to constantly be chasing the pitch trim around since the increment per button press seems way too coarse. There are solutions floating around here for several other aircraft that involve modifying the joystick default.lua file, but the F-14 is missing the relevant entries to do so. Has anyone come up with a solution to this over the past four years?

Brand new in box Loupedeck Live custom button/dial console. My original LL was defective and so I got a replacement, but I’ve decided to sell it rather than keep it. New LLs sell for $270 (plus tax) online. Selling for $250 with free shipping, but within the US only. Using Wombat778's utility I was able to set mine up as an F-16 ICP pretty quickly, for example:

I've used DCS UFC in the past but stopped about a year ago. Today I've tried it again and I cannot get the MFDs to register any button presses. I'm using 3 Android tablets - one for each of the F-16's left MFD, right MFD and ICP. All three can control the ICP without any issues, but none of the 3 can control any MFD, even after I select from the 'left / right / center' option in the middle. Has anyone else had any issues getting the MFDs to work recently?

Thank you! The new download solved it, looks great, such an improvement in readability.

This looks great, but can you explain exactly how to darken the map? I'm not familiar with which of the four values need to be changed; I figured it was the fourth, as maybe it was an alpha channel, but it didn't seem to have any effect.

This works perfectly, thank you!! In just a few minutes I got an F-16 ICP set up using your plugin. Really nice job.

Thanks - yes, turned out I was on stable without having even realized it; I'd uninstalled DCS a few months ago and when I recently re-installed it, must've forgotten to do the Open Beta version. Still though, the '@openbeta' option refused to work for me, but worked when I specifically used '2.8.0.32066@openbeta'.

So did this fix it for you? I'm still getting the same "2.7.18...' is up to date" message no matter what I try.

Bought new in February but only used a few hours. Perfect condition with no problems at all. Goes for $443 shipped from the WinWing website site; I'm selling for $375 which includes free shipping within the US.

Sold!