PeterU

This will be addressed in the next release of PeterUCallouts with a configurable shortcut. Do you have the whole log file from that incident? I can't see anything here relating to PeterUCallouts except Unknown command or variable "peteru"

Could you please post a RagePluginHook.log from your GTA V folder from when you have this problem?

If you are working on translations, please head over to Discord and the translation channel.

Are those files in the extracted zips that you downloaded? It looks like RPH is killing LSPDFR during initialization because it is taking too long. Click the Settings icon while Rage Plugin Hook is launching to bring up this dialog: Increase the Plugin Timeout Threshold value. Here I have it to 20000 (20 seconds). Experiment with increasing this value until LSPDFR is given enough time to initialize! As mentioned by @XTREMEHEAT, this works with Search Warrant by Darkmyre. It also works with Police Search.

Are you able to provide a RagePluginHook.log from when this happens? What other plugins do you have installed?

Click the Settings icon while Rage Plugin Hook is launching to bring up this dialog: Increase the Plugin Timeout Threshold value. Here I have it to 20000 (20 seconds). Experiment with increasing this value until LSPDFR is given enough time to initialize! PeterUCallouts was the last line in the RPH log here, but I don't see anything saying that PeterUCallouts is actually not working. It looks like this crash might be to do with something else. These 0xc0000005 (EXCEPTION_ACCESS_VIOLATION) are typically due to custom content installed in the game files, such as vehicles. For most callouts, the plugin will continue to work even with customized XML files. If the plan is for other people to use the translations, please PM me and we will figure out how to get this to many people in future PeterUCallouts updates. I am not seeing anything immediately obvious in the log file there. Are these crashes full game crashes, or just LSPDFR crashes? Do they occur during a specific callout? Can you do a specific set of actions to reliably get it to crash again?

This was an omission on my part in the global INI file. The absence of these lines means the callouts will be offered at their normal likelihood -- you only need to add the lines back in if you'd like to make those callouts less likely.

@THEMIGHTYCB I don't think this was ScenariOh!

Do you have a RagePluginHook.log file from one of these crashes? It isn't possible to investigate without the further details that this file can provide. You are welcome to PM me with any translated strings, but it is possible to also edit the XML files on your own install. If the plan is for other people to use the translations, please PM me and we will figure out how to get this to many people in future PeterUCallouts updates.

Are you thinking about translation? The dialog can be changed and this will work as long as you are careful with the XML format. It will trigger the "custom modifications to PeterUCallouts" warning when you go on duty, which prevents some features (Community Engagement Event) from working as this requires the files to be unmodified. If you are just doing a straight translation, perhaps you'd like to share your changes and maybe they could be included in the base PeterUCallouts?

Please check you are copying the files correctly. This sounds like you are copying the .dll into the right place, but missing all the other dependent files. The zip package should be unzipped, and then copy the files inside it and paste in your GTA V folder. Can you give details of the "memory errors"? It is unlikely that the presence of audio files would cause these issues. The audio files themselves are used by the LSPDFR Police Scanner playback mechanism. PeterUCallouts checks, shortly after going on duty, to see if the files it wants are in the right place and stores a simple "yes" or "no" in memory for each file, so it knows what audio files it might be able to use later. This prevents some stuttering when you're in a callout and the game wants to check for an audio file.

Can you get any RagePluginHook.log files from this crash? Does this always happen, or did it happen just once?

Thank you for providing the log. It does not appear that PeterUCallouts is the crash in this case. Unfortunately, it is rather difficult to determine which plugin caused the crash, as the developer's obfuscation means we can only see the "?????" lines where the important information would be. It would be a plugin that used RAGENativeUI, however. Can you provide a RagePluginHook.log from when this happens? Can you please provide a RagePluginHook.log? Which version of Traffic Policer do you have installed? Do you have Traffic Policer installed at all? The PeterUCallouts License screen simply requires you to press Enter, scroll through the pages of the license as you read it with the arrow keys, and then press 'Enter' on the last page. I'm interested to know if you noticed improvements here. I did catch a full game crash bug in my testing stages for the Speeding Vehicle callout. I thought I had managed to address it before public release, and there haven't been other reports of issues with it except for the two here, so I'd like to know if there is still an issue I need to hunt down.

Which actions is it asking you to add to your Police Smart Radio ini? Can you post your Police Smart Radio ButtonConfig XML files?

I wasn't able to reproduce this issue in my testing, although I did make improvements to the license screen which are likely to have addressed the cause of this reported issue.

What were you doing at the moment of the crash? It seems that you were in a RAGENativeUI menu of some kind — do you remember which menu you had open or were trying to open?

Entire game crashes are usually the result of custom vehicles/peds and other game data modifications. Does this happen on all callouts, all my callouts, or a specific callout? I am awaiting a further update to Rage Plugin Hook — some issues with RPH 0.58 have been identified that mean I can't complete my testing successfully for the next PUC release.

Please see the compatibility table: v0.57 Tested v0.56 No issues anticipated v0.46-v0.55 No issues anticipated v0.45 and earlier Not compatible

Can you provide logs from the crashes? I can't investigate anything without that technical detail. You can press 'End' to end the call. I used to prompt for this, but these days I'm assuming people have something like Police Smart Radio to allow them to end the call! Can you provide logs from the crashes? I can't investigate anything without that technical detail.

This has been implemented in v2.2.6519.9466.

PeterUCallouts.defaults.ini is new for this release, but is provided in the upgrade package only. It shows you what the default PeterUCallouts.ini would look like for that release (in case there are any new options that aren't in your current PeterUCallouts.ini). This allows you to look and manually transfer any new settings to your PeterUCallouts.ini file. It does not itself do anything. I probably should explain this more clearly in the readme! The issue with the keybindings here was probably that the lines you added were not added underneath the [KeyBindings] heading. If they appear under a different heading, the options will be ignored.

Can you add to the end of the PeterUCallouts.ini (first snippet) that you posted?

Are you able to explain what kind of visual bug, or provide a screenshot? If you need to see the license screen again, you can delete the [License] section from your PeterUCallouts.ini file. Are these entries directly underneath a [KeyBindings] heading in the global PeterUCallouts.ini file?