thatmaxplayle

Thank you very much, if you wouldn't mind leaving a review in the Reviews tab, that would be much appreciated! I appreciate your kind words 🙂 I'm glad you're enjoying them. Thank you for your kind words. If you wouldn't mind leaving a few words in the Reviews tab that would be much appreciated!

Good news! You can now track the progress on the newest updates using this link: https://github.com/users/maxplayle04/projects/1/views/1

No problem... I'd made this ages ago, but thought it would be useful to share it with other devs. 🙂

Make sure you do not have LSPDFR set to load at startup. If set to load at startup, it can cause Section136Callouts to have problems loading. I'm working on a fix. @Winnerjuri Thank you for reporting this. I'll be sure to get it fixed in the next update. CORRECTION: This issue is related to the Cop Holster mod. Please report it to the author of this mod. DEVELOPMENT UPDATE 📣 Another little development update! Hope you enjoy seeing what I've been up to!

Hey everyone 👋 Just wanted to post an update on what I'm currently working on, I'm going to try and do this every so often so you do know I'm not actually dead! Anyways, I'm currently working on a new callout which relies on AI being smart. I know, you didn't think you'd ever hear the words "AI" and "smart" in the sentence when GTA is within the context, but hey - I'm trying to improve that. As you can see in the attached video, I've been working on an Automatic Tasking system for one of the new callouts, which will make the AI Police Officers aware of when they have exceeded the range of the callout. When this happens, they will turn back around and head back for the subject area. They can, as you can see - be a little bit slow about this time, and can occasionally get quite distant from the area before they actually turn around, although I suspect this is something to do with the different types of Road Nodes within the game. This shall be apart of the next update to the pack, hopefully. I don't want to tempt fate, but what I'm working on is coming along nicely. You'll see more in a bit. I'm hoping to get some more videos up on my new playlist of Section136Callouts Development Videos which you can on which I plan to screen record the process of beta callouts. Of course, if you want to see these features progressively developed for yourself, you can always check out my Early Access Club. Happy patrolling! - Max

BUG UPDATE Just to confirm to anybody who is having trouble with this screen. I have "fixed" the issue of the screen remaining blurry after the message has dismissed. Simply by removing the blur. This update is coming very soon.

Hi, I know this was posted a long time ago - but I wanted to let you know that this is being fixed in an upcoming update. I know this is being fixed in an upcoming update, because the blurry screen itself is being removed in said update. Just to let you know, I do hear you - I've just been busy with other things!

Development Update • October 18 2021 As regular users of Section136Callouts will know, I haven't published an update for the pack in quite some time. So, I'm writing this post to explain why and to give some information about my plans for the future of Section136Callouts. Firstly, I'd like to acknowledge that the pack recently turned 1 year old. Thank you so very much for all the support shown over this year, it's been amazing to see and I would like to express my sincere thanks for all of your contribution to my mini-community! Now, the part you're probably more interested in - the future. I've been extremely busy with work and other commitments recently. It has taken up a lot of time, and I have not even had the time (let alone the interest) in developing new stuff for the pack. The truth is I've completely run out of ideas. That's not to say there's not an update in the works, but it is more of a "long time support" update, which will allow users to use the pack for as long as they wish, whilst I do not have time to update it as much. I will still be working on the pack, just not very much. Please do continue to engage with the pack and suggest features. If I see an idea for it that I would like to implement, I will be sure to implement it. The problem as it stands, is a lack of ideas for features to implement. There is, however, another announcement I must also make with regards to the next update: Ambient Events - Discontinued Although Ambient Events were a fun challenge to try and implement, the truth is they have been nothing but a pain in the ass and have led to no end of support complaints due to basic bugs. The truth is Grand Theft Auto V was not designed to deal with such content, and as such it can lead to unexpected bugs and crashes. Whilst they were fun to play with, and added an amount of realism to the LSPDFR experience, they give me way much more work than pleasure and I do not have the time to maintain them anymore. As such, from the first Long Term Support (LTS) release, Ambient Events will have been discontinued, and will not be present within the pack.

There's a couple things I could find useful from your RPH log. If you get a chance to send it, rather than just telling me it "doesn't show anything suspcious" please do.

Can you please open a support ticket in my Discord Server, if possible? I'd like to ask you a few questions. Thank you. If you're not already in the server, visit https://maxplayledev.org/discord to join.

Thank you bro! There's a reason why said person is so annoyed, and it isn't exactly valid one. But nonetheless, we'll leave it up to site moderation to deal with it! 😛

Sorry about the false-update notification! The website bugged out and sent it when I hadn't yet published the update. My apologies for this inconvenience. The update will be published shortly. This bug will be addressed in the update, being published today. As a quick side note, can I ask why you declined to take part in auto bug reporting? It's a very useful tool for fixing issues with the pack. This will help make the pack more stable for everyone!

If the screen blurs, just hit enter.

I’ve got one in the works, but it won’t be ready for a while yet. Let us know what you’re trying to do, and me or one of my support folk will guide you through in disabling it. Alternatively, join my Discord for 1-to-1 instant support.

You can just disable Ambient Events altogether in the mainconfig.xml file. That part of it didn't quite make the cut into the code. Thought that would limit my potential player base a little bit too much. Sorry! 😁

Sorry?

I suspected it might’ve been. Not to worry! We all forget things sometimes 😛 What was the cause, out of interest? What was the cause, out of interest? What was the cause, out of interest? What was the cause, out of interest?

Don't we all, please do - I anticipate your response 🙂

Interesting. I'll look into it.

Ohh - okay. I'll look into it. Just to confirm, you're editing the values of the brand new mainconfig.xml, and not the old INI files (which should've been automatically deleted) - right?

What you're saying is making no sense. I understand there is quite clearly a language barrier, so I would advise speaking in your native language and letting the website translate your message on your behalf. What you're referring to by saying "the grab issue" is completely unclear; and I cannot solve your issue - because I do not understand what the issue you're trying to describe actually is. What do you mean "ignoring big numbers"?

Firstly, thank you for checking out my pack. I have watched your videos for a while. If possible, I'd appreciate a log so I can investigate the issue. Just to clarify, we're talking about a plugin crash here and not a game crash, right? Or does the crash prevention handle it and cancel the event? Otherwise, feel free to disable the Ambient Events in the "mainconfig.xml" file in Plugins\LSPDFR\Section136Callouts. Find the attached reference image in file and replace "true" with "false". Let me know if I can help anymore, Thanks, Max Please try disabling the Ambient Events system, as detailed in my previous comment in response to Double Doppler. I'm investigating a potential link between Game Crashes and the Ambient Events, which isn't very explainable, although does seem to be an issue. If not, feel free to install - try it, and send me a log of the issue; this will help me in finding the cause. Thank you. That honestly makes no sense whatsoever but since I do nothing to do with grab tasks in my pack, I would suggest this is either LSPDFR or StopThePed (if you have it installed) Your RageNativeUI is so out of date, Section136Callouts cannot even display the "Installed version of RageNativeUI is too old" warning. Update RageNativeUI from https://github.com/alexguirre/ragenativeui/releases and that should fix your issue! 🙂 Thank you for reporting this, nonetheless.

Nothing to do with me, as you can see by the lack of mention of my callout pack in the stack trace of the crash. This is probably a one-off crash, and if it happens more than once it should be reported to the LSPDFR Dev Team as a bug. You are getting confused with the warning displayed when my logging system shuts down. This is just a side-effect of LSPDFR crashing due to another issue. It's not my fault.

It should be enabled by default, as far as I know. If they aren't - try enabling them in the mainconfig.xml file. If it doesn't seem to be enabling, join the Discord and make a ticket and we'll look into it! 👍