thatmaxplayle

Well... if you wanted to see what was coming next. I don't think these officers are feeling too good... I don't think these officers are fee

Oh yeah, I'm still working on it - those who look a little deeper into the picture will figure what I'm actually working on ...

Well, development for the next version of Section136Callouts is underway! I've just published the first bug-test update for my Early Access Club! I've not forgotten about the pack by any means, whatsoever! The first bug-test release includes: - One of the callouts, but rewritten in my new format. This improves stability, and allows for things such as automatic entity deletion/dismissal. Not to mention, new spawn locations and storyline possibilities! - Many bugs fixed around the pack! - Better integration for Callout Interface by opus49. I'm excited to share these updates with you, they're coming soon. I'm looking to update the pack a little more often. I hope you're as excited as I am for the new changes to come around, as I'm feeling particularly motivated to get the pack patched up and back on the trending list! 😉 Yes, I did rewrite a callout - a day and a bit after writing an entirely new callout. Call me mad, but when you're motivated, you're motivated. Enjoy your week guys!

I'm live, implementing this now! https://twitch.tv/thatmaxplayle

I can happily announce this is on the To-Do list! 😄

Thank you so much for the feedback, if you have time, consider leaving a review on the pack (click Reviews at the top of the comments section) Thank you for playing, and enjoy the plugin! 🙂

Sorry, but how can I be more specific when I’ve literally quoted the location and name of the file. GTA V/Plugins/LSPDFR/Section136Callouts/mainconfig.xml

I use StopThePed and have experienced no conflicts. Either way, yes you can - use mainconfig.xml in plugins\lspdfr\section136callouts (I use XML files instead of INI files for automatic config generation) I'll look into it 🙂

Coming on here and saying that helps nobody. Send your RagePluginHook.log so I can actually tell what went wrong (and if it's 136 at fault)

Sometimes, peds become invalid - as happened here. We can't really do a whole lot about it. Depending on the specs of your computer, the memory pools can get full up relatively quickly which causes this to happen. The game might spawn the ped, but if RAGE Plugin Hook doesn't give me a handle (which is a number which I can give to the game to tell it which ped to manipulate) I cannot do anything about this. Sadly, it's just one of those things that happen. We cannot expect this to change, because we have to remember this was a game built without modding in mind. The only thing us developers can do is handle it properly to stop it becoming a major issue. If you notice these popping up frequently, a game restart is generally enough to sort them out. If you've got a lot open on your computer - restart your computer, then launch the game. That is how you avoid these types of issues 🙂

Hi, Thank you for this comment - although in this instance, I cannot find anything in your log file alone to suggest that Section136Callouts caused your game to crash. I believe the log line you are referencing is the one I've attached below, although this is printed whenever a Section136Callouts callout has it's End function called. This is simply to narrow down "why a callout was asked to end" and can sometimes help troubleshoot bugs within callouts. However, like I said - I cannot find anything that is necessarily out-of-the-ordinary here. Thank you, however, for reporting something you believe to be wrong. 👍 Enjoy your day. 🙂

Brilliant idea, I had never thought of this!

Very interesting concept. As discussed, I'm looking forward to when developers can integrate with this plugin via an API!

I always like taking on ideas from people who play the pack. The latest idea comes from @wid3spreadpanic and involves a Prisoner Transfer. I hope you enjoy it. Don't forget, Early Access Club members currently have access to this content. Why don't you consider joining? More information is at https://maxplayledev.org/section136callouts/earlyaccess

Install this - https://www.gta5-mods.com/scripts/open-all-interiors

This is an issue with the Audio Engine used by Section136Callouts. It's something I am aware of, and am working on changing for other reasons. Don't worry, there's a fix coming soon. Sidenote: That's Section136Callouts preventing those crashes, not RPH. ATTENTION - Before you comment about dependency checks failing! I am aware of an issue due to a renamed library. This slipped under my radar and I didn't notice this whilst packaging the newest version of Section136Callouts. But, there's more to it. I've been looking into changing which Sound Engine I use within the pack, to cut down on the amount of files you have to download to play Section136Callouts. So, instead of simply repackaging this build with a file which won't really work because the existing Audio Engine is a bit rubbish, I'm half-way through changing which Audio Engine is being used within the pack, this way the next release will feature new audio systems which are a lot more stable. Long story short - ignore these messages for now. I am aware they're inconvenient and I can only apologise for them at this moment in time. With Christmas, and work, I've had very little time to monitor and test things like this - which I am sure you will understand. A new build will be out soon. Hopefully today, but if not - in the coming days.

Hey there, I'm afraid you're going to have to be more specific in your questioning as at least I cannot make sense of it? I believe you're trying to ask about a popup that says CODE 4 - DISREGARD after a callout is initiated? If you could let me know if that's correct, that would be great. Thank you.

Thank you very much, I appreciate your kind words! You have a great Christmas too! I thought RNUI may have been outdated. The outdated version was causing a few problems (not just with the updated game version) hence why I'm so strict on RNUI version compatibility (the plugin won't load unless you have 1.8+ installed) The new RageNativeUI can now be found at https://github.com/alexguirre/ragenativeui/releases/tag/1.8.2 I'm up to something, gang.

It doesn't destroy anything, just so you know. Section136Callouts requires an up-to-date version of RageNativeUI to work, otherwise it'll do absolutely nothing other than refuse to load. Simple as. It doesn't "destroy anything" whatsoever.

I'll look into it, thank you.

I'll look into it. Some people on lower end PCs are having trouble with serious frame dropping whenever an inbuilt LSPDFR pursuit is created. Can you let me know what your PC specs are please? Thank you Cyan is right (thank you for your input @Cyan) but that does reveal a bug to me. Make sure to update RNUI at https://github.com/alexguirre/ragenativeui/releases Compatibility Note I would also suggest removing Albo1125's mods, as they can cause problems due to being a little outdated.

A very interesting project. I'm yet to take a look, but by the videos at least it looks like good fun.

Hello all Virtual Police Officers! 👋 Just wanted to post a quick update on here as well as on my Discord server to let you all know that my BuyMeACoffee page is back up! You can now leave a tip at https://buymeacoffee.com/maxplayle! Of course, if you'd like to donate an amount that goes directly to me, rather than gets divided up between Stripe and BuyMeACoffee - there's always the https://paypal.me/maxplayle link at the top of the page. Whichever floats your boat! Section136Callouts is available for free, and always will be. Donations are never necessary, although if you enjoy the pack - and can afford to leave some spare change, please do feel free. Thank you for your continued support.

This is a very unuseful and quite a rudely worded comment. Please be reminded that this pack is developed in my own free time, and is made available to the general public for free. Be a little bit more respectful please. With regards to your, albeit rather rude, question - they have been fixed for a long time.