0 files liked
18 comments
0 videos
1 upload
0 followers
678 downloads
5mods on Discord
@KxldHearted Awesome, really glad to hear it! And thanks for pointing out the SHVDNE detail, updating the requirements section now to recommend ScriptHookVDotNet Enhanced for both Legacy and Enhanced players, since that's clearly what works. Appreciate you sticking with this the whole time, couldn't have figured it out without your reports.
v1.0.5 fixes the mod completely failing to load on Legacy edition (showed as a LoaderException in ScriptHookVDotNet.log for some users). Root cause was an internal bug in how the mod looked up a system type for notifications, which crashed inside ScriptHookVDotNet's own resolver before the mod even started. Also fixes the F7 toggle not showing an enable/disable notification.
Sorry for the long gap in updates, and thanks for the patience from everyone who reported this - especially KxldHearted, whose reports were what let me actually track it down. If you were affected by the mod not loading, the ini not generating, or F7 not doing anything, please update once it's approved and let me know how it goes.
@KxldHearted Update: Found the actual root cause, and it wasn't really an Enhanced-vs-Legacy thing at all. Turned out to be a bug in how the mod looked up a system type, which triggered a crash inside ScriptHookVDotNet's own internal resolver before any of my code even ran. Fixed it by grabbing the type a different way that avoids that path entirely.
Sorry it took so long to get back to this, life got in the way for a bit. v1.0.5 has the fix and is pending approval on the site right now, requirements section is also updated to be clearer about Legacy vs Enhanced. Once it's up, could you grab it and let me know:
1. Does ScriptHookVDotNet.log show "Found 1 script(s) in TruckSpawner.dll" with no errors?
2. Does the .ini finally generate?
3. Does it actually work in-game?
Really appreciate you sticking with this the whole time, your reports were what let me actually track this down.
@KxldHearted Kk i found the actual issue. Turns out i built this using a different version called “ScriptHookV .Net Enhanced” which is specifically for enhanced, not the normal ScriptHookVDotNet you’re using on legacy. So there actually isn’t a 3.9.0 for you to download, the nightly build you have is the right one.
The problem is on my end, i gotta look into whether i can make it work with the normal version too, or if the way i built the mod just doesn’t support legacy right now. gonna have to look into it properly, appreciate you bearing with me
@KxldHearted I found the actual error, thank you! This means the dll itself is failing to load as an assembly before any of my code even runs, likely a version mismatch with scripthookvdotnet. Can you check exactly which version of ScriptHookVDotNet3.dll youre running? I built this against 3.9.0 so if yours is different that could be exactly it
@KxldHearted Heythat's actually different from the other reports. If literally nothing shows up in temp either, that means the mod might not be loading at all on your end, not a path issue. Can you check your scripthookvdotnet.log (in your gta v root folder) and see if it mentions TruckSpawner.dll anywhere? It should say something like "Found 1 script(s) in TruckSpawner.dll".. If that line isnt there, or shows an error, that means it's failing to load in the first place. Also, what version of scripthookvdotnet are you running? Since youre on legacy that could matter.
@KxldHearted Hey thanks for reporting this, this is actually the first legacy report ive gotten since i only tested on enhanced. can you check %TEMP%\TruckSpawner_diag.txt (paste that into your file explorer address bar) and send me whats in it? that'll show me exactly what path its resolving to on legacy so i can actually see whats different
@BillyVong amazing, thank you for actually testing and confirming! glad this
finally worked, appreciate you sticking with it through all the back
and forth
@nj5050 The mod was built and tested on GTA V Enhanced only, not verified on Legacy. It Should theoretically work since it uses standard SHVDN/native functions, but if you will try it on Legacy, let me know how it goes either way
update: 1.0.4 is out (pending approval) and should actually fix the
ini/log generation bug for real this time - tested and confirmed on
my end. if you had issues with 1.0.1-1.0.3 grab this update once its
approved. sorry for the back and forth on this one, appreciate
everyone's patience testing it