Quote:
Originally Posted by kimosabi
Fool proof suits me perfect. 
Thanks for all the time you spend on this, MikkOwl. |
It is becoming very tedious work now that I'm already finished with features but try to get 'user friendliness' into it, making sure people can use it. I developed a tool that scans EVERY axis on EVERY controller and detects if the user is moving them, then also figured out how to make the tool write the correct device and axis ID to the mikkonfig.ini.
I have so many extra G940 extra features only now though. Reversal bug fix, reversal bug fix AMOUNT for each throttle (and more axises too), option to use the two trims on the throttle as trims through my program as elevator/rudder trim, so that I can then process the axis data and remove the reversal bug, another option to set the range of movement of the trims in-game (they are way too sensitive if left at 100% range, impossible to trim perfectly to fly hands off).
Quote:
Originally Posted by Sokol1
For us that use MikkOwl multi-throttle and MODs, and dont desire disable HUD to not show boring "selected/unselected engines" messages, go to folder:
\IL-2 Sturmovik-1946\Files\i18n
Open the file (with notepad):
hud_log_ru.properties
And erase these messages in right side:
"Engine: Engine1 Selected" etc.
Leave the entries in left side (EngineSelect1...)
Now you see only % of power, ie 83%...
Sokol1
|
Sokol, that is GREAT stuff. For the same reason and more, I fly without hudlog except when testing for development reasons. Maybe with tweaks like this I can get rid of everything unecessary and just leave some basic things.