Coop Campaign can't read AAR log file

[BatSpoggy]

As title, after completing a coop mission clicking combat report generates this message:

 

 

The log files are in the data folder and the missionReport(2022-07-14_10-23-50)[0].txt has the following line with the correct mission file path:

T:0 AType:0 GDate:1941.10.1 GTime:13:30:0 MFile:multiplayer/cooperative/Coop 1941-10-01.msnbin MID: GType:1 CNTRS:0:0,101:1,102:1,103:1,201:2,202:2,203:2,301:3,302:3,303:3,304:3,305:3,401:4,402:4 SETTS:1111000000100001001000011100010 MODS:0 PRESET:0 AQMID:0 ROUNDS: 1 POINTS: 500

Are coop campaigns working in this version of PWCG?

[PatrickAWlson]

Please press "Report Error" and post the zip file.

[BatSpoggy]

1 hour ago, PatrickAWlson said:

Please press "Report Error" and post the zip file.

I tried moving the log files around and ended up deleting them to see if that changed the error message, so I'll have to try to re-run it.

Ok, so this is after regenerating a 2-player coop mission. I hosted a local server and joined with only me and let the AI that took over the second slot take off before I hit escape and went "finish mission". I got the same error as before so hopefully it'll have the same issue despite only having one player and no real mission events.

Coop202207141507774.zip

[BatSpoggy]

I'm going to be away for a week or so on a work trip from tomorrow morning, Are you likely to need any more info to work out what the problem is here? I'll be away from my computer and unable to send anything, so let me know in the next few hours if you need anything else.

[PatrickAWlson]

That zip should do it

[BatSpoggy]

On 7/17/2022 at 6:25 PM, PatrickAWlson said:

That zip should do it

I'm back from my trip now. I was planning to run another campaign mission tomorrow, is there any way I can work around this problem?

[Stonehouse]

Passing thought. It has been a long time and I tend to tweak my startup.cfg so don't know if this section is standard or not but I see the below in my cfg file under the system area with the bold bits being the relevant items. This puts the logs in IL-2 Sturmovik Great Battles\data\logs and PWCG has no problem finding them. I have a vague memory of a PWCG enhancement from ages ago which was to read your startup.cfg to figure out where to look for logs.

 

Could your startup.cfg have a missing or bad reference? So in other words PWCG is looking in the wrong place for your logs because it is getting bad advice?

 

[KEY = system]
      bin_log_folder = ""
      chatlog = 0
      debug_info = 0
      debug_render = 0
      dlgbox_sky = 0
      gamelog = 0
      keep_binary_log = 0
      mgenlog = 0
      mission_text_log = 1
      modes = 1
      playoffline = 0
      reset_configs = 0
      reset_effects = 0
      reset_textures = 0
      sdebug = 0
      show_net_skins = 1
      skin_dir = "graphics\Skins\"
      text_log_folder = "logs\"
[END]

[BatSpoggy]

On 7/17/2022 at 6:25 PM, PatrickAWlson said:

That zip should do it

I seem to have fixed this on my own. It looks like the program didn't like me naming the campaign "Coop". I made another named "MP Hurricane" and it appears to be working fine. I had remade one named "Coop" and it still didn't work so it seems like the name is the issue. Maybe that name can be restricted in a future version.

 

4 hours ago, Stonehouse said:

Passing thought. It has been a long time and I tend to tweak my startup.cfg so don't know if this section is standard or not but I see the below in my cfg file under the system area with the bold bits being the relevant items. This puts the logs in IL-2 Sturmovik Great Battles\data\logs and PWCG has no problem finding them. I have a vague memory of a PWCG enhancement from ages ago which was to read your startup.cfg to figure out where to look for logs.

 

Could your startup.cfg have a missing or bad reference? So in other words PWCG is looking in the wrong place for your logs because it is getting bad advice?

My startup.cfg had this:

text_log_folder = ""

It didn't fix the issue (see above) but I changed it to text_log_folder = "logs\" and now it's putting them in the log folder rather than straight into \data and it's a lot tidier, so thanks for that.