The in-game throttle motion does not correspond to the motion of my physical throttle (honeycomb). I have to push the physical throttle forward by as much as half an inch before the in-game throttle starts to respond. I tested the throttle response itself, it is correctly calibrated. But I remember I had the same problem with the CRJ, and there I had to calibrate my throttle inside the module using the EFB tablet.
Is that necessary for the BAE 146 also, and if so, where would I calibrate it?
A group of us has come across a bug. I didnāt read the entire thread, but it seems when there are multiple 146s in an area (like at an airport) the sound starts glitching and getting all choppy. Even if someone isnāt flying the 146 (but has it installed) they will experience this glitch. It only happens on multiplayer (obviously). Itās quite reminiscent of the sound bug the default F/A18 had when it was first released. It needs a swarm of about 5 or 6 people in the 146 to reproduce this bug.
a beautiful plane, very complete, I really recommend it, although I have some stutter in the cockpit view in general! Itās a bit strange since I have a 3080 TI and an i9 11900k and 128 gb ram, does anyone else have this? thank you
Just finished my 1st successful flight in the plane⦠my first one ended in disaster because I didnāt understand the SYNC button. But this time I ran into another problem; flying YVR-YXS the LNAV couldnāt keep a straight line. Or maybe I should say wouldnāt, as it would get established on the correct path, then turn hard left, fly off to the side, turn hard right, find the line again, get pointed in the correct direction⦠and repeat. Ended up flying the heading, and intercepting the ILS by hand, which worked a treat. And in my first flight it followed the LNAV just fine. Strange issue, but otherwise a great flight.
Flew patterns around Bristol for a few hours learning systems and getting key binds set up. Everything is working great s far and the VR experience is wonderful.
Looking forward to many hours in this aircraft.
Ah yeah, forgot that obviously with the trigger on the gamepad that wonāt work because it springs back.
As for having all 4 throttles on the one quadrant lever, that sounds like a good compromise, especially as the real plane lets you sync the four engines as well. You wouldnāt be able to start each engine individually though.
Anyone having an issue where going direct to a waypoint on the FMS, engage the LNAV the A/C just starts to turn left into a 30degree turn never going direct to the waypoint? even if you line it up on the track and engage LNAV it will still turn away
Did you hit EXE in FMS after selecting DIR to the new waypoint? You also need the HSI yellow switch on the front panel switched over to HSI/RNAV. and AP+LNAV mode engaged. It should work. Iāve had DIR to function working a few times now as I have had a few flight plan track issues relating to the start of the flightplan that required DIR to interventions to get the aircraft on track. Itās probably because of my unfamiliarity with the WT FMS - itās close to the CRJ but not quite.
Iāve also seen a few FMS āhangā like things where it continually says āworkingā after doing a change, but I find I have to hit āEXEā and itās then fine after that situation too.
OK, did my first ILS approach. For those that need to find out-
Use flightplan(VNAV) or manual (HDG) mode to get yourself lined up on approach.
Have ILS frequency dialed in to the VHF/NAV panel
Switch HSI (yellow switch) to NAV
When in range hit V/L to lock on to the LOC {you should hear a call out from your copilot} and localiser should be captured.
To capture G/S select GSL. {again you get a callout}
Manage flaps as per callouts and speed (much like the CRJ, it needs good throttle management on final.)
If Iāve missed anything let me know! Not sure if say the ILS frequency can be pulled automatically from the FMS in NAV mode, but manually dialing in ILS freq works fine.
Hi all. A new update is available, primarily targeted at fixing the trim axis issue:
v1.2:
Trim axis controls (elevator, aileron, rudder) - fixed
EFB fixes, including Navigraph authentication issue
NO SMOKING switch label typo - fixed
HSI course indication changing when thereās no electrical power - fixed
New JF_146.ini option added:
[HARDWARE]
THR_LATCH=0
ā0ā is the default value and is compatible with the Honeycomb hardware. Changing that manually to ā1ā (make sure the aircraft isnāt loaded at the time) will provide compatibility with the TCA hardware
Your instrumentation is not broken, itās just unpowered.
I flown the BAE yesterday and need more than half an hour to got through all switches and what to do to bring life to all that stuff.