⚡Megatron LLM Hub
←返回搜索
Website

逆向 PUBG 载具物理,通过清零物理标志位维持坐标写入。

展示了 UE4 内存写入与物理状态耦合的调试细节,可参考其偏移定位思路。
逆向内存游戏
Hi, Internal research on UE4 vehicle physics in PC PUBG (2610.1.1.71). Target: keep a vehicle at a fixed altitude for testing. Verified in-process (RPM/WPM from an injected DLL): 1) USceneComponent +0x230/234/238 = ComponentLocation +0x25C/260/264 = RelativeLocation +0x204/208/20C = ComponentToWorld.Translation (render source) 2) Writing +0x238/+0x264 holds for seconds when FBodyInstance(+0x4D0)+0x74 bits 2/5 are cleared (bSimulatePhysics=0, bEnableGravity=0, RootFlags=0x02). But ComponentToWorld (+0x20C) is recomputed every frame from the physics scene, and writing +0x20C is overwritten within one frame. So the car never moves visually. 3) UVehicleMovementComponent (vehicle+0x470): Velocity at +0x470/474/478 is reset to 0 every frame. 4) PhysX actor linear velocity (+0x70/78): short lift ~1000cm, then drops back. Questions: - Is ComponentToWorld strictly driven by the physics scene, or is there a flag that makes it read RelativeLocation directly? - For PxRigidDynamic vehicles, is writing force/torque (instead of velocity) the right input? Does the vehicle solver overwrite it? - Any known offsets for VehicleCommonComponent / ReplicatedMovement (+0x90) in 2610.x? Thanks.