klem

Just upgraded to Windows 10 from 7

Have a look at this video of a RL SpitIX flight. Quite interesting. I watched it several times and gleaned some notes from it (see below). I think our SpitIX needs some tweaking/damping in directional stability? ============================== Observations:- Taxi: -6lbs, Trim0, prop fully fine Rudder/brake input as necessary, typically showing turn rate 2 on the rate of turn indicator, using brakes and rudder (Watch the video Turn indicator, up to ± 2 to 3 needle deflection with not much dancing) Takeoff: Trim 0, fully fine (I have been using -0.5 grad trim) Power up from -6lbs to +6lbs (8-10 secs). passing 0 lbs around 5 secs achieving 2800rpm Quick firm but small rudder inputs as necessary. (Watch video Turn indicator, ± 1.5 needle deflection with some dancing) Push tail up at 60mph and hold Lift off at 120mph Brake wheels and raise u/c. Trim to level flight. Flight observations: +7lbs, 2650rpm, 260-300mph level flight, Trim -1 grad 0lbs, 2000rpm, 200-220mph level flight, Trim 0. Landing: -6lbs, fully fine, achieves 2200rpm at higher speeds. Speed/rpm bleeds off. @160mph Gear down, small backpressure, Trim out to approx +0.75 grads (I am finding it necessary to go to about 1 grad) @140mph, Flaps down, larger backpressure, Trim out to +1.25 grads (I have found it necessary to go to +2 grads and still have some weight in my hand) Into Base leg -6lbs at 110mph, 2200rpm Into finals holding 100mph, 1800rpm, no Trim changes, bleeding speed Threshold 90mph, bleeding speed, rudder and aileron as necessary 80mph stick back for 3-point landing, rudder and aileron as necessary Touchdown 70mph. Stick well back, much rudder input (dancing) as necessary on roll out Rollout: Allow Speed to bleed off with quick firm rudder inputs as necessary (Watch video Turn indicator, up to full needle deflection with dancing) Use brakes with rudder only at lower speeds. Flaps up asap. Return trim to 0 when convenient. ================================

I only just found this thread. Meantime after changing my memory and then the OS to Win10 I followed the repeated requests to re-activate and now only have 8 activations left from 12 or 13. How do I recover those in case I need them in the future?

It is tricky. Have you tried stick hard back once airspeed has been lost? Also braking only near the end when slow and again dancing on the pedals.

Very nice. And Google for translate readable it is Yoda. :)

I think you are saying that the trim tab moves up when trimming the nose down. This is correct. When the Trim tab moves up in the airflow (i.e. when flying) the airflow acts on it and it pushes the actual elevator down so that the tail rises (the nose goes down). Some people have difficulty getting their heads around that but it is true. Also be sure that when you think you are trimming nose down the gauge needle does go down. If not, your trimmer calibration needs to be reversed in your control settings (assuming you are using an axis). Your description sounds as though the nose is being trimmed up when you expect it to go down. I can assure you that the trimmer does have the capacity to trim the nose down for level fight. Have you adjusted it's calibration so that you don't get full trimmer travel (e.g. put in an extreme curve or reduced the saturation). EDIT: never take off with the flaps down.

There is something wrong with your setup. There is more than enough trim to bring the nose level and what you say contradicts your earlier statement that the Spit rears up after takeoff. First if all, the correct takeoff trim is somewhere between 1 grad down (training load with no ammo) and zero trim (fully loaded with rear internal and an external fuel tank - see real pilots notes). I set trim to half grad down and it is fine. After takeoff you will need to adjust the trim according to changing airspeed. I have to trim up to remove the takeoff setting but as airspeed develops I can feather that off a little. Of course I also have to wind off much of the right rudder trim that I have set. I find about 40% right trim is enough for takeoff whereas full right trim as pilots notes is too much so I do agree there is perhaps some trim work to be done. By dumbing down your controls (especially saturation) like that you are removing the sensitivity that the Spit is famous for. A friend of mine used to fly the Spit and he always said you could fly it with two fingers (thumb and forefinger). I do have curves set - 20% - but assuming the FM is designed to be faithfully responding to the standard linear stick inputs from Windows Devices I hope to remove that when I get used to it. One thing I have never been sure of is if the FMs are designed like that but I assume they are. Also we do not have a faithful reproduction of the feel of the control column - I doubt if even FFB gives the correct feel for every aircraft - so we are fighting that problem anyway which is one reason why people add curves.

Well you wanted realism :music_whistling: In CoD on SoW server we often fly 1 - 1.5 hours with GCI and don't find a fight. Somehow it doesn't feel wrong. Actually I'm finding the current set-up not too bad for dogfighting. Dd ED change something?

Nice. Tiny touches of rudder after touchdown, increasing as it slows. When she's slowing right down it's much rudder and dabs of brake. Not too much mind. <<< expert :megalol: I've swerved down the runway to a halt several times now!

Yes I understand the theory. I just compared the standard files with the ProperNeck files in my Saved Games and no, it isn't incorporated into DCS. Because the ProperNeck files have always been there I was fooled into thinking it was now in DCS. Stupid Boy as they say. I don't want to use a universal FOV. With my screen layout I create individual FOVs (using RALT + 0) for each aircraft which are all very similar. They only vary because in one cockpit an instrument may be partially cut off between upper and lower screens and then I will have a similar problem in another so I set them individually. But they are all within a few degrees of eachother.

Thanks. TBH I thought proper neck had been incorporated into DCS.

:thumbup:

Yes, sorry my mistake I left out the UIMainView = GUI. You define the GUI and then you tell UIMainView to use it so I have UIMainView after the definition: GUI = { x = 1920; y = 0; width = 1920; height = 1080; } UIMainView = GUI

Some of you may be using far too much power, the legacy of past "flying on rails" sims or simplified FMs. Even COD does not do the Spit justice due to the underlying FM algorithms. I am getting up with no real problem using figures given me by a current MkIX display pilot. He uses max +6lbs boost and 2400 rpm, reducing to +4lbs boost for general flying and +6lbs for the displays. All these of course to protect the engine but there's more than enough power to get you flying. What you do next is up to you but in combat I generally keep to the Cruise settings +7/2650 unless I need to push it up but don't leave it there for too long or you'll damage the engine.

Can someone leak me the launch hour? :joystick:

Change your UIMainView = Viewports.Center to ** --UIMainView = Viewports.Center GUI= { x = 0; y = 0; width = 1920; height = 1080; } ** i.e. overpaste the existing UIMainView line with everything from ** to ** excluding the **'s.

Just so that I am clear: 1. Will early release be useable in 1.5.5 or will I need DCS 1.5 openbeta? 2. Will the pre-release discount price be available after early release? If so, until when?

Don't feel alone. Until a couple of years ago our prime minister was signing off his emails with lol thinking it meant lots of love. He's gone now :)

I try not to use the brakes until under 60 kts

Ensure dampers are on. Ensure Air Brake is in. Ensure Flaps are at Auto. Ensure nose-wheel is hiked. Set correct trim setting (see here https://forums.eagle.ru/showpost.php?p=2974281&postcount=17 ) (+3 deg AOA doesn't actually do anything ref TO, its just an instrument) Line up carefully. If brakes on, go Throttle to near max before releasing although I find no brakes is just fine. Anticipate deviation from centreline and apply lightest touches of NW steering up to 60 kts to keep straight. Remember NW steering is 'direct' like a car steering wheel and you need to bleed off the rudder as you ease back to the line, probably correcting a little to get on centre. Use Rudder above 60 kts (may require larger inputs when still slow). Anticipate when to come off rudder. Rotate around 165kts - 180kts and before 230 or risk tyre blowout. Also see attached.

Immediately deploy the chute on nose contact, don't use nose-wheel steering until below 60 knots (rudder is effective above that although increasing input is required as speed bleeds down). Use nose-wheel steering very carefully, only the lightest touches. Stay right on top of it.

I don't need it but I have to say, what a nice gesture. Great community.

OK I can just about see them, very very faint grey, almost the same as the background. I would never see these without a pointer plus the time to examine the screen very very carefully so for me 'seeing too far' isn't an issue. In fact I am usually the last person to see distant dots. And yes, even a 'good' distant dot/imposter tends to disappear with zoom although Models don't.

Well in that case I can't explain it. I just took off empty with nose erected but with nil trim just to see. Hauled it off at 200 ok.

As BIGNEWY says, check Trim as attached. I also sometime get blowout but I am conscious I am too fast when still on runway.