Print

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

[SAS~Storebror]

Patch Pack 302 has been released in 1st post.

New feature enhancement:

Code: [Select]

- SB-2 M-100 and M-103 playable nose gunner station added
New fixes:

Code: [Select]

- MBR-2 top gunner fixed
- SB-2 M-100 and M-103 Top and Ventral gunner fixed
- Cant Z-1007 bis Top gunner fixed
- All bomb/cargo/flare loads with parachutes fixed
- YAK-7 Center of Gravity issues fixed
Other updates:

• IL-2 Selector updated to Version 3.4.2
• IL-2 Common Utils update to Version 1.10

Mike

[SAS~Storebror]

Patch Pack 303 has been released in 1st post.

New feature enhancement:

Code: [Select]

- Animated FOV mod included as optional JSGME Module
- Enhanced FPS Display Mod included as optional JSGME Module
- Nvidia Screenmode Mod included as optional JSGME Module
- Enhanced Time Compression Mod included as optional JSGME Module
- Widescreen Mod ("Ecran Wide") included as optional JSMGE Module
New fixes:

Code: [Select]

- YAK-7 Cockpit location fixed
- When a house's dead mesh is not available, the game should proceed normally in case the house gets "killed" (without visual representation of the kill though)
Other updates:

• IL-2 Selector updated to Version 3.5.0
• Installation Process reworked

The Installation Process will now automatically disable all JSGME mods, delete outdated UP3 RC4 contents (like old il2fb.exe and old, non-RC4 JSGME options), perform the installation, activate UP3 RC4 and latest Patch Pack, and leave JSGME open to let you choose additional options.

This Patch Pack ships with the latest (and so far unreleased) IL-2 Selector 3.5.0.
This new Selector introduces a new Logging Mechanism called "Piped Logging". Details about this new logging are as follows:

Stock IL-2 uses a logging mechanism relying on buffered logfile access using Windows OS'es built-in file buffers to keep logfile access fast in most conditions.
However, this mechanism has two major flaws:

• When lots of data need to be written quickly, even buffered access causes slowdowns on IL-2.
  This happens for instance when there's a bug/glitch that causes repetitive logfile output, such as dropping parafrag bombs in Stock IL-2, which causes endless log lines written to inform you that a stretched mesh (the parachute of each bomb in this case) cannot have shadows.
• Most notably, when IL-2 crashes, the logfile will be truncated.
  This is particularly annoying because the relevant and much needed information about the reason for the crash would be at the very end of the logfile, but since that part has not yet been flushed from the filesystem buffers, exactly this valuable information will get lost.

For the second reason (truncated logs), years ago an "InstantLog" mod was developed which bypassed file system buffers by flushing, closing and re-opening the logfile after each line written to it.
This reliably solves the issue of truncated logfiles, but makes matters worse on the performance impact of massive logfile write accesses in short time.

"Piped Logging" brings the best of both worlds together.
A separate Process ("PipeLogger.exe") accepts log data from IL-2 at no time (literally!). IL-2 can run at full speed all time with no delays from any log output.
At the same time, PipeLogger.exe works independently from IL-2 and takes care of handling the log data, including a temporary in-memory buffer, and writing and flushing that data to disk absolutely reliably. For instance, if IL-2 crashes, PipeLogger.exe got all log data from IL-2 already (because it happens at no time) and keeps running until the last bits of log data have successfully been written to disk.

In order to use "Piped Logging", please set...

Code: [Select]

[Mods]
InstantLog=2...in your conf.ini.

You can find an outline of how the different logging mechanisms are working in the graph below:



Mike

[SAS~Storebror]

Just in case you're wondering how PipeLogger can be fast on one side and deal with slow file writes on the other:
It's heavily Multithreaded.

PipeLogger uses one dedicated Thread just to accept connections from IL-2.
Yes, connections, plural.
The logfiles created by IL-2 (so far we have logs.lst and eventlog.lst usually) are treated separately.
Each of them spawns a new thread in PipeLogger which solely deals with incoming data from IL-2 for that particular file.

Internally, PipeLogger runs another thread for each logfile being active, in order to put all incoming log data on an in-memory fifo buffer, implemented as a deque with focus on synchronized access among several threads.
That's necessary because on the backend (right hand side of the graph) where the slow file access happens, PipeLogger runs another thread per logfile again.
That thread only waits for it's deque to notify the thread of new data and once it receives such notification, it will write deque data (which is log data) to the logfile until the deque is empty, when it will enter a waiting state again.
Additionally, it will flush the created logfile at regular intervals if necessary (if new data has been written since last flush).

Got it?
So... how many threads do we have when IL-2 starts?
And how many when a mission is running?
The answer is "4" and "7".
Got different results? Don't understand what I'm talking of?
Doesn't matter


Mike

[printenduevel]

I only understand railway station! 

[SAS~Storebror]

It's all bohemian villages to you?
Our english is not the yellow from the egg today, let me tell you...
Anyway, life is no sugar-licking
Or as we Krauts like to put it: "Das Leben ist kein Ponyschlecken!"


Mike

[BalDaddy]

Marvellous stuff! (Not that I understood an iota of your posts Mike)
Being somewhat technically challenged, ( how did I manage to breed 2 sons involved in the most complex aspects of IT?) I've had trouble with patch & updates previously, so to watch it all unfold before my very eyes was wonderful!
Thanks to all involved.

[bomberkiller]

Mike, thanks a lot! 

Can I say you to you?

           

Gerhard 

[JG51_Ruski]

Is this for BAT?? When I went to install it it picked up on my VP ModPack install,,So I've held off for a bit until I grasp what to do

[bomberkiller]

Is this for BAT?

No!

It is for UP3RC4

[JG51_Ruski]

OK so it belongs in the vpmod pack ?? Sorry I'm a bit confused just trying to get going with the various setups..

[BalDaddy]

It's for those that have a UP3 install for 'flying' on the SAS server

[JG51_Ruski]

Thanks BalDaddy guess I borked my VP mod install ..Guess it's time to start over..BAT is running fine so far and got DCG running well..Think it's best just to stick to a simple stock install until i figure out what's going on..