4.12.2 de-bugging

[gaunt1]

Its much more effective if used vs german planes, but indeed, ShKAS needs fixing. The problem is that you can fire it all the day, while doing minimal damage, just like the MG15/17 or .30 Browning. Seems like rate of fire isnt modeled properly.
ShKAS should run out of ammo very quickly, but in exchange, should do massive damage compared to guns mentioned above.

[Janosch]

Based on a test firing, QMB stats, wikipedia and calculations, I say that the ShKAS rate of fire is modeled correctly, at least on paper. But I would have to fire and hit with every round to be sure...

Gladiators may well feel overly strong, being able to fly while looking like Swiss cheese, but it's possible that nothing vital was hit. But it's actually like breakfast cheddar. You poke it and you get cheese on your fingers: firing from behind, you don't have the option to aim precisely at a weak spot. I thought I was aiming well with Cr.42, and shot at the fuselage, seemingly wasting tons of ammo, but a lucky close range short burst from a different angle took out the Gladiator's wing.

Wing mounted ShKAS are tricky weapons, especially with a plane that has poor gunsights, high instability and no elevator trim. The key is to set weapon convergence to much less than 150m and fire at close range. With a bit of luck and an angle that just exposes e.g. the target's engine, even a short burst does the job.
The problem is that even AI may start evading properly once you get to an effective range. And that imho is what makes early 109 sauerkraut guns (e.g. if the cannon is damaged) sometimes feel underpowered, too.

[Pursuivant]

Originally Posted by Janosch

Gladiators may well feel overly strong, being able to fly while looking like Swiss cheese, but it's possible that nothing vital was hit. But it's actually like breakfast cheddar.

Something that IL2 doesn't model, or model well, is the fact that many 1930s era planes which had fabric over wood or metal frame construction were actually quite resistant to gunfire.

Many bullets would just punch through or shred the fabric without hitting any part of the frame. Additionally, explosive rounds might not be triggered if they just hit fabric. Or, if they do explode, they just blow away the surrounding fabric with little actual damage to the airframe (since there is very little solid structure to contain the blast and increase its intensity).

So, it's realistic for planes like the Cr.42, Gladiator or Hurricane to still be able to (sort of) fly if their fabric is shredded.

Obviously, any hit of that sort will cause increased drag, though. Also, hits to the wings can easily cause strips of fabric to tear away due to slipstream effects, causing bigger problems in maintaining lift than the same damage to a monocoque or metal-skinned plane.

[sniperton]

Yep, but what about the Wellington? They do fly with 1/3 (or even more) of their wing surface gone due to MG hits. They are not like cheese, they're like flying skeletons.

[dlian]

Anyone noticed online style lag stutters when playing ntrk recordings of offline (ie QMB) fights? I didn't notice these odd stutters (eg recording playback skips quite a few frames like in online lag) before v4.12.2m - but I could be wrong.

My actual dogfights are very smooth averaging 120+ fps using the the built-in fps meter.

When I playback stock recordings like The Black Death, the stutters don't seem to appear. So the stutters seem to have been introduced by v4.12.2 perhaps?

It's a shame because I can't make nice smooth videos anymore.

Has anyone figured out how to fix this problem via some Win 7 settings?

[Ventura]

Not sure if this has been addressed, but the 'Radio Silence' box in the FMB doesn't have AI stay off the radio.

Or is it only supposed to keep AI from non-important chatter? When they get attacked, they're all over the net..

Was trying to use this as a decoy to keep enemy form hearing calls on friendly wave length...

[Pursuivant]

Originally Posted by Ventura

Not sure if this has been addressed, but the 'Radio Silence' box in the FMB doesn't have AI stay off the radio.

If the "radio silence" option just keeps AI from calling out things like course changes and waypoints, but still allows it to use radios in combat, that's realistic.

Radio silence is used to keep the enemy from detecting your presence. Once you're under attack or you attack yourself, the enemy has, by definition, detected you so there's no more need for it.

There actually need to be three options for radio use:

* No radio silence.

* Radio silence. AI only breaks radio silence when they attack or are detected or spotted by the enemy.


* No radio. AI doesn't use the radio at all. Necessary for planes that weren't equipped with radios.

[sniperton]

We have buttons for
pitch +/-
supercharger +/-
mixture +/-
etc.

Please, please, could I have a button for radiator- ?

[stovak]

Originally Posted by sniperton

Please, please, could I have a button for radiator- ?

+1

[sniperton]

We have HUD messages for actual
pitch
supercharger
mixture
throttle
etc. setting adjustments.


It would be great to have one for trim settings as well. Could be made optional, via config.ini.

Thanks