EDIT - Sorry I didn’t realize that the SU9 hot fix was released. My install has a engines cfg that is from before SU9 so perhaps try renaming it to engines.cfg and see if it’s working again. Based on the release notes for the hot fix I wouldn’t expect a fix.
Look above. You need to set a dead zone of sorts for the throttle axis.
It’s possible the update hasn’t reached the Marketplace version yet. Does your version match 3.2.0? I can confirm the latest versions listed a few posts up, along with the amended engines.cfg file and an extremity deadzone do work properly. I have not tried them after yesterday’s hotfix though, but up to yesterday they were working.
hi, dead zones in msfs i guess, if set in joystick software settings dead zones means your 99% physical position will 100% virtual position. and if set in msfs physical 100% means 99% in virtual
I finally got around to trying the 104 out post-patch and the original engines cfg still doesn’t work, so the SU9 patch doesn’t address whatever bug caused the AB issues with this.
I sure hope someone fixes the engine issue when reaching 10000 feet because this plane isnt really usuable when you lose power…and i have 2 of them just collecting dust…
i’m not talking about absent thrust, just feeling afterburner don’t add thrust to max mil, not course acceleration and not speed+ after add afterburner. but may be just not so as in hornet and lightning.
The AB handles differently from the previous version, as the dev had to implement the old AB to get around this bug with SU9, however the performance is still the same, as I can achieve the same speeds. One thing that I am missing from the pre-SU9 version is the bleed off of speed when you come out of AB. Currently if you drop just out of AB, you’ll hold a ton of speed and the plane acts like it’s in super cruise, which from some pilot accounts is realistic, but it’s hard when you’re about to overspeed the plane and you can’t bleed speed fast enough.
as was before out from afterburn and entry in give some acceleration impulse, what you can feel by pov moves forth and back respectively. that was before and stay with hornet and lightning. so may be speed stay by this cause military power give you afterburner power, but afterburner give nothing + just take mil power at 100% then add afterburner - nothing. have to say is not very principal for me, almost all time i fly not more than 93-96% in f-35 and f/a-18 just take ff about 6 btw in 104 same ff at 95(?)
i think it can be problem about default afterburner for f/a-18 and we got some conflict. for example f-35 if we have settings for throttle 1 axis x reverse and x- for afterburner we and same for throttle 2 y reverse y- alternative aferburner. hornet works perfect. but f-35 in afterburner section start to jump off on and so gltching. so i just create two porfiles with afterburner binding and without. first only for f/a-18 osobo. withour for each another ac. but in 104 whatever profile you use same behavior. any out or in afterburner don’t give any feeling it go to accelerate or decelerate. another situation with this osobo implementation. you can bind afterburner to button and this start to works for f/a-18 only after throttles goes 100% but if you push that button in f-35 afterburner starts in any throttle position. so i think devs have to go around of sdk part of afterburner and create their own afterburner what will never ever cross with osobo afterburner. funny was i bind afterburner at gear brakes button, that was convenient if you wanna take up with afterburner you just push throttle forward and here you go. if without, just don’t push to the end. but in f-35 i had afterburner when i taxy to the runway lol. i think in 104 we got some same conflict when 104’s afterburner cross with osobo’s afterburner