Jump to content

.list file created by Mission Editor (STEditor.exe) is empty


Recommended Posts

SAS_Storebror
Posted

Dear Devs,

 

Could you please have a look at this.

I have 5 Systems "under my hood", 4 normal PCs (3x Windows 10, latest Fall Creators Update, 1x Windows 7) and 1 acting as Dedicated Server (Windows Server 2016).

 

On the 4 normal PCs, I can't for my life get anything else but a 0-byte ".list" file saved from the Mission Editor.

On the Server, the .list file gets created as expected.

 

Steps to reproduce:

  1. Run STEditor.exe
  2. Don't touch anything, proceed directly to step 3...
  3. Save the mission (File->Save), with it's default name "MyMission" to the "data/Missions" folder.

On the "good" Server, this gets me a 276 byte ".list" file.

On the "bad" PCs, the ".list" file remains empty.

 

Reinstalling the whole BoS package on one of the 4 PCs for testing solved the issue for a single time, now it's back again with no changes.

Both Steam and "IL2_setup_BoM.exe" installs are affected.

 

Since there's no setting and no logs available for the Mission Editor, "John Doe" is left clueless here.

 

Cheers!

Mike

SAS_Storebror
Posted

Small Update:

On my Windows 7 PC I can solve the issue by uninstalling BoS/BoM and manually copying the "1C Game Studios" folder from one of the non-working (!!) Windows 10 PCs.

 

I thought I'd reinstall Visual C++ Runtime to be on the safe side, but to no avail, it doesn't solve the issue on Windows 10.

For the record, I have read that Visual C++ 2008 Runtime was required for BoS, so I installed the latest and greatest (Version 9.0.30729.6161 aka "Microsoft Visual C++ 2008 Service Pack 1 Redistributable Package MFC Security Update") from here: https://www.microsoft.com/en-us/download/details.aspx?id=26368

 

Currently I have a feeling like this issue could have been triggered by a Microsoft Update and it mostly affects Windows 10 Fall Creators Update.

Would be great to have a Dev's voice on this, but I'm afraid that this "Bug report" forum is too cluttered with other (user error?) messages to make any Dev become aware of real issues reported here.

 

Cheers!

Mike

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...