What are you working on? - WAYWO

/// <summary>
/// Apply a torque to the ragdoll as a whole rather than on every body individually
/// </summary>
/// <param name="torque">The axis to spin around and speed in radians per second</param>
public void ApplyTorqueToRagdoll( Vector3 torque )
{
	var spinAxis = torque.Normal;
	var spinSpeed = torque.Length; // radians per second
	var angularVelocity = spinAxis * spinSpeed;
	var massCenter = ModelPhysics.MassCenter;

	var rotationCenter = Renderer.TryGetBoneTransform( PELVIS_BONE, out var trasform ) ? trasform.Position : massCenter;
	var centerLinearVelocity = Vector3.Cross( angularVelocity, (massCenter - rotationCenter) );

	foreach ( var body in ModelPhysics.Bodies )
	{
		var bodyVelocity = centerLinearVelocity + Vector3.Cross( angularVelocity, body.Component.WorldPosition - massCenter );
		body.Component.Velocity += bodyVelocity;
		body.Component.AngularVelocity += angularVelocity;
	}
}

• Build from game data a unified hierarchy of directories, files, binary slices, and structs.
  • Allow any source of binary data to support being dumped to a file or viewed in the browser as hex.
  • Allow all resources to be previewed.
• The logic for mounting a game is broken in to a series of discrete steps that may be shared between mounts.
  • Much of this logic could be stored in configuration files that the user may easily modify themselves.
  • The time of each step is recorded, making it easy to benchmark changes.
• All unsafe code is abstracted away from the framework, and loaded only through a plugin system.

• Assets are encrypted, requiring that AES keys be extracted from the game executable.
• Assets are deeply nested. Archive files have their own internal file table with a hierarchy, and files within archives may comprise many smaller files.
• GTA V contains a large enough variety of high fidelity assets to stress resource management and codec performance.