Solved Impossible to move take-off time to less than 20 mins from current time in online MP campaign
-
On an online MP BMS 4.36 KTO campaign server, after fragging a flight in a non-HQ squadron, I am not able to move the take-off time to less than 20 mins from the current time. The UI will say something like “Flight has departed”.
This used to be possible in 4.35 on the same server.
Admins are currently unaware of what causes the issue, if due to BMS 4.36, server- or campaign config, so I’m asking on their behalf.
If it is configurable, how? -
@Logic said in Impossible to move take-off time to less than 20 mins from current time in online MP campaign:
omg!
Well not even weapons loadout can be modified within the 20 mins for that matter.
It’s a pita for players that want to quickly hop into an improvised MP flight.
Why not make it configurable at least?Weapons will be modifiable in U1 again ,
For the rest it is obvious you can’t change anything , that’s because the flight spawned already , so if you change take off time for instance , the whole ATC queue can be screwed
-
Investigating
-
@spooky Any progress in the investigation?
-
This is by design now. No more editing of flights in MP, other than weapons load-outs, within 20 min of takeoff. I’ll let a Dev explain it further, but it deals with the placement of the aircraft in the 3D world.
-
omg!
Well not even weapons loadout can be modified within the 20 mins for that matter.
It’s a pita for players that want to quickly hop into an improvised MP flight.
Why not make it configurable at least? -
@Logic said in Impossible to move take-off time to less than 20 mins from current time in online MP campaign:
omg!
Well not even weapons loadout can be modified within the 20 mins for that matter.
It’s a pita for players that want to quickly hop into an improvised MP flight.
Why not make it configurable at least?Weapons will be modifiable in U1 again ,
For the rest it is obvious you can’t change anything , that’s because the flight spawned already , so if you change take off time for instance , the whole ATC queue can be screwed
-
-
I disagreed with most of what the responses to the above feedback right up to the point when ATC was mentioned.
The reason ATC threw a spanner into the argument was that I recalled a number of times with ATC getting broken in 4.35. There were plenty of times that AI flights would just stack on the EOR not taking off. I never knew why, but I also haven’t seen that behavior in 4.36 so thank you for that.
That being said I think the solution should be to keep working on ATC to accommodate trying to push the flight time up. I’m not a coder or even computer literate but perhaps a fix can be to have the code check on departing flights, and if departing flight < or = X minutes from your flight plan a dialog box comes up saying “There is a flight conflict, please adjust takeoff time.”
I hope you devs keep working on this, I’d support the feedback that this is a sub optimal solution to the ATC problem just as much as I’d acknowledge ATC needed fixing. I would also support a fix returning the 4.35 functionality with accommodations to the other items that were impacted. I’d also support a server option to turn the ability to move launch time to <20 minutes on/off with a warning it could impact ATC and let folks decide for themselves.
PS-I don’t frequent the site too often and I’m not up to date on all the stuff here, I can say this was the second thread I came across which mentioned a change in 4.36 which wasn’t adequately documented in the change log. Getting that feedback more than once in a release should be all the feedback required to improve the process on the dev side to correct that moving forward.
-
@Buttons said in Impossible to move take-off time to less than 20 mins from current time in online MP campaign:
I disagreed with most of what the responses to the above feedback right up to the point when ATC was mentioned.
The reason ATC threw a spanner into the argument was that I recalled a number of times with ATC getting broken in 4.35. There were plenty of times that AI flights would just stack on the EOR not taking off. I never knew why, but I also haven’t seen that behavior in 4.36 so thank you for that.
That being said I think the solution should be to keep working on ATC to accommodate trying to push the flight time up. I’m not a coder or even computer literate but perhaps a fix can be to have the code check on departing flights, and if departing flight < or = X minutes from your flight plan a dialog box comes up saying “There is a flight conflict, please adjust takeoff time.”
I hope you devs keep working on this, I’d support the feedback that this is a sub optimal solution to the ATC problem just as much as I’d acknowledge ATC needed fixing. I would also support a fix returning the 4.35 functionality with accommodations to the other items that were impacted. I’d also support a server option to turn the ability to move launch time to <20 minutes on/off with a warning it could impact ATC and let folks decide for themselves.
PS-I don’t frequent the site too often and I’m not up to date on all the stuff here, I can say this was the second thread I came across which mentioned a change in 4.36 which wasn’t adequately documented in the change log. Getting that feedback more than once in a release should be all the feedback required to improve the process on the dev side to correct that moving forward.
Next time we will publish the thousands pages of the full changelog and you will do the summary by yourself
Thanks for your help proposal