khorio

I've been wanting to ask this for a while but I never got round to it; Is there a specific reason you went with including a fork of RNUI (which for some unexplainable reason uses the same version logic as the official build) that is going to break every single plugin as soon as the official build of RNUI gets updated. I don't see why you wouldn't just inherit the rnui classes you need to modify and use them instead of needing a custom build, all it does is add a lerp function so it's piss easy to implement. The potential for users to install the wrong rnui version other plugins include is already problematic on its own and this just adds to the problem. It is completely avoidable and you won't even need to update anything when using inheritance instead.

just press enter on the stream id and enter the id you want

You'll need to come to the support channels on ulss or my discord as I cannot provide support here.

I may have magically shaved off about ~40 fps from XScanner (on my end) today, will need some further testing before I update. (Was about 100-115 on my end depending).

I wish I knew what exactly clashed that suddenly started consuming frames this badly so I could fix it, but you need to consider the following: A) XScanner has no interaction whatsoever with any other plugin or even the main fiber because it runs in a thread separated from the game (which is why XScanner usually logs lines after the game has exited, the thread ends later). B) If I can run XScanner with a few other plugins and mods at 130 fps with no drops, there is no chance there is an issue with its internal functions (which are async anyway). The only interaction XScanner can have with any other plugin is through the relay (if it is enabled). I don't see how it's XScanners responsibility to aggressively block other plugins from hammering the API through the relay like there's no tomorrow, as this is the only way it can be affected. Most users have no frame drops whatsoever, and sadly, the only logs I have received concerning these issues are accompanied by completely broken setups with outdated/known problematic plugins (uc, jm, ig, section316, etc). As long as I don't receive more complete information, I can not proceed with trying to fix something as I can not reproduce the issue myself. This has never been a discussion about whether it's XScanner's fault or not, I'm happy to fix things when I have the information needed to do so.

It doesn't spawn helicopters but it does play helicopter voice responses when there's a helicopter in the pursuit. All pursuits

We've had support tickets about this before, it is not related to XScanner. "No more falling peds" and/or "enhanced vehicle actions 2" can be the culprit if you have those installed, either way try running only xscanner (and xpu if you have it), fps drop will be 0. Feel free to come to the support channel on discord (or ULSS) if you're still having issues.

Support is provided on Discord in the #support channel.

When you set ShortLocation to True it will never use landmarks for pursuit updates, same for UpdateOnNewStreet (because the audio would become very long and you kind of want to have fast updates when they swap streets a lot)

That's normal with obfuscation, I'll have a look after Christmas. Thanks for the log You're obviously missing default files as well. Set your intro and outro sounds from the menu.

You will need to upload your ragepluginhook.log Other than that, no it does not interfere with it

Only seeing an error from Immersive Ambient Events, but it seems to be a handled exception. Not seeing anything else from your log.

I'll have a look after christmas but not much has changed afaik.

done and done.

It's a false positive. XScanner does a lot of memory injection (not unlike what ragepluginhook does) which is also what trojans do. It is completely safe.

You can either specify one in the ini or select one in the menu. It does not use a weird dial tone by default, it's because you have a sound called "intro" somewhere from another plugin that is a dial tone.

Download the required audio (or the FULL install) and make sure to put them in the correct folders. I just did some baseline testing and I get at most a 5fps drop (if any)

From first glance you seem to be missing the required audio files

You'll need to upload your ragepluginhook.log

It is, XScanner (just like ragepluginhook) does memory injection to achieve what it does so antivirus might trigger on it. It's completely safe.

After further investigation it seems like I've missed an LSPDFR hook on the backup unit request/respond audio which still continues playing on the LSPDFR scanner as a result. Additional hook has been added for the next update.

You have an extremely old version of ragenativeui. Xscanner refused to load while another plugin crashed which is why it's shown in the log (XScanner will just refuse to load if the requirements aren't met so it should never crash). Update your ragenativeui and then try again, link is on the main page above here ^^

You will need to upload your ragepluginhook.log There is no currently known bug that would cause this. If you go on broadcastify.com you can look up your desired stream(s) and just note down the broadcast id at the end of the url. That's id you enter in xscanner