We need you to copy and paste everything from the white text box. You can get this when it crashes by clicking on "send report", then on "details". When you crash on OSX we will need to see your stack trace. See this article on Valve Developer Wiki: These contain information we can use to work out why you have crashed. (Usually SteamApps/common/GarrysMod/) They end with. You can find crash dumps in your game folder. They should be of the date the crash happened. You can find out where to find crash dump files below. If you are unsure how to report a crash, you can create a new issue on official Garry's Mod bug tracker, after reading the read me on the front page, and attach crash dumps as well as steps to reproduce if possible. If you were linked the page, that means we just want the information mentioned above from you. You need to provide information on how to reproduce the crash when possible, a crash dump or at the very least the console log at the moment of the crash. If you're crashing - then just telling us you're crashing isn't very helpful. Reporting bugs/crashes relating to Garry's Mod itself If you don't use equivalent or better hardware, don't expect to run Garry's Mod. You can find them on the Steam Store page for Garry's Mod. Please make sure you meet the minimum specifications to play Garry's Mod, shown below. See below for more instructions on how to be most helpful. In this case the only and the best thing you can do is to report the crash to the developers of the game, either on GitHub, email (found on the GitHub website linked below) or on the official Garry's Mod Discord Server. It's possible the crash is just due to a Garry's Mod update. Both AMD and NVidia drivers are known to create issues like this sometimes. You should try to update your drivers and if that doesn't work, roll them back to a version older than the one you initially had. If your game is crashing on start up without any error messages, it is very likely an issue with your drivers. Send a message to the creator of the addon, along with the specific error if any appear and what you were doing when the crash occurred. Once you are done testing, you can simply remove those 2 commands and the game will go back to normal. You can safely and quickly run your game without any addons by adding -noworkshop -noaddons to your launch options for Garry's Mod through Steam. It is also possible it's simply the sheer amount of addons you have installed. If it does, you'll need to enable them one-by-one or in groups to see which one is causing the crash. If that does not help, try disabling all of your addons and unmounting all your mountable games temporarily to see if that fixes the problem. You will want to make sure to let the addon author know about the problem. If so, then it's likely the addons fault. If you just installed an addon, disable it and see if that stops the crashing. Please visit the following articles on our official support website: The first thing you should do is eliminate common crash issues that are outside of our control. This article explains what to do to try to solve the issue, why it might be happening, and what to do to be most helpful in reporting the crash. I've also added debug prints to every line of the code to see where the issue was and the bug fixed itself when I added them but when I removed them the bug came back.So, your game is crashing. I don't know what is happening.Īlso, side note, the function gets called multiple times per second based on the player's movement. I tried recalling them but that didn't work at all. Self:RecomputeTargetPath(self:GetEnemy():GetPos())Īs far as I know, all variables in the if are called before each. It's used in the context of an if that looks like this or something very close: if (CurTime() - self.LastPathRecompute > 0.1) then When this function is run, it recomputes the target path for the nextbot to make it move differently. If (CurTime() - self.LastPathingInfraction 0.005) then PrintMessage(HUD_PRINTTALK, 'recomputing target path') here is the function: function ENT:RecomputeTargetPath(path_target) So I have been coding a nextbot in Gmod for a while now and have found a bug that causes Gmod to crash every time the function is run.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |