March 17, 20215 yr 19 hours ago, fogboundturtle said: 3. Some users reports they are unable to map reverse thrust with Warthog X I think this is a known issue after Sim Update 3, a MSFS bug itself. Cheers, Ed Cheers, Ed MSFS2020 Steam // Rig: Corsair Graphite 760T Full Tower - ASUS MBoard Maximus XII Hero Z490 - CPU Intel i9-10900K - 64GB RAM - MSI RTX2080 Super 8GB - [1xNVMe M.2 1TB + 1xNVMe M.2 2TB (Samsung)] + [1xSSD 1TB + 1xSSD 2TB (Crucial)] + [1xSSD 1TB (Samsung)] + 1 HDD Seagate 2TB + 1 HDD Seagate External 4TB - Monitor LG 29UC97C UWHD Curved - PSU Corsair RM1000x // Thrustmaster FCS & MS XBOX Controllers
March 17, 20215 yr There are lots of problems with how hardware buttons map to actions in the CRJ. The most critical in my opinion are that flaps and spoilers can't be controlled with an axis, only with buttons. This means if you have real flap/spoiler controls (Bravo quadrant, Airbus TCA quadrant addons) you can't use them and need to map a button instead! The lighting switches on the Honeycomb Alpha also don't work so you need to manually switch lights on/off in the cockpit.
March 17, 20215 yr 58 minutes ago, Sinorm said: There are lots of problems with how hardware buttons map to actions in the CRJ. The most critical in my opinion are that flaps and spoilers can't be controlled with an axis, only with buttons. This means if you have real flap/spoiler controls (Bravo quadrant, Airbus TCA quadrant addons) you can't use them and need to map a button instead! The lighting switches on the Honeycomb Alpha also don't work so you need to manually switch lights on/off in the cockpit. That makes me think about those beta tests. Where are they?. Cheers, Ed Cheers, Ed MSFS2020 Steam // Rig: Corsair Graphite 760T Full Tower - ASUS MBoard Maximus XII Hero Z490 - CPU Intel i9-10900K - 64GB RAM - MSI RTX2080 Super 8GB - [1xNVMe M.2 1TB + 1xNVMe M.2 2TB (Samsung)] + [1xSSD 1TB + 1xSSD 2TB (Crucial)] + [1xSSD 1TB (Samsung)] + 1 HDD Seagate 2TB + 1 HDD Seagate External 4TB - Monitor LG 29UC97C UWHD Curved - PSU Corsair RM1000x // Thrustmaster FCS & MS XBOX Controllers
March 17, 20215 yr Not a bug, but omission maybe: the velocity vector on the HUD (whatever it's called) doesn't react to lateral motion. Said another way, in a crosswind landing, the velocity vector isn't displaced laterally. Overall, a great aircraft. I do see the red ladder appear on the speed tape when lowering flaps; not to contradict anyone. Richard Chafey i7-8700K @4.8GHz - 32Gb @3200 - ASUS ROG Maximus X Hero - EVGA RTX3090 - 3840x2160 Res - KBSim Gunfighter - Thrustmaster Warthog dual throttles - Crosswind V3 pedals MSFS 2020, DCS
March 17, 20215 yr Well never had one single problem with my Warthog Throttle in the sim to date using any other plane. But in the CRJ the throttle is dead, non responsive. When I push forward or back on the hardware throttle nothing happens in the sim. Sat here nearly 1 hour now trying to figure it out. Bug??? Literally just figured it out!!! You have to start the blooming engines to be able to "see" the throttles move!!! Hmmmm - now they non responsive again, offensive initials not allowed is going on here Edited March 17, 20215 yr by sidfadc Thomas Derbyshire
March 17, 20215 yr Author did you select Dual Axis ? https://fsprocedures.com Your home for all flight simulator related checklist.
March 17, 20215 yr Just now, fogboundturtle said: did you select Dual Axis ? And NOT (0-100%) EddieKABQ
March 17, 20215 yr 12 minutes ago, RichieFly said: I do see the red ladder appear on the speed tape when lowering flaps; not to contradict anyone. It only comes down to 230kts and it should drop down progressively with flap settings. At 230 is OK down to flap 20. Flap 30 should be 185 and flap 45 should have the overspeed cue at 170kts IAS. I’m also relatively sure the low speed cue checkers on the speed tape is not modeled right but need to test a bit more.
March 17, 20215 yr Author I put the flaps at 8 degree about 230kits and I didn't get a master alarm nor the red ladder. https://fsprocedures.com Your home for all flight simulator related checklist.
March 17, 20215 yr 8 minutes ago, haskell said: And NOT (0-100%) Nope because I don't use dual axis even though my hardware supports it. I use the other thrust lever typically for Prop assignment. I have my throttle mapped to THROTTLE AXIS in the sim because I'm only use one hardware lever - works fine in A320 and other aircraft which have 2 or more engines. Edited March 17, 20215 yr by sidfadc Thomas Derbyshire
March 17, 20215 yr It may be be me but I'm not getting glide slope capture and the indicator is way off? Is this because I have installed Navigraph data into the CRJ?
March 17, 20215 yr Author well. You do have to change your NAV Source to LOC1 https://fsprocedures.com Your home for all flight simulator related checklist.
March 17, 20215 yr 2 minutes ago, fogboundturtle said: well. You do have to change your NAV Source to LOC1 I did.
March 17, 20215 yr 21 minutes ago, sidfadc said: Nope because I don't use dual axis even though my hardware supports it. I use the other thrust lever typically for Prop assignment. I have my throttle mapped to THROTTLE AXIS in the sim because I'm only use one hardware lever - works fine in A320 and other aircraft which have 2 or more engines. On further investigation, I can see the numbers in the EFB - Throttle Calibration > Raw input Data actually move through the full range -16384 to 16384 when I push forward & back. However the actual throttles in the flight deck don't move at all visually??? Anyone else seeing this. EDIT: Ok top tip. The thrust levers do not move in the sim visually when you have the Thrust Calibration window open on the EFB. That was my problem all along! Edited March 17, 20215 yr by sidfadc Thomas Derbyshire
March 17, 20215 yr Bugs so far: 1. FADEC completely broken, thrust just reverts to whatever the sim thinks is full power in the climb, toga, and mct detents. It completely overshoots the target N1. Currently not possible to have realistic climb and takeoff performance 2. Airplane lifts off the runway before VR by itself 3. Duct pressure not effected by engine N1 or bleed system loads 4. Spoilers move even without hydraulic pressure. 5. Crazy pitch changes when engaging the autopilot 6. Really bad lnav tracking in tighter turns 7. Engines sluggish to respond to throttle input even at higher N1 8. No landing gear sound 9. Engines too loud at cruise 10. Wrong or really bad cockpit wind sound 11. Sometimes switches dont work. Other than that, its a really nice plane with a lot of potential once they iron out these bugs. Edited March 17, 20215 yr by Pilot53 Lian Li 011 Air Mini | AMD 9800X3D | Asus ROG STRIX B650E-F | Arctic Cooling Liquid Freezer II 280mm RGB | 2x32GB G.Skill DDR5-6000 | ASUS TUF RTX 5090 | Seasonic Prime Platinum 1000W | Pimax Crystal Light
Archived
This topic is now archived and is closed to further replies.