![]() |
|
#1
|
||||
|
||||
![]()
What, specifically, is the bug you're mentioning...?
|
#2
|
|||
|
|||
![]()
I hope to see it better from this screenshots
![]() ![]() |
#3
|
||||
|
||||
![]() Quote:
First, what "guncam footage" was ever used by a Zero or an I-16? Second, in the game you still get a score if you ditch your plane in sea and your guncamera drowns. Third, I just rammed a B-29 and I had my wingman as a witness but I didn't get a kill because my plane crashed before B-29 did. So I pointed out a simple problem of scoring system employed by the game's engine. I believe this should and can be fixed. |
#4
|
|||
|
|||
![]()
In Il-2, the problem is that the kill is credited to the plane and not to the pilot. If the attacking plane crashes before the attacked plane does so, then the kill is lost for the surviving pilot who in RL could still claim that kill.
|
#5
|
|||
|
|||
![]() Quote:
In some ways, as frustrating as it is, the current kill scoring system is incredibly generous since it usually counts planes that crash as a result of damage that isn't immediately fatal. Realistically, those kills would only count as "probable kill" or "damaged" claims. Quote:
* Assign kills to the pilot, not the plane. * Assign kills as soon as a plane catches fire, break up, has a pilot & co-pilot kill result, or when the AI prompts the crew to bail out. * Instantly assign kills when a plane ditches or force lands (i.e., anything but a wheels down landing at an airfield). |
#6
|
|||
|
|||
![]()
the same on FW and tempest models
![]() Last edited by shelby; 12-22-2014 at 10:32 AM. |
#7
|
|||
|
|||
![]() |
#8
|
||||
|
||||
![]()
Also, with one or two other aircraft (don't remember which), part of the main wheel clips through the upper surface of the wing after the gear is fully retracted.
Didn't know that about the Hurri's and FW's gear mechanism, though... |
#9
|
|||
|
|||
![]()
Althought I like this feature, it still is plagued with too many inconsistencies.
Taxi to Takeoff works for any OnlyAI flight; Taxi to Takeoff in SP mode is great for humans if you use the overhead "guide" graphic (otherwise, it's not really needed). But for OnlyAI flights, in SP or COOP, the delay tag is INCONSISTENT! Below, I have a flight where Plane1 starts tagged to a stationary plane. This flight is AI only. [r0100_Way] TAKEOFF_005 172819.92 133867.21 0 0 &0 TRIGGERS 0 0 5 0 TAKEOFF_005 172763.92 133838.48 0 0 &0 TRIGGERS 0 2 5 0 TAKEOFF_005 172678.29 133898.70 0 0 &0 TRIGGERS 0 2 5 0 Nine times out of ten, this flight will NOT delay 2 minutes at waypoints 2 and 3. Or, they will delay at the WRONG waypoint. What gives with this feature and can we have a more definitive instruction set than what came with the readme? As it's too ambiguous or the feature is broken... ? |
![]() |
|
|