DTOS point of impact jumps during high-altitude delivery
-
We ran some more experiments, and we’re confident the problem is not related to ground intersection - the exact same problem happens over open ocean. We learned a few other
thats a ground intersection function issue.
Related to innacruacy in the different transformation in the ground intersection function that uses quaternions extensively.
it does not matter if terrain is flat or not,
it’s relatively well know, and it is very far in the bottom of our priority list (at least mine, dont kow for tumbler )
Edit : unless i fixed it already, but i dont remember well…4.35 is too old already
-
[…] The jumping - both when designating in DTOS with TMS up, and when slewing the TD box after designation - seems proportional to aircraft pitch. The steeper the dive angle, the larger the jump.
[…]As I predicted above
[…]
it’s relatively well know, and it is very far in the bottom of our priority list (at least mine, dont kow for tumbler )
[…]Ran into it for something else, so fixed it.
-
Edit : unless i fixed it already, but i dont remember well…4.35 is too old already
Don’t reference a build that we don’t have. (And probably won’t have for at least a year.) It serves no purpose and is extremely pompous.
-
Don’t reference a build that we don’t have. (And probably won’t have for at least a year.) It serves no purpose and is extremely pompous.
Fact is that everyone - with some knowledge of BMS community - know that current developpement is between 1.5 and 2 years ahead of current public version.
Fact is that this part of code has been modified In The last 2 years because was part of a bigger plan
Fact is that I communicate that I don’t remember if I fixed it or not , good news tumbler fixed it
So one the one hand when we don’t communicate we are tagged as arrogant , and when we communicate now we are Pompeus because we state for a fact that we are developing
Wow man !!!
You wish to have some news about development ?: be ready to discover that we can talk about things you will not see in the next 3 to 4 years
Sorry to be pompous I don’t feel I am
-
Fact is that everyone - with some knowledge of BMS community - know that current developpement is between 1.5 and 2 years ahead of current public version.
Fact is that this part of code has been modified In The last 2 years because was part of a bigger plan
Fact is that I communicate that I don’t remember if I fixed it or not , good news tumbler fixed it
So one the one hand when we don’t communicate we are tagged as arrogant , and when we communicate now we are Pompeus because we state for a fact that we are developing
Wow man !!!
You wish to have some news about development ?: be ready to discover that we can talk about things you will not see in the next 3 to 4 years
Sorry to be pompous I don’t feel I am
You are not, but you Devs have the Right to be as pompous as you like! You do the hard work! You deserve at least that. So …. Be pompous AND proud for the grate job you have been doing! :Yo:
-
You are not, but you Devs have the Right to be as pompous as you like!
That’s a very strange attitude. Treating those around you with patience and charity is important, no matter who you are or what you do.
Just as the devs work very hard to develop BMS, many members of the community spend their precious free time debugging problems, or building free tools. They do this out of a love for the game, and to help make the BMS experience that much better. I would hope there’s some mutual respect between everyone involved.
-
So, this is fixed in an upcoming version of BMS then? We can mark the issue as “Resolved” then… is this likely to be a “future Update” or a “future Version” type fix?
-
Well…
Whether you like it or not, we live in the future within the dev team. Development is about making sure a new code feature is stable and accurate enough for release…
Now, it is impossible to remember every bit of code given that there hundred of thousands lines modified between major versions…
It is what it is…
Hold your comments next time please, it serves no purpose here in the end.
Cheers
-
@Mav-jp said in DTOS point of impact jumps during high-altitude delivery:
Fact is that I communicate that I don’t remember if I fixed it or not , good news tumbler fixed it
4.37.3, this bug still remains.
How to reproduce:
- Start training mission 10 (GPbombs).
- Select AG mode.
- Select DTOS.
- Move the cursor and press TMS Up.
- Try moving the cursor.
-
@VirPilot I think your problem is that you’re not pointing at the ground when you first press TMS Up. Try moving the cursor to the ground and then press TMS Up. No problem then.
-
@jc1 The problem appears at high altitudes and at long distances from the aircraft. Try moving the cursor at altitudes > 20,000 feet and at long distance from the aircraft.
-
@VirPilot Even at high altitudes, 20K-25K, if I point at the ground first, I don’t have the problem.