4.09 - Support & Bug Reporting - Page 18

ZaltysZ · #**171** 02-16-2010, 06:27 PM

Quote:

Originally Posted by Arrow

I have a very strange sound problem that I wasn't able to solve for some days of trying everything possible and impossible. I am using soundblaster X-FI extreme as my sound card and win 7 enterprise OS. TO get EAX effects I am using latest creative alchemy and latest sound blaster driver. Everything works quite well appart from a bug that occurs in the following situation:

When I fly with a wingmen in any mission and I turn off my engine I can still hear my engine running, like my engine sound wouldn't turn off. When I hit pause and then unpause only silence remains as it should. I am of course running a clean absolutely unmodded install and I've tried all different sound settings and even older snd.dlls to no help. It doesn't happen without HW acceleration. I don't know if anything can be done about it, and I think that it is a bug in the sound engine.

Try "Duration=5" in Alchemy.

Arrow · #**172** 02-16-2010, 06:50 PM

Just tested it with different durations, buffer settings and even the downloaded new alchemy dll from M4T didn't help at all. I send wingman back to base and switch off the engine and the sound is still there.

MikkOwl · #**173** 02-21-2010, 12:45 PM

DESCRIPTION / SYMPTOMS

When using IL-2's native courves or deadband functions for joysticks, IL-2 in-game joystick will move away from true center if physical joystick is centered.

VERSIONS AFFECTED

Observed since at least version 4.08m. Mods or not does not alter outcome.

HARDWARE

WinXP-32 Home Edition (latest service pack). ASUS P5-B Deluxe with up to date drivers. Tested with older and newer drivers, including for USB. Tested with different USB ports and USB drivers, hubs vs no hubs.

TESTED WITH:
Logitech Extreme 3D PRO
Logitech G940
Logitech G25 Racing Wheel (!)
Saitek Quadrant
All devices tested with different versions of their corresponding drivers.

Was present from beginning, no mods. Have reinstalled completely fresh to make sure. Have deleted all config files for user and conf.ini for testing purposes.

TO REPRODUCE

Start IL-2.
Go to Hardware > Input
Change deadband for joystick pitch and roll to something so large it leaves no doubts (50% for example).
Move joystick around and observe the red input and green output squares in the monitor on the same screen. Move around some ways from center, and then center repeatedly, slowly and quickly, especially near and at center.

The red is where the user's joystick is, the green is how it is moved in IL-2 after being adjusted/filtered by IL-2. When moving it around the center, the green square is centered (since deadband means there should be no reaction at all in IL-2). But when centering the red square (actual joystick), the green moves approximately one pixel up and to the left away from center. Moving away from center, makes the IL-2 adjusted/filtered green square move INTO center again (where it should have been all along).

You may enter a cockpit on the ground and zoom in on the stick in the cockpit, and repeat the same movements. With a big deadband, the stick should not move at all when moving the stick around, only remained static in center. But it moves slightly (very little) to the left, and forward, when joystick is centered. Behaviour also visibly seen with rudder pedals and levers (if they use courves or deadband).

If using a normal no deadband & sensitivity courve (going from 5, 10, 15, 25 etc) you can observe this: moving away from center slowly, makes the IL-2 adjusted/filtered green square move INTO center first, until a certain point is reached (not far), at which it starts behaving completely correctly. Bug is only when near or at center.

NOTES

Affects every type of controller from various manufacturers.
Affects every axis that is bindable in IL-2 (trims, flaps, rudders).
Device calibration is irellevant. It applies even to axes and IL-2 things that have no center (throttle etc). If the red input square is centered, the adjusted green will move offset from center.
The offset is always to the left, or if the axis is vertical (like pitch) it is upwards.
The offset is seen only when any kind of deadband or less than 100 sensitivity is set at the center (i.e. the leftmost sensitivity slider in the hardware > Input screen). It does not affect the axes already set uniformly by default to be flat (like flaps, trims, prop pitch, throttles) but they too will display it if deadband or sensitivity is tweaked.
The offset bug is not visible in the third party IL-2 joy utility, but by using that utility, lowering sensitivity or having deadband near the center of any axis bound to anything (like flaps) can show that in game, the bug really does affect every single axis.
The only way to not experience this self-moving offset is to set the sensitivity to 100, deadband to 0 and use external programs to try to tweak in a joystick/device courve, such as dxtweak2 or the Logitech Profiler.
Reported by two additional individuals (lacking detail to verify). The rest either do not have the bug or they are incapable of that level of perception (users in forum tend to be unwilling to even test, and instead try to explain that it is just IL-2's realistic torque modeling that we are seeing).

Rubberchicken · #**174** 02-24-2010, 10:06 PM

Hi,

I installed the 4.09 patch and everything seems to work right. There is but one problem. If i'am in a quick mission or flighing an online mission i can't refly after being shot down or after landing. The "escape" button doesn't seems to work. The ony way to leave the game is by ctrl+alt+del.

AndyJWest · #**175** 02-24-2010, 10:40 PM

Quote:

Originally Posted by Rubberchicken

Hi,

I installed the 4.09 patch and everything seems to work right. There is but one problem. If i'am in a quick mission or flighing an online mission i can't refly after being shot down or after landing. The "escape" button doesn't seems to work. The ony way to leave the game is by ctrl+alt+del.

That's an odd one. I'd check you haven't accidentally configured the Esc key to do something else.

KG26_Alpha · #**176** 02-25-2010, 03:22 AM

In the conf.ini

[HotKey gui]
Escape=activate

Rubberchicken · #**177** 02-25-2010, 03:13 PM

Thanks Alpha, i wrote the lines into the config file and it works. Strange do that the entire line was erased after intalling 4.09m. The chapter [HotKey gui] wasn't even in the file.

MikkOwl · #**178** 02-25-2010, 10:42 PM

Quote:

Originally Posted by MikkOwl

DESCRIPTION / SYMPTOMS

When using IL-2's native courves or deadband functions for joysticks, IL-2 in-game joystick will move away from true center if physical joystick is centered.

VERSIONS AFFECTED

Observed since at least version 4.08m. Mods or not does not alter outcome.

HARDWARE

WinXP-32 Home Edition (latest service pack). ASUS P5-B Deluxe with up to date drivers. Tested with older and newer drivers, including for USB. Tested with different USB ports and USB drivers, hubs vs no hubs.

TESTED WITH:
Logitech Extreme 3D PRO
Logitech G940
Logitech G25 Racing Wheel (!)
Saitek Quadrant
All devices tested with different versions of their corresponding drivers.

Was present from beginning, no mods. Have reinstalled completely fresh to make sure. Have deleted all config files for user and conf.ini for testing purposes.

TO REPRODUCE

Start IL-2.
Go to Hardware > Input
Change deadband for joystick pitch and roll to something so large it leaves no doubts (50% for example).
Move joystick around and observe the red input and green output squares in the monitor on the same screen. Move around some ways from center, and then center repeatedly, slowly and quickly, especially near and at center.

The red is where the user's joystick is, the green is how it is moved in IL-2 after being adjusted/filtered by IL-2. When moving it around the center, the green square is centered (since deadband means there should be no reaction at all in IL-2). But when centering the red square (actual joystick), the green moves approximately one pixel up and to the left away from center. Moving away from center, makes the IL-2 adjusted/filtered green square move INTO center again (where it should have been all along).

You may enter a cockpit on the ground and zoom in on the stick in the cockpit, and repeat the same movements. With a big deadband, the stick should not move at all when moving the stick around, only remained static in center. But it moves slightly (very little) to the left, and forward, when joystick is centered. Behaviour also visibly seen with rudder pedals and levers (if they use courves or deadband).

If using a normal no deadband & sensitivity courve (going from 5, 10, 15, 25 etc) you can observe this: moving away from center slowly, makes the IL-2 adjusted/filtered green square move INTO center first, until a certain point is reached (not far), at which it starts behaving completely correctly. Bug is only when near or at center.

NOTES

Affects every type of controller from various manufacturers.
Affects every axis that is bindable in IL-2 (trims, flaps, rudders).
Device calibration is irellevant. It applies even to axes and IL-2 things that have no center (throttle etc). If the red input square is centered, the adjusted green will move offset from center.
The offset is always to the left, or if the axis is vertical (like pitch) it is upwards.
The offset is seen only when any kind of deadband or less than 100 sensitivity is set at the center (i.e. the leftmost sensitivity slider in the hardware > Input screen). It does not affect the axes already set uniformly by default to be flat (like flaps, trims, prop pitch, throttles) but they too will display it if deadband or sensitivity is tweaked.
The offset bug is not visible in the third party IL-2 joy utility, but by using that utility, lowering sensitivity or having deadband near the center of any axis bound to anything (like flaps) can show that in game, the bug really does affect every single axis.
The only way to not experience this self-moving offset is to set the sensitivity to 100, deadband to 0 and use external programs to try to tweak in a joystick/device courve, such as dxtweak2 or the Logitech Profiler.
Reported by two additional individuals (lacking detail to verify). The rest either do not have the bug or they are incapable of that level of perception (users in forum tend to be unwilling to even test, and instead try to explain that it is just IL-2's realistic torque modeling that we are seeing).

After more testing, I've found that it is not as apparent with using only deadband as I suggested using. When using only deadband to test it, it does move offset, but since the stick never returns to true center this is almost impossible to notice when in the cockpit visually.

So if anyone could please try the following method and I would be very happy.

REVISED STEPS TO REPRODUCE BUG

1. Set sensitivity of your roll and pitch in IL-2 to zero for the three leftmost ones, and set deadband to zero for both.

2. Step into the cockpit ON THE GROUND (do not be airborne since it is harder to verify) and zoom in on the control column/stick.

3. Move your joystick very carefully across it's center point, as if barely moving from center at all. What I see is that the column moves slightly to the left (just a bit) and slightly forward whenever the joystick is at true center. When moving away from it, the (cockpit) control column returns to true center.

If you have any external software to change the curves of your stick, set it to lowest sensitivity, as that will make it much easier to hit the centermost positions of the stick.

I just tried this with my Saitek Quadrant with nothing Logitech control-wise connected and the virtual driver bus interface disabled in the system settings even, and I observed the above.

I find it very unlikely that IL-2 would be any different on my computer compared to others', and it cannot be a hardware problem since it is only brought on by trying to use the IL-2 curves (Sensitivity) native to that application. The bug itself appears when a control input is at true center, which implies that there could be a coding mistake where the curve sensitivity processing is turned off if the controller is centered, as 'there is no need for it', and it re-engages as soon as the controller leaves center. But for some reason what is considered 'center' for the processed input is slightly offset, perhaps the exact same distance that is required for the controller to move before the curve processing is re-enabled again.