A suggestion for PWCG

[Yogiflight]

From what I understand, the game and therefore PWCG, too, stops a mission, and therefore its outcome, when the player ends the mission. I just had to do a forced landing on the next friendly airfield, after a squadmate didn't want me to shoot the next IL-2 down. After I had landed, I quit the mission, as the escort would have lasted about an hour or so and I, of course, didn't want to wait that long.  So the result of the mission is, we destroyed five IL-2. The bombers did not fly, there was no bomber shot down, nor any enemy fighter, because all this didn't happen anymore.

Would it be possible, that PWCG writes the mission to an end in a way the game's career mode writes the missions, the player doesn't fly in, just better, as what the game's career mode does, is pretty lame?

Of course I have no idea, how much work this would be. But I think this would be a cool addition to PWCG, as I always find it a bit dissappointing, that the story of missions, I can't fly to the end, just is not told.

[PatrickAWlson]

First scenario is telling a better story for events that actually did happen.  It's possible.  Maybe.  Not easy. I'm pretty sure that in game career mode has access to information that I do not have.  I really don't think that the logs tell the whole story.  In fact, BoX is significantly worse than RoF because RoF used to put flight path events into the logs for the players flight.  That was taken away in BoS for some reason.

 

That leaves me with ... I really don't know.  I'm not sure that I am in a position to ask for logging improvements.  I would like to have flight path and weapons release information.  

 

What you are talking about is extrapolating the story on things that didn't occur.  In the case that you point out I would probably say something like nice job on shooting down five IL2s but the bombers had to turn back for lack of escort.  Even there I would need better information from the logs.  if I now something should be in the logs if it happened, then I can determine that it did not happen by its absence.  If it's not there and never there, it's hard to extrapolate.

 

Take your story: did you shoot down 5 IL2s on the way to or from the target?  I have no way of knowing, so I cannot determine if your bombing flight actually reached the target and you completed the escort.

 

Edited March 5, 2020 by PatrickAWlson

[Yogiflight]

@PatrickAWlson thanks for your answer. As I posted, I don't know, how much work it would be or if it is even possible. I just thought it might be a cool addition, so I asked.

1 hour ago, PatrickAWlson said:

 I'm pretty sure that in game career mode has access to information that I do not have.

In game career mode doesn't anything more than PWCG. The mission gets told, until the player exits. What I meant about the career mode was just, that the career mode gives you a result for missions of the player's squadron in which the player doesn't fly himself. That was just, what I was thinking about, that PWCG could give a result for the mission the player quit after crashlanding or forced landing, how the mission might have been going on after the player exited,that seems reasonable. The results of the career mode missions, the player is not flying himself are very boring (usually one bomber or one bomber and one fighter, one or two trucks)

 

[Murleen]

On 3/5/2020 at 1:32 PM, PatrickAWlson said:

First scenario is telling a better story for events that actually did happen.  It's possible.  Maybe.  Not easy. I'm pretty sure that in game career mode has access to information that I do not have.  I really don't think that the logs tell the whole story.  In fact, BoX is significantly worse than RoF because RoF used to put flight path events into the logs for the players flight.  That was taken away in BoS for some reason.

 

That leaves me with ... I really don't know.  I'm not sure that I am in a position to ask for logging improvements.  I would like to have flight path and weapons release information.  

 

What you are talking about is extrapolating the story on things that didn't occur.  In the case that you point out I would probably say something like nice job on shooting down five IL2s but the bombers had to turn back for lack of escort.  Even there I would need better information from the logs.  if I now something should be in the logs if it happened, then I can determine that it did not happen by its absence.  If it's not there and never there, it's hard to extrapolate.

 

Take your story: did you shoot down 5 IL2s on the way to or from the target?  I have no way of knowing, so I cannot determine if your bombing flight actually reached the target and you completed the escort.

 

 

You could perhaps do it with "Objective" MCUs - these get logged when they succeed or fail, so if you had a secondary objective for "Bombers bombed their target", you could see that happen or not in the log.