4.11 General debugging

[Aviar]

Originally Posted by Lagarto

Could you possibly provide a quick fix for the new lighting effects, namely restore the old ones? The new "changes to darkness of night" are terrible. I have to skip every third mission or so because it's too dark to fly. The sky is strangely dark with white clouds or the other way around. Clouds are occasionally solid brown, or white on top and coal black when you look at them from below. Quite distracting.
Yes, I know it's been reported before.

Of course you are correct. This problem has affected a number of my coop missions. As you mentioned, DT is aware and so there is not much more we can do.

I think we need to be patient and let DT handle the situation. We all want 4.11 to be perfect, but these things take time. Hang in there.

Aviar

[RPS69]

Originally Posted by Lagarto

Could you possibly provide a quick fix for the new lighting effects, namely restore the old ones? The new "changes to darkness of night" are terrible. I have to skip every third mission or so because it's too dark to fly. The sky is strangely dark with white clouds or the other way around. Clouds are occasionally solid brown, or white on top and coal black when you look at them from below. Quite distracting.
Yes, I know it's been reported before.

What's wrong with this? Clouds do look clearer from top when there is a full moon. And IL2's nights are always full moon...

[Lagarto]

Originally Posted by RPS69

What's wrong with this? Clouds do look clearer from top when there is a full moon. And IL2's nights are always full moon...

The start of the mission is at 14:15 (02:15 PM), that's what's wrong with this.

[Treetop64]

--- Removed and placed in the AI Debugging Thread ---

[6BL Bird-Dog]

Flying the Beaufighter on the Burma map both Pedro & myself had grey square patches on the cockpit glass instead of the bullet holes.

Also Would it be possible to put a map dimmer in the next update as in night flights the regular lighting on the map messes up your night vision ?

[Luno13]

This is a bit old, but I was wondering if we could get a proper configuration file for the i-15 in order to select whether or not it carries wheel spats. I think a few other planes are missing this feature, but I can't remember which.

[Luno13]

This is achieved by pressing Shift F1 from the bomber's chair



Iron sight is kinda useless on the MC 202 (not a good photo, but the aim point is too high)



Large hole in the Yak-9

[Luno13]

Tanks driving under a bridge:



Tail-wheel retraction issue:



In the Bf-110, the damage pattern in the wingtip disappears as the camera gets closer. I did not realize anything was wrong with my plane until I zoomed out!



I've heard it said that the default camera position in the Tempest is too far aft which makes the headrest appear too large.

[Whacker]

I'm unsure as if this is the right thread or not. If it's not, then I trust the mods will move it as necessary.

I have a part-question/part-seemingly bug/possible feature request to report on.

When I'm flying in offline campaigns in career mode, I've noticed a number of times that I've shot the bejeezus out of other aircraft, yet not been given kill credit when they go down. I started paying more attention during the missions, restarted careers with all the allowable views enabled. What I found was that even if I pumped an enemy full of lead to the point where the engine's quit and they've got the canopy open with arms flapping trying to escape, I still won't get the kill credit if a friendly so much as puts a single shot into them before they go down. In essense, what I see is I do maybe 75% plus of the critical damage to a single plane, and a friendly will come along and do the other 25% after me yet get the credit. I tried the converse a few times as well, wait for a wingman to shoot the piss out of somebody, then as they were heading down I'd swoop in and give them a few shots. In most of the cases I get the credit. Another irritating thing is sometimes I'll shoot up a bad guy enough that they'll go down, but they won't nosedive in, they'll kinda belly flop it on a flat piece of land, maybe a few chunks come off, etc. I don't get kill credit for those, when the plane's clearly a write off and loss.

So, in summary, it *seems* to me that the formulae for calculating who gets credit for kills and when is either wrong in some ways or incomplete.

My questions then become, is it just me? Am I wrong here? I don't think I am, given my highly unscientific testing... Is it handled differently for online and offline play? (I don't play online)

Possible courses of action as I see it:
- Team D could document some kind of short 'n sweet write up on how this mechanic works for our education.
- Fixing any wonky or weird code mechanics so kill accreditation is more accurate. (bug fix request?)
- Fleshing out the code mechanics so that kill accreditation is more accurate. (feature request?)

Cheers all

[IceFire]

Whacker: I take it you don't fly online all that much?

We call it kill stealing and it's sort of a blight on some online matches. I've observed the AI closely and they behave like humans up to a certain point after which they are much more fair. If the enemy aircraft has initiated the bailout or if the pilot is dead the AI will stop firing and ignore the plane. They will also ignore if there is a wing or the entire tail section is missing.

Otherwise they continue to shoot.

To some degree this "bug" is a historically and very human type response. The bigger problem isn't really the AI doing this but the scoring involved and that's where the game part of this comes in. It would be nice to share points relative to the amount of damage that one aircraft has dealt to another aircraft. So the magic BB for the steal is no longer a problem.