Id like the MIDS LVT added!

Internet security programs are, for the most part, an excellent way to damage your computer’s security.

Security in IT comes from secure operating practices, not installing some software then operating insecurely.

would be nice to get a version with a map and nav data waypoints, for radar approach control (human ATC potential)

@Warmoer:

I know it is possible, but without an SDK or published guides it is hard to say what exactly is possible.

You dont need an SDK to make 3D models, and there are published guides on this very forum!

Or, well. There were. I guess Im not sure if they survived the great Purge.

Introducing BMSBugs, a centralised community bugtracker for BMS.

https://bmsbugs.blu3wolf.com/

Easier to query than the forum for looking up specific issues. Easily accessible by browsers across whatever platform you are currently using.

@Dee-Jay:

No! No you Blu3wolf

DO IT! TEST THE GAME? DO THE LIST? PUBLISH IT!

Well, this is a community bugtracker, not a Blu3wolf bugtracker. If you know of a defect in BMS, but cant see it in the bugtracker, please feel free to add it. You can view bugs without an account, but account signup is is required to report bugs (requires email verification). Signing up allows you to report bugs, monitor the progress of your bug, as well as update it with further details, add attachments, and identify yourself.

Writing a bug report is pretty easy, follow the link and follow the prompts. If you want guidance on writing a good report, Nick has written an excellent post here. Keep reading below for more specific instructions relevant to writing a useful bug report.

You can file a report here. Thanks for doing your part to improve BMS!

Bug Report Checklist
1. Has this bug been reported already? Search to see if the bug is already known.
2. If the bug hasnt been reported, create a new report.
3. Describe clearly and concisely the actual behavior, and the expected behavior of the software.
4. Describe clearly, the steps to reproduce the behavior, or if you cannot reproduce the bug, the steps you took when the bug occurred.
5. Supply additional information to help clarify the bug, like pictures, logs, crash dumps, etc.
6. Stop and read your report before submitting. Can it be made clearer? Can you follow the instructions to reproduce the bug?

Bug priority versus bug severity
Bug severity should be set based on how significantly it affects your ability to use the sim. Options include feature, trivial, minor, major, crash, or block. Feature requests are the least severe ‘bug’. Trivial bugs do not affect your ability to use the sim - such as very minor graphics glitches rarely seen, or issues affecting the display of a menu which do not prevent you using that menu, etc. Minor and major bugs both affect your ability to use the software as a combat flight sim - for example, a bug preventing you from contacting AWACS would be a minor bug, while a bug preventing you from firing missiles would be a major bug. Major bugs have no workaround, while minor bugs can be worked around. Crash is for critical bugs - for example, bugs which crash or lock up the software.

Bug priority should be left as “normal” - the default value. Bug priority is decided on by the team, internally, and setting “high” or “low” priority on issues will not have any effect whatsoever on the team’s decision making process. Therefore, new issues should be set as “normal” priority.

Bugs in other theatres
Bugs in other theatres may be a bug in BMS’ code, or a bug in the data defining that other theatre. If you experience a bug in another theatre, before reporting it as occurring in that other theatre, try reproducing the bug in KTO. If the bug occurs also in KTO, it is more likely a bug within BMS.

If the bug only occurs in that other theatre, it can still be reported. In fact, there are separate projects here specifically for reporting bugs in other theatres, including ITO and EMF. You can use the drop down menu in the top right of the page to select whether you are reporting a BMS bug (in KTO), or another theatre bug.

You can visit the BMS project home page here, and the ITO project home page here.

Resolved issues versus closed issues
Issues which are marked as “resolved” will still be present in the current release. Issues marked as “closed” should not be present in the current version.

When an issue is fixed, the issue will be marked “resolved” and may have a target version set. When the issue is fixed in a public release, it will be marked “closed”. If you are searching to see if your issue has been reported already, this should include checking resolved issues. Resolved issues are fixed, but the fix is not yet included in a public release. Searching for closed issues may help see if similar issues have been reported and fixed in the past - sometimes fixes are not as perfect as we would like.

If in doubt, open a new issue - we can link the new issue, to the old one, if need be - and it may be that a bug that seems similar is actually a totally new bug, and not related to old bugs.

You can see issues fixed in the next version here. If you report an issue and it is fixed in a new version, we would appreciate you closing the issue when you confirm the issue is fixed. Thanks for doing your part to improve BMS!

Search the forum for Saitek X52 radar cursor ministick and it should be pretty easy to find, theres at least 2 or 3 threads explaining how.

err… 2TB you mean? I don’t know if anyone even made a 2GB NVMe drive!

@Warmoer:

I know it is possible, but without an SDK or published guides it is hard to say what exactly is possible.

You dont need an SDK to make 3D models, and there are published guides on this very forum!

Or, well. There were. I guess Im not sure if they survived the great Purge.

weapon effects is probably one of the lesser developed parts of BMS. Should be able to pull up hitpoints and damage data with the BMS editor.

mono does not, but you can use winetricks to install native SAPI5. I’ve been working with that to try get a System.Speech method working (in vatSys, an air traffic control client for Vatsim).

As regards the keypress stuff, I’m not entirely sure sorry.

@foxster:

Hoover,

If you’re up for the beta testing, I’ll add you to the distribution and send you a download link. Currently requires 64 bit windows with .net 4.7 or higher installed.

I mean, Im currently running software which requires 64 bit and .net 4.7.2 or higher… on linux. So it might not be so hard and fast as you might assume.

What licence is this under? If no choice has been made yet, may I suggest GPLv3?

@bbostjan:

No idea if this is true, but my logic says that empty fuel tank can be reused. Either at AAR during flight (can you refuel your fuel tanks midair???) or back at home base. It’s a piece of equipment that you don’t need to replace with new one.

Yes, it is possible to refuel the fuel tanks midair, provided they are depressurised.

@Frederf:

Why would that matter? You’re saying “keep the fuel tanks, the airplane will go that fast with them.” Doesn’t matter, more drag, more fuel burn, less fuel margin.

Those last three lines are the key bit - in general, the fuel gained by keeping the tanks tends to outweigh the potential fuel savings by ditching the tanks.

Exceptions obviously exist, Operation Opera for example.

Spooky, distinguishing between the “concept” and the “idea” is not meaningful in English - perhaps this is something that has been lost in translation?

@spooky:

available to the public eye

At least in theory, this is what should limit all such discussions on this forum, from a rules perspective.

It lets you fairly quickly appreciate where you need to get the nose, in order to establish lead for accurate snapshots out of plane. If you are in plane with the target, you dont really notice the difference.

Most Air to ground stores are limited to 1.2 mach and 600 knots for the store, which limits your ability to do 1.5 mach 150 foot penetration runs with ground stores. The TERs (when loaded) are limited to 550 knots or 0.95 mach (600 and 1.6 when empty - 700 knots in some configs). After dropping bombs, the remaining suspension gear (if no TER used) is limited to 700 and 1.6, and the tanks suspension gear, to 750 and 1.6.

The fuel tanks on the other hand are 600 and 1.6, so Im not seeing why the fuel tanks are the issue with a high speed low level penetration?

Okay, the funnel doesnt show the projected path of the shells. Thats the misconception.

The Firing Evaluation Display System (FEDS) shows the projected path of shells fired, and is used in level II (no lock). In level III and up, the Bullets At Target Range (BATR) symbol is used instead to show where bullets passed the target.

In level II and III, the funnel works very similarly to with LCOS. It does NOT show where the bullets will travel. In levels II and III, it shows a range of valid solutions for the current normal acceleration (G) in plane, with the wingspan currently selected being used as the gap between the lines of the funnel. In level IV and V, the funnel is in the targets plane of motion (POM) rather than your POM.

Thing is, your target isnt maneuvering, so picking their plane of motion is a bit of a crapshoot.

I guess Id suggest having another look at the EEGS symbology levels explanations, particularly the explanation of how the funnel works? The short version is that the funnel isnt showing you where the bullets will go, its showing you how much lead you need - and once you have a radar lock, it starts showing you the lead in the plane of motion of the target - which is VERY useful for figuring out how much lead you need to pull when you are not in the targets POM, such as for snapshots.

For abnormal situations, one useful thing you can do real world is point out your needs to ATC: Seoul Tower, Falcon 1 requires RWY 01 due heavyweight.

I guess that could be a neat improvement to have for the ATC code at some stage, although Id imagine this would have a little complexity to the arrivals process.