BUG REPORT: ATO TE - Changing Flight Role causes Game to Hang/Crash
-
VERSION
4.34.2 (x64)BUILD
20805(NOTE: I did a “ATO BUG” search for this in the forums but didn’t see a title/thread about it.)
DETAILED DESCRIPTION
Changing the role of a flight in the ATO page causes the game to lockup/crash. This occurs regardless of whether creating a new TE, editing a pre-existing TE, or modifying the ATO from the “Commit” “Mission Schedule” playing of the mission.
Sometimes it locks up on the 1st attempt to change the role. The most flight role changes it took before the sim locked up was 8.
Sometimes when I waited for a minute or so for the game to -unlock- itself, the game self-terminated instead.
PICTURES
One attempt showing the game locked up and what I was doing at the time.EXAMPLE FILES
The TE that I was working on when first noticed this behavior.CRASH LOGS
None, not sure what would be useful. Please message me for any support files you’d like to see.REPRODUCIBILITY PROCEDURE
1. Tested this 5 times in a row by restarting BMS opening up a TE then the ATO page and then a flight role. The game hung each time.
2. Then I went to a second computer (same build, same HOTAS, but no Weapon Delivery Planner, different CPU and different video card) – and still the game hung.EXPECTED BEHAVIOR
To be able to change the role of a flight in the ATO.And thank you to all the folks that make BMS the best game of all time!
-
I confirm this one, been reported a couple of time a very long while ago as well on dev .
I just encountered this one by accident doing a TE I inadvertently clicked that down arrow in the ATO menu and a lot of work went down as the game crashedIt’s a reproducable CTD 100% of the time, it should be Prio1
-
Hi!
it should be Prio1
To me, prio1 is “showstopper”. Showstopper is when user has no way to avoid it and/or no workaround. There is a workaround => do not change task. If needed, suppress flight, re-add it. It is still on bug-tracker. No fix yet.
-
We had a CTD because of request formation landing
It was reproduceable
It could be avoided, just don’t ask formation landing
It was prio 1, It was fixedDon’t look for excuses, there are always ways to avoid a known CTD.
A reproduceable CTD is Prio1, yes it’s a showstopper, yes it’s should be fixed, just like any other CTDEven if you do whatever it takes to avoid it:
1. ppl might not know
2. As proven above it can still happen by accident, and it’s a pain.and btw, do you realise how painful it can be for a TE designor not to be able to change role as he designs his TE?
A pain that could be avoided if we weren’t looking for lame excuses like that
I perfectly understand the issue when we overlooked the bug, or forgot about it or had bigger fish to fry or even when we hadn’t time to fix it, but this:Showstopper is when user has no way to avoid it and/or no workaround. There is a workaround => do not change task
is just nonsense, sorry
Game CTD upon launch
=> don’t launch game, problem solved…
-
Don’t look for excuses
It is not a matter of excuses. It is a matter of having somebody willing of able to fix it.
I can’t fix it per say, but I can do something different to avoid the CTD (showstopper): I am gonna remove it from UI.
No more CTD. Problem “solved” (at least, no longer prio1).
-
Remove option to change flight role in ATO
This is a pure non sense as flight path generation depends on the role
Changing the role of the flight after its creation shall be avoided , plenty of variables will be not set up properly
Remove it from UI please
-
Remove option to change flight role in ATO
This is a pure non sense as flight path generation depends on the role
Changing the role of the flight after its creation shall be avoided , plenty of variables will be not set up properly
Remove it from UI please
In process by DJ
-
Clean (vanilla) 4.34.2 : I am unable to repro the CTD or the hung.
-
…
@Jp: Spent few hours on it looking for the UI resources about it. Wasn’t able to find it. I now believe it is barcoded.
-
Constantly removing FEATURES is also a way of “bugfixing”.
A way I personally DISLIKE!
-
Constantly removing FEATURES is also a way of “bugfixing”.
A way I personally DISLIKE!
Check JP post above. This “feature” is not working … Additionally, when you change flight task, it is only changing the name of the mission in Mission Briefing but it doesn’t change the other stuff (flight type, weapon loads, mission profile, track profile, action point, target assignation … etc …).
Better suppressing the flight then re-add the correct one. -
This “feature” is not working …
This works since eons without a hassle.
A perfect example of a bug.4.33 = ok
4.34 = bugNow, as we don’t find someone to fix it, we simply remove a feature.
Wise decision! aka DISLIKE!
-
This works since eons without a hassle.
A perfect example of a bug.4.33 = ok
4.34 = bugNow, as we don’t find someone to fix it, we simply remove a feature.
Wise decision! aka DISLIKE!
Kolbe, this is NOT the place to debate this subject
And yes , if we can not find someone to look at it and fix it , then it’s better to remove to avoid a CTD
That is just plain logic
If the problem is to find reliable people to fix it , that Is another subject to debate , but assaulting BMS developers on public forum by other BMS members will certainly participate to reduce our workforce !
-
This works since eons without a hassle.
It has ever never worked.
4.33 = no bug … correct. But this feature never changed the flight type, weapon loads, mission profile, track profile, action point, target assignation … etc … So it has never fully and properly converted a mission into another.
Now, as we don’t find someone to fix it, we simply remove a feature.
Wise decision! aka DISLIKE!
So lets keep the CTD then and deal with Red Dog’s reproaches.
I can’t suppress it myself anyway cause it is probably harcoded. So do what you want with it gents. I am off. (I don’t care because I am not using it because I know that this thing is not fully working and may cause CTDs).
Cheers!
EDIT: I’ve missed Jp’s post who replied to the point. Sorry about that.
-
-
Ok, so what does that tell you?
Sorry, I don’t understand buddy.
When I say : “No bug” … I mean … there wasn’t any CTD in 4.33 … But mission wasn’t properly modifed. Only the label in ATO, Briefing page and Frag Oder was changed … but action points wasn’t modified, en-route actions wasn’t modified, mission structures & profile wasn’t modified neither … etc … So an experienced used could maybe fix this manual by editing the entire flight plan (and according to Jp, maybe even AI brain could be effected and no working/initialized properly in 3D/2D … but Joe Pilot will just think that mission is modified into another role while the AI will (partially) act as in the first defined mission type. For example … create a BARCAP, change it into a STRIKE, change weapons if you wish … hit “FLY” => AI will fly a CAP between two station points.
Anyway … Either we keep this wrongly and which is inducing CTD*, or remove it, or one find someone to fix it. Jp say to should be kept. Now one have to one the one who think different and who will fix it.
- Now I can repro and after few further quick tests, I’ve noticed that CTD occurs when we keep the window open for more than few seconds on the non expended ATO window.
I wonder why I noticed it after 5min of test while nobody told us that this CTD happens only on the un-expended ATO window and only when no action during several seconds with the list open!?!
So … in case nobody fix it and nobody remove this (partial/not working) feature.
- Bad workaround: Use expended ATO list mode (Show all package set ON) to do this. As far as I can see, there is no CTD that way. (But entire mission is still not entirely modified).
- Proper workaround: Delete Flight, Add desired mission type. Now you have the correct mission properly set.
- Now I can repro and after few further quick tests, I’ve noticed that CTD occurs when we keep the window open for more than few seconds on the non expended ATO window.
-
@Red:
I confirm this one, been reported a couple of time a very long while ago as well on dev .
I just encountered this one by accident doing a TE I inadvertently clicked that down arrow in the ATO menu and a lot of work went down as the game crashedIt’s a reproducable CTD 100% of the time, it should be Prio1
Sorry … I can’t find you Bug report from you on the Dev Bugtraker. Found only the one from Malc and Radium. Details found above added on those ones.
EDIT: Found it. And found the one from ZipGun also (Four similar bur-tracker entry! … keeping the oldest, setting all other as duplicates)
-
All I’m saying is:
Remove bugs, not features.
Thank god I don’t have to justify myself for your decisions.
-
All I’m saying is:
Remove bugsI can’t.
And just to try to explain a last time (not for you Kolbe but for ppl who may still not have understood): this is not an achieved feature … it is an eternally incomplete function badly initiated. To sum up: the entire feature is “a bug” and never been a actual feature. It should be a complete suppression (including track) and re-recreation.Thank god I don’t have to justify myself for your decisions.
If you are speaking about the PM you are receiving from ppl, do like me, close you PM box. … we have nothing to justify to anyone.