shrimpy_dikdik

Thanks for the reply. I will try and keep this easy to understand if anything for my own benefit. Take two graphs, both with x and y going from -10 to 10. One is for your trim position the other for aircraft state. At take off before any torque is added both are at 0,0. You take off and enter a cruise where you have had to trim. Now the trim graph is say at 3,4 but the state graph is back at 0,0. Level trimmed flight. Now you get into a situation maybe by changing the torque and start spinning and hit the trim rest button. The trim returns to 0,0 but what about the aircraft state? Its now very different to before take off, different torque, attitude, altitude, effects on control surfaces etc. So as the trim returns to 0,0 the aircraft state might go to -6,-8 or something. Could put you in a worse situation. Cam use any numbers you want for the example it's not important, but what is is how the state of the aircraft changes when you reset trim. It could make any situation far worse. I have spring base stick and rudders, I have never used the diagram. I just control the aircraft using stick amd rudder to achieve level flight and hit force trim and recenter the stick and rudders. Works very well. If I start to spin one way I use my rudders to counter it till I'm am no longer spinning and hit and trim. I basically trim all the time. Edit: if the trim reset does not affect the aircraft state then I can see how it would benefit those that have "run out of trim" so to speak. Can't see it helping anyone get out of a hairy situation, you will still need to counter.

No I mean use your skills to get the aircraft situation to one you can comfortably fly. So if your spinning, apply rudder to counter, get your steering cue straight, get you vertical speed close to zero, ensure little roll or pitch is happening, then press and release the force trim and return your stick and rudder to center. It works very well for me, hence why I am struggling to understand this need for a "reset trim". To me that means reset the trim to nominal, as in when no forces are acting on the aircraft which you won't ever have in flight. What you describe however sounds very much like what we already have. I've never use Rctrl+enter.

I've asked this before but no one answered but what is the expected outcome of a trim reset? What state does it reset to? Scenario: your spinning around with your nose down and will likely crash soon. You hit this reset trim button. Then what? I would assume it would put the trim as if no forces are acting on the aircraft, as in before take off. But that won't help. You'll possibly spin violently either the other way or even increase you existing spin and shoot up towards the sky. You'll go from one unfortunate situation to another, possibly worse. I think some of you are expecting an auto trim button, press it and everything magically rights its self. The existing force trim can work like that, you just need to use your flying skills a little, press and release and recentre the controls (spring centering stick and rudders). It's a very simple and effective system for what I use (TM tca stick and logitech pedals).

Had this thought too. Either with myself using rockets or just concentrating on the flying and dodging whilst George mops up what is still standing with the gun. Selecting each target is both a distraction and immersion killer.

So if you find yourself in a bit of a pickle, say diving towards the ground and spinning around, you hit this theoretical trim reset. This puts the aircraft trim back to nominal right? As in when? The trim state before take off? The aircraft will be in a completely different state to when the trim was nominal. How is that supposed to help? The control surfaces will be all over the place, you could find yourself in an even worst situation. If i am wrong please someone tell me what state trim the trim resets to. If in said pickle, counter it as best you can and press and release force trim and let your controls return to centre. Might not be 100% spot on but I bet a lot easier to control, and if not spot on just force trim again.

Is it that trim and collective resets when you switch back to pilot? I've not played CP/G yet but did switch once out-of curiosity and it went into an immediate spin when I switched back.

Trim reset? So after 30 mins flying and trimming you press a trim reset to return to I assume the trim conditions at take off? How's that going to help? You will likely shoot upwards and spin all over the place. Maybe I'm missing the point and someone can explain how this would help, perhaps describe the situation it would be used. For me the current trim is working great. I take off using a bit of rudder, neutralise my attitude and vertical speed, force trim, return controls to center, lovely level flight. I turn to the direction I want, increase torque, nose down, gain speed and have to compensate with the controls for the change in aircraft situation. Aka fly the aircraft. Once I'm happy with my cruise I trim again as before and I have perfectly controlled flight with my legs and hands relaxed. For going back to hover its the same, maybe a few more trim steps added as torque control is more difficult for this.

Use the controls to neutralise the movement with both stick and rudders, press and release force trim, let controls recenter. Should now fly trimmed. Do so whenever the situation of the aircraft changes, torque, speed, attitude etc. When transitioning to hover you may need to do this several times and/or do it in stages. Expect there will still be a lot of non-trimmed flying however as the aircraft situation will change a lot during transitions.

Exactly. I retrim at every change in input. So for transitions to hover I will retrim several times as my speed, attitude and torque change. I'm by no means perfect at it, sometimes end up spinning all over the place, but it's only day 3 of owning the module.

I'm not following why everyone is having such issues with the force trim. With a self centerring device just control your stick and pedals so that there is zero or as little as possible attitude change and press the force trim. Letting the stick and pedals recenter should result in trimmed flight. It does mean you have to retrim at every change that alters the attitude, like change of torque or speed, and it will become one of the most used buttons on the aircraft.

5950x, 3090 and a G2 using vrperfkit and I can get perfectly smooth vr with steam motion smoothing. As others have said the monocle is great and gives us VR users far more immersion compared to pancake users. Only flown a few training missions and instant action and not fired the weapons yet but I'm sure the HMD targeting is an absolute joy in VR. Agree that the George menu is not located in a good place.

1. Set up controls 2. Curse that I have a TM Airbus sidestick with 16 buttons and only one hat 3. Set up voice attack 4. Fly whilst remembering the set up (VR only so cannot look to see what I did). Probably swear a lot. 5. Try to justify to my better half the parting of 400+Eur for a decent Hotas

In multiplayer this missile is no longer a threat. 30+ shots fired and 2 kills. Most (90%+) lose track within 20secs from launch, those that actually make it to the target are easily defeated. I've watched other players missiles and they loft so high that when they come down it is at such an acute angle it loses all its energy. I've seen unaware players defeat it just by simply keeping their speed and attitude and flying underneath the missile as it slows to 300kn. No need for evasive action. I fire usually at 45nm, 40k, M1.1 and 20° (less if lower). I then try and get under the targets altitude before I lose track but even then that is exactly what happens most of the time. Also it's a big sign to the enemy that you've fired when they see you dive and crank, so easy to defeat. My normal procedure is fire, watch the missile either lose track or just slow to a walking pace, turn around, flee, gain altitude, rinse, repeat, quit. The only two kills were at similar altitudes and I suspect they were asleep. I was actually not too bad a couple of weeks ago. On GS maybe 2-5 kills per sortie and usually make it back home alive, on Blueflag 1 or 2 but usually the players are a lot more switched on. I know I need to "relearn" the missile, or adjust my style, but to be honest for any multiplayer enemy that is of moderate skill and not asleep it is so simple to defeat. I have zero interest in offline play. I will continue to try and work out how to use this missile in multiplayer. If someone can explain how to not lose track about 95% of the time it would be appreciated. If it is lag (ping on GS server (Canada) 135ish) then there's not much I can do I guess.

It was on the GS server which is based in the same country as myself so ping was very low. They have changed the mission recently and that usually causes weird lag issues with aircraft bouncing all over the place. I was using the GS server to test the recent changes to the missile as there is a large supply of willing victims often without the experience to defeat the Aim 54. 10 out of 10 shots all around 35k+ with good firing situations all lost track during the first half of the flight before the radar picked them up instantly but the missile was trashed. I did go on the Blueflag Persian Gulf server yesterday and had a 1v1 with a JF 17 at around 40nm, myself at 35k he was around that or slightly lower. Not sure what missile they have but we both went pitbull at the same time (8 second till impact), I got away he didn't. I'm guessing it's most likely the mk60 had more energy than whatever they had which is exactly how I'd expect the aim 54 to behave.

Is anyone else having issues with Aim-54 in TWS mode online? I've played a fair bit online in the last year but very recently it seems every shot I do I lose track within about 10-20 seconds without the enemy doing anything special. They will immediately show up again and Jester will acquire and IFF again but the missile is wasted. And we are talking 40k 1.2M 20 degree loft shots, solo head on target at around 20k with nothing to hide behind and not notching or chaffing. The servers have shown a lot of lag recently, does this impact the track somehow? Must be the last 20 fired go this way and as mentioned I've played a lot the last year online with reasonable success.

Sorry dont know where my text went with the above images. This was the the 28nm shot with the mk60 where the missile lost a lot a speed as the F16 dived and turned 90°, from M2.0 to M0.7 in 8 secs. I am not complaining, if this is realistic then fair enough. I had a few multiplayer kills tonight from 40nm and 30k, maybe not as many as a I would have a week or two ago, but I can live with adapting my style.

Fired a mk60 at a hot F16 from 28k and 28nm traveling M1. F16 at 25k did a partial split-s at pitbull and the mk60 slowed to around M0.7 trying to dive with it. On GS server and unless it's someone very new who hasn't realised a missile is coming their way you're most likely not going to get the kill.

I used miles for the Apache. To be honest I didn't read the bit about extra miles so my fault really. After the delay announcement I contacted for a refund as I will have a major real life change later in the year so no time to learn a new module but was told as per the policy no reimbursement of used miles. For now I will keep the preorder but if it slips beyond March I will just have to take the lost miles hit and get a refund. You live and learn....

Seems to have worked for me too. From 100% 2nd mission or usually in my case 2nd spawn during multiplayer crash to none. The windows 8 compatibility mode solution also worked but increased load times and vr shaking during multiplayer menus.

I play mostly MP and I crashed every time I reselected my role following being killed, which for me is very often! Yesterday I did a DCS clean and repair, this did not fix the issue. I then tried the Windows 8 compatibility suggestion mentioned in this thread and can confirm that after several hours play in MP and multiple respawns I did not have a single crash in this way. I did have two crashes in other ways but nowhere near like the issue before, which as I said was 100% respawn or 2nd mission if playing campaign or instant action. Load times were a little longer but quick enough for it to not be an issue. Lag and performance seemed no different. Until an official fix is released I will continue to use this method unless someone suggests there's a reason not to. SteamVR has a little moan about it but that seems the only negative.