Mission files created, but not "seen" by BoS?

[Bearfoot]

So, I installed this, set up the "startup.cfg" to save mission logs, selected available aircraft (actually, I had to select "all" because the graphics showing the aircraft and text were all messed up and I could not read anything), created a campaign etc. etc. 

 

I created the first mission, and then went into BoS ... but the mission did not show up under the "Missions" section.

 

I looked into the "data/Missions" folder, and it seems like the mission files are all there.

 

Is there anything I am missing? The aircraft I am flying is the Bf-109 F-4, which I definitely do have.

[PatrickAWlson]

Can you zip up and post the mission?  Sometimes an error in the mission will cause it not to appear as flyable.

[Bearfoot]

Attached is the "Missions" sub-directory.

 

Note that my game folder is "D:\Program Files\1C Game Studios\IL-2\data", with the PWCG directory located at "D:\Program Files\1C Game Studios\IL-2\PWCGCampaign".

 

Also, a mission log is created at "D:\Program Files\1C Game Studios\IL-2\data\missionReport(2016-07-19_02-45-38)[36].txt".

Missions.zip

[Bearfoot]

Hi Patrick,

 

Any update on this?

 

Thanks.

Edited July 21, 2016 by Bearfoot

[Bearfoot]

Ok, it turns out that the reason for this is that the assigned aircraft is a Bf-109 F2, which I do not have. Some trial and error got me into the F4, which I do have, and now the mission shows up.

 

The difficulty in specifying the available aircraft is due to the available aircraft graphics screen being glitchy. I have described this in a separate thread: http://forum.il2sturmovik.com/topic/24011-messed-iconscreen-arrangements-makes-it-difficult-select-air/

[PatrickAWlson]

I'm glad you figured that out because I would have run the mission and scratched my head .  I replied to the planes owned screen thingy in the other thread.

[Bearfoot]

I'm glad you figured that out because I would have run the mission and scratched my head .  I replied to the planes owned screen thingy in the other thread.

Sorry for contributing to the noise --- I know how frustrating it can be to get vague bug/problem reports that are difficult or even impossible to replicate due to insufficient context, misleading information etc.!

 

Thank you for your fine work with this add-on!