Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[UberDemon]

One way to see which items in a mission are incompatible with the current version of IL-2 you have running, is to look at the Log file (typically "log.lst") and look at the mission you loaded that had issues.  The Log file lists which objects are not present in the current version.  Whereas FMB+ tells you about each moving vehicle/object, the log file tells you about stationary objects as well.

Is there a way to have a feature that only extracts a manifest of what items are not compatible with the last mission loaded?  Something that produces a "lastmission.lst" file that contains a list of incompatible objects.

Maybe an entry in "conf.ini" or in the native IL-2 command prompt could have a feature that allows two choices:
1) List each unique object that is incompatible or...
2) List only the type of object that is incompatible (if there are 10 unique objects of the same class that are incompatible, only list the type of object once)

The list of incompatible objects would need to include at a minimum something like

Code: [Select]

The following items are NOT compatible with your current IL-2 version:
==========================================================================

[Map]
* MAP Endor/load.ini

[Units]
* rogue0120

//If aircraft are not compatible then weapons are not necessary
[Aircraft&Weapons]
* air.TIE_Fighter
* air.X_Wing

[Chiefs]
* 0_Chief Vehicles.Juggernaut 1
* 23_Chief Ships.Viking 2 1080 0 1.0

[NStationary]
* etc...

[Buildings]
* etc...

This would be useful for mission designers and modders alike to help in converting missions from different versions/releases.

[Frankiek]

there is a tool that is doing exactly what you are asking for is called the campaign validator

https://www.sas1946.com/main/index.php/topic,65584.0.html

You just need to point it to a campaign folder and then to the folder with your ini files and it will tell you what items in the mis files are missing in your inis  issuing a report for each mission in the folder

[UberDemon]

That is AWESOME.  Had no idea.  Will try this now.