The jsf start switch
-
How about this attitude? The man contributed nothing but criticism.
That’s all, I’m not here to fight- in other news , I found during the reinstall, U3 changed something about the UHF backup, I referenced the other bugs here which were minor, like the resolution being capped to 1920 etc etc.
Something’s rotten, that’s three people with same problem, at least.
The way I fixed this, was by installing fresh, and runway starting a few times and auto saving. That seemed to fix it, when it was broken- waiting for audible ground sounds seemed to help. Something is happening because I’m using only keyboard, has nothing good to do with an analog throw . I may not have mentioned this but I didn’t make changes and then have problems, problems started after many hours of no problems. Than the JSF went screwy.
The other thing/ look I’m not religious and the evidence that this is an Orthodox Church is building, that’s all I’ll say. I’d really like to be a part of this community and hive mind but traditions are for stupid people, scientifically speaking. I hold nothing sacred .
-
like the resolution being capped to 1920 etc etc.
Hu? I’m running BMS on a 4K resolution since 4.33, still doing that with U3 without problem?
-
Hu? I’m running BMS on a 4K resolution since 4.33, still doing that with U3 without problem?
and I run at 8000x1440 - across 3x27" screens - no problem
-
How about this attitude? The man contributed nothing but criticism.
No he tried to help pinpointing the obvious, you fight it
That’s all, I’m not here to fight-
Yet that’s what you do. And even more when answering a mod that asks you to cool off.
Something’s rotten,that’s three people with same problem, at least
Rotten? Have you seen my remark about arrogance above, that’s my last warning before you taking a holiday sir
Some ppl worked for free so that you can call it rotten?3 ppl, even if this is right is nothing compared to the hundreths who can’t replicate your issue
The way I fixed this, was by installing fresh
proof AGAIN, that the issue is on your side
It’s been notified to you before, you refuse to listen -
Thanks for your help. I realy need to start learning the manual of the F16…
JSF switch works perfect. What did i do on your advise.
1. i activated the cutoff/Idle on the throttle
2. throttle calibration
3. Power to forward position
4. Fuel to norm
5. Hold the jsf several seconds until the green indicator lightens up.
6. After 20 pct , move the throttle to idleup to the next cable to make ( gear panel)
-
I get the feeling, English is a learned art here. That’s the only way I can account for the nerves being so hyper sensitive. You’re getting lost in translation. "Something rotten " is a well known English phrase, when you can google “BMS JSF” and you get the same problem in a Reddit thread.
If you feel it necessary to censor this narrative, that’s on your head. No one can explain why it stopped working, and was still on op on reinstall until after a few runway starts. If you feel like that is unimportant, act accordingly.
Cloud 9 as you say, didn’t help me pinpoint anything, he told me in lesser words, I altered files and shouldn’t have even posted, or how would you interpret his responses?
Such as : “this is devs problem?”No skin off my back.
-
I’m fairlycertain the fault is now sorted. Shall we close and move on?
-
i did mention the discrepancy between UHF backups in u1 to u3(U3 being non functional with AI and TOWER ATC), the resolution problems now upon reinstall, and the fact that the JSF switch stopped working in all aircraft which remains a mystery, but I always loved a little Roswell.
-
UHF backup comms work fine in all version of BMS 4.33.
-
i did mention the discrepancy between UHF backups in u1 to u3(U3 being non functional with AI and TOWER ATC), the resolution problems now upon reinstall, and the fact that the JSF switch stopped working in all aircraft which remains a mystery, but I always loved a little Roswell.
Can I point you to this thread detailing the sort of information etc you should be providing when making a bug report. Just saying it’s broken helps nobody. You need to indicate what your running environment is including any mods that have been applied to BMS, what version (update level) of BMS you are running, what you did that caused the issue, what you expected to happen and what actually happened. That’s the bare minimum information you need to provide.
Before you do any of this though you NEED to make sure you can replicate the bug in a clean install of BMS. Mods are provided by folks other than the BMS team and if a Mod has broken BMS you can expect the BMS Team to fix it. The responsibility lies with the person who wrote the Mod.
The “bug” might only show with a particular operating system.
It might be a bug with a Mod being run.
It might not even be a “Bug” but a misunderstanding of what should happen.