Print

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

[SAS~Storebror]

6D4C5A79371FDE4B is 3do\Buildings\Russia\Piter\Kotlin\Kronstadt01\skin1o.tga
7EDDB82116B15423 is 3do\Buildings\Russia\Piter\Kotlin\Kronstadt01\skin1p.tga

Quite possible that the texture sizes differ, but "bigger" doesn't necessarily mean "better".


Mike

[SAS~Storebror]

Hotfix 18 has been released: https://www.sas1946.com/main/index.php/topic,67406.msg772282.html#msg772282

All reported (and confirmed) issues so far have been solved.
Some of the reported issues could not be solved because the reporters did not react on any questions following their initial (incomplete) report.


Mike

[Whiskey_Sierra_972]

Hi mates!

I'm pretty sure that I'll be the only one with this issue....lately I run out of lucky....

 

Just installed HF18 and tested new FOV setting a personal FOV of 120 degrees from conf.ini....but not have it working because the cockpit view start from the initial value of 70°....:

My conf.ini setings:

Code: [Select]

FOVAnim = 1     // 1 enables animated FOV transition, 0 disables animation (which is like stock game, immediate FOV change unanimated)
FOVMin = 5      // Minimum FOV value in degrees
FOVMax = 175    // Maximum FOV value in degrees
FOVSpeed = 200  // Speed of FOV transition in percent. Default 200 means "2x speed" animation
FOVDefault = 120 // Default FOV value in degrees at mission start time
FOVLog = 1      // 1 enables logging of FOV changes, 0 disables it

And here the resulting log....

Code: [Select]

[2023-06-01 18:33:15.447 UTC +2] dT:  141 startFOV=70.0, targetFOV=90.0, speedFactor=2.0, Steps: 20
[2023-06-01 18:33:16.848 UTC +2] dT:   46 startFOV=90.0, targetFOV=95.0, speedFactor=2.0, Steps: 5
[2023-06-01 18:33:18.000 UTC +2] dT:   39 startFOV=95.0, targetFOV=100.0, speedFactor=2.0, Steps: 5
[2023-06-01 18:33:19.176 UTC +2] dT:   39 startFOV=100.0, targetFOV=105.0, speedFactor=2.0, Steps: 5
[2023-06-01 18:33:20.347 UTC +2] dT:   39 startFOV=105.0, targetFOV=110.0, speedFactor=2.0, Steps: 5
[2023-06-01 18:33:21.431 UTC +2] dT:   36 startFOV=110.0, targetFOV=115.0, speedFactor=2.0, Steps: 5
[2023-06-01 18:33:23.742 UTC +2] dT:   77 startFOV=115.0, targetFOV=120.0, speedFactor=2.0, Steps: 5
[2023-06-01 18:33:25.541 UTC +2] dT:   60 startFOV=120.0, targetFOV=125.0, speedFactor=2.0, Steps: 5
[2023-06-01 18:33:26.488 UTC +2] dT:   32 startFOV=125.0, targetFOV=130.0, speedFactor=2.0, Steps: 5
[2023-06-01 18:33:27.396 UTC +2] dT:   30 startFOV=130.0, targetFOV=135.0, speedFactor=2.0, Steps: 5
[2023-06-01 18:33:36.334 UTC +2] dT:  299 startFOV=135.0, targetFOV=30.0, speedFactor=2.0, Steps: 30

From starting FOV after clicking increase FOV the first click give a 20° of increment while other give 5°....

[Whiskey_Sierra_972]

Another strange issue with conf.ini:

If I set the log output command as 'log_game.rtf' by no way after closing the game I have such log_game.rtf file but always the standard log.lst output....btw the mission log changed succefully (like all my other installations) into log_game.rtf....

When I change the command line in conf.ini at the exit of the game the engine furthermore revert it to the standard log.lst

When I set conf.ini as read only the game engine doesn't change the command line but the file output is always the standard log.lst

[Frankiek]

I am sure that the game engine can only output simple text files so being unable to comply with the command reverts automatically to the default log.lst

[Whiskey_Sierra_972]

I am sure that the game engine can only output simple text files so being unable to comply with the command reverts automatically to the default log.lst

Sorry but no mate...all my other installation conf.ini are set to output logs in rtf....and are doing that....

Moreover...the mission log output is in the changed rtf extension...only game log give this lock issue....

[Frankiek]

Always something to learn

[SAS~Storebror]

Another strange issue with conf.ini

I can shed some light on this.
Hotfix 18 intentionally applies fixed settings here:

• Logging is always enabled
• "LOGKEEP" is always 0
• The log file name is always log.lst

Simple reason is that after 15 years supporting other IL-2 users I got sick and tired of "I can't find any log.lst file" replies when asking for it.

Frankiek is right when saying that the game output is never true rtf (regardless the file extension) but always plain text.
If you want to be able to simply open the logfile in wordpad by double clicking on it, you just need to shift+rightclick on log.lst once, then select wordpad and tell windows to always open .lst files in wordpad.


Mike

[Whiskey_Sierra_972]

Roger Mike!

Now I understand why and is a worthwhile motivation!

I used to change the extension to rtf because of the more option in rtf than in simple notepad....

I can adapt to this condition without any clue....

Still wondering how can I set a 120° FOV....as my test doesn't manage to have it different from my previous logs....

EDIT

LAST SITUATION

Code: [Select]

FOVAnim = 1     // 1 enables animated FOV transition, 0 disables animation (which is like stock game, immediate FOV change unanimated)
FOVMin = 120      // Minimum FOV value in degrees
FOVMax = 120    // Maximum FOV value in degrees
FOVSpeed = 200  // Speed of FOV transition in percent. Default 200 means "2x speed" animation
FOVDefault = 120 // Default FOV value in degrees at mission start time
FOVLog = 1      // 1 enables logging of FOV changes, 0 disables it


Code: [Select]

[2023-06-02 11:20:10.543 UTC +2] dT:  146 startFOV=70.0, targetFOV=90.0, speedFactor=2.0, Steps: 20
[2023-06-02 11:20:11.579 UTC +2] dT:   34 startFOV=90.0, targetFOV=95.0, speedFactor=2.0, Steps: 5
[2023-06-02 11:20:12.108 UTC +2] dT:   18 startFOV=95.0, targetFOV=100.0, speedFactor=2.0, Steps: 5
[2023-06-02 11:20:12.445 UTC +2] dT:   11 startFOV=100.0, targetFOV=105.0, speedFactor=2.0, Steps: 5
[2023-06-02 11:20:12.669 UTC +2] dT:    8 startFOV=105.0, targetFOV=110.0, speedFactor=2.0, Steps: 5
[2023-06-02 11:20:12.875 UTC +2] dT:    6 startFOV=110.0, targetFOV=115.0, speedFactor=2.0, Steps: 5
[2023-06-02 11:20:14.445 UTC +2] dT:   53 startFOV=115.0, targetFOV=120.0, speedFactor=2.0, Steps: 5
[2023-06-02 11:20:14.662 UTC +2] dT:    7 startFOV=120.0, targetFOV=125.0, speedFactor=2.0, Steps: 5
[2023-06-02 11:20:15.773 UTC +2] dT:   37 startFOV=125.0, targetFOV=130.0, speedFactor=2.0, Steps: 5
[2023-06-02 11:20:15.993 UTC +2] dT:    7 startFOV=130.0, targetFOV=135.0, speedFactor=2.0, Steps: 5
[2023-06-02 11:20:16.185 UTC +2] dT:    7 startFOV=135.0, targetFOV=140.0, speedFactor=2.0, Steps: 5
[2023-06-02 11:20:16.374 UTC +2] dT:    6 startFOV=140.0, targetFOV=145.0, speedFactor=2.0, Steps: 5
[2023-06-02 11:20:16.592 UTC +2] dT:    7 startFOV=145.0, targetFOV=150.0, speedFactor=2.0, Steps: 5
[2023-06-02 11:20:16.772 UTC +2] dT:    7 startFOV=150.0, targetFOV=155.0, speedFactor=2.0, Steps: 5
[2023-06-02 11:20:16.989 UTC +2] dT:    7 startFOV=155.0, targetFOV=160.0, speedFactor=2.0, Steps: 5
[2023-06-02 11:20:17.184 UTC +2] dT:    6 startFOV=160.0, targetFOV=165.0, speedFactor=2.0, Steps: 5
[2023-06-02 11:20:17.363 UTC +2] dT:    7 startFOV=165.0, targetFOV=170.0, speedFactor=2.0, Steps: 5
[2023-06-02 11:20:17.575 UTC +2] dT:    6 startFOV=170.0, targetFOV=175.0, speedFactor=2.0, Steps: 5


[SAS~Storebror]

Yeah, I will have to check that FOV thing later on.
Quite possible that a default FOV outside IL-2's standard limits doesn't work as expected.
Note that the current implementation of the "animated FOV mod" was intended to be as unintrusive as possible, which enables it to "snap on" to many different game versions without any further ado. The flip side of that coin is that I had to play some dirty tricks in the CmdFov class to get all things done in that single class and not touch others (which would break the cross-version compatibility), and that seems to fire back here.
But no worries.
It's software.
We can do anything in software


Mike

[Whiskey_Sierra_972]

Rogre again Mike!

Is not a big issue for me....I can wait or live with in the meantime....

But you make me think a thing....

I'll check what happen if animation is set to 0....I'll report eventually different logs output....

EDIT

DIFFERENT LOGS when switching FOV at mission start with same conf.ini settings (only animation disabled)

Code: [Select]

[2023-06-02 11:30:41.880 UTC +2] dT:  138 startFOV=70.0, targetFOV=90.0, speedFactor=2.0, Steps: 20
[2023-06-02 11:30:42.140 UTC +2] dT:    9 startFOV=84.66565, targetFOV=95.0, speedFactor=2.0, Steps: 10
[2023-06-02 11:30:42.348 UTC +2] dT:    7 startFOV=95.0, targetFOV=100.0, speedFactor=2.0, Steps: 5
[2023-06-02 11:30:42.532 UTC +2] dT:    6 startFOV=100.0, targetFOV=105.0, speedFactor=2.0, Steps: 5
[2023-06-02 11:30:42.722 UTC +2] dT:    7 startFOV=105.0, targetFOV=110.0, speedFactor=2.0, Steps: 5
[2023-06-02 11:30:42.916 UTC +2] dT:    6 startFOV=110.0, targetFOV=115.0, speedFactor=2.0, Steps: 5
[2023-06-02 11:30:43.105 UTC +2] dT:    6 startFOV=115.0, targetFOV=120.0, speedFactor=2.0, Steps: 5
[2023-06-02 11:30:43.289 UTC +2] dT:    7 startFOV=120.0, targetFOV=125.0, speedFactor=2.0, Steps: 5
[2023-06-02 11:30:43.501 UTC +2] dT:    6 startFOV=125.0, targetFOV=130.0, speedFactor=2.0, Steps: 5
[2023-06-02 11:30:43.931 UTC +2] dT:   15 startFOV=130.0, targetFOV=135.0, speedFactor=2.0, Steps: 5
[2023-06-02 11:30:44.365 UTC +2] dT:   14 startFOV=135.0, targetFOV=140.0, speedFactor=2.0, Steps: 5
[2023-06-02 11:30:44.812 UTC +2] dT:   15 startFOV=140.0, targetFOV=145.0, speedFactor=2.0, Steps: 5
[2023-06-02 11:30:45.269 UTC +2] dT:   15 startFOV=145.0, targetFOV=150.0, speedFactor=2.0, Steps: 5
[2023-06-02 11:30:45.725 UTC +2] dT:   15 startFOV=150.0, targetFOV=155.0, speedFactor=2.0, Steps: 5
[2023-06-02 11:30:46.177 UTC +2] dT:   16 startFOV=155.0, targetFOV=160.0, speedFactor=2.0, Steps: 5
[2023-06-02 11:30:46.660 UTC +2] dT:   15 startFOV=160.0, targetFOV=165.0, speedFactor=2.0, Steps: 5
[2023-06-02 11:30:47.095 UTC +2] dT:   15 startFOV=165.0, targetFOV=170.0, speedFactor=2.0, Steps: 5
[2023-06-02 11:30:47.544 UTC +2] dT:   15 startFOV=170.0, targetFOV=175.0, speedFactor=2.0, Steps: 5
[2023-06-02 11:30:47.976 UTC +2] dT:   14 startFOV=175.0, targetFOV=175.0, speedFactor=2.0, Steps: 1


[SAS~Storebror]

With animation disabled the tool will basically just skip the smooth transition and jump to the end (target) FOV instead.
At least that's the theory
I have to admit that this switch made it into the mod just two days ago and you're kind of an alpha tester here.
That being said, our UP3 beta testing group is still enjoying their sabbatical (for 10 years and counting now).


Mike