-
Posts
7942 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Everything posted by imacken
-
If you look at this thread, I think I've solved the trim transfer issue when taking control FROM George, but the collective remains a big issue. However, just to repeat what I said there re trim: "However, with regard to trim, then that can be transferred, I've just noticed. If you keep the Control Display panel open you can see what happens. When control is taken back from George, you can see where the cyclic/rudder inputs are and also your centred ones marked with the red crosses. Now, just like normal trim, if you DON'T move your control from centre and press the trim button, your controls then take on what George was set to. So, I feel that is a non issue. However, it's the collective that is the issue. Maybe, as I said above, the collective input could be held until your physical collective reaches the same point, similar to trim. Now, that could be shown as a 'ghost' level on the Controls Panel until the correct position is reached."
-
OK, I think we're going to get confused with 2 threads going on this. Maybe @BIGNEWYcould merge them, but I'll link to this in your bug thread. I'm not sure why BN keeps talking about the transfer TO George when it's the transfer FROM that is the issue. However, with regard to trim, then that can be transferred, I've just noticed. If you keep the Control Display panel open you can see what happens. When control is taken back from George, you can see where the cyclic/rudder inputs are and also your centred ones marked with the red crosses. Now, just like normal trim, if you DON'T move your control from centre and press the trim button, your controls then take on what George was set to. So, I feel that is a non issue. However, it's the collective that is the issue. Maybe, as I said above, the collective input could be held until your physical collective reaches the same point, similar to trim. Now, that could be shown as a 'ghost' level on the Controls Panel until the correct position is reached.
-
I agree with what you say, but the rudder/cyclic transfer can easily be handled in the same way that trim is. i.e. the stick/rudder are centred after trimming, so the same could (should?) happen with transferring from George. Having the ctrl-enter control panel showing demonstrates all this perfectly. I also agree that the collective is more difficult to find a solution to, for the reasons you said. Maybe the collective input from George could remain the same until your physical stick reaches that point, and then it takes control?
-
Thanks but, as I said, it doesn’t have to be going to the back, it happens when you take control from George in the front as well. Same situation there. It doesn’t matter if it’s trim or control input, there should be some transfer of George’s input to avoid the situations I describe, especially in relation to the collective. A slight touch and you can be out of control! I don’t think you can see what position that is on screen before taking control apart from seeing the %age in numbers. We surely shouldn’t have to be guessing these inputs.
-
Sorry, force of habit, yes I meant collective! it makes no sense to me that George’s collective and trim positions are not carried over when you return to the pilot seat or take control in CFG. It’s illogical and creates uncontrollable situations. If George is not used, then trim and collective settings are passed between pilot and front seat.
-
I think - as some of you have been hinting here - the problem is definitely that George trim AND throttle settings are not carried over when taking back control of the aircraft. The trim thing has been discussed here, but I haven't seen mention of the throttle issue. Say, for example, you are in flight at around 80% throttle, then drop it down to 30% (could be anything), go to George and he stabilises back to around 80%. Then go back to pilot, touch the throttle, and you'll see it go to around 30% where it was when you left. As has been suggested here, surely, when transferring from George to aircraft control (pilot or CFG) the trim and throttle levels have got to be transferred as well. Otherwise, crazy things happen.
-
I was replying to @Swift. who did want it to go to the neutral position in a reset.
-
Sure, but I don't get why anyone wold want to trim back to the neutral position anyway. If you are in a trimmed situation, surely you just want to make minor adjustments.
-
Yep, I personally can't see what use a reset button would be. I mean why would you want that dramatic change of trim?
-
You can see the inputs on the Controls Panel overlay. As I said, when you take control in CPG, you have to immediately trim up BEFORE you move the stick/rudder at all. Otherwise, the trim gets reset and that causes the spinning effect.
-
correct as-is Can't adjust HDU brightness in CP/G
imacken replied to imacken's topic in Bugs and Problems
I showed the Symbology binds as well as the Brightness ones. -
OK, so I think it's mostly related to Force Trim and taking control when in CPG. I haven't worked it out exactly, but it's something like this. Show controls panel with ctrl-enter, go into a hover to a few hundred feet, force trim. Then, go to CPG. (The first thing I see is a change of heading, but that's another issue, I think.) Looking at the controls panel, you can see that the controls are untrimmed but do have the pilot trim showing. Then, press 'request aircraft control' button. Once that is done, if you do ANY movement on the cyclic or rudders, the trim resets and the Apache goes into a spin as it has lost the left rudder trim. To resolve this, after pressing 'take aircraft control', it is necessary to press Force Trim when the controls are centred to align with the pilot levels WITHOUT making ANY movement on the controls. It's difficult to do a track as there are so many things going on with controls etc. that are not obvious.
-
BN, can I ask, do you 'Request Aircraft Control' when in CFG?
-
As this seems to be unusable at the moment, I feel we must be doing something wrong, as even in EA, I doubt if this would have slipped through.
-
correct as-is Can't adjust HDU brightness in CP/G
imacken replied to imacken's topic in Bugs and Problems
-
correct as-is Can't adjust HDU brightness in CP/G
imacken replied to imacken's topic in Bugs and Problems
-
Joystick Diagrams - Automated DCS Joystick diagrams
imacken replied to rexehuk's topic in DCS Modding
Really don’t understand your point about this forum. It’s a very active place and easier for users to find and exchange info and solutions than Discord, imo. Still, I joined your group there and I’ll drop a message over there a bit later. Thanks. -
Don, please see my post above yours to get it working manually.
-
correct as-is Can't adjust HDU brightness in CP/G
imacken replied to imacken's topic in Bugs and Problems
Got it! Thanks a lot for that. -
There is no 'VCP SYM BRT' axis command in the CP/G, so no way I can see to adjust the brightness of the display.
-
Joystick Diagrams - Automated DCS Joystick diagrams
imacken replied to rexehuk's topic in DCS Modding
Thanks for that, however, I'm getting the same situation with the new version as I did above over a year ago, as above. You said you would check this, but never came back! I just get 'No template found' even for devices that are on your list, e.g. VPC Alpha R, Total Controls MFBB. -
cannot reproduce AH-64D training mission bug.
imacken replied to KermitOG's topic in Bugs and Problems
Stated as a known issue on release. -
It works if you manually put the files into the folder I mentioned above.
-
Yep, same here. In fact, my app crashes when I try to do anything AH-64 related. Have to resort to the manual method!
-
Sadly, not including the long awaited missing kneeboard fix.