2 indicator bugs
-
1. The real f-16 mach indicator range from 0.5 - 2.2 mach, but in the game the max range only 1.4 mach
ps The rpm indicator is not correct for the F110-GE-129 engine
There is a community bugtracker for issues in the public versions of BMS: https://bmsbugs.blu3wolf.com
Please feel free to log a report there.
-
I made a video of the rpm indicator bug.
-
Video is private. Can’t watch it.
Please, give all information about your install … mod, no mod? … which theaters? … etc … : https://www.benchmarksims.org/forum/…e-a-bug-report
-
Definitely something is jack up, your right indexer is covering the DED…
I take that back, needed to put on my cheaters.
-
the video now public.
This is bms 4.35u1 install.
No mod.
Korea theatre -
So … need a step by step repro case.
-
I maked a simple mission step by step.
Sorry for the video quality (bandicam free version)
-
This post is deleted! -
Anybody else able to confirm on a 4.35.1 ?
I can’t repro on my Dev version, so it is probably already fixed (?)
-
I cannot repro also on 4.35.1 EMF theater.
The needle is pegged at 108% at full AB. -
It must be tested on stock install, KTO, no mod. Otherwise the test is void (on Dev side at least).
-
Anybody else able to confirm on a 4.35.1 ?
I can’t repro on my Dev version, so it is probably already fixed (?)
it was never broken
-
I meant, “if it was” … for sure, it is no more on dev version.
-
I meant, “if it was” … for sure, it is no more on dev version.
it"s not in 4.35 , it was not in 4.34 nor in 4.33 nor in 4.32
-
-
-
I reinstalled the full bms 4.35u1 and the error was resolved.
I don’t know what could have caused the error during the first installation. -
Weird (but good for you).
However, do you remember if you had any mode installed?
And/Or (another possible source of issue that we should better know about if it is the case) did you installed the U1 patch over an existing 4.35.0 or did you installed the 4.35.1 from scratch? -
Weird (but good for you).
However, do you remember if you had any mode installed?
And/Or (another possible source of issue that we should better know about if it is the case) did you installed the U1 patch over an existing 4.35.0 or did you installed the 4.35.1 from scratch?told you….
-
Oky. Giving up.