Skip to content
View in the app

A better way to browse. Learn more.
LCPDFR.com

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.
Spring 2026 Site Update - New Features, Improvements & More

1803's Car HUD + Fuel System 1.2

(0 reviews)

By 1803 Creations

2 Screenshots

This is release V1.2 of my Car HUD. This is a scripthookdotnet script. Files go into the GTAV\Scripts folder.

Showcase:

https://www.youtube.com/watch?v=3bs_zvPYR5w

The Car HUD Shows: Speed, Gear, Direction, Road, Fuel Levels Fuel system can be turned on or off in JSON file. Other settings are configurable in the json file. There is also a separate json file to manage refueling stations. Settings like fuel range, screen placement, and MIles/Kilometers are in the CarHUDDisplay.json file.

Also included and can be turned on/off is a refueling system.

Fuel System settings are in the CarHUDDisplay.json

Locations for refueling has its own file: CarHUDDisplay.RefuelLocations

Here is a picture of what it looks like:

image.png

Edited by 1803 Creations

What's New in Version 1.2

Released

V1.2

Moved everything a line up to fit more in the box,

Changed Jurisdiction to JUR:
Now also getting jurisdiction multiple ways, I have not seen any "unknown area" since this update

V1.1

Added Jurisdiction

Fuel Bar got some horizontal lines

Short Description

On-screen display + Fuel System shown when player is in a vehicle. Shows Speed, Fuel level, Gear, Heading/Direction, and Street

AI disclosure

The author has disclosed that AI tools were used in creating the following aspects of this file:

  • Mod and Mod Content (Substantial)

AI helps bring another idea to life. Enjoy!
Previous File NoBlipBloat
Next File MoveThatPed

User Feedback

Recommended Comments

Upstanding Citizen

Lepoisson

Members

Hello, I just wanted to point out that the assembly version of your plugin is: 1.0.0.0instead of: 1.1

Detective

1803 Creations

Members Author

10 hours ago, lepoissongamer said:

Hello, I just wanted to point out that the assembly version of your plugin is: 1.0.0.0instead of: 1.1

The assembly number does not change. The build number changes. If you install V1.0, or V1.1, they are different versions of the C# project.

Upstanding Citizen

Lepoisson

Members

4 hours ago, 1803 Creations said:

The assembly number does not change. The build number changes. If you install V1.0, or V1.1, they are different versions of the C# project.

If the assembly version does not match the one shown on LSPDFR.com, there is no way to know if the user has the latest version of the plugin. Because in the ScriptHookVDotNet log, your plugin will always show: script assembly version: 1.0.0.0. regardless of whether the user has version 1.1 or v1.0.

Here a quick fix:

[assembly: AssemblyVersion("1.1.0.0")]
[assembly: AssemblyFileVersion("1.1.0.0")]

Detective

1803 Creations

Members Author

(edited)

20 hours ago, lepoissongamer said:

If the assembly version does not match the one shown on LSPDFR.com, there is no way to know if the user has the latest version of the plugin. Because in the ScriptHookVDotNet log, your plugin will always show: script assembly version: 1.0.0.0. regardless of whether the user has version 1.1 or v1.0.

Here a quick fix:

[assembly: AssemblyVersion("1.1.0.0")]
[assembly: AssemblyFileVersion("1.1.0.0

Yes, I do not change the "assembly" version, or "assembly file version"

On 4/26/2026 at 3:33 PM, lepoissongamer said:

If the assembly version does not match the one shown on LSPDFR.com, there is no way to know if the user has the latest version of the plugin. Because in the ScriptHookVDotNet log, your plugin will always show: script assembly version: 1.0.0.0. regardless of whether the user has version 1.1 or v1.0.

Here a quick fix:

[assembly: AssemblyVersion("1.1.0.0")]
[assembly: AssemblyFileVersion("1.1.0.0")]

I will look into changing the assembly name every time if you think its a big deal but I'm not going back and editing all of my current projects to match.

When I upload a new version, the file/folder names/structure is how I keep track of versions.

I also post comments when I upload to Github so when you look in the repository, it is clear which versions are out there.

Edited by 1803 Creations

Captain

JM Modifications

Members

24 minutes ago, 1803 Creations said:

Yes, I do not change the "assembly" version, or "assembly file version"

I will look into changing the assembly name every time if you think its a big deal but I'm not going back and editing all of my current projects to match.

When I upload a new version, the file/folder names/structure is how I keep track of versions.

I also post comments when I upload to Github so when you look in the repository, it is clear which versions are out there.

It's kind of a big deal cause it's very confusing to alot of people.

Detective

1803 Creations

Members Author

1 hour ago, JM Modifications said:

It's kind of a big deal cause it's very confusing to alot of people.

Okay, this is the first time I am hearing about it in four months of uploading projects, Ill try to stay consistent with future uploads/updates.

    • Create an account or sign in to comment

    Latest Mods

    Account

    Navigation

    Search

    Search

    Configure browser push notifications
    Chrome (Android)
    1. Tap the lock icon next to the address bar.
    2. Tap Permissions → Notifications.
    3. Adjust your preference.
    Chrome (Desktop)
    1. Click the padlock icon in the address bar.
    2. Select Site settings.
    3. Find Notifications and adjust your preference.