Chief1942 Posted October 3, 2015 Posted October 3, 2015 (edited) I'm having some issues with the flaps in the new 1.5 Beta with the F-86F. Initially on landing I would place the flaps in the "up" position via the flaps switch on my TM Warthog throttle. Using the external view, only the right flap would raise. If I cycled the flaps switch and applied throttle, eventually the left flap would raise. It happened a couple of times. Thinking I may have a key binding issue, I removed the input file for the F-86F in the Config folder and built a new one. No joy. I can get the flaps to extend via the Throttle flap switch, but they will neither retract now once on the ground. I tried using the mouse click on the flaps lever in the cockpit view, still would not raise the flaps even though the flaps lever went to the "up" position. Not sure if it is a bug or something I'm not doing correctly. I do not have this issue with my regular DCSW F-86F install. Any thoughts? I appreciate both F-86F and 1.5 are Beta and we WILL have issues, but so far other than the above, 1.5 is about as good as it gets. Edited October 3, 2015 by Chief1942 Intel i5-4690K Devil's Canyon, GForce TitanX, ASUS Z-97A MB, 16GB GDDR3 GSkill mem, Samsung SSD X3,Track IR, TM Warthog, MFG Crosswind pedals, Acer XB280HK monitor,GAMETRIX KW-908 JETSEAT
Art-J Posted October 3, 2015 Posted October 3, 2015 Hydraulic- and eletric-operated systems are much more prone to insufficient hydro pressure or insufficient amps in 1.5 now. That includes flaps (electro) and nosewheel steering (electro and hydro) mechanisms. Whether it's accurate in current form or not, I don't know. However, keep the RPM high enough for the generator to run and all things should work allright. i7 9700K @ stock speed, single GTX1070, 32 gigs of RAM, TH Warthog, MFG Crosswind, Win10.
Chief1942 Posted October 3, 2015 Author Posted October 3, 2015 Thanks Art-J, I should have expected some of these things. So much has been added to 1.5 that it is almost a whole new learning curve. Must have gotten complacent with the function of the F-86F up to this point. Will have to pay attention to subtle changes until I once again get into my comfort zone. Any suggestions as to what an appropriate on-ground RPM might be now to keep those systems functioning adequately? Intel i5-4690K Devil's Canyon, GForce TitanX, ASUS Z-97A MB, 16GB GDDR3 GSkill mem, Samsung SSD X3,Track IR, TM Warthog, MFG Crosswind pedals, Acer XB280HK monitor,GAMETRIX KW-908 JETSEAT
Spetz Posted October 3, 2015 Posted October 3, 2015 Found out that yesterday trying to raise flaps and close the airbrake. Nothing would happen until I got my RPM's up and the warning light went out. Pretty cool I think.
markuscha Posted October 3, 2015 Posted October 3, 2015 Any suggestions as to what an appropriate on-ground RPM might be now to keep those systems functioning adequately? If you keep it at 60% all should be fine : ) Regards, Markuscha CPU: i7-5820K, 3.3GHz GPU: nVidia GeForce GTX1080 Motherboard: Gigabyte X99-UD3 RAM: G.Skill DDR4-2133 16GB SSD: Crucial MX200 500GB OS: Win 10 64Bit
Toxic Posted October 4, 2015 Posted October 4, 2015 Make sure you're not deploying air brakes and flaps at the same time. This will cause a lack of pressure in the lines and make the aircraft very sluggish for the duration of the deployments. (If modeled correctly). #CHOPPERLIVESMATTER http://www.aircombatgroup.co.uk/ [sIGPIC][/sIGPIC]
Chief1942 Posted October 5, 2015 Author Posted October 5, 2015 Thanks to all! As I suspected, it was not a "bug" just a low information pilot who had a brain fart. Intel i5-4690K Devil's Canyon, GForce TitanX, ASUS Z-97A MB, 16GB GDDR3 GSkill mem, Samsung SSD X3,Track IR, TM Warthog, MFG Crosswind pedals, Acer XB280HK monitor,GAMETRIX KW-908 JETSEAT
jocko417 Posted October 8, 2015 Posted October 8, 2015 ...I would place the flaps in the "up" position via the flaps switch on my TM Warthog throttle. Using the external view, only the right flap would raise. If I cycled the flaps switch and applied throttle, eventually the left flap would raise. Not sure this should be happening. Each flap was electrically actuated, powered by the primary bus. If the generator is not online (too low idle) perhaps the flaps should not work, but they were protected from any asymmetry by being mechanically connected to each other. This way, one flap motor could drive both flaps if required. From the F-86F manual (highlighting my own):
Chief1942 Posted October 8, 2015 Author Posted October 8, 2015 Jocko417, That makes sense. can't imagine the response of an aircraft where one side flap went fully deployed while the other was completely retracted. So I think one can appreciate the interconnect design to prevent such an occurrence. I will try to do a screen grab the next time I am flying the F-86F and it does this anomaly. Seems to only be happening in the 1.5 Beta install. But as noted, as long as I now keep the RPM's at 60-65%, no issues. Intel i5-4690K Devil's Canyon, GForce TitanX, ASUS Z-97A MB, 16GB GDDR3 GSkill mem, Samsung SSD X3,Track IR, TM Warthog, MFG Crosswind pedals, Acer XB280HK monitor,GAMETRIX KW-908 JETSEAT
jocko417 Posted October 9, 2015 Posted October 9, 2015 I've tried it in the game and you're right. Usually on the ground but also in flight, if the engine is allowed to spool right down you'll get an asymmetric flap event. At low speed it causes an uncommanded roll and could potentially ruin your day. Mechanical interconnect is supposed to prevent this from occuring. I could maybe see the flaps being slower to move with only one motor driving the whole works but not one up one down...
Chief1942 Posted October 9, 2015 Author Posted October 9, 2015 Got a screenshot of the issue. Here is the problem. Yes fully retarded throttle after touchdown. Go up to 60-65% the left flap comes up. Intel i5-4690K Devil's Canyon, GForce TitanX, ASUS Z-97A MB, 16GB GDDR3 GSkill mem, Samsung SSD X3,Track IR, TM Warthog, MFG Crosswind pedals, Acer XB280HK monitor,GAMETRIX KW-908 JETSEAT
Art-J Posted October 10, 2015 Posted October 10, 2015 Well, the manual is pretty clear on the subject. It seems they were mechanically interconnected, so the current modelling, although better than in 1.2.16 version, still needs improvement and can be considered a bug. i7 9700K @ stock speed, single GTX1070, 32 gigs of RAM, TH Warthog, MFG Crosswind, Win10.
Recommended Posts