thatmaxplayle
Members
-
Joined
-
Last visited
Everything posted by thatmaxplayle
-
For the first time in more than a couple of months, Section136Callouts is back in development. I look forward to bringing you more content. Sorry for the radio silence over the past year, life has got seriously busy. As it always does, hey! Hopefully there will be a Christmas Update, but this depends on whether Rockstar release the second update to GTAO this month or not.- 422 comments
- 25 reviews
-
-
-
- 2
-
-
If you're being asked to send me a log, attaching the log to the post would be helpful. 10/10 for trying, though! 🙂 You seriously need to update the pack... ambient events were removed a long time ago. This particular crash is being caused by a ped becoming invalid. There isn't unfortunately, aside from more error checking, anything I can do about this. If you have a lower-end PC, and turn down your graphics settings, the memory pools will have more space to store entities. This should reduce how often this error occurs. If you have any particular other problems, let me know. Thanks for using the pack!
- 422 comments
- 25 reviews
-
You need to set your Plugin Timeout Threshold to 60000. This will instruct RPH to allow LSPDFR 60 seconds to load. Currently, you've got too much content installed given your computer specs for LSPDFR to load within 10 seconds. To do this: 1. Start RPH, whilst holding down the LEFT SHIFT KEY. 2. Under General, set Plugin Timeout Threshold to 60000 (60 thousand, please do not include a comma) 3. Click SAVE AND LAUNCH. This should fix your problem. Let me know how you get on. As far as the reported by Section136Callouts, this was due to an API outage - meaning the server that handles all of the network requests for Section136Callouts was down whilst you were trying to play. This did not prevent you from playing, however, it just meant Section136Callouts couldn't perform an update check. The API is back up, and has been since about 10am local time on the day you reported this crash. This is what your General page will look like if you've done this correctly.
-
Does this happen everytime you play the callout? I can't see anything directly related to the callout 🙂
- 422 comments
- 25 reviews
-
Hey guys, thought I would let you know about this. Caused a LSPDFR crash during initialization. Not 100% sure what caused it, because it hasn't happened before; but I thought I would let you know regardless. Thanks, Max- 446 comments
- 46 reviews
-
You can unbind the key in mainconfig.xml Thank you for reporting this. I'll look into it. Be aware: I'll only be looking into why Section136Callouts didn't catch this exception. The error alone is caused by a vehicle being invalid. I can't do anything about this.
- 422 comments
- 25 reviews
-
-
- 1
-
-
Yes I believe it is by default toggled by F10, will also display an MDT-sort-of-thing when you receive a callout. I must admit, I've been lacking on watching the YouTube content recently so. That's fine - I'll look into the bug, thank you for reporting it.
- 422 comments
- 25 reviews
-
That’s interesting. Just to ask, do you have Callout Manager installed? To clarify - this is the old Callout Manager - not the new Callout Interface by opus49. I’ll take a look into this. Thanks for reporting it. Max
- 422 comments
- 25 reviews
-
The EAC error wouldn’t have anything to do with an access violation. Not 100% sure why this is happening, but a full log file (hopefully containing a stack trace so I can pinpoint the error) would be beneficial to the debugging effort. Also, if this doesn’t happen everytime you play the callout - I‘m not too concerned. GTA doesn’t play well with modding, that’s a well known fact. Access Violations are, in most cases, a one-time crash. 🙂 Furthermore, since you don’t have EAC I would advise disabling the automatic EAC login check as it’s just unnecessary unless you become a Patreon. Just more work the pack has to do when it starts up lol
- 422 comments
- 25 reviews
-
Hey Doppler, Thank you - let me know how you get on. Kind regards, Max General Note: I am aware of the version name being incorrect in the file download on this page. Sorry, I'll get it patched ASAP
- 422 comments
- 25 reviews
-
I have since updated it, so would suggest giving it another download. I wouldn't say it's unstable per say - and I've updated it to enable it to be a little more forgiving to your system.
-
The log you're looking for Is in your base game directory; and will not have any numbers in the name.
-
You don't actually have pass any parameters to the ForceDuty command. These are merely optional parameters, that most players won't find any use for. I'll give you the rundown on what they do, to satisfy any curiosity you may have. In short, you don't need to specify anything when passing this command. If an exception is being thrown when you execute this command, there's probably something wrong with either: Your LSPDFR installation A plugin you have installed If you send the RAGEPluginHook.log file located in your main GTA V folder once you've encountered this issue, to this thread, I'll be able to take a look in greater detail and let you know how you can fix this issue. If you need some help with sending a log file, let me know. Kind regards, Max
-
@nocknick Let me know if it helps 🙂
-
@OfficerChris1 I've just uploaded an update to Section136Callouts which should address this bug. Thank you for being in the minority of people who actually alert the developers, rather than just prompting pack removal. 🙂
-
Thank you for reporting this. I'll have a look now.
-
The update I pushed last night changes the way the UI shows. It now shows in it‘s own thread - or in general terms: „It is now initialised in a way that allows LSPDFR to continue loading whilst the user reads the dialog“ whereas before it would not allow LSPDFR to continue loading until after the dialog was dismissed. I hope this fixes your issues, and should fix any issues with loading LSPDFR at startup too. If you do need additional help, you’re more than welcome as always to open a 136 ticket in my Discord server. It does help me keep track of people‘s issues and fixes for those issues if they‘re reported on Discord.
- 422 comments
- 25 reviews
-
Hey Doppler, I'm really sorry to hear you've been having issues with the pack. Could you please describe to me what's going wrong? Neither myself or my testers encountered any issues whilst loading/playing the pack - aside from a couple of issues I've had involving: EAC Authentication Above-ground positioning of the packages in the Airport Security Threat callout. Issues relating to the first start procedure where the automatic bug reporting prompt pauses the loading of LSPDFR if you have RPH setup to start LSPDFR on startup. Aside from this, I've not had anything reported to me. Do you have automated bug reporting enabled? I've not had a look at the dump submissions for a couple days, but will take a look through now. Furthermore, if you could describe to me in a little more detail about what trouble it is you're having with the pack; I'd be most appreciative. An RPH log file would also help Thank you, Max Hey carpless, I'm sorry to hear you've having issues with the pack. Could you please provide me with an RPH log file and I'll look into these issues. I really do not see how the callout pack could hang your computer, as I've never had this issue - and neither have any of my testers. To help you further, I'll need the following information: A full list of all other Callout Packs you have installed. Your computer's specification list (GPU, CPU, RAM etc.) An RPH log file. Also, please try disabling LSPDFR from loading automatically when you start RPH. I would always recommend keeping this off anyway. Could you please also elaborate on what you mean by "hanging your computer"? Does your device physically freeze, requiring a full hardware restart when the plugin loads; or does the game freeze/crash. I would assume that the plugin is trying to display the "Thank you for installing Section136Callouts!" automatic bug-reporting prompt UI, which is displayed on the first time you load the pack up; however this has been known not to work when you load LSPDFR at startup. Don't worry, I've been made aware of this bug and am working to fix it in an upcoming patch.
- 422 comments
- 25 reviews
-
A ped was invalid. There’s nothing I can do about this. It happens when RPH cannot get a handle for an entity. If it happens a load, restart your PC.
- 422 comments
- 25 reviews
-
-
- 1
-
-
📣 Development will resume shortly. I'm currently fixing my game so it will actually load with a mods folder. Not sure why it won't currently, but I'm very much still developing and hope to get a new update out shortly.
- 422 comments
- 25 reviews
-
-
- 1
-
-
-
Mad. Section136Callouts hasn't been updated in 3 months. Don't worry though, 136ers. I'm working on something. It's a rather beefy callout; so yeah may be a little while yet - but something is coming. Don't worry. To put it into perspective, the callout is nearly 1500 lines of code currently, and I've only implemented one out of a possible three situations.
- 422 comments
- 25 reviews
-
-
- 1
-
-
Charlie, you know how many hours I spent trying to get those to work. Those were painful times. I learned many lessons from them, haha 😂 To be fair, I do still blame RAGE (not RPH, the actual engine itself) for a lot of those issues. The engine wasn't designed to do a lot of what I was trying to get it to do, so that I guess was part of the problem.
-
I appreciate you being supportive of my point, here. Again, it's not a personal matter asuch, but I can only suggest things that could potentially make the experience better for everyone. I can assure you, if my plugin were added in the times of Section136Callouts - Ambient Events, then I can say I definitely don't blame you - that was not my proudest move, and although I couldn't reproduce any of the hard crashing that was reported to me, I for sure know it was causing issues. That "functionality" has since proudly been removed. I do understand your perspective on this - and am glad there are people to guide inexperienced users on 'fixing crashes'. Again, I'm sure our opinions differ on whether removing a plugin is actually fixing anything (rather than just suppressing the problem) but with that said, I am glad we could find some middle ground on the matter.
-
My friend, trust me, I've given more than enough support in my time within this community (like yourself, mainly off-site) to understand what it's like helping people who just cannot be helped. I know where you're coming from in that regard. I see in your site signature, you have a link to the ULSS Discord Server. I know for a fact (as I am one of them) a lot of the developers of well-known plugins, possibly with a few exceptions, are in this server. It is, after all, one of the more well known ones. Could you not just give a simple @mention to the developer of the plugin causing issues? I know I wouldn't be at all irritated with support reps offering assistance for my plugin, so long as issues were reported to me. Think about how much of an immersive experience this community could be offered, if support representatives in well-known support offering communities were to work with developers, indirectly even, to better the work they produce. I know for a fact that players in this community would certainly appreciate it. For instance, personally, if you encounter issues with my plugin - in ULSS, feel free to give me a ping. My username on Discord is @thatmaxplayle#8811 (just as it is here). Developers will admit that the pings can be frustrating, of course -- but the more work they put into fixing bugs and other issues reported via these pings, the less pings they'll wind up getting in the future. I'm just trying to offer basic solutions which take very little time to implement. The vastttt majority of plugins will implement some sort of logging at startup giving information about who the developer is. It's quite a common convention in all software, let alone LSPDFR plugins. My only reasoning for the request of moving into direct messaging, is the red warning notice quite clearly displayed above the reply box - and was only in the interest of complying with the site rules. LCPDFR.com moderators can view direct messages in the event of an issue, if that was your concern.
