Upcoming Games

(UTC times)


Full list
Add a game

Upcoming Events

No events to display

Log file

You are here: Home > Forum > General > General questions, comments, and issues > Loader V5 > Log file

Page 1 of 1

Log file 06/02/2024 at 17:46 #155247
postal
Avatar
5200 posts
For those who keep copies of their log files in case they want to go back and check something in the future, a word of warning about the way that Loader V5 handles the log files. When the log file is getting near to 10Mb there is a pop-up before the main loader screen appears informing the user that the file is getting large and asking them to press "Ignore" to continue with the old file or "Retry" to start a new log file. My SimSig Loader0.log has now triggered this message.

IIRC starting a new log file in previous versions of the loader opened a new file with an incremented serial number (e.g. SimSig Loader1.log). Pressing "Retry" in v5.28 of the loader does not create a new file with a different serial, it overwrites SimSig Loader0.log with a new blank file SimSig Loader0.log losing any data in the previous large file.

Those who wish to retain the log for whatever reason will need to create a copy before going any further if they wish to use the "Retry" option.

“In life, there is always someone out there, who won’t like you, for whatever reason, don’t let the insecurities in their lives affect yours.” – Rashida Rowe
Last edited: 06/02/2024 at 17:47 by postal
Reason: None given

Log in to reply
Log file 06/02/2024 at 18:45 #155248
GeoffM
Avatar
6311 posts
The functionality has not changed since the Loader was released. The number is simply the instance of the Loader - if it can't open 0 (because it's in use by another Loader instance) then it tries 1, and so on, up to 9.
SimSig Boss
Log in to reply
Log file 06/02/2024 at 20:36 #155250
postal
Avatar
5200 posts
GeoffM in post 155248 said:
The functionality has not changed since the Loader was released. The number is simply the instance of the Loader - if it can't open 0 (because it's in use by another Loader instance) then it tries 1, and so on, up to 9.
My memory is clearly at fault then. I was convinced that previously a new incremented log file was created when the warning message was triggered. I've checked back as far as v4.0.0 from 2013 and the file is over-written (v3.248.2 doesn't generate the pop-up) so I don't know where my memory has gone astray!

Anyway, if you want to keep the log-file you need to create a copy.

“In life, there is always someone out there, who won’t like you, for whatever reason, don’t let the insecurities in their lives affect yours.” – Rashida Rowe
Last edited: 06/02/2024 at 20:54 by postal
Reason: None given

Log in to reply