Flame CZE at 11:19, 14 February 2026

2026-02-14T11:19:55Z

Bokujishin: Created page with "== Introduction == The '''H'''ot'''L'''ap '''V'''alidity packet is sent by LFS when a car violates the HLVC system for hotlaps. In other words, you can use this to enforce tr..."

2026-02-10T15:32:44Z

Created page with "== Introduction == The '''H'''ot'''L'''ap '''V'''alidity packet is sent by LFS when a car violates the HLVC system for hotlaps. In other words, you can use this to enforce tr..."

New page

== Introduction ==

The '''H'''ot'''L'''ap '''V'''alidity packet is sent by LFS when a car violates the HLVC system for hotlaps. In other words, you can use this to enforce track limits in the same way that hotlaps are validated. This packet can also be used on open configurations, but you get less control over what constitutes an HLVC violation, as you will not get reports for out-of-bounds events or speeding in the pit lane.

{| class="wikitable"
|+ IS_HLV packet properties
|-
! Type !! Name !! Description
|-
| byte || Size || 20
|-
| byte || Type || ISP_HLV
|-
| byte || ReqI || 0
|-
| byte || PLID || player's unique id
|-
| byte || HLVC || 0: ground / 1: wall / 4: speeding / 5: out of bounds
|-
| byte || Sp1 ||
|-
| word || SpW ||
|-
| unsigned || Time || time stamp
|-
| CarContOBJ || C ||
|}

== Packet Details ==

=== Size ===

The size of the packet is always 20 bytes.

=== Type ===

The packet type from the [[InSim_enumerations#ISP|ISP_]] enumeration, always ISP_HLV.

=== ReqI ===

ReqI is always equal to zero.

=== PLID ===

The player's unique ID.

=== HLVC ===

The nature of the HLVC violation:
* 0: Ground (at least 3 wheels over an invalid surface)
* 1: Wall
* 4: Speeding in the pit lane
* 5: Out of bounds

=== Time ===

The timestamp of the HLVC violation.

=== C ===

The [[InSim_structs#CarContOBJ|CarContOBJ] representing the offending car's state.

== Notes ==

The "3 wheels over an invalid surface" does ''not'' require the wheels to be touching the surface: if you have 2 wheels touching an invalid surface, and the other 2 wheels are not touching the ground, but one of them is over the same invalid surface, HLVC will trigger.

HLVC considers the following as "invalid surfaces":
* grass
* gravel traps
* fake grass at Kyoto Ring
Gravel ''roads'' are not invalid surfaces, nor is "grasscrete" (asphalt or concrete areas painted green).

Rolling the car results in a "Wall" violation with the road.

[[Category:InSim packets]]

@@ Line 1: / Line 1: @@
-== Introduction ==
+{{Infobox InSim packet
-The '''H'''ot'''L'''ap '''V'''alidity packet is sent by LFS when a car violates the HLVC system for hotlaps. In other words, you can use this to enforce track limits in the same way that hotlaps are validated. This packet can also be used on open configurations, but you get less control over what constitutes an HLVC violation, as you will not get reports for out-of-bounds events or speeding in the pit lane.
+The '''H'''ot'''L'''ap '''V'''alidity packet is sent by LFS when a car violates the HLVC system for [[Game Modes/Hot Lapping|hotlaps]]. In other words, you can use this to enforce track limits in the same way that hotlaps are validated. This packet can also be used on open configurations, but you get less control over what constitutes an HLVC violation, as you will not get reports for out-of-bounds events or speeding in the pit lane.
 {| class="wikitable"
@@ Line 26: / Line 36: @@
 | CarContOBJ || C ||
 |}
 === Size ===
@@ Line 72: / Line 80: @@
 Rolling the car results in a "Wall" violation with the road.
 [[Category:InSim packets]]

IS HLV - Revision history

Flame CZE at 11:19, 14 February 2026

Bokujishin: Created page with "== Introduction == The '''H'''ot'''L'''ap '''V'''alidity packet is sent by LFS when a car violates the HLVC system for hotlaps. In other words, you can use this to enforce tr..."