@kyros - Like FEW before you, I bid you farewell.

The most disrespectful and ego-driven character I’ve seen here authored this topic.

My serious questions and bug reports have always been met with courtesy and patience. Strange and mystifying how your experience seems so different.

But I do kind of understand why you should rail against something that has cost you so much to use.

The main thing I’m wondering about is your factual data source to support the notion that the Falcon BMS community is “rapidly shrinking”, if you care to share. How much and over what period of time? Just wondering, because my take is just the opposite.

@vfp said in Quick update from the BMS Frontlines - November 2021:

yes i think those of us that dont have access like few ,we deserve a screenshot or something as a preview

Perhaps English is not your native language. “Deserve” is a poor choice of words. “Appreciate” would be far more appropriate. The BMS Dev team owes no one anything-- we “deserve” nothing. We appreciate everything they do.

@DarkGable - If you have nothing accurate to say, please be a real man and not whine when you don’t apparently bother to edit your own words. I have not the time nor the inclination for THRR childish shit. Go cry to someone else.

@b0bl00i

Many, many years ago, Falcon BMS set out to make Falcon 4 better.

Over those many years, they have gone so far beyond that original vision that it’s safe to say that they have made Falcon 4.0 utterly amazing, and the more they do, the more they dare to do.

The Falcon BMS phenomenon is utterly unique. I’ve never seen another example of such enduring evolvement with no corporate structure and no money involved-- anywhere in the world in my 70+ years on this planet.

In previous versions of Falcon (perhaps up to about 4.33), mouse behavior in the 2D Map was much more user friendly. That is, if you wanted to zoom to a particular point on the map, you simply moved your mouse cursor to the point of interest and zoomed. Both the mouse and the spot on the map you were interested in would automatically move to the center of the 2D Map as it zoomed in. Very intuitive. Go play on Google Maps to see what I’m talking about.

That’s not how it behaves anymore, though. Now, if you want to zoom in to any particularly point on the map, you need to first grab and preposition the whole map with your area of interest as close to the center as you can estimate, then zoom, then correct, then zoom some more, then correct, etc. etc. etc.

No sure why the user-friendly method was abandoned during version updates, but it sure would be far faster, more convenient, and easier for the 2D Map user if the map automatically zoomed and centered to where the mouse cursor was placed. Just a suggestion.

@awmk1 said in ATTENTION: action needed for U3 update:

set g_sPriorityFixes “-76”

Seifer, if 4.36 doesn’t replace the prior Falcon BMS.cfg file, please put a post-it note somewhere on your monitor to remind us to delete that hotfix entry when possible. Thanks.

PS - Thanks, Mav

Falcon BMS team member Micro_440th suggested that documentation errors be provided in the following “bug format”:

Document:
Page:
Original sentence: “”
Corrected sentence: “”

Hopefully, this Topic will serve as a central point to make bug reports regarding the 4.36 documentation, as that would be a very convenient central resource for Falcon BMS team members who are responsible for the 4.36 documentation.

@Micro_440th - If you agree with this in principle, could you pin this topic?

Let me start with something I noticed the first day I downloaded 4.36…

BMS User Manual
Page 2-9

"To be able to run the 64-bit version of BMS you obviously need a 64-bit operating system. It is now advised to r

At the time of writing this manual Windows 10 x64 is probably the best choice of operating system for BMS."

As you can see, whatever was supposed to be after “It is now advised to r” is missing.

@kyros said in Done:

I’m absolutely done with BMS and the disrespectfull and egodriven characters in this forum and especially in the ‘development’ team. With each new release more bugs than new features are introduced. The fact that there have been (and still are) so many serious bugs in the most basic systems makes me wonder how many people fly this game in a realistic fashion. Actually how many fly this game at all in this rapidly shrinking community. There’s a serious lack of proper testing, wrong priorities and lack of documentation. Serious questions and bug reports are met with sarcasm, rude comments or completely ignored. This community is littered with ego and some individuals are really sick. Like many before me, I’m out.

Where I was born/raised (deep south Louisiana), we call this a hissy-fit. Or a brat-attack. Always amusing when grown people do it.

@VDK - Thanks!

@ Quasi - Thanks! I just added that Wiki link to my Falcon BMS shortcuts.

@Micro_440th - I’m going to take your suggestion and run with it.

Check out the ‘Documentation’ group shortly…

User Manual:

Page 2-14
“IVC config files is not compatible”
Should be:
“IVC config files are not compatible”

Page 3-26, bottom of page
“g_fSmartScalingThreshold defaults to 1.0 which is 1nm. Replacing 1.0 with 0.2 or 0.5 will provide no automatic scaling for objects closer than 0.2 or 0.5 Nm respectively and start the BMS Smart Scaling from that point”
Suggest instead, for clarity:
g_fSmartScalingThreshold defaults to 1.0. This means that SmartScaling will not begin until the object is 1nm away. You can make this value higher or lower, which will determine at what distance SmartScaling will begin

Page 9-192
“The ACMI conversion has been greatly improved, so you get from 3D to briefing much shorter.”
Suggest:
“The ACMI conversion has been greatly improved, so you get from 3D to briefing much more quickly.”
or
“The ACMI conversion has been greatly improved, so you get from 3D to briefing in much less time.”

@DarkGable - I think that’s great! I hope your forthcoming explanation makes more sense than your original question! I await with bated breath.

@DarkGable - If you have nothing accurate to say, please be a real man and not whine when you don’t apparently bother to edit your own words. I have not the time nor the inclination for THRR childish shit. Go cry to someone else.

In previous versions of Falcon (perhaps up to about 4.33), mouse behavior in the 2D Map was much more user friendly. That is, if you wanted to zoom to a particular point on the map, you simply moved your mouse cursor to the point of interest and zoomed. Both the mouse and the spot on the map you were interested in would automatically move to the center of the 2D Map as it zoomed in. Very intuitive. Go play on Google Maps to see what I’m talking about.

That’s not how it behaves anymore, though. Now, if you want to zoom in to any particularly point on the map, you need to first grab and preposition the whole map with your area of interest as close to the center as you can estimate, then zoom, then correct, then zoom some more, then correct, etc. etc. etc.

No sure why the user-friendly method was abandoned during version updates, but it sure would be far faster, more convenient, and easier for the 2D Map user if the map automatically zoomed and centered to where the mouse cursor was placed. Just a suggestion.

@kyros said in Done:

I’m absolutely done with BMS and the disrespectfull and egodriven characters in this forum and especially in the ‘development’ team. With each new release more bugs than new features are introduced. The fact that there have been (and still are) so many serious bugs in the most basic systems makes me wonder how many people fly this game in a realistic fashion. Actually how many fly this game at all in this rapidly shrinking community. There’s a serious lack of proper testing, wrong priorities and lack of documentation. Serious questions and bug reports are met with sarcasm, rude comments or completely ignored. This community is littered with ego and some individuals are really sick. Like many before me, I’m out.

Where I was born/raised (deep south Louisiana), we call this a hissy-fit. Or a brat-attack. Always amusing when grown people do it.

@kyros - Like FEW before you, I bid you farewell.

The most disrespectful and ego-driven character I’ve seen here authored this topic.

My serious questions and bug reports have always been met with courtesy and patience. Strange and mystifying how your experience seems so different.

But I do kind of understand why you should rail against something that has cost you so much to use.

The main thing I’m wondering about is your factual data source to support the notion that the Falcon BMS community is “rapidly shrinking”, if you care to share. How much and over what period of time? Just wondering, because my take is just the opposite.

Falcon BMS team member Micro_440th suggested that documentation errors be provided in the following “bug format”:

Document:
Page:
Original sentence: “”
Corrected sentence: “”

Hopefully, this Topic will serve as a central point to make bug reports regarding the 4.36 documentation, as that would be a very convenient central resource for Falcon BMS team members who are responsible for the 4.36 documentation.

@Micro_440th - If you agree with this in principle, could you pin this topic?

Let me start with something I noticed the first day I downloaded 4.36…

BMS User Manual
Page 2-9

"To be able to run the 64-bit version of BMS you obviously need a 64-bit operating system. It is now advised to r

At the time of writing this manual Windows 10 x64 is probably the best choice of operating system for BMS."

As you can see, whatever was supposed to be after “It is now advised to r” is missing.

@Micro_440th - I’m going to take your suggestion and run with it.

Check out the ‘Documentation’ group shortly…

@Micro_440th - Would it be possible to set up a post dedicated to allow users to submit documentation errors? I’ve run across dozens of mostly inconsequential errors, usually spelling, grammar, or syntax. Such a post would be a great resource for the documentation writer (whoever that is) to use in correcting/updating the documents.

@mjones - Maybe click the ‘Stop’ button to start the scenario running for a moment or two?