Bug #25835

Tracked Vehicles can drive underwater.

Added by HeinBloed almost 4 years ago. Updated over 3 years ago.

Status:Closed Start date:10/24/2011
Priority:Normal Due date:
Assignee:Suma % Done:

0%

Category:Vehicles
Target version:1.60.87580
Affected ArmA II version:1.59.79384 First affected build:Please Specify...
Reproduced by another DH user:Yes First affected ArmA II version:1.09.78183
I am using some Mods:No Single / Multi Player?:
I am using: BIForumURL:
Reproducible for you:Yes NGUrl:
Related to content of DLC: WIKIurl:

Description

Tracked Vehicles (class tank with canFloat = false) can drive underwater.

Start the attached mission "tank_underwater.utes" and drive to the waypoint.

I've tried to make an video and failed to reproduce the bug, but found out some strange behavior:
- Every time i drive into the water the bug is reproducible. I can drive underwater.
- Every time i drive into the water, while Fraps is recording, the tank will be disabled and destroyed.

The damage is dependent on FPS:

I had more than 200 fps in the test mission. With Fraps rocording the fps dropped to 25.

Here are the results from some more testing by adding some AI to dropp the fps. The bug appears at circa 130-150 fps.

Circa 150 fps and higher: No damage.
Circa 130-150 fps: Slowly increasing damage,
Circa 130 fps and lower: Abruptly damage,

tank_underwater.utes.zip (765 Bytes) HeinBloed, 10/24/2011 14:00

History

Updated by Buliwyf almost 4 years ago

100% reproducable for me.

Updated by HeinBloed almost 4 years ago

Additional test:

1. I drive into the water. (Fraps is running, but not recording).
2. I start recording with Fraps. The tank will get instantly some damage.
3. As soon as i recognize the damage i stop recording with Fraps. The damage will instantly remaining in the current state.
4. I cruise underwater here and there.
5. I start recording with Fraps. The tank will get instantly more damage until it blow up.

Updated by Fireball almost 4 years ago

  • Due date set to 02/24/2012
  • Status changed from New to Assigned
  • Reproduced by another DH user changed from No to Yes

Updated by kju over 3 years ago

  • Due date changed from 02/24/2012 to 11/14/2011
  • Status changed from Assigned to Feedback

Updated by Suma over 3 years ago

The only idea I have is that perhaps sometimes when fps is very high the damage might be registered incorrectly. What is your fps when not recording with Fraps? How it changes when recording?

Updated by HeinBloed over 3 years ago

Yes, i can confirm that the damage dependence on the fps.

I had more than 200 fps in the test mission. With Fraps rocording the fps dropped to 25.

Here are the results from some more testing by adding some AI to dropp the fps. The bug appears at circa 130-150 fps.

Circa 150 fps and higher: No damage.
Circa 130-150 fps: Slowly increasing damage,
Circa 130 fps and lower: Abruptly damage,

Updated by Fireball over 3 years ago

200 FPS?? Holy cow, I doubt that anyone at BIS ever gets such a framerate, not even 150 FPS, I'd bet. I'm not surprised that this one slipped through.

Workaround: Turn on VSync! :D

Updated by Fireball over 3 years ago

  • Description updated (diff)
  • Status changed from Feedback to Assigned

Updated by Fireball over 3 years ago

  • Due date changed from 11/14/2011 to 01/14/2012

Updated by Suma over 3 years ago

  • Assignee set to Suma

Easy to simulate using slow time. With fps 50 and setAccTime 0.25 you get a simulated fps of 200, which is enough to shown the issue consistently.

I will fix this particular issue easily, but it is quite possible other issues may appear in other similar situations (e.g. collision response). If you see anything strange with high fps like this, feel free to report it - I consider it quite important to make the game future safe, as it is quite possible such high fps will not be uncommon on computers 10 or 20 years from now.

Updated by Suma over 3 years ago

  • Status changed from Assigned to Resolved

Fixed in 86035

Updated by kju over 3 years ago

  • Due date deleted (01/14/2012)
  • Target version set to Upcoming version

Updated by kju over 3 years ago

  • Target version changed from Upcoming version to 1.60 BETA

Updated by Dwarden over 3 years ago

  • Status changed from Resolved to Closed

closing as fixed ...

Updated by kju over 3 years ago

  • Target version changed from 1.60 BETA to 1.60.87580

Also available in: Atom PDF