Falcon BMS 4.35 U1 Wishlist
-
For me it’s the opposite, DX11 is a big step up. Graphics are finally as crisp and sharp as I thought they should be, which I never could quite get with the previous Directx version in Falcon regardless of graphical settings. I have a fairly high end graphics card (RTX 2070S) and I guess the more modern DX11 is more compatible with it. It also appears to run smoother on top of it.
Yep. Watched a HARM impacting a radar from inside my pit and it was impressive. Never remember such a flash in any previous version- and it was bright daylight.
And please @all: The dev team consists of people experienced in software development and the tools used in such an environment. There is no need to tell them what or how to do. It makes no sense to create another bug tracker eating the time of the dev team. Report all the bugs you find with a detailed bug report and wait until they are fixed.
And until those points are fixed that prevent you from actually flying 4.35 stay with 4.34 and wait for 4.35 U1. If there are none, enjoy 4.35.
I’m glad that someone takes his free time to improve this awesome flight sim and I really appreciate it. Just look at other commercial sims, lacking the depth BMS has to offer. -
You should not use time acceleration. Acceleration changes the outcome, frequency, and perhaps other things beyond my observations in 2D combat.
So we shoud not use time acceleration at all in campaign, and run it real time?
-
So we shoud not use time acceleration at all in campaign, and run it real time?
We ppl free … but you should not accelerate in game more than x2 or maximum x4 … or expect issue depending also on your system.
Same in 2D … avoid more than x16. -
you seem to be quite new to our community
Yes, and no. I usually just don’t get involved, but am more of an lurker. But I’ve been watching the F4 community, on and off, since 2001.
you should know that we never let the community down with nasty bugs…
just be patient, we know what we are doing , OK ?
Mav, I know you do, really. I know what it’s like, too. I’ve been in the core team of a major (like 100k downloads per release) open-source game project for five years. I know that users can get annoying, and that you’ve already forgotten about the current release by the time it hits the torrents when you’ve been working on the next one for half a year already. And that users have different ideas than you about what should be important and what shouldn’t. I know, I’ve been there lots of times.
But that’s why it’s important that your processes like bug and feature tracking are absolutely on point. They need to be transparent and discoverable. It will help you keep the users off your back. Just saying ‘open a thread and keep track yourself’ doesn’t cut it. Not only is that pretty awful as a technical solution, but from a PR standpoint it’s downright abysmal.
All I’m saying is that it just might lower the level of frustration on both sides. Which is important, because in the end everyone is doing this for fun. You won’t get rid of all annoyances. You’ll never be able to make everyone happy. Such is life. But you can help make it easier and more enjoyable for yourselves.
And with that I’ll be going back to lurking.
-
The teams fixes bug at an incredible speed. There would be an update every day if it was for every fix or feature.
EDIT: or several a day….
-
Yes, and no. I usually just don’t get involved, but am more of an lurker. But I’ve been watching the F4 community, on and off, since 2001.
Mav, I know you do, really. I know what it’s like, too. I’ve been in the core team of a major (like 100k downloads per release) open-source game project for five years. I know that users can get annoying, and that you’ve already forgotten about the current release by the time it hits the torrents when you’ve been working on the next one for half a year already. And that users have different ideas than you about what should be important and what shouldn’t. I know, I’ve been there lots of times.
But that’s why it’s important that your processes like bug and feature tracking are absolutely on point. They need to be transparent and discoverable. It will help you keep the users off your back. Just saying ‘open a thread and keep track yourself’ doesn’t cut it. Not only is that pretty awful as a technical solution, but from a PR standpoint it’s downright abysmal.
All I’m saying is that it just might lower the level of frustration on both sides. Which is important, because in the end everyone is doing this for fun. You won’t get rid of all annoyances. You’ll never be able to make everyone happy. Such is life. But you can help make it easier and more enjoyable for yourselves.
And with that I’ll be going back to lurking.
We dont have to explain the “why” of the bugs, since you wont understand them anyway, because you dont have the code so the only thing we can do is;
- thank you for bug report
- provide a repro case
or - known issue
And then you will know when it will be fixed in the next update.
If we dont want to fix it, we clearly state it in general
so now just be patient, we know what we are doing here and you dont need to know what we do since it’s usless
-
There is a bug tracker in this forum.
The section is here: https://www.benchmarksims.org/forum/forumdisplay.php?30-Technical-Support
and here is a marvelous guide how to help us help you: https://www.benchmarksims.org/forum/showthread.php?35644-How-to-make-a-bug-reportIt’s as simple as that.
In the internal team bug tracker there are things that will make it super hard to follow.
Developers look closely to this Technical-Support topic.
what we ask is just try to reproduce the bug so that is verifiable and an actual issue or bug. In many cases it was a mod or a theater or a settings thing.
Yesterday I was looking at something and I was about to report a stupid bug when I found out after 20 tests that it was my vga settings. The bug was narrowed and pin pointed down afterall and it wasn’t a all things are wrong with it, ending to a minor bug instead of a “major” bug.
No need to add more load to the team for things that are not verifiable or crystal clear, like I read in this thread the sim is dark… well m8 you have a brightness setting at your monitor and your vga, have you tried them? -
Given the capacity the devs have I would put none of those onto a wish list for a U1. Getting bug fixes for real issues such as Display extraction working reliable again, AC Spawn on top of each other in MP, or anything that relates to stability should be addresses in a U1.
Well it is a wish list after all. It’s always up to the devs of course if they want to do it at all or push it back. Scheduling is up to them. I’m just letting them know my desires here. Yeah I just encountered that spawning on top of each other issue last night too and I agree that one is priority. It totally ruined a flight for me last night.
-
Think about Smart Scaling
Fighter sizes are already realistic without Smart Scaling but as we see a monitor and not a real view, the Smart Scaling option provides realistic orientation detection.Same for MFD fonts.
Even if it is realistic in terms of font size on the MFD screen, it might not be realistic in terms of readability.
Even in the 4K monitor, Bullseye and cursor altitude range are hard to read.If you want the old fonts back, you can go into the 4.34 art/ckptart folder and there are some font folders. Copy them and paste them in the same folder as 4.35. Allow to overwrite
-
FPS improvement on “cockpit shadows” (it takes away too muuuch fps… regardless older or latest high end systems - we tried in Benchmark_TE)
-
@Hawkeye4040:
Well it is a wish list after all. It’s always up to the devs of course if they want to do it at all or push it back. Scheduling is up to them. I’m just letting them know my desires here. Yeah I just encountered that spawning on top of each other issue last night too and I agree that one is priority. It totally ruined a flight for me last night.
have you created a bug report?
-
have you created a bug report?
FL server owner have taken care to report those issues to the devs.
Reporting possible Bugs occurring on Coop Server and related to MP might be better to be handed of to the ones running those servers as they have the material i.e autosaves to create repro casesGesendet von meinem SM-G930F mit Tapatalk
-
It would be really nice to have the config option: “Use old MFD/DED fonts (might improve readability)”
If it’s as simple as copying a folder, just put this information in the manual and provide a download link somewhere.
-
This is not that simpe. As said on another thread old fonts can break other things and scrub efforts to get the correct MFD layouts (compared to RL one). It is not only a matter of font but also need code support.
-
???
When we say this is a known issue: it means we have acknowledge it already somwhere else : internal Btesting or Discord or any other communication means
That does not mean at all we want to hide anything
Status “known issue” means " we are working on it "
Have a look at the post I was replying to Mav. In your rush to defend yourself, you’ve attacked the post defending your position.
I’m not going to bother quoting you DeeJay, but the same remonstration applies.
EDIT: changed my mindNo! No you Blu3wolf
DO IT! TEST THE GAME? DO THE LIST? PUBLISH IT!
Come on !!! I AM DREAMING!
Reading you guys is depressive! What do you think?!? … We are at your service?
DO YOUR PART!
(me more and more sad and disappointed by the behavior this community :()
Changed my mind, it is worth responding directly:
One, it was very clear that I am saying the current position is that there is open communication, and that I was opposing a proposal that would change that.
Two, you want a public bugtracker? This is very easy to achieve. I can’t take seriously calls to “do my part”, though. In the last 8 years I have offered many times to do just that, and been rebuffed nearly every time.
-
Nothings and AFAIK nobody prevents anybody to make a thread listing the known issues if he wish.
We are hiding nothing, among active Dev, we just don’t have the resources to make such a list. That is all.
-
If you want the old fonts back, you can go into the 4.34 art/ckptart folder and there are some font folders. Copy them and paste them in the same folder as 4.35. Allow to overwrite
That did not change the font size.
It’s not the matter of font type but the hard coded font sizes. -
We are hiding nothing, among active Dev, we just don’t have the resources to make such a list. That is all.
You werent accused of hiding anything!
Nothings and AFAIK nobody prevents anybody to make a thread listing the known issues if he wish.
Okay, I will make such a thread.
Edit: The thread.
-
That did not change the font size.
It’s not the matter of font type but the hard coded font sizes.Isn’t it both? Perhaps it’s my imagination, but font type looks a bit different now. The biggest issue, like it was already mentioned, is the bullseye reading. Very hard to see now.
-