Engines.cfg indeed did nothing. But maybe my issue is something else ? Let me explain exactly what I do:
I use XBOX controller, which is pushing it with F104, but still I doubt it’s source of the issue. I use no assistance beyond auto ATC and unlimited fuel.
I start at runway with engines running.
I start LNS and flick the generator 1 button, to remove all alarms, and align main artificial horizon.
I start with or without AB, after gears up / flaps up I turn off AB if it was on.
I use 30ish degree climb to 30k. I have like 300kts indicated.
I level up using autopilot altitude hold mode.
I kick up the AB. And in short while the ‘problem’ occurs. Last time I tried it happened right away, inside a second. The turbine spins down to idle RPM. Fuel flow drops to 0. Nozzle position is still fully open, and looking from outside there is still orange flame inside the engine, as if AB was on. I also lose all thrust. There are no abnormalities on any other gauge, inlet temperature is bellow 0, outlet is fixed on 6, it hardly moves at all during the flight.
When I decrease thrust just to turn off AB the turbines spins up again, fuel flow goes back near max, and I have back the non-AB thrust I had before.
I’ve watched several videos of people flying supersonic, mine just wouldn’t.
Sometimes the AB works for some time before it stops … it almost looks like there was something preventing me from going too fast ? But compressor stall should look different. And shouldn’t happen in this situation.
before topgun fuel flow at 93% show 6 now it’s going to 11 and stay there whatever i do after 75-80%. so what’s your secret? versions 1.2.0 fighter and 3.2.0 trainer
So it IS controller issue ! It applies to XBOX controller and keyboard. Both use buttons to set thrust (F2, F3 on keyboard). Keyboard can do it in smaller steps, but other than that both behave the the same.
I fly at 300kts at 30k feet, without AB. Now I start to click F3. There is one click where AB kicks in. Second click shuts down the turbine as I described above. There is still several click to go to the max thrust though. So if I hold the button to go to the max, turbine always shuts down.
With keyboard there is however indeed single click wide thrust position, where the AB works, and the plane will go supersonic and generally behave as expected.
With XBOX controller it’s basically impossible to hit the spot.
Sadly you cannot limit keyboard control not to go to full 100%, AFAIK.
now 104 react at mixture control, you can kill engine by move mixture axis to cut off. is it really only in my case fuel flow show 6 at 75% and go to 11 at 90? i create copy profile and remove afterburner. must be i have to create new profile from default, because in copy something still interfere with 104? i just need to know what is going on. you guys said now problem in market place version, but i use orbx versions for both models. please answer. what is that
i did everything. set default joy profile and add gas by f3. del 104 from community and install again from orbx. what could so hard break them?
p.s. exactly your numbers i saw before that was broken in my system. p.p.s don’t sure about exactly k about same
found one more thing. even after change profile and remove prop and mixture from axis. after restart msfs and check they aren’t present in control. i stay can kill engine by touch mixture axis, that was mapped.
del this c:\Users\name\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalState\packages\simskunkworks-aircraft-frf104g
use default profile there no more mixture axis for sure, because i can not kill engine by this. push *- buttons for brake and add f3 and got same 6ff at 75%. please help. where to dig? change ac to c152 out from game start game. without 104. add 104… nothing help. i try everything yet. i think that start after i binding afterburner to prop because this convenient to use with f/a-18 and darkstar. but default profile and del mention dir doesn’t help. i sure is not only me. and problem can to be solved, because other guys hasn’t this. i can wait update, but afraid what if after update this stuff stay with me. and must be not only with me. i hope you guys rework this for stop interfere with default afterburner and mixture and may be prop rpm or whatever can be yet. i think after that this problem will gone. but as i said. default profile for sure without mapped any axis and buttons stay give me 75% 6ff. please say something about this
Is working fine for me, scroll up, theres an engine.cfg to fix the fuel flows published a while ago, please, before claiming a problem, just try to read the rest of the posts.
looks like i have big problem with my brain, because i download this file before, just month ago, problem is start, when the file was installed. so must be my brain is ok if could forgot stuff that will not need after next patch or msfs update. i mean in this case. in general my brain absolutely bum bum
p.s. in any way thank you. hope this help, it’s may be something redownload original file. so i remember it works ok yet, then stop works ok lol
Hello,
MS told me that test phase is almost over, soon TF 104 G, FRF 104 G and G-91 should be update to latest version also in Marketplace.
Those version should fix SU9 old problem.
As soon as Asobo fix the >10K feet engine kill we will restore native afterburner.
/SSW
flight and engine model completed and tested
next step will be to animate external model and send it to the texture artist, after which we will proceed with cockpit modelling and system developing.
We do not expect to release it before October 2022
/SSW
Hm, found another weird thing. Most of the plane specific controls are mapped to obscure actions you wont need in this plane, and some actually never. But not all. Radar target select and radar lock are fixed … and even that behaves strangely.
First on my XBOX controller Y is always target select, even if I use it for Autopilot master toggle. Space also does target select, even if it’s by default mapped to move cockpit camera to upper position. Strangely if I remove this mapping, space stops working as target select.
Shift space also seems to be hardcoded, and it works, even if sim by default doesn’t use this combination for anything.
Can these mappings be changed somewhere ? Also do I understand correctly range and azimuth radar cursors are not implemented ?
why and how are you using an Xbox controller on PC ?
by chance you’re using it on an Xbox ?
this would be even more strange because it has never been released for Xbox and could not work with an Xbox because WASM is not yet enabled.
And… where did you get the F-104 package?
As far i know, MS does not distribute it.
/SSW
XBOX controller is normal Bluetooth controller, you just pair it with PC an it works.
It’s surprisingly good for MSFS, as MSFS is released on consoles and has decent controller mappings. Controlling your plane with tiny thumbstick can be an issue, it certainly is for F104. But for Cessna or A320 it’s perfectly fine. And you get another analog stick for camera. After few tries I can confidently land F104, I just have to trim it properly.
Every time I pull my big joystick I miss the camera controls the most. And I can’t have it on my table all the time, unlike XBOX controller.
So no, I’m not using it on XBOX
I got the single seat F104 on SimMarket.
I think Windows take the Y button as simply button 3 on Joystick 1. Which is what is used for selecting the target according to the radar idiot guide.
But why use MSFS events for everything, and use direct mappings for selecting and locking the target ?
Xbox 360 and Xbox One gamepads work natively on PC, just plug and play or use bluetooth and they’re pretty commonly used for a lot of games on PC. I use mine to control the drone camera sometimes in MSFS although I’ve never tried flying with it.
Hello,
much more clear now.
Unfortunately we can’t assure that all key mapping will work on Xbox controller, no test were done for it.
We are using “hw signals” (ie: space bar and , button 3 and 4) for selecting and locking target for practical reason since button 3 and 4 are located on top of all standard joysticks, i’m afraid that XboX controller does not generate such signals.
Other events such as mode, range, antenna tilt and gain are linked to unused sim events instead, antenna tilt can be linked to propeller switch axis as well.
I’m sorry guess we can’t solve your problem, I only can suggest to get a good joystick.
/SSW
When are we getting an update or fix? The plane has been unusable for over a month now, setting a deadzone on throttle is not a fix, and also the fuel burn is wrong without afterburner. Most other devs fix bugs in a matter of days or weeks…
