ThePutzer Posted February 9, 2016 Posted February 9, 2016 (edited) F-86 Sabre: As stated above, the changes in RPM, and the small window in which it does operates is silly stupid fast. I watched over 1/2 doz. guys try an taxi that, on my server. They all, most all, end up in dirt,,hitting buildings,,going in circles. The RPM and window is just fine in 1.5.. Hope you guys think this is a issue that you can address. That is unless I an the others are doing something wrong. ThePutzer Edited February 9, 2016 by BIGNEWY inappropriate language 1.1
AH_Sid Posted February 9, 2016 Posted February 9, 2016 Have you tried turning the new option off on the 'Special' options page for the F-86F? I'm not sure why this option was introduced, but I turned it straight off and have just been using the 'nose wheel steering button' as normal, just like I've always done.
derelor Posted February 9, 2016 Posted February 9, 2016 The F-86 got realistic NWS behavior in the latest update. ALWAYS - NWS switch must be held depressed to engage the steering unit. SIMPLE BEHAVIOR (default, corresponds to behavior before the update) - To engage the NWS system, only the NWS button has to be pressed. - Unrealistic, because the positions of the nosewheel and rudder pedals do not play a role for engaging the NWS system. The nose wheel is "automatically synchronized" with rudder pedal position when NWS button is pressed. REALISTIC BEHAVIOR - To engage the NWS system, the NWS button has to be pressed AND rudder pedals must be aligned in the direction the nose wheel is turned, i.e. you need to "catch" the nose wheel with rudder pedals for synchronization (When nose wheel and rudder pedals are coordinated in this manner, the nose wheel steering unit is automatically engaged) - Wheel can be in position outside of rudder pedals authority and not be caught at all: Nose wheel unit will not engage if the nose wheel is more than 21 degrees either side of the center. Should the nose wheel be turned more than this, it must be brought into the steering range by use of the wheel brakes. - Realistic behavior according to flight manual (T.O. 1F-86F-1 Section I Page 1-43) 1338 - beyond leet ED Forum rules EN|DE|RU
ThePutzer Posted February 10, 2016 Author Posted February 10, 2016 Thanks 4 quick response. RPM ?? So I understand the catching now. I was not having problems getting it engaged, it is the speed at which it activates is FAST 2 fast, and stops (disengages) working if you travel at reasonable speed.. I will have to try the dumb ed down setting, as shown above I guess. Thanks again for quick response.. ThePutzer
ac5 Posted April 25, 2016 Posted April 25, 2016 Hello well, the problem persist here... Even with SIMPLE BEHAVIOR selected, in BOTH 1.5.3 AND 2.02 there is no way that this corresponds to behavior before the update.... I clearly remember that keeping pressed the NWS button AND pushing forward left / right pedal corresponded to a left or right turn. This is not any more so! To turn I have to press left or right toe brake, like in the russian jets or BF-109. And YES, the NWS is correctly mapped on Joystick AND keyboard. Mainboard: ASUS Maximus X Hero Intel Z 370 CPU: Intel 12-Core i7-8086K @ 4.0 GHz Memory: 32GB Corsair DDR4-3000 MHz Graphics Card: ASUS NVIDIA GeForce RTX 4090 24 GB Monitor ASUS - Oled PG42UQ 41.5" @ 4K 1 SSD Samsung 860 PRO 256 GB 1 SSD Samsung 990 PRO NVMe M.2 4 TB Windows 11 Home - 64 CH Products Combatstick, Throttle and Pedals
Buzzles Posted April 25, 2016 Posted April 25, 2016 Non-simple works fine and as expected for me in 1.5.3... Fancy trying Star Citizen? Click here!
ac5 Posted April 25, 2016 Posted April 25, 2016 Non-simple DOES NOT work fine for me in 1.5.3... AND in 2.02 there is no way that this corresponds to behavior before the update.... Pressing the NWS button either on keyboard or joystick AND pushing forward left / right pedal just does NOTHING. CH Combat Stick, throttle and CH pedals. Mainboard: ASUS Maximus X Hero Intel Z 370 CPU: Intel 12-Core i7-8086K @ 4.0 GHz Memory: 32GB Corsair DDR4-3000 MHz Graphics Card: ASUS NVIDIA GeForce RTX 4090 24 GB Monitor ASUS - Oled PG42UQ 41.5" @ 4K 1 SSD Samsung 860 PRO 256 GB 1 SSD Samsung 990 PRO NVMe M.2 4 TB Windows 11 Home - 64 CH Products Combatstick, Throttle and Pedals
Buzzles Posted April 25, 2016 Posted April 25, 2016 Non-simple DOES NOT work fine for me in 1.5.3... AND in 2.02 there is no way that this corresponds to behavior before the update.... Pressing the NWS button either on keyboard or joystick AND pushing forward left / right pedal just does NOTHING. CH Combat Stick, throttle and CH pedals. You're not trying to do it on idle/low (<60%) throttle are you? Fancy trying Star Citizen? Click here!
flask Posted April 27, 2016 Posted April 27, 2016 Yes I am one of the 1/2 doz ending up in the dirt, :( I am using the Warthog stick and the steering ( non latched) on button( little tiny wee speck of a thing it is to my sausage fingers) is behind the brake ( default afaik) I will try as suggested going to simple steering , but jeeze the way it is now its like trying to rub your stomach in a circular manner and patting your head at the same time but I've an ugly suspicion its not the designers problem but my lack of co-ordination:joystick: BTW: Take the opportunity to thank the guys that brought us the F86, glad I bought it, nice one.
ac5 Posted April 27, 2016 Posted April 27, 2016 Of course I am not trying to do it on idle/low (<60%) throttle, even at full throttle and pressing the NWS button either on keyboard or joystick AND pushing forward left / right pedal just does NOTHING AT ALL. This DOES NOT correspond to the behavior before the update.... 100% sure. Mainboard: ASUS Maximus X Hero Intel Z 370 CPU: Intel 12-Core i7-8086K @ 4.0 GHz Memory: 32GB Corsair DDR4-3000 MHz Graphics Card: ASUS NVIDIA GeForce RTX 4090 24 GB Monitor ASUS - Oled PG42UQ 41.5" @ 4K 1 SSD Samsung 860 PRO 256 GB 1 SSD Samsung 990 PRO NVMe M.2 4 TB Windows 11 Home - 64 CH Products Combatstick, Throttle and Pedals
Art-J Posted April 27, 2016 Posted April 27, 2016 Switch to realistic mode then. It works perfectly and as long as You remember about pressing/depressing the NWS button when the plane taxis straight (to avoid the whole "catching" issue), it's not more difficult then in pre-update times. i7 9700K @ stock speed, single GTX1070, 32 gigs of RAM, TH Warthog, MFG Crosswind, Win10.
ac5 Posted April 27, 2016 Posted April 27, 2016 Also in realistic mode! pressing the NWS button either on keyboard or joystick AND pushing forward left / right pedal just does NOTHING AT ALL. This DOES NOT correspond to the behavior before the update.... 100% sure. Mainboard: ASUS Maximus X Hero Intel Z 370 CPU: Intel 12-Core i7-8086K @ 4.0 GHz Memory: 32GB Corsair DDR4-3000 MHz Graphics Card: ASUS NVIDIA GeForce RTX 4090 24 GB Monitor ASUS - Oled PG42UQ 41.5" @ 4K 1 SSD Samsung 860 PRO 256 GB 1 SSD Samsung 990 PRO NVMe M.2 4 TB Windows 11 Home - 64 CH Products Combatstick, Throttle and Pedals
Art-J Posted April 27, 2016 Posted April 27, 2016 What can I say, I don't have pedals with toe brakes, using ones from racing wheel instead, and the steering mechanics works OK as per manual. "100% sure" as well, 'cause I've been extensively flying F-86 in both 1.5.3 stable and 2.0.2 after latest updates. Maybe it's some issue with Your hardware then. What pedals do You use, so that people can try replicating the problem? i7 9700K @ stock speed, single GTX1070, 32 gigs of RAM, TH Warthog, MFG Crosswind, Win10.
ac5 Posted April 28, 2016 Posted April 28, 2016 Art-J, I already wrote that: CH Combat Stick, throttle and CH pedals. Same exact hardware that worked before the update, so no issue there. 2.01 the steering was fine, 2.02 is not: DOES NOT work fine for me in 1.5.3... AND in 2.02 there is no way that this corresponds to behavior before the update.... Pressing the NWS button either on keyboard or joystick AND pushing forward left / right pedal just does NOTHING. CH Combat Stick, throttle and CH pedals. Mainboard: ASUS Maximus X Hero Intel Z 370 CPU: Intel 12-Core i7-8086K @ 4.0 GHz Memory: 32GB Corsair DDR4-3000 MHz Graphics Card: ASUS NVIDIA GeForce RTX 4090 24 GB Monitor ASUS - Oled PG42UQ 41.5" @ 4K 1 SSD Samsung 860 PRO 256 GB 1 SSD Samsung 990 PRO NVMe M.2 4 TB Windows 11 Home - 64 CH Products Combatstick, Throttle and Pedals
Art-J Posted April 28, 2016 Posted April 28, 2016 Sorry, didn't notice that before. Well, we can only wait for other CH gear users to ask how / if it works on their machines. i7 9700K @ stock speed, single GTX1070, 32 gigs of RAM, TH Warthog, MFG Crosswind, Win10.
flask Posted April 28, 2016 Posted April 28, 2016 (edited) I have had another go last night on the F86 to do with this steering conversation,( after choosing/ticking the box "simple steering" in both Nevada DCS and standard DCS world Versions) The Nevada Multiplayer,first 1) worked a dream on one multiplayer ( simple steering that is) 2) logged onto another Nevada Multiplayer, no simple steering BAH! 3) logged onto DCS World standard multiplayer worked a dream( simple steering) NB: I do not consider this a true reflection on the situation , its only as I see a quick try out after reading previous posts and in no way infers a problem with code or hardware, or to degrade any persons who are experiencing problems, it should not be taken as any other way than stated. Edited April 28, 2016 by flask
Art-J Posted April 28, 2016 Posted April 28, 2016 Don't server providers force difficulty options for all clients? Hence different behaviour on different servers? Just asking, 'cause I fly SP only. i7 9700K @ stock speed, single GTX1070, 32 gigs of RAM, TH Warthog, MFG Crosswind, Win10.
71st_AH Rob Posted April 28, 2016 Posted April 28, 2016 Don't server providers force difficulty options for all clients? Hence different behaviour on different servers? Just asking, 'cause I fly SP only. Yes, we do force some settings on our servers, however the settings are actually in the mission so two missions on the same server could give different results. The only option that would affect the NWS I think is GAMEFLIGHTMODE, this could be enforced on so everyone uses the simplified mode, enforced off so everyone uses the Simulator mode or left up to the users own settings to decide so two users on the same server in the same mission experience it differently. The bottom line is that it works fine, and in Sim mode is a bit more difficult because it is more realistic. Update 4 introduced some new default commands and new options for mapping actions that were not there by default before. Once I went through my various commands and deleted duplicates everything worked fine, might be worth a try.
ac5 Posted April 30, 2016 Posted April 30, 2016 After update 2.02 / 30.04.2016 it is still not working for me. CH Combat Stick, throttle and CH pedals. Same exact hardware that worked before the update, so no issue there. 2.01 the steering was fine, 2.02 is not: DOES NOT work fine for me in 1.5.3... AND in 2.02 there is no way that this corresponds to behavior before the update.... Pressing the NWS button either on keyboard or joystick AND pushing forward left / right pedal just does NOTHING. BELSIMTEK? SOMEBODY? Mainboard: ASUS Maximus X Hero Intel Z 370 CPU: Intel 12-Core i7-8086K @ 4.0 GHz Memory: 32GB Corsair DDR4-3000 MHz Graphics Card: ASUS NVIDIA GeForce RTX 4090 24 GB Monitor ASUS - Oled PG42UQ 41.5" @ 4K 1 SSD Samsung 860 PRO 256 GB 1 SSD Samsung 990 PRO NVMe M.2 4 TB Windows 11 Home - 64 CH Products Combatstick, Throttle and Pedals
Buzzles Posted April 30, 2016 Posted April 30, 2016 (edited) Posting a track might help, as per Sith's bug reporting guide. Edited April 30, 2016 by Buzzles Removing track Fancy trying Star Citizen? Click here!
Flamin_Squirrel Posted April 30, 2016 Posted April 30, 2016 After update 2.02 / 30.04.2016 it is still not working for me. CH Combat Stick, throttle and CH pedals. Same exact hardware that worked before the update, so no issue there. 2.01 the steering was fine, 2.02 is not: DOES NOT work fine for me in 1.5.3... AND in 2.02 there is no way that this corresponds to behavior before the update.... Pressing the NWS button either on keyboard or joystick AND pushing forward left / right pedal just does NOTHING. BELSIMTEK? SOMEBODY? Works fine for me.
ac5 Posted April 30, 2016 Posted April 30, 2016 RESOLVED! Stupid of me... The update somehow erased my rudder bindings. Now It's OK! Mainboard: ASUS Maximus X Hero Intel Z 370 CPU: Intel 12-Core i7-8086K @ 4.0 GHz Memory: 32GB Corsair DDR4-3000 MHz Graphics Card: ASUS NVIDIA GeForce RTX 4090 24 GB Monitor ASUS - Oled PG42UQ 41.5" @ 4K 1 SSD Samsung 860 PRO 256 GB 1 SSD Samsung 990 PRO NVMe M.2 4 TB Windows 11 Home - 64 CH Products Combatstick, Throttle and Pedals
Chief1942 Posted April 30, 2016 Posted April 30, 2016 Not just you. RESOLVED! Stupid of me... The update somehow erased my rudder bindings. Now It's OK! Only speaking for myself, but I to have too often overlooked the obvious when I run into an issue.:doh: I have become pretty regular at checking all my controller assignments after every update.:book: They don't all change all the time, but some do change within a particular module. Glad you sorted it out. I really enjoy the F-86:pilotfly: 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
Flamin_Squirrel Posted April 30, 2016 Posted April 30, 2016 RESOLVED! Stupid of me... The update somehow erased my rudder bindings. Now It's OK! If you encounter this kind of problem again, use RCtrl-Enter to bring up a display to show your controls. Very useful for diagnosing control difficulties.
ac5 Posted May 1, 2016 Posted May 1, 2016 Okidok! Mainboard: ASUS Maximus X Hero Intel Z 370 CPU: Intel 12-Core i7-8086K @ 4.0 GHz Memory: 32GB Corsair DDR4-3000 MHz Graphics Card: ASUS NVIDIA GeForce RTX 4090 24 GB Monitor ASUS - Oled PG42UQ 41.5" @ 4K 1 SSD Samsung 860 PRO 256 GB 1 SSD Samsung 990 PRO NVMe M.2 4 TB Windows 11 Home - 64 CH Products Combatstick, Throttle and Pedals
Recommended Posts