When asking for help with any kind of CTD etc.
its
mandatory to post the log, but:
how to get the log file?Open the conf.ini (find it in the root of your game),
then find the [Console] section and change there
this lines parameters :
LOG=1 --> change this to
1 if it is set to 0 (0: log disabled, 1: log enabled, recommended: 1)
LOGTIME=1 --> timestamp at the start of the log lines (0: disabled; 1: enabled, recommended: 1)
LOGFILE=log.lst --> name of the logfile, will be saved in the games root (recommended common standard: log.lst)
LOGKEEP=0 --> log gets cleared with every new games start: 0; keep the log: 1 (recommended: 0)
Only for 4.10 Users (DBW, Modact 3) - Don't install this if you have Modact 5/6, UP3, BAT, VP Modpack etc.Find here a handy mod by SAS~Storebror that allows you
to read the
log in real-time:
https://www.sas1946.com/main/index.php/topic,19308.0.html
When you want to post only the relevant parts of your log file in a reply please do this:Please shorten your log as the editor can handle only 50.000 characters per reply,
otherwise your log will be truncated! The beginning of the log is rarely interesting.
Interesting are all this Java error lines mostly reported at the end of the log file.
Java issues can be identified quite simply they all look similar to this one:
java.lang.RuntimeException: Can't set property
at com.maddox.il2.objects.vehicles.planes.PlaneGeneric$SPAWN.getS(PlaneGeneric.java:735)
at com.maddox.il2.objects.vehicles.planes.PlaneGeneric$SPAWN.LoadPlaneProperties(PlaneGeneric.java:761)
at com.maddox.rts.Spawn.get_WithSoftClass(Spawn.java:57)
at com.maddox.il2.game.Main.preloadStationaryClasses(Main.java:210)
....
Starting with some kind of exception followed by a lot of "at ..." lines.
If you happen to have some issue at game start time already, please try to identify the error accordingly (see typical java error above).
Flight Model related errors sometimes can be found when you look at your log.lst lines where all the plane's FMs are being loaded. The load order corresponds to the order of the aircrafts appearing in your air.ini file, so e.g. if the A-26B is the 101st entry in the list, it will be the 101st FM to be loaded in your log.lst and you should see the FM error somewhere around there.
Please make use of the 'insert code' option for easier forum reading!(to use this find the code # button, located at the top of the editor, above and
to the right of the crying face)!
Detailed explanation here:
https://www.sas1946.com/main/index.php?topic=39780.0see a example here:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~When you want to post all lines of the logfile we suggest to use: https://pastebin.com/See more detailed info how to do this (with pics!
) here:
https://www.sas1946.com/main/index.php/topic,39780.msg627220.html#msg627220
Author
Topic: Be able to look into the LOGFILE ! (Read 39420 times)
