Floyd1212

The code in your snip doesn't really match the code in my snip, so I'm not sure what you were using for your starting point before editing. Your code is referencing a variable control_pos_offset that you don't have defined anywhere (that I can see). In my code snip, that variable is defined locally on line 34, but I don't see that line in your snip. I haven't taken the time to fully understand all the math that is going on in this code, but my assumption was that it finds your "main viewport" and places the UI objects relative to the center of that screen; meaning it should work universally, regardless of your specific multi-display orientation. But I could be wrong. It just occurred to me, looking at that block of code, that none of it runs if it can't find viewport "GU_MAIN_VIEWPORT". Do you have this last line present in your CustomMonitor.lua file? Beyond that, I'm afraid I am out of ideas...

Try "AH-64D_BLK_II"

I guess it really depends on what your actual problem is. If the problem is that the George interface is not showing up in the corners of your primary display, this is the fix: And this is my PrestonAI_page_common.lua file, which is working for me: PrestonAI_page_common.lua

There are examples directly above in this thread. ED, can you mention this to the devs, again?

Thanks for the feedback. I did not add any friendly air patrols or attack helos that take off from friendly airfields. I can see how that might be helpful if you are playing it solo, though. I was mostly playing it with a small group of friends and we were often 2 Apaches and 1 Warthog. Maybe I will go back and add some additional AI help. Even if they aren't super effective, they also add the immersion, like you mentioned. I think the friendly CAP that you call in with the comms menu are getting distracted and drawn into dangerous territory. That being said, if you are just getting started, it is all dangerous territory. There is definitely some fine-tuning that could be done there, and I probably have them pushing too far the way they are setup right now, but I also think the smaller area has something to do with it. When they get shot down, I just call in another patrol. If I go back and make changes, I will be sure to post the new version here.

I can confirm this still happens to me as well.

Well, for one thing, if the Collective channel becomes saturated (as it often does) it may mean that the SAS can no longer keep the helo from falling out of the sky. This is useful when you have your head buried in the F10 map, but I'm sure it is unlikely a real Apache pilot would be in that situation.

Yes. When you correct those three errors, it shows up in the list. When DCS starts up, it sees those files in the folder and reads them. It gets to the mistakes towards the end of your file, which invalidates the whole thing, and it just skips the file and keeps going. You don't need Sublime Text to make the changes required, I was merely suggesting it if you think you will be doing a lot of .lua editing in the future.

You need to be very careful with your syntax. It can help if you use an editor like Sublime Text (or others) that are aware of the language you are using, and can help with coloring the syntax to help spot issues. You are missing two "=" on those last two exports, and one of your curly braces is backwards.

and the one that shows up as an eligible monitor profile is working now?

So, can you edit one of the ones that do show up in the list, instead of trying to create your own? Just change the contents of the file to suit your monitor layout.

Maybe the problem is just with the way the Controls Indicator is showing the symbology, and the actual Trim functions are working properly in the aircraft? When you are in forward flight with the nose pitched down, and the press and release FTR, then release your joystick to center, does the aircraft stay nose-down, or does it pitch up to be level again?

It's kind of funny to see different people's reactions after each patch, when we really have no idea if ED made any changes whatsoever to the FM in any given patch. I think the key is that if you fly it exclusively, and frequently, you will adapt and get used to it. If you go off and fly something else, then come back to it after being away for a couple weeks, I would think it would take some time to get back in the groove.

Question: Can we now have a pair (left and right) of MFD bezels in our Helios profile that directs the button presses to the correct MFD based on which seat we are occupying, or was that fix in a recent patch only to have the correct display export track the correct seat? In other words, do I still need to have a pair of bezels defined for the PLT, and a different pair defined for the CPG, and one is hidden while the other is displayed?

@Derbroomaster I would go back and check the syntax of your DCS Apache.lua file compared to others people have posted. I'm seeing a semicolon after the description line that may be tripping something up. Start by taking the Helios.lua file that works, and simply change its name. Test. Then change another line. Test. Etc.

Right, I think they are related in that a button press by the CPG can toggle a setting seen by the PLT, instead of actually synchronizing the intent of the button press. Maybe not "related" so much as another example of similar behavior happening out of sync between the PLT and CPG.

I have also seen this bug recently where as PLT I am unable to set a DIR TO, either by cursor selecting the WP, or by typing "W12" into the keyboard. This was while the CPG was in the aircraft, but it's possible he had previously disconnected and then rejoined again mid-flight.

There used to be a related bug when the CPG would join the aircraft after it was already started, and would then go to enable the laser on the WPN > UTIL page at L6, and this would enable NOE for the pilot, which is also at L6 of a different page. Not sure if this bug still exists, as I have been flying missions with "hot" aircraft recently to avoid these kinds of things.

Outstanding!

You should be able to start into a cold/dark Apache on the Instant Action missions, simply flip the battery on (and nothing else), and see the trim functions working properly on the Control Indicator. If this isn't working for you, not sure what the resolution is, but it sounds like a fundamental problem with your setup.

What do you mean by "deployable"? You can click on it and move it or something?

Post a short track file please, so others can hop in and take a look. My guess is that you have something going on with the setup of the aircraft, or your control binds. Lots of people complaining that the FM doesn't suit them, but no one is complaining that the FTR command stopped working.

You should take some time to look through the other posts in the Bugs forum, as a lot of the things you are noticing have been discussed already.

I think you will need to do a better job of describing your issue, as what you have said does not make much sense. With Central Position Trimmer mode: Move your joystick to the desired position and press and release the Force Trim Release (Up) to "trim" the controls to that position Release your joystick so it re-centers itself. You will notice the helo continues as though you were still holding that position on the cyclic. Make further adjustments to the flight controls with your joystick and press and release the FTR button. Carry on like this as long as you wish. If you want to cancel all trim settings, use the "cheater" command that was added later called Trim Reset.

I think this has more to do with what George is doing in the front seat. He was recently changed so that he doesn’t safe the aircraft between hellfire engagements, so my guess is he is keeping the aircraft armed for his needs. Try setting him to guns as well, or even switching off the George AI interface, then try to safe the aircraft.