RHS Feedback - USAF
View Issue Details
0000237USAF[All Projects] Generalpublic2015-02-01 14:332015-02-03 21:40
Snippers 
RedPhoenix 
normalmajorrandom
closednot fixable 
0.3.5 
 
0000237: Vehicle PhysX / Teleportation issues. [M1 Abrams & Bradley]
Some vehicles (Bradley 'RHS_M2A3_BUSKIII' & M1 tank 'rhsusf_m1a1aim_tuski_d' ) have a random tendency when driving that they appear to be 'teleporting' into a void grey area to the user. Video (From bradley commander view) - https://www.youtube.com/watch?v=3aFxiISqCCU&feature=youtu.be [^]

My guess is that this is a PhysX issue note in the video the speed goes to >70,000 km/h and the rpt on the server is spammed with the following when this occurs:
'2015/02/01, 0:12:00 Matrix is not valid as physx transform!'

The server fps went down to 0 FPS causing desync. I was able to bring up the debug console up retrieve the position of the effected vehicles, it returned something like [#QNAN,#QNAN,#QNAN]. I was able to call setPos on the vehicles to teleport them to [0,0,0], after doing this the server FPS and desync promptly went back to normal.

My best guess is that something is wrong with the PhysX configurations but I am no expert in the Arma 3 engine. Unfortunately this makes these assets fairly unusable if there is a high probability of this occuring and in both missions we ran with 3-7 of these assets it happened in both, with 1 bradley suffering this in the first mission, and later 1 M1 and one bradley.
Unfortunately this is difficult to reproduce but we have had this happen three times last night, with approximately 10 of these assets crewed by players. Maybe the video will be of some use. It happened to me later and I could upload a video of that if it is useful.
No tags attached.
Issue History
2015-02-01 14:33SnippersNew Issue
2015-02-02 09:33SnippersNote Added: 0000635
2015-02-02 12:58RedPhoenixAssigned To => RedPhoenix
2015-02-02 12:58RedPhoenixStatusnew => assigned
2015-02-02 13:06RedPhoenixNote Added: 0000636
2015-02-02 18:13TheConenNote Added: 0000637
2015-02-02 19:05SnippersNote Added: 0000639
2015-02-03 21:40RedPhoenixNote Added: 0000652
2015-02-03 21:40RedPhoenixStatusassigned => closed
2015-02-03 21:40RedPhoenixResolutionopen => not fixable

Notes
(0000635)
Snippers   
2015-02-02 09:33   
Maybe the latest dev branch fixes this (we were using v1.38 stable):

Snippet Latest dev build version (30/01/2015) ChangeLog:
- Fixed: Problem with non-valid PhysX transforms and forces
http://forums.bistudio.com/showthread.php?149636-Development-Branch-Changelog&p=2870115&viewfull=1#post2870115 [^]
(0000636)
RedPhoenix   
2015-02-02 13:06   
Please upload the other video. I will check in it, but I am pretty sure it's not our fault.
(0000637)
TheConen   
2015-02-02 18:13   
'2015/02/01, 0:12:00 Matrix is not valid as physx transform!' is an issue introduced with the latest ArmA patch (1.38).
(0000639)
Snippers   
2015-02-02 19:05   
Thanks RedPhoenix! Here is the second video - https://www.youtube.com/watch?v=tqYEQ8qd3x8&feature=youtu.be [^]
(0000652)
RedPhoenix   
2015-02-03 21:40   
Yeah,it's BIs fault.
Nothing we can do, only waiting for the new patch.