Can anyone explain the concept of “SIMTIME” in version 3.2.3 in the log file when a scenario file is running, please. Here’s an excerpt…
[14:56:56 <<<2 EGPH_M_GND]
$CREGPH_M_GND:EGPH_GND:CAPS:ATCINFO=1:SECPOS=1:MODELDESC=1:ONGOINGCOORD=1:TEAMSPEAK=1:SIMULATOR=1:ICAOEQ=1
[14:56:57 >>>> EGPH_M_GND]
$CQEDDF_M_TWR:@94835:SIMTIME:20230414000106
[00:01:06 >>>> EGPH_M_GND]
$CQEGGP_M_TWR:@94835:SIMTIME:20230414002143
[00:21:43 <<<2 EGPH_M_GND]
$CQEGPH_M_GND:@94835:SIMTIME:20230414000000
[00:00:00 <<<2 EGPH_M_GND]
$AXEGPH_M_GND:SERVER:METAR:EGPF
I was EGPH_M_GND running a scenario for about an hour. A logfile over 2 million lines long was generated but can’t be replayed in PLayback Logfile connect mode. The clock in the connect dialog goes to 00:01:06 and never goes any further, presumably because of the break in timestamp sequence after that.
This makes it impossible to replay sessions - an extremely useful feature of previous versions!. Is there any way to prevent the logging of events from other scenarios?