LukeD

That's good work and much better code. A great improvement from your first try so well done 🙂 The try/catch is good for helping you find faults and deal with things internally. As you have done in your code you can see how you can stop the program from crashing and log the error. This is great for debugging or catching things you're not too sure about, and allows you to move on to better practices when releasing plugins. The use of "IsValid()" is good, the alternative would be ".Exists()". Both achieve similar things. By testing for this condition before executing further code you eliminate the issue that the vehicle doesn't exist yet or hasn't spawned, if either of these things were true and you tried to warp your character into it you'd crash for trying to execute code against an object that doesn't exist in memory yet. In theory because of this check you don't need to try/catch the code anymore as you have checked for and made sure the vehicle exists before doing anything else with it. When in doubt, try/catch the problem to find the exact code that breaks. Once you know the problem, find out how to make it safe code. Once you have safety checked your code it shouldn't cause any issues (it's still code though and will still throw you a curveball every now and then). This is how you make good, well written code. Keep going and you'll do well 🙂

You don't need a call to Hibernate() as this tells the thread to sleep until another thread wakes it up. The result means it stops processing (it won't even loop through) which means it will block any other threads from processing further if not done concurrently. (Feel free to look up information on multi-threading) What you're doing in your while loop is correct, Yield the thread, this allows other threads to tick through as well and thus not block the game from executing. However having two while loops inside each other not so much. Everything below the second loop won't execute at all. I would add a safety check in so that you're not trying to warp the player into a car that doesn't yet exist. I won't post any code yet on how to solve your problem. I'd much prefer to tell you how to fix it and see if you can learn yourself. However if you still struggle by all means come back to me and I'll help out further. Good luck! 🙂

LSPDFR is responsible for loading your plugin during its setup so no, there unfortunately is currently no way to fully reload your plugin during runtime.

Your topic has been moved to LSPDFR 0.4 Support. Please post in the correct location in the future.

Your topic has been moved to LSPDFR 0.4 Support. Please post in the correct location in the future.

This has now been rectified with 0.4.7 I'll mark this up as solved 🙂

As previously advised you should add comments throughout your code, especially things like Game.LogTrivial("Blip exists:" + myblip.Exist()); as this will allow you to see in your log file where it stops existing (and therefore help figure out why it doesn't delete.

Would need to see the rest of the code to fully confirm. However my guess is for whatever reason the reference in memory to that blip is lost during the runtime of your callout, which means myBlip.Delete(); is never called because the callout doesn't think it still exists. I would check what you do with the blip and whatever you attach it to (if anything) to be sure. When in doubt debug too. Add Game.LogTrivial("stuff here"); at various points in your code and see where it goes and what happens yo your blip.

This is more of a support request than it is a discussion, move to the correct forum for you. This topic has been moved to the appropriate forum. Please post in the correct location in the future.

Not exactly critical but the page for viewing all categories is squished and not using the full width of the white space. It's no major issue and it doesn't make the wiki unusable. Screenshot in spoiler Using chromium based browser with no plugins.

I think you should look at my callouts list and the release date vs albos lol

Somewhere around 3 years lol. It's great to be back 🙂

Hello all! I posted the following large message on my download page! I've also posted the following on my profile! CalloutsV Update Progress for 0.4.6 Updated roadblock, ped check and end callout menus to use RageNativeUI instead of old internal code Added new interaction menu system for player observations and notes Altered native calls and various backend functions to make the plugin more stable and scalable Breakdown callout no longer is a simple "repair the car and leave" scenario (cops don't repair cars lol) Added towtruck functionality to new asisstance menu Oh yeah...Added an assistance menu for different agencies (I will look to making this an API for other plugin authors to add their assistance types) Probably lots more, I forget...

Based on this I would definitely recommend picking up a few generic C# tutorials. But if you want to dive straight in I would definitely grab the API Example plugin (see the links thread pinned in this forum) and start reading it. Anything you don't understand google, anything which google doesn't give you a reference for just ask. Creating an LSPDFR plugin to do something other than a callout isn't too difficult at all. But having a basic pursuit callout and tweaking it bits at a time is a great way to quickly learn what everything is doing and how it all runs together. Definitely check out all of the resources in this forum section if you get stuck. Welcome to the plugin modding scene and best of luck to you 🙂 PS. Never be afraid to ask, some of the best devs here still need to ask questions every now and then.

For anyone reading the above issue I have mentioned in the RPH discord server that I have briefly spoken with LMS on this issue last night. Possibly found the issue but not yet confirmed or fixed. I'll post an update as and when I know more, unless LMS gets to it before me. UPDATE: For anyone reading the issue should be resolved for the next LSPDFR release. Sadly this means you'll have to make do with manual log file debugging for now.

Moderator Notice - Please keep all your videos relating to a particular series in one thread. Normal rules for bumping do not necessarily apply here, it is ok to add a new reply to this post for each video you make. I have merged your two latest threads into this one. Thank you

If people can't be bothered to read that message which is at eye level when you load the forum then I can bet your ass nobody will read a bigger one. From experience, nobody reads the announcements or alerts we put up, nobody read the basic set of instructions for getting support to start with they just clicked "ok" and posted anyway. Nobody reads install instructions properly, nobody reads readme's. My advice? If the amount of "my game stopped working" threads annoy you, stop browsing the support forums.

Yes, but I can counter argue that by saying the exact same thing for Intel so that kind of invalidates your point lol

Ryzen isn't all that great for gaming. You're better off with intel for that if you're gonna go down the route of future proofing.

This topic has been moved to the appropriate forum. Please post in the correct location in the future.

This topic has been moved to the appropriate forum. Please post in the correct location in the future.

This topic has been moved to the appropriate forum. Please post in the correct location in the future.

@Archie 'Dusty' Davies I have merged your two threads here in the media section, you are welcome to post your LSPDFR youtube videos here however please keep them all in one thread rather than a new thread for each time you release a video. @Fenix2525W0T Wrong, the OP is posting LSPDFR media in the LSPDFR media forums, we allow users to do this, that is the point of a media forum. Please do not ever tell other users what they can or cannot do in future. We do not allow backseat moderation.

CPU: Intel Core i7-6700k overclocked at 4.5GHz GPU: PNY GeForce GTX 1070 8GB RAM: 16GB Corsair LPX 2400MHz DDR4 Motherboard: Gigabyte Z170 Gaming K3 Storage: Samsung Evo SSD (250GB), Seagate 1TB 7200rpm, Hitachi 500GB (generic HDD) Peripherals: Samsung SyncMaster SA300 monitor Razer Blackwidow Chroma Razer Mamba TE Chroma Sennheiser HD598 Blue SnowBall Only thing letting me down right now is my monitor. Can't decide if I should spend £800 on a HTC Vive or a 38" curved ultrawide screen. Decisions decisions.

Closing because this has been discussed before multiple times, and we don't need another thread of conflicting arguments about guns and their usage in the police forces. If you feel this topic has been closed in error, please report this post.