August 25, 20205 yr can someone do a test for me, can you clear the "set beacon lights" and see if that fixes it. it's set to joystick 21. Edited August 25, 20205 yr by FPStewy Ryzen 5 5600X - Noctua U12A, 32Gb Vengence, Sapphire Pulse 5700xt, WD Black SN750 NVMe SSD
August 25, 20205 yr Ok I've cleared all buttons for magnetos and exterior lights and it's working fine now. Can someone else confirm. If you leave the ex. lights assigned it will work until you turn them on and the you get the 10 increments but 1 if there off. but de-assigned mags and ex. lights and it seems to work fine for me. Edited August 25, 20205 yr by FPStewy Ryzen 5 5600X - Noctua U12A, 32Gb Vengence, Sapphire Pulse 5700xt, WD Black SN750 NVMe SSD
August 25, 20205 yr 12 minutes ago, FPStewy said: can someone do a test for me, can you clear the "set beacon lights" and see if that fixes it. it's set to joystick 21. It's not just the beacon light. It is any of the toggles. Here's the thing that makes this confusing. Take the beacon switch on the controller for example. It has two positions. In the up position, button 21 is pressed/active. In the down position, button 22 is pressed/active. So no matter which position the switch is in, at least one of those buttons is showing in Windows as being in the "on" state. Here's where it gets confusing to troubleshoot. There are 2 ways that you can bind commands to the beacon switch in MSFS to manipulate the beacon light in the sim. 1. Assign the "set beacon lights" command to button 21, leave button 22 unassigned 2. Assign "Beacon lights on" command to button 21 and "Beacon lights off" command to button 22. If you do option 1, then the "10 degree bug" occurs when the beacon switch on the controller is in the up position (button 21 "on"). It is ok when the switch is in the down position because nothing is assigned to button 22 in the sim. If you do option 2, then the "10 degree bug" occurs with either switch position because both 21 and 22 are assigned a function in the sim. Now propagate that scenario across all 9 toggle switches and magneto control of the Honeycomb and you see the scope of the problem Chris
August 25, 20205 yr 3 minutes ago, snglecoil said: Now propagate that scenario across all 9 toggle switches and magneto control of the Honeycomb and you see the scope of the problem agreed, in other words deactivate all toggle buttons including the Bat/Alt/Bus1/2 Ryzen 5 5600X - Noctua U12A, 32Gb Vengence, Sapphire Pulse 5700xt, WD Black SN750 NVMe SSD
August 25, 20205 yr 1 minute ago, FPStewy said: agreed, in other words deactivate all toggle buttons including the Bat/Alt/Bus1/2 the best part about the yoke is all the buttons and toggles 🙂 They just need to fix the issue instead of us having to unmap a $250 yoke and only be able to use half of it lol i9 11900K @ 5.3 RTX 3070TI 8GB 32 GB RAM @ 4200 GHZ 1 TB SSD 1080p G-Sync 27" Monitor
August 25, 20205 yr Author 32 minutes ago, FPStewy said: Ok I've cleared all buttons for magnetos and exterior lights and it's working fine now. Can someone else confirm. If you leave the ex. lights assigned it will work until you turn them on and the you get the 10 increments but 1 if there off. but de-assigned mags and ex. lights and it seems to work fine for me. It's odd, but I have never gotten rid of the lights and, of course, some are on during flights like Beacon and Strobe and I don't have the jump by 10 issue (after killing off the magneto assignments). i7 8700K @4Ghz, EVGA RTX3080 Ultra, 32GB RAM, Two 2K displays. Alpha Yoke, Bravo Throttle Quadrant, CH Pedals.
August 25, 20205 yr 31 minutes ago, atlflyer said: the best part about the yoke is all the buttons and toggles 🙂 They just need to fix the issue instead of us having to unmap a $250 yoke and only be able to use half of it lol I don't think though that the problem is with Honeycomb coz on some planes I don't have that issue with all the buttons assigned, it's just in some planes, patches will eventually fix this I hope, I think there's one due out in 2 days, we'll see. Ryzen 5 5600X - Noctua U12A, 32Gb Vengence, Sapphire Pulse 5700xt, WD Black SN750 NVMe SSD
August 25, 20205 yr Author 1 minute ago, FPStewy said: I don't think though that the problem is with Honeycomb coz on some planes I don't have that issue with all the buttons assigned, it's just in some planes, patches will eventually fix this I hope, I think there's one due out in 2 days, we'll see. There's one what due in two days? The only thing I know of is Asobo, in two days, telling us when to expect a patch, but not actually a patch. i7 8700K @4Ghz, EVGA RTX3080 Ultra, 32GB RAM, Two 2K displays. Alpha Yoke, Bravo Throttle Quadrant, CH Pedals.
August 25, 20205 yr 5 hours ago, Muklum said: That's useful to know, but I'm not prepared to go that far. The yoke and its switches behave correctly in every other sim I've tried, so I shouldn't have to cripple it to get it to play nicely with FS2020. And what new problems are going to be found when the Honeycomb throttle quadrant becomes available? I do hope they get the problem fixed, because I think FS2020 has a lot to offer, but for the present I'd rather have the full use of my current hardware. Agreed. But is the problem with just Honeycomb or any controller that uses "always on" toggle type switches? If the latter, certainly this would be an issue at the top of the patch list for Asobo. Is that not how the Saitek radio panel works? Maybe someone who owns one can confirm. Ryan
August 25, 20205 yr Author Just now, rjack1282 said: Agreed. But is the problem with just Honeycomb or any controller that uses "always on" toggle type switches? If the latter, certainly this would be an issue at the top of the patch list for Asobo. Is that not how the Saitek radio panel works? Maybe someone who owns one can confirm. I believe this bug is showing up on other devices, but since the Alpha is so hot now, it's the one most people are noticing. i7 8700K @4Ghz, EVGA RTX3080 Ultra, 32GB RAM, Two 2K displays. Alpha Yoke, Bravo Throttle Quadrant, CH Pedals.
August 25, 20205 yr 2 hours ago, Agrajag said: There's one what due in two days? The only thing I know of is Asobo, in two days, telling us when to expect a patch, but not actually a patch. sorry it's the announcement for the patch is due, your right. Ryzen 5 5600X - Noctua U12A, 32Gb Vengence, Sapphire Pulse 5700xt, WD Black SN750 NVMe SSD
August 25, 20205 yr Author 2 hours ago, FPStewy said: sorry it's the announcement for the patch is due, your right. Not a problem. I just wanted to be sure I had the right info. Any news at this point is going to be welcome. i7 8700K @4Ghz, EVGA RTX3080 Ultra, 32GB RAM, Two 2K displays. Alpha Yoke, Bravo Throttle Quadrant, CH Pedals.
August 26, 20205 yr I have a Warthog Throttle and Joystick. In the alpha I was plagued by this 10 degree HDG increment issue. Although when I first started the alpha I was fairly certain I could use the HDG bug in 1 degree increments. Downloaded the release version and I was happy to see that I had 1 degree increments, looked like the issue was fixed for me. However yesterday I set up a flight in the C172 G1000 which I use on a regular basis and I was back to 10 degree increments. Fortunately I had only made 1 change to the controls yesterday. I finally got around to assigning buttons 27 & 28 on my Warthog Throttle to Gear Up and Gear Down. Cleared the assignments and I am back to 1 degree increments. This is 100% repeatable. So it appears the issue is a bug in making binding changes that invokes this 10 degree issue. I will file a report at the Zen Desk. Michael M System: AMD 9950X3D II Asus X670E Hero MB II 64GB 6000 CL30 DDR5 II RTX4090 II 2TB NVMe Samsung 980 Pro II EKWB CR360 AIO II Dell Alienware - AW3821DW 3840 X 1600 G-Sync Ultimate
August 26, 20205 yr On 8/24/2020 at 7:23 PM, Jetman67 said: That does not warrant a refund Not sure who you are to determine that for other people. But you are right, that alone may not justify a refund. For me it was a combination of all the issues (41 issues and no longer counting), plus the fact that they delivered terrible airplanes and sceneries on their “premium ultra mega plus “ version that I wouldn’t have paid $1 for. Quite honestly I am even considering if I should keep it running at $4 a month until this paid beta ends or 3rd party comes for the rescue.
September 22, 20205 yr Just saw this over on the official flight simulator forum. This looks like a really interesting way to fix the problem and be able to use the switches. I’m going to look into trying this. Credit to pjoerg over there I have found a workaround, using vJoy and Joystick Gremlin. If you are interested, please see - and share - the following link for details…https://drive.google.com/drive/folders/1kIJlzjDzELPxd2LpRxzlTmZsuqmXHB4F?usp=sharing AMD Ryzen 9950X3D | Asrock X870E Taichi | Gigabyte Gaming OC 4090 w/EK waterblock | Full Custom Loop Cooling | Corsair Dominator Titanium DDR5-6000 | Samsung & WD NVME/SSDs | Phanteks Enthoo 719 | Seasonic Vertex Gold 1200W | Keychron Q5 Max | Corsiar Scimitar Elite SE Wireless | Honeycomb Alpha and Bravo | Logitech Pro Flight Pedals | VKB Gladiator Pro NXT L&R handed | MiniCockpit MiniFCU | Alienware AW34DWF | Asus PG279Q | Win 11 Pro
Archived
This topic is now archived and is closed to further replies.