Bienvenido a GTA5-Mods.com

@7777N Yes, that is the in-game clock, and it can be disabled through the **INI file**.
@DirtyDan999 Thank you for helping answer the question! I really appreciate it.

@a012345 BTW, I also noticed that your game folder is build 1.0.3889.0, that's the version number for GTA V Legacy, not Enhanced. SHVDNE itself is designed to work with both versions, so that's not the issue.

However, for our GTA V Legacy script support, we use the SHVDN nightly build rather than SHVDN Enhanced. That may be what's causing the error. Please correct me if I'm wrong.

You can download the SHVDN nightly build here: https://github.com/scripthookvdotnet/scripthookvdotnet-nightly/releases

@SER2022 Hi! That seems to be an issue on your end. Here's why, this script spawns addon peds based purely on coordinates from PedSpawnPoints.json. It does not scan sidewalks, does not use navmesh, does not call GetNextPositionOnSidewalk, and has no pathfinding logic whatsoever. So no matter what map mods you have installed (as long as you're not adding a completely new map), the spawn system will work just fine. The JSON coordinates are fixed and independent from any map changes.

@Bigsossa Thanks mate! Glad you enjoyed it!

@nj5050 Thanks mate! Glad you enjoyed it!

@a012345 Hey, could you help me check two things so I can look into this properly?

1. Which SHVDN version are you using, Legacy Nightly or SHVDNE, and what’s the exact version number?
2. Please send me the full contents of `ScriptHookVDotNet.log` from your GTA V folder.

That error usually only shows up when the SHVDN version is incompatible or not up to date enough. The file itself is already complete out of the box, so it’s most likely not an issue with a missing file.

@Herobrine7707 Hey, thanks for trying it out! Regarding the targeting, that's actually a known behavior of the soft-lock system, the scanner checks everything that can be hacked (vehicles, ATMs, street lights, power boxes, NPCs using their phones, etc.) within a 20m radius in front of the camera, then picks the closest target, rather than the one that's most "centered" on screen. The camera angle only acts as a small tiebreaker when multiple targets are at roughly the same distance.

So if there's a car, NPC, or another object that's closer to you than the pad (even if you're already aiming the camera directly at the pad), the system can "steal" the lock and prioritize that object instead. This happens most often in crowded areas like parking lots or along the roadside.

Temporary fix: try moving your character/camera closer to the pad so it becomes the closest candidate. Alternatively, you can lower ScanRadius in GHOSTLINE V.ini (default is 20.0) so objects farther away won't be considered as candidates. You can also enable ShowDebugTargetInfo=true in the INI to see which objects are competing for the target when you're in that area.

For the next version, I'll consider increasing the weight of the camera angle so the target you're actually looking at gets prioritized more over distance alone. Thanks for the report!

@Bigsossa Ah my bad for the confusion, "Block Native Traffic" is actually a setting in AddonToRoad, not TrafficXCustom. If you have AddonToRoad installed, it's under: Main Menu > Settings > Block Native Traffic. If you don't see it there, make sure you're on the latest AddonToRoad version. If you're not using AddonToRoad at all, then that setting isn't relevant to you, sorry for the mix-up earlier!

@Edwin Rosero ¡De nada! Avísame si sigues teniendo problemas cuando lo pruebes. ¡Gracias por tu paciencia!