flyco Posted December 27, 2020 Posted December 27, 2020 I find the rate at which you can change the pitch trim of the Spitfire totally inadequate. I have over a 1000 hrs flying single engine training aircraft (prop and jet), and am well used to the need to trim constantly. When you make a flap or power change, you get to know how much trim you need to put in before fine trimming it. However on a normal aircraft this takes 1-2 secs to move the trimming wheel, whereas on the DCS Spitfire it takes very much longer. I have timed how long it takes the DCS Spitfire trim to move through its full travel and it is over 40 secs, as compared to less that 4 seconds in, say, a Chipmunk. This surely cannot be accurate. Surprisingly, I have never seen this remarked on in these forums. Does anyone else find this a problem?
Art-J Posted December 28, 2020 Posted December 28, 2020 On the contrary, there was a time when many found 4-sec. full travel way too fast, although that appplied to hyper-sensitive rudder trim back before it was slowed down this year to comparable speed with the elevator one. Previously, trimming (or rather overtrimming) the rudder was a bloody nightmare in DCS Spit - for the same reason I don't think many would like the elevator trim to be more sensitive. 40 sec.-sensitivity is perfect for cruise flight for me. I agree it's somewhat slow when I prepare for dropping gear and flaps, but I just deal with it by trimming in advance. Also, If you really need to trim fast, left-mouse click and drag rotates the wheel as fast as you dare, although it's not very convenient. i7 9700K @ stock speed, single GTX1070, 32 gigs of RAM, TH Warthog, MFG Crosswind, Win10.
Hornetjock Posted December 29, 2020 Posted December 29, 2020 Before the new sensitivity of the trims in the Spit, I used to use the actual trim wheels in the cockpit. Now I have them mapped to a HOTAS trim switch - up/down for elevator and left/right for rudder. You get used to the number of seconds it takes and your eyes are on other control settings. Removing the right rudder trim for takeoff is important for co-ordinated flight and can be done easily this way. It used to bug me but used to it now. The main one is pitch - I use very little rudder trim if any - I find the pedals accurate if you get the tail up. Still loving it!
Helles Belle Posted December 30, 2020 Posted December 30, 2020 Like @Hornetjock and I guess most people I have the trims mapped to the stick. I also have the nose down & rudder right trim mapped to two buttons side by side on the keyboard. I find if you press both until nose trim indicates 1 unit UP, the rudder trim will be right for takeoff. Slowly bringing the power up to 10-12 boost it almost lifts off the ground by itself and flies away. I also find the trim rate better now. I think slower you are able to finesse the trim to a point where minimal input is required for straight & level. At other times I’ll just use rudder to keep it balanced and hold elevator & aileron as required. Now if only they would fix the trim rate on the Bf-109, that is way to quick. Send lawyers, guns and money......... for the …. has hit the fan. Windows 10 Home 64-bit | CPU: AMD Ryzen 7 5800X3D 8-Core Processor | RAM: Corsair 32.0GB Dual-Channel | MOBO: ROG STRIX X570-F GAMING (AM4) | GPU: MSI G271CQP on NVIDIA GeForce RTX 3080 | SSD: Samsung SSD 860 EVO 2TB & Samsung SSD 970 EVO Plus 1TB for Gaming CH Fightersick - Pro Throttle - Pro Pedals | Thrustmaster MFD Cougar x 3 | Buddy Fox A-10C UFC
Holbeach Posted December 31, 2020 Posted December 31, 2020 On 12/27/2020 at 8:02 PM, flyco said: I find the rate at which you can change the pitch trim of the Spitfire totally inadequate. I have over a 1000 hrs flying single engine training aircraft (prop and jet), and am well used to the need to trim constantly. When you make a flap or power change, you get to know how much trim you need to put in before fine trimming it. However on a normal aircraft this takes 1-2 secs to move the trimming wheel, whereas on the DCS Spitfire it takes very much longer. I have timed how long it takes the DCS Spitfire trim to move through its full travel and it is over 40 secs, as compared to less that 4 seconds in, say, a Chipmunk. This surely cannot be accurate. Surprisingly, I have never seen this remarked on in these forums. Does anyone else find this a problem? On 12/27/2020 at 8:02 PM, flyco said: ASUS 2600K 3.8. P8Z68-V. ASUS ROG Strix RTX 2080Ti, RAM 16gb Corsair. M2 NVME 2gb. 2 SSD. 3 HDD. 1 kW ps. X-52. Saitek pedals. ..
Terry Dactil Posted January 1, 2021 Posted January 1, 2021 Have you noticed that the Spitfire has very little longitudinal stability (by design)? This means that only very small trim adjustments are normally required in flight. I imagine that if ED increase the trim speed they would then get complaints that it moves too fast to be accurately set. I have no problems with it in flight; it is only a pain setting pre-flight where possibly a large adjustment is needed. Our main problem is that we are using a computer and a fixed rate, whereas in the real aircraft the trim can be manually moved as far and fast as you desire. I guess life wasn't meant to be easy.
grafspee Posted January 1, 2021 Posted January 1, 2021 ED should make all trim wheels work like in p-51 if you press it for longer time trim change accelerates, but at the beginning it is very precise and slow. 1 System specs: I7 14700KF, Gigabyte Z790 Aorus Elite, 64GB DDR4 3600MHz, Gigabyte RTX 4090,Win 11, 48" OLED LG TV + 42" LG LED monitor
Eisprinzessin Posted January 5, 2021 Posted January 5, 2021 I have the problem that my spit always pulls up. did the first flights today and not be able to trim ist that it takes level flight. also pulls up. 2000 rpm....4 boost....pulls up. and rolls to the left. on top with rudder trim fully right...hm, did i miss something? 1 Specs: 12th Gen Intel(R) Core(TM) i9-12900K 3.20 GHz, RAM 128 GB, Win11 Home, RTX3080Ti
Terry Dactil Posted January 8, 2021 Posted January 8, 2021 Suggest checking all your axis controls. The default values have things like the rudder also wanting to control pitch, roll and throttle. The default settings bind anything that can control an axis to everything it can find!
Fri13 Posted January 8, 2021 Posted January 8, 2021 The trimming is fixed value. I don't know what file it was, but it was mentioned in these forums once in topic of P-51. You could adjust the trimming speed in it. In modern jets it is too fast, you can't example trim L-39 to level flight as it always gets over the wanted trim position so you are constantly going up/down. Adjusting the file you got it much slower so you could have nice smooth trimming by holding trim down. But, you can do it otherway around as well, set it faster so less time moves it more. i7-8700k, 32GB 2666Mhz DDR4, 2x 2080S SLI 8GB, Oculus Rift S. i7-8700k, 16GB 2666Mhz DDR4, 1080Ti 11GB, 27" 4K, 65" HDR 4K.
Sandhill Posted January 24, 2021 Posted January 24, 2021 (edited) Oddly, I have had the exact opposite problem with pitch trim in the Spit. It is viciously fast near center using button presses. To trim for straight and level I go from too much up to too much down in the course of a super quick button push. I have had this problem with no other aircraft. Yes it does take forever to go from full Nose UP to full Nose Down, but that range around center had been pretty useless for me. I had a long throw axis available which I have put to use, but even then I had to turn the saturation way down and put quite a bit of curve on it to get to where I can consistently trim to within a couple hundred FPM for straight and level. I'd prefer to use the same hat for pitch trim that I use for every other aircraft, but I've had to make the exception for the Spit. Edited January 24, 2021 by Sandhill smelling
LeCuvier Posted March 2, 2021 Posted March 2, 2021 (edited) On 1/8/2021 at 1:51 AM, Fri13 said: The trimming is fixed value. I don't know what file it was, but it was mentioned in these forums once in topic of P-51. You could adjust the trimming speed in it. .. Changing the "gain" in the file "clickabledata.lua" in the folder "...\Cockpit\Scripts" helps only if the HOTAS control is directly linked to the sim cockpit object. That's not the case in the Spit. For fine-tuning of the elevator trim you could bind a rotary encoder to the two trim commands (in addition to the POV hat). You could then use the POV hat for coarse trim and the rotary encoder for fine adjustment. Edited March 2, 2021 by LeCuvier 1 LeCuvier Windows 10 Pro 64Bit | i7-4790 CPU |16 GB RAM|SSD System Disk|SSD Gaming Disk| MSI GTX-1080 Gaming 8 GB| Acer XB270HU | TM Warthog HOTAS | VKB Gladiator Pro | MongoosT-50 | MFG Crosswind Pedals | TrackIR 5
Fri13 Posted March 2, 2021 Posted March 2, 2021 1 hour ago, LeCuvier said: only if the HOTAS control is directly linked to the sim cockpit object. What do you mean with that? i7-8700k, 32GB 2666Mhz DDR4, 2x 2080S SLI 8GB, Oculus Rift S. i7-8700k, 16GB 2666Mhz DDR4, 1080Ti 11GB, 27" 4K, 65" HDR 4K.
LeCuvier Posted March 2, 2021 Posted March 2, 2021 3 hours ago, Fri13 said: What do you mean with that? Some of the bindable commands defined in the "default.lua" are linked to "clickable" cockpit objects visible in "clickabledata.lua". Others are "parallel" objects implemented separately for binding. Technical answer unfortunately, but it's a technical subject. 1 LeCuvier Windows 10 Pro 64Bit | i7-4790 CPU |16 GB RAM|SSD System Disk|SSD Gaming Disk| MSI GTX-1080 Gaming 8 GB| Acer XB270HU | TM Warthog HOTAS | VKB Gladiator Pro | MongoosT-50 | MFG Crosswind Pedals | TrackIR 5
Sandhill Posted March 5, 2021 Posted March 5, 2021 On 3/2/2021 at 10:45 AM, LeCuvier said: For fine-tuning of the elevator trim you could bind a rotary encoder to the two trim commands (in addition to the POV hat). You could then use the POV hat for coarse trim and the rotary encoder for fine adjustment. Nice, hadn't thought to try that ... it seems to be working well! Thanks!
Recommended Posts