4.12.2 de-bugging

[Pursuivant]

Originally Posted by IceFire

Different model. I'm not sure... those are more accurate from a visual 3D standpoint at least.

I agree that the "short nosed" P-40 has a much prettier visual model and a much nicer looking cockpit, but its DM suffers from the same "one hit kill" to the engine, cockpit and coolant/oil coolant system as the later P-40s. My guess is that it was just copied from the P-40E-M model.

Flying the P-40C, I repeatedly get pilot kills by rifle-caliber bullets directly through the front of the of the cockpit at ranges of 50 m or more. That despite armor glass which was supposed to be proof against rifle-caliber bullets.

All this is based on lots of testing flying in arcade mode flying mostly against formations of rookie Ki-21, but flying relatively aggressively, just taking quick overtaking shots from the rear rather than high-side or frontal attacks. So, I know exactly where the bullets hit, where the bullets come from and what sort of gun is shooting the bullets.

My results are:

ANY hit directly through the prop spinner = instant engine kill. Despite the fact that a rifle-caliber bullet will not penetrate an automobile engine block at any great range, much less the block of a heavy engine.

Just about any hit directly through the front of the radiator = instant massive black smoke followed by the engine straining and dying within a few seconds. The quick engine failure might be realistic given the pressures and temperatures involved, but the massive black smoke is not. Instead, there should just be an oil leak or coolant leak effect, although IL2 doesn't model those.

Additionally, typically there is no engine overheat warning before the engine fails. For an oil or coolant leak, you should get a fast rise in temperature and an overheat warning first. Also, while the P-40 is normally very good about letting you run the engine for minutes after an overheat warning, the engine dies quickly after any sort of oil or coolant failure.

Any hit to the engine = massive black smoke and engine damage. Even for glancing hits by rifle-caliber bullets at long range.

Most hits to the front and bottom of the plane = fuel tank leak, even when it's a rifle-caliber bullet that has to pass through the firewall to hit the fuselage tanks. Furthermore, the self-sealing fuel tanks don't seem to work, so the fuel leak effect persists until you run out of fuel. And, mind you, this isn't against multiple hits, it's after just ONE bullet.

Any hit to the front of the cockpit = penetration to the cockpit and possible PK or multiple "X control destroyed" results, despite the armor glass.

Hits outboard of the P-40's guns, or even its ammo troughs, will occasionally result in a "gun jammed" result.

I can't tell you how many times I've had to abort a QMB bomber intercept mission with 1 P-40C vs. 16 Ki-21 because my engine was dead or dying, or because my pilot was killed, badly wounded or couldn't control the plane, but with less than a dozen rifle-caliber hits in my plane.

[Aviar]

Strange little bug. On the Kuban map, I can't get any AI planes to land on the airfield located in grid V-8.

When landing from the northeast, the planes will just keep circling. When landing from the southwest, they will attempt to land, but they crash into the hills before they reach the runway.

The funny thing is that they will land ok from the northeast on my HSFX-7 version. However, they still crash when landing from the southwest.

Aviar

[shelby]

navigation lights missing on lagg3's skin

[Aviar]

The following Japanese Stationary Objects as well as moving Vehicles cannot be padlocked:

-Japanese Type 94 Truck
-Japanese Type 95 Hurogane Car

*When these vehicles are in Japanese Columns, they also cannot be padlocked.
The three Japanese Columns that include one or more of these vehicles:

-Japanese Command Staff Column
-Japanese Transport Column I
-Japanese Transport Column II

Game Version: 4.12.2

Aviar

[Pursuivant]

It's impossible to kill the pilot when he's flying a P-39D-1, at least using rifle caliber MG and shooting directly through the cockpit windshield.

Additionally, the P-39D series seems to benefit from the following things:

* Far less prone to overheating than any other contemporary Alison-engined fighter (notably the P-40C).

* Far less prone to engine failure when the coolant system or oil coolant system is hit than just about any other plane in the game.

* Almost invulnerable to "control destroyed," "gun jammed" or "engine inoperable" critical hits.

Given the accuracy of the AI bomber gunners, the P-39D's remarkable durability, plus the cannon in the nose, makes the "Iron Dog" one of the best bomber interceptors there is!

More seriously, it would be wonderful if TD could take a look at the damage modeling for some of the other early-war planes (or maybe just the original IL2 models) like the P-40 series, the Bf-109E series and perhaps the early Spitfires, to make them much less vulnerable to critical hits by rifle-caliber MG fire.

As it stands, planes like the P-40 and the Bf-109 are "one hit wonders" where a single 0.30 caliber MG through the prop spinner kills the engine, a single bullet through the engine firewall or windscreen kills or injures the pilot or wipes out the controls, or a single hit elsewhere to the engine often results in massive smoke and quick demise of the engine.

[ECV56_Guevara]

Hey DT, still strange conection issues since 4.12.2, online.
Massive discos, game frezzing for all players (16/20 players) then game shut down.
Not any issue till 4.12.1, same campaign, same map, several hosts, same kind of missions. Maybe it s a bug since 4.12.2. It was like a domino effect.
the game saves any log of the crash to post it?

[Loku]

Bug report for Hs-123:main gear bug is fixed, thanx but markings bug is still there,left side of the fuselage dont display correct numbers or code letters.Iv made a little investigation:3D is ok, Overlays are placed in right order, bug is on java side, PaintSchemeFMPar00s class lack some references wich cause that.

[idefix44]

Originally Posted by ECV56_Guevara

Hey DT, still strange conection issues since 4.12.2, online.
Massive discos, game frezzing for all players (16/20 players) then game shut down.
Not any issue till 4.12.1, same campaign, same map, several hosts, same kind of missions. Maybe it s a bug since 4.12.2. It was like a domino effect.
the game saves any log of the crash to post it?

+1.

[KG26_Alpha]

Originally Posted by ECV56_Guevara

Hey DT, still strange connection issues since 4.12.2, online.
Massive discos, game freezing for all players (16/20 players) then game shut down.
Not any issue till 4.12.1, same campaign, same map, several hosts, same kind of missions. Maybe it s a bug since 4.12.2. It was like a domino effect.
the game saves any log of the crash to post it?

Make sure you have in the conf.ini
[NET]
checkRuntime=2
set on the server,
the client needs not to set this only server/host.

See if that stops the problem

[idefix44]

Originally Posted by KG26_Alpha

Make sure you have in the conf.ini
[NET]
checkRuntime=2
set on the server,
the client needs not to set this only server/host.

See if that stops the problem

I use the CRT=2 option on my 4.12.2m Dedicated Server.
And we have too the massive disconnections problem.

Some other more hilarious idea...