[Csantucci]

I remember also a hidden .ini file for settings...

[cjakeman]

Weter, on 21 September 2021 - 06:43 PM, said:

What is Loading progress bar?
Is it customizable then?

When starting the activity|timetable|exploration, the loading image has a progress bar across the bottom.

The first time round, this just shows that something is happening but the timings are stored in this folder in a *.dat file. The next time that activity is loaded, the progress bar uses those timings to give an accurate indication of progress.

[Aldarion]

cjakeman, on 21 September 2021 - 06:40 AM, said:

Error: System.IO.IOException: The process cannot access the file 'C:\Users\AYUSH\AppData\Local\Temp\tmp5B12.tmp' because it is being used by another process.

I used to have similar message but with the *.TDB file.

[Weter]

@Chris
Thanks for answer: yes I noticed, that first time, the bar is shown in whole and rippled as a water surface for showing the player, that loading is not freeze, but after that, the same activity's loading is illustrated by white bar's progress. So, maybe if "loading timings" or so, would be mentioned instead of "bar" in that table above, it would more clear for users?

[dforrest]

I have raised this issue before but still see that it is not always implemented in the manual.

For example, in section 8.14.1 there is an example of a long include file which is shown in full. Following this is the note "Take into account that the fist line must be blank (before the include line)". This blank line is not shown in the example.

In other similar instances, there is not even a note concerning the need for the blank line.

[Weter]

Furthermore, that didn't work in my experiments.

[ErickC]

I noticed today that the air compressor no longer cycles. Either that, or the sound triggers stopped working.

[Csantucci]

Eric, try the Unstable release. The compressor should cycle there.

[cjakeman]

dforrest, on 25 September 2021 - 05:16 AM, said:

I have raised this issue before but still see that it is not always implemented in the manual.

For example, in section 8.14.1 there is an example of a long include file which is shown in full. Following this is the note "Take into account that the fist line must be blank (before the include line)". This blank line is not shown in the example.

In other similar instances, there is not even a note concerning the need for the blank line.

It's tricky. The processing that builds the manual automatically removes any extra blank line. I haven't found a workaround for this yet.

[Weter]

<blank line is here>