M1ax

Hi everyone, As an audio creator currently developing a complete dispatch overhaul for the Francophone community—aiming to bring the level of procedural realism seen in English projects like Blue Line Dispatch to French-speaking players I’d like to share some feedback regarding the current Scanner Engine (PoliceScanner). While English audio often masks these engine limitations as generic background noise, attempting to build a high-fidelity, procedurally accurate dispatch system in another language immediately exposes several hardcoded logic flaws. To keep this post concise, here are just two examples among others illustrating where the scanner logic breaks tactical immersion: REPORT_SUSPECT_IS_ON_FOOT: Located across all officer voice directories in LSPDFR/Audio/Scanner/ (s_m_y_cop_*, s_f_y_cop_*), this event is triggered purely by !ped.IsInAnyVehicle(). When a suspect exits their car and statically surrenders with hands raised, LSPDFR still forces the officer voice profile to play REPORT_SUSPECT_IS_ON_FOOT_01 ("Hey dispatch, the suspect is on foot!"). Announcing an active foot pursuit during a static surrender completely breaks procedural realism. SUSPECT_NEUTRALIZED: Triggers the moment 1 ped reaches 0 HP. If an officer neutralizes 1 suspect inside a vehicle containing 3 other active shooters, dispatch announces "Threat neutralized" while automatic gunfire continues. Opening the Discussion: I am not sharing this to demand fixes or claim that resolving these two specific cases would instantly solve everything for LSPDFR 0.5. I simply wanted to bring a creator's perspective to the table. These examples highlight how the underlying scanner logic could benefit from deeper contextual checks (such as differentiating a surrender from an active foot pursuit, or checking remaining threat counts). I have encountered several other similar edge cases during development, and I would be more than happy to discuss them further with the staff or community if there is interest in exploring this topic.

Hello, I'm writing to let you know that I have finally fixed the issue! The crash was caused by an outdated version of the Menyoo mod menu. After updating Menyoo to the latest version compatible with the current game build (v3788.0), the game now launches perfectly with both ScriptHookV.dll and dinput8.dll enabled. It seems that ScriptHookV itself was fine, but it was struggling to load the old Menyoo script.

Thank you for your advice. I followed your instructions and deleted all the .old plugin files from my directory to avoid any CLR assembly errors. However, the problem persists: The game won't launch (with or without the RAGE Plugin Hook) as long as ScriptHookV.dll is present in the main folder. If I delete ScriptHookV.dll, the game launches and runs perfectly with or without RPH. This confirms that the crash is directly related to ScriptHookV or a specific .asi plugin it is trying to load. My current game version is v3788.0. Is this a compatibility issue with the latest update, or should I look into a specific .asi file? Thanks for your help!

Hello, After the latest update, I am experiencing an issue when launching Rage Plugin Hook; it hangs and crashes on startup because of the new ScriptHookV.dll file. Interestingly, if I disable both dinput8.dll and ScriptHookV.dll, the game launches perfectly with RagePluginHook. I would appreciate your help in identifying the culprit. I have attached my ScriptHookV.log and RagePluginHook.log files. ScriptHookV.log RagePluginHook.log