Solved Speed caret bug
-
On the old forum was a thread about a bug in the speed caret:
https://www.benchmarksims.org/forum/showthread.php?41677-Speed-carret/page2&highlight=speed+carretIt was mentioned that the bug has been identified and will be fixed in 3 to 4 weeks but it is still present in the latest release. Hope it will be fixed in the next update.
-
I did a quick test and the caret was always visible if activated properly in my case. I activated it from the CRUS page using the ICP 0 (zero) button.
-
The thread is here too:
https://forum.falcon-bms.com/topic/20251/speed-carret
Remember 3-4 weeks is Falcon (even pre-BMS) for it will get fixed eventually since they are a community developers and do this on their free time. In that thread @Mav-jp says it is being addressed, it will be fixed. It was confirmed in a lull in releases since 4.35 is no longer getting updated and 4.36 will be released relatively soon, @Seifer said Q1 2022, which is a big deal that someone in BMS actually put a real time frame on a release! Ironically DCS community says 2-3 weeks as a joke too. -
Hi, according to @Mav-jp this is already fixed in next version 4.36.
Regarding time frame, I will give MY personal opinion on this, which is not necessarily the team official position.
I don’t like the 3-4 weeks joke. Nor do I like the sentence: “ask for your money back”. I hope you will never hear it from me, nor from other team member (but that is out of my control). I’ve been to the other side (player) and I know what it is to spend a lot of time on the sim and have absolutely no idea when a loved new feature is coming in, or a long standing bug gets squashed. On the other hand, speaking too much spoils the fun a bit as well. Finding the balance is an art.
Now, it is true that we don’t get any money out of this and we work on our free time. So yes, sometimes things get out of hand and less professional. But that does not mean we should act like that. We should aim high, even if we cannot get there.
BMS is not the first time I work for free, in fact, I regularly work on other free projects and I’ve done my share of contributions to the open source community. IMHO, working for free does not mean we can deliver low quality stuff, treat our users badly or play with people’s time. But yes, it is a good reminder that we, devs, deserve respect and sometimes we will not be able to fulfill all expectations.
I would try to be even more precise with our time frame. I’d say February 2022, but that is a bet. Q1 is safer and reasonable, don’t expect anything in January. Still, if things go wrong, we can get past that mark. But we will try.
As for the code state, we just stabilized most of the critical bugs (races, memory corruptions), now we are paying more attention to small details. Little by little, with the help of our testers, we fix those small things. Sometimes, a regression shows up, but it is becoming less common. As for the data side, I think it is mostly stable, with some additions still being made. But that is not my area, so I will leave this open for data folks IF they want to talk about it.
-
@seifer thanks for the update. I do really appreciate you being so open about your personal estimates and I won’t hold you to it! To even have a general timeframe is different than most times in the past, but we should all understand how sometimes projects can take longer than expected. We’re mostly all adults and have experienced that even if not software developers
-
@seifer you are a true champion, thank you for the infos you give us.
-
@dumba champions are the folks who maintained this for more than 2 decades. Those guys really deserve applause!
-
take your time as a team i mean , i really apreciate that you give your opinion and if you can give any info what we can expect in 4.36,wil there be any surprise? not the new terain obviously as this is planned for 4.37 as i have understood .
ty
-
@vfp hi, sorry, I cannot speak much about it, out of respect for our other devs who prefer to stay quiet about the work they do.
Visually, it is not that much different from 4.35. There are fixes to some graphical glitches and a totally new fog implementation (which does not make much different in the regular game, unless fog is dense). We have even published one screenshot for xmas, make sure to check the screenshot thread. There are some cool things there if you know what to look at…
Most of the changes in 4.36 are not visual, they are under the hood (AI, data and more avionics). There are changes, though.
But for me, the main thing is that work has been going on for a long time for 4.36 that is about time to release it. Because 4.35 had so many problems, we spent a great amount of time fixing it (and 36 as well, which shared those same problems and others). So 4.36 closes this gap and I expect that after it, things will go faster, since it is much closer to the next version than 4.36 was to 4.35.
-
I also think that the cross wind also causes:
- ILS steering cue not guiding you to extended centerline but offset
- Weapon release steering in CCRP requiring continuous correction in one direction when releasing perpendicular to wind direction (I would not expect this if ownship speed and altitude and cross wind remain constant) and this steering deviating significantly from steering in NAV mode
- Released weapons instantly displaced horizontally with respect to ownship
-
Hi there, I read about the speed caret issue. But what about TOS calculation? I try to keep the TOS via ICP CRUS meanwhile. But the speed, I would reach the right TOS with, is reducing the more I get closer to the next steerpoint, even if I hold the expected speed. After reaching the steerpoint and switching to the next one, the speed for TOS is higher again, so I can deal with it. An average value for TOS calculation would be great. What am I doing wrong?
-
@gryfinoxx From memory TOS calc is right. If you ignore caret and fly to make the clock right then you’ll arrive on time. By the way it’s not sufficient just to show up on TOS. You want to hit the TOSs at the scheduled groundspeed. If you do both at those together then the caret won’t jump on steer passage.
E.g. if you’re supposed to show up at 0900:00 with 480 GS and you’re on schedule to arrive on time but at 510 GS then you’re behind schedule. Fly faster or slower to “massage” your RGS to scheduled then resume matching predicted TOS. Then you’re both on time and on speed.
-
@frederf yes, you are right. Didn´t swith to GND speed before. Now it´s working properly. I can´t see the carret but if needed for navigation I can use the TOS over CRUS page to stay in time. Thank you.
-
Are you supposed to always be able to see the caret on the tape (if activated on the CRUS page) or can you be in a speed regime where it does not appear?
I ask because I have a TE where it does not appear but then again, I am well ahead of time according to the CRUS page. So can that cause the caret to not appear at all ?
-
@jayb no, not always. But if the TOS of my F-16 is close to ETA. With 2-3 secounds difference the caret should be close to my g-speed marker at least. Or exactly on it, if the ETA matches the TOS. But can´t see any caret, so it can´t be out of the scale.
-
@seifer said in Speed caret bug:
@vfp hi, sorry, I cannot speak much about it, out of respect for our other devs who prefer to stay quiet about the work they do.
Visually, it is not that much different from 4.35. There are fixes to some graphical glitches and a totally new fog implementation (which does not make much different in the regular game, unless fog is dense). We have even published one screenshot for xmas, make sure to check the screenshot thread. There are some cool things there if you know what to look at…
Most of the changes in 4.36 are not visual, they are under the hood (AI, data and more avionics). There are changes, though.
But for me, the main thing is that work has been going on for a long time for 4.36 that is about time to release it. Because 4.35 had so many problems, we spent a great amount of time fixing it (and 36 as well, which shared those same problems and others). So 4.36 closes this gap and I expect that after it, things will go faster, since it is much closer to the next version than 4.36 was to 4.35.
Thumps up to hose sucking. So much posibilities to epic fail
-
I did a quick test and the caret was always visible if activated properly in my case. I activated it from the CRUS page using the ICP 0 (zero) button.
-
@jayb ICP 0 at CRUS page. …Thank you mate. Did read the DED section of the avionic manual (TO BMS 1-F16CM-34-1-1) but missed this information. Found my way back to Falcon 4.0 after years, so I burrow my way through the basics again. Thy Seems I confused the mauals.
-
@gryfinoxx said in Speed caret bug:
@frederf yes, you are right. Didn´t swith to GND speed before. Now it´s working properly. I can´t see the carret but if needed for navigation I can use the TOS over CRUS page to stay in time. Thank you.
I didn’t mean GS HUD display. I mean looking at the DED for GS/RGS and memorizing the GS planned from the briefing.
-
@frederf yes, but helped me too in that situation.
-
-
<p>This isn’t solved. It’s still bugged.</p>