Vehicles (programming): Difference between revisions
No edit summary |
Thunder4ik (talk | contribs) m (Unicodifying, replaced: [[Image: → [[File: (2)) |
||
(11 intermediate revisions by 6 users not shown) | |||
Line 1: | Line 1: | ||
{{Abstract Coding}} | {{Abstract Coding}} | ||
[[Category:Vehicle Programming]] | |||
{{stub}} | |||
== Interfaces == | This article is meant to give an in-depth analysis of the vehicles in Source and to provide the necessary information to create and modify source vehicles. | ||
== In General == | |||
All vehicles, including the airboat, inherit from the same base classes: | |||
{{Note|Note that abstract interfaces aren't properly represented here as separate nodes. However, classes that inherit from an interface will have it listed under its name along with every other parent class.}} | |||
[[File:2011April25_Source_Vehicles_Class_Diagram_ServerSide.png|920px]] | |||
At the end of the day, the typical source vehicle is made up of 3 parts: | |||
*The main vehicle, inheriting from [[CPropVehicleDriveable]]. | |||
*The "Server" Vehicle, inheriting from [[CBaseServerVehicle]]. | |||
*The vehicle physics, [[CFourWheelVehiclePhysics]]. | |||
=== prop_vehicle_driveable Entity === | |||
This is the main part of the vehicle, it's the entity that has the actual name of the vehicle and inherits from [[CPropVehicleDriveable]]. Like [[CPropAirboat]]. | |||
This entity doesn't handle passengers or passengers entry, since the code the player used to ride vehicles needs a [[IServerVehicle]]. That's why there is a member pointer on a [[CFourWheelsServerVehicle]] stored in the instance. | |||
=== Server Vehicle === | |||
This class's primary purpose is to handle passenger entry, and sound state, along with acting as a proxy between the Driveable Vehicle, and the physic vehicle. It uses data structures named operating, control, and vehicle params, to share information between the driveable and physics classes. | |||
Its other purpose is to trigger the loading of the vehicle script data on its creation, along with the creation of the physics vehicle object. | |||
=== Vehicle Physics === | |||
This class isn't an entity, it's mostly a wrapper between the driveable and server vehicle entities and the vehicle physics controller ([[IPhysicsVehicleController]]). It transmits data from the [[IPhysicsVehicleController]] object (that's in the physics DLL) through the <code>GetVehicleOperatingParams()</code> method. It also transmits to the [[IPhysicsVehicleController]] the data in the control params (<code>m_controls</code>) structure. | |||
This object is responsible for loading and parsing the physics vehicle data, through the <code>bool ParseVehicleScript( const char *pScriptName, solid_t &solid, vehicleparams_t &vehicle )</code> method. | |||
=== Vehicle Data Structures === | |||
{{todo|Info on the data structures used to transmit physic data and controls data back and forth between the physic DLL and the server DLL. See '''"..\src\public\vphysics\vehicles.h"''' and '''"..\src\game\server\vehicle_sounds.h"'''}} | |||
== Vehicles Specifics == | |||
=== Vehicles types values === | |||
From '''"..\src\public\vphysics\vehicles.h"''' | |||
<source lang=cpp> | |||
#define VEHICLE_TYPE_CAR_WHEELS (1<<0) | |||
#define VEHICLE_TYPE_CAR_RAYCAST (1<<1) | |||
#define VEHICLE_TYPE_JETSKI_RAYCAST (1<<2) | |||
#define VEHICLE_TYPE_AIRBOAT_RAYCAST (1<<3) | |||
</source> | |||
=== The Buggy and Jalopy === | |||
[[File:Buggy.jpg|thumb|none|100px]] | |||
The buggy | |||
{{todo|Buggy and Jalopy specifics.}} | |||
=== The Airboat === | |||
[[File:prop_vehicle_airboat.jpg|thumb|none|100px]] | |||
The airboat uses the same physical entity as the buggy [[CFourWheelVehiclePhysics]]. But it changes the vehicle type value to <code>VEHICLE_TYPE_AIRBOAT_RAYCAST</code>. | |||
{{todo|airboat specifics.}} | |||
== Player Interaction == | |||
{{todo|describe what goes on when the player uses a vehicle.}} | |||
== Vehicles Components == | |||
=== Interfaces === | |||
* [[IClientVehicle]] - Client Side | |||
* [[IVehicle]] - Vehicle Generalizations | * [[IVehicle]] - Vehicle Generalizations | ||
* [[IServerVehicle]] | |||
* [[IDrivableVehicle]] | |||
* [[INPCPassengerCarrier]] | |||
* [[IPhysicsVehicleController]] | |||
=== Classes === | |||
*Server: | |||
**[[CFourWheelVehiclePhysics]] | |||
**[[CBaseServerVehicle]] | |||
**[[CFourWheelServerVehicle]] | |||
**[[CPropVehicle]] | |||
**[[CPropVehicleDriveable]] | |||
*Client: | |||
**[[C_PropVehicleDriveable]] | |||
== Multi-passenger vehicles == | == Additional Help == | ||
* [[Jurassic Rage]] coding team has released | ===Source code:=== | ||
==== Multi-passenger vehicles ==== | |||
* The [[Jurassic Rage]] coding team has released their multi-passenger vehicle code: | |||
** [https://web.archive.org/web/20090227184301/http://www.chatbear.com/board.plm?a=viewthread&t=573,1125931904,10177&id=901881&b=4991&v=flatold Here is the forum thread (archived)] | |||
** [http://web.archive.org/web/20080325223407/http://www.users.on.net/~emlesz/Al/PassengerVehicle Here are the files (archived)] [[https://docs.google.com/file/d/0B2UEgCeQJPISdHhHN0RZSVU4Z00/edit?usp=sharing mirror #1]] | |||
* [[Multipassenger Vehicle Abstract]] | * [[Multipassenger Vehicle Abstract]] | ||
== Pilotable code == | ==== Pilotable code ==== | ||
* [[User:TheQuartz|TheQuartz]] has released the Strider, Helicopter, and APC | * [[User:TheQuartz|TheQuartz]], creator of the [[Pilotable Strider Mod]], has released the "Strider, Helicopter, and APC" source code: | ||
** [https://web.archive.org/web/20090228053802/http://www.joluis.com/archives/2005/08/strider_mod.html Here is the blog post (archived)] | |||
** [https://web.archive.org/web/20051214234801/http://www.joluis.com/zips/PilotableCode.zip Here are the files (archived)] | |||
== Half-Life 2 SDK vehicles == | === Fixes: === | ||
==== Half-Life 2 SDK vehicles ==== | |||
* Some information on fixing source vehicle code for use in Multiplayer can be found [[Multiplayer Vehicle Fixes|here]]. | * Some information on fixing source vehicle code for use in Multiplayer can be found [[Multiplayer Vehicle Fixes|here]]. | ||
== HL2DM | ==== HL2DM vehicle fix ==== | ||
* A partial fix to make vehicles predicted and work in HL2DM can be found [[HL2DM Vehicle Fix|here]]. | * A partial fix to make vehicles predicted and work in HL2DM can be found [[HL2DM Vehicle Fix|here]]. | ||
== External links == | |||
* [http://www.design3.com/source-engine/coding/source-vehicle-programming Design3 Vehicle Programming Video Tutorials] |
Latest revision as of 02:13, 9 January 2024
Abstract Coding series Discuss your thoughts - Help us develop the articles or ideas you want |
---|
Levels & XP | Optimization | Procedural Textures | Sights & Sniperrifles | Special effects | Vehicles | Threads | Save Game Files | Night Vision | Non-offensive Weapons | Dynamic Weapon Spawns | Dynamic Weapon Spawns (Advanced) |
This article is meant to give an in-depth analysis of the vehicles in Source and to provide the necessary information to create and modify source vehicles.
In General
All vehicles, including the airboat, inherit from the same base classes:

At the end of the day, the typical source vehicle is made up of 3 parts:
- The main vehicle, inheriting from CPropVehicleDriveable.
- The "Server" Vehicle, inheriting from CBaseServerVehicle.
- The vehicle physics, CFourWheelVehiclePhysics.
prop_vehicle_driveable Entity
This is the main part of the vehicle, it's the entity that has the actual name of the vehicle and inherits from CPropVehicleDriveable. Like CPropAirboat.
This entity doesn't handle passengers or passengers entry, since the code the player used to ride vehicles needs a IServerVehicle. That's why there is a member pointer on a CFourWheelsServerVehicle stored in the instance.
Server Vehicle
This class's primary purpose is to handle passenger entry, and sound state, along with acting as a proxy between the Driveable Vehicle, and the physic vehicle. It uses data structures named operating, control, and vehicle params, to share information between the driveable and physics classes. Its other purpose is to trigger the loading of the vehicle script data on its creation, along with the creation of the physics vehicle object.
Vehicle Physics
This class isn't an entity, it's mostly a wrapper between the driveable and server vehicle entities and the vehicle physics controller (IPhysicsVehicleController). It transmits data from the IPhysicsVehicleController object (that's in the physics DLL) through the GetVehicleOperatingParams()
method. It also transmits to the IPhysicsVehicleController the data in the control params (m_controls
) structure.
This object is responsible for loading and parsing the physics vehicle data, through the bool ParseVehicleScript( const char *pScriptName, solid_t &solid, vehicleparams_t &vehicle )
method.
Vehicle Data Structures
Vehicles Specifics
Vehicles types values
From "..\src\public\vphysics\vehicles.h"
#define VEHICLE_TYPE_CAR_WHEELS (1<<0)
#define VEHICLE_TYPE_CAR_RAYCAST (1<<1)
#define VEHICLE_TYPE_JETSKI_RAYCAST (1<<2)
#define VEHICLE_TYPE_AIRBOAT_RAYCAST (1<<3)
The Buggy and Jalopy
The buggy
The Airboat
The airboat uses the same physical entity as the buggy CFourWheelVehiclePhysics. But it changes the vehicle type value to VEHICLE_TYPE_AIRBOAT_RAYCAST
.
Player Interaction
Vehicles Components
Interfaces
- IClientVehicle - Client Side
- IVehicle - Vehicle Generalizations
- IServerVehicle
- IDrivableVehicle
- INPCPassengerCarrier
- IPhysicsVehicleController
Classes
- Server:
- Client:
Additional Help
Source code:
Multi-passenger vehicles
- The Jurassic Rage coding team has released their multi-passenger vehicle code:
- Multipassenger Vehicle Abstract
Pilotable code
- TheQuartz, creator of the Pilotable Strider Mod, has released the "Strider, Helicopter, and APC" source code:
Fixes:
Half-Life 2 SDK vehicles
- Some information on fixing source vehicle code for use in Multiplayer can be found here.
HL2DM vehicle fix
- A partial fix to make vehicles predicted and work in HL2DM can be found here.