dotChuckles

Ok. I think I know what causes this. Is everyone with this problem got rudder pedals that don't return to centre like real anti torque pedals? Because I can 100% replicate the issue if my rudder pedals are centred. Centred normal start, not centred hung start.

Ok. I think I know what causes it. Is everyone with this problem got rudder pedals that don't return to centre like real anti torque pedals? Because I can 100% replicate the issue if my rudder pedals are centred. Centred normal start, not centred hung start.

The weird thing is that it all works fine for ages and then suddenly it doesn't. Been starting up all grand and then after a while, hung start doing everything exactly the same. It makes no sense. It's not the collective thing for me either. I've verified in the control window and physically.

Thank you Sir. I will look into this. Seems like a good solution.

However there is an option to disable that in the special tab. Seems an oversight if it doesn't include the OFF/IDLE gate. But hey ho. Not going to die on a hill over it.

It would seem that I can't move out of OFF into IDLE with a physical axis and have to use a keybind. I have a Virpil CM3 with detents. So with the option to automatically lift the finger lifts set in the special tab, should I not be able to push the levers out of detent? Am I doing something wrong or misunderstanding, or is this a mistake?

How do you contact a moderator to have this topic moved back? This is not a Wishlist item request, I am asking a question about a feature standard to other modules that doesn't appear in to be implemented. Could the mod that took the effort to move this to a low traffic part of the forum also take the effort to answer the question?

I noticed in the HDU video, that there were no options for left/right/both eye in VR. I am left eye dominant, and have degraded eyesight in my right eye. When I view stereoscopic images it's fine, as my left eye compensates. However if I'm only getting the image to the right eye it won't. Every other module has this and it works. Is this function just not done yet, or do you intent to release like that? Thanks dC

The yaw on take off is one thing but the constant roll to the left with certain symmetric stores loadouts is another. Don't want that to get lost in this debate.

I'm going to second the people who are saying the tanks might be the problem. Using the instant action takeoff mission (TCTS pod is not loaded). Takeoff the roll to the left is present. Reset the mission and remove the tanks, aircraft is rock solid stable and maintains hands off straight and level. Although it is possible that the TCTS pod is also doing it, I didn't test for that. In both tracks I take off and turn towards way-point 1 and stabilize the aircraft. In the track with the tanks present I have to make two attitude corrections by the time I reach the lake. With no tanks it's stable. The roll is very slight but it is there with the tanks and not when you remove them. tanks roll left.trk no tanks no roll left.trk

Yup, having the exact same issue. Having to trim all the time. Thought the aircraft was supposed to be always "in trim". And usually it's always a left roll too.

A little yes lol... I just find the mechanical nature of it pleasing.

Haha! sadly true. I can still do a good few of those in my head. Always good as a confidence check though. 1:60 and drift rules are particularly handy still in sim flying. I've even been known to break out my CRP whizzwheel every now and then... just for fun :lol: And you're probably on the money about the busting the MMo as well as the ATC in the F-18 can't hold above mil power so you can't really get above M1.0 Like I said in my edit above... and I am totally guessing here, but I think TAS would offer you less granularity (if i'm using that word correctly) in coordinating with other aircraft, think formation flying here. The difference between say M.88 and M.89 is larger then one unit of TAS. But I'm totally guessing with that. Maybe a military flyer could offer insight? It's not the first time I've seen TAS referenced in military flying, so they proably have a good reason for choosing it over mach.

Except for, wind vectors, fuel use calculations, or anything involving movement through the air mass... which is my I said. "Mental math rules of thumb" and Mach is just a function of True Airspeed :-) Edit: Stab in the dark... but I would think that the use of TAS gives you less granularity then the mach number to two decimal places perhaps? Making a couple of things easier in co-coordinating between other aircraft. Just guessing though. It's not the first time I've seen TAS referenced in military flying as opposed to civilian.

IIRC correctly this would be the same as A/T mode on airliners after changeover speed or above ATC speed restriction level. Edit: Some of the features we should be getting are actually very similar to Boeing airliner FCS pages. Top of climb best cruise and climb performance calculators and all that good stuff if you're used to flying tubeliners. An IAS hold would be more like a combat auto throttle which would hold an airspeed to give you wing performance. The F-18 (if my reading of the NATOPS is correct) only gives you Cruise and Powered Approach mode. In cruise though you'd want TAS to be able to do your rules of thumb mental math for navigation with IAS being relatively useless for that at altitude.

Your air nav calcs are done with TAS which is probably why it's done that way. In PA mode it holds your AoA as which is kind of IAS (sort of) From the NATOPS: 2.1.2.2 ATC Cruise Mode. The ATC cruise mode is engaged by pressing and releasing the ATC button on the left throttle with the FLAP switch in AUTO. When ATC is engaged in the cruise mode, the existing airspeed is used by the flight control computer to modulate engine thrust to maintain this existing airspeed. The existing airspeed is the airspeed being sent from the ADC to the flight control computers via the mission computers. An ADC failure inhibits the ATC cruise mode of operation. The FCC uses true airspeed from ADC via the mission computers at the time of engagement to generate a command signal. This signal is then used as a reference to generate an error signal that drives the engine mounted throttle control units. Normal disengagement is accomplished by pressing the ATC button or applying and holding force to either throttle. Automatic disengagement occurs for the following reasons: Flaps HALF or FULL ATC button fails FCES channel 2 or 4 fails FCS reversion to MECH or to DEL in any axis Left and right throttle angles differ by more than 10° for more than 1 second ADC true airspeed failure ADC degrade Any internal system failure

True airspeed not IAS. Freaked me out when I couldn't figure out why my IAS was dropping as I was in the climb at first. Then I realised it was holding my TAS.

So the other suggestions are totally valid, and a lot of this comes down to your equipment. I would say you want to use the central position trimming mode if you have any kind of spring. That way when you trim and return to center you have no forces acting on the stick at all, which is how it would feel in the real machine. In reality what trimming would do is engage a magnetic brake to remove the forces from the stick. When you are trimmed you should be able to move the stick with finger tip pressure. Now unless you have force feedback or no springs at all or a stick that has equal force throughout the range you will need to center it after trimming. With center trim mode, the stick input is switched off until you recenter the stick, as opposed to the default mode which just waits a short while and then re-enables the controls. I find the center trim function to be better as the time the default mode waits is pretty short and I might not have centered the stick fully leading to a bump in the pitch or roll of the helo as the controls "turn back on". However center position mode can be fiddly if you have weak springs that don't let you feel where the exact center of the stick is. Ultimately, what ever works for you and lets you trim properly and not have to apply constant force. Having to apply constant force it what will make for poor control. Your mileage may vary though.

Well 4000rpm is about 65Hz and 6000rpm is 100Hz. You really should be able to hear that difference I would have thought.

Expect that to be £500 in the UK, we seem to pay the same in £ as $ for stuff for no good reason. -Edit... yeah I get it, shipping and warehousing... but still.

Pretty much nothing in the sim (at the moment) but the switches on the IFEI select what source the video recorders in the pit are taking, either HUD, radar, left or right DDI. Can't remember fully from the NATOPS but it's something like that.

Oh and trim... always be trimming. Change something... hit the trim, recenter stick. You should avoid having to old pressure on the stick as much as possible. Pop it up into the hover, then trim. Move cyclic forward, Trim. Add collectiveand pitch for for speed, TRIM! :-) The only exception to this is the rudder pedals I have rudder trimming off, unless you have proper anti torque pedals that don't recenter themselves it can be easy to get yourself out of sorts in your head as to where your pedals are set in reality. So I just set my spring to the weakest and keep constant pressure on it so I can feed out the anti torque smoothly as I change my collective. Your mileage may vary though.

Yup, same here. Tracks do not play back properly... the inputs are all there, but desynch. For example, I taxied out of a hanger at Kutaisi, turned left for the active on November taxiway and went on my way. In the replay, I taxied out of the hanger, turned early and ended up stuck in the grass. The track then continued to playback all my inputs from the flight while still bogged into the grass. Trez amusing.

Like a lot of the mission editor shortcomings, this can probably done with some investment in learning the MOOSE scripting engine. https://forums.eagle.ru/showthread.php?t=138043 I did this with making a tanker stay on station over the carrier using MOOSE with polygon zones, user flags to trigger the next orbit point and an IF THEN ELSE statement. There are other ways that you could do it in MOOSE that are more elegant no doubt, but that's all my brain could come up with quickly. You'll need to learn a bit of lua scripting but well worth the time as you can open up a limitless amount of possibilities. For example, proper Integrated air defense systems, GCI controlled CAPs, ground patrols, I even wrote a range script that gave you proper bombing scores in both length and left right offset. I first got into it because of a problem not dissimilar to yours. Six months on and I can run up some pretty nifty solutions now, where as before I couldn't write a line of code in lua. Brew a pot of coffee and start here...

Touch controllers would work better with proper left/right button mapping for sure, but again, it's the problem of what to do with them when not needed. While I get it that it's more immersion, I have a track pad just behind my throttle which is far easier. Well it would be it the 3d cursor was properly implimented and not slaved to your head as it is now (user option of course for those that are happy with the status quo eg. those that don't use VR).