Jump to content

PeterU

Members
  • Content Count

    107
  • Joined

  • Last visited


Reputation Activity

  1. Like
    PeterU reacted to PNWParksFan in Most problematic issues with LSPDFR 0.3.1 API that ought to be fixed in 0.4   
    I'm aware of Sam's post regarding plans for an API update after the main release of 0.4, and look forward to more discussion of that in the near future. In the meantime, with release fast-approaching, there are a handful of major issues that have caused headaches for many developers using the LSPDFR 0.3.1 API which I am really hoping will be fixed in 0.4: 
     
    During pursuits, Cop and Suspect Ped tasks are reset every 2 seconds. Functions.SetCopAsBusy doesn't consistently prevent this from happening. This makes it nearly impossible to alter how suspects and cops behave in pursuits, e.g. if you want to make a suspect jack a new vehicle (their enter vehicle task will get terminated before they're even in it), or have a cop do something in particular. SetPursuitDisableAI turns off all AI for the entire pursuit, there needs to be a way to disable AI on individual peds (cop or suspect). 
      Whenever LSPDFR is running, regardless of whether a pursuit is active, all law enforcement peds in the game (even add-on peds) can't change their secondary accessory/vest clothing component, because of LSPDFR's holster management. This makes it entirely impossible to give plugin-spawned peds specific vest clothing. 
      SetPedAsArrested doesn't actually seem to do anything, leading to a bunch of mods doing their own "arrested" implementation involving animations and trying to clear tasks, which sometimes conflict. 
      If pursuit suspects get far from the player, the pursuit goes inactive and if they're very far away terminates. This makes sense in default "bunch of cops chasing a car on a road" situation, but doesn't make sense in a lot of other scenarios. Constantly looping SetPursuitIsActiveForPlayer is super glitchy and doesn't really work anyways.   
    Obviously there are many more things devs would like to see in the API once we get a sense for what new features LSPDFR will have to offer, these are just a few of the biggest issues IMO that have really hindered plugin development over the past couple years. 
  2. Like
    PeterU reacted to Sam in LSPDFR 0.4 - Information for developers   
    As LSPDFR 0.4 nears completion, we hope this topic will help in providing some clarification for developers who make use of our API about what the changes in 0.4 mean for them and their work.
     
    Firstly, the significance of the changes to LSPDFR that 0.4 brings can't be overstated.  LSPDFR 0.4 introduces changes to almost every aspect of the mod and will take a little getting used to.  We think that the overall experience is much improved from 0.3, and a lot of the features that we introduced in 0.3, or earlier versions, have been dramatically changed, expanded upon or entirely re-worked.  It's important to keep this in mind as such drastic changes will unavoidably have the potential to cause issues across the board.
     
    In regards to our current approach, our main priority at this time is to release a public version of LSPDFR 0.4 as soon as is possible.  In short, this means that our focus is and has been very much on the core experience of the mod.  As a result, while we will still ship the first public release of LSPDFR 0.4 with a functioning API, it will not be substantially different from the current LSPDFR 0.3 API.  Additionally, we are committed to ensuring that custom callout plugins remain compatible with LSPDFR 0.4.
     
    We understand that this approach might cause some initial disappointment, but we think it is the most sustainable way of doing things both in terms of people being able to play 0.4 as soon as possible (which obviously is very important), but also from an API and development perspective.  As said above, a lot has changed in 0.4 and we want developers to have the opportunity to properly familiarise themselves with the new version and get a feel for what sort of content they'd like to create and what sort of things they'd like to change.  
     
    Just like with previous versions of LSPDFR, we are committed to pushing post-release updates and hotfixes for 0.4, with a view to following up with a minor 0.4.1 version, which will focus primarily on extended API functionality.  During this process, we will work with developers to incorporate their suggestions and requests for the 0.4.1 API, and will also provide development builds of 0.4.1 to developers for testing.
  3. Like
    PeterU got a reaction from Stickmangames0 in Computer+   
    To re-enable the controller binding for opening Computer+, you may need to look at its .ini file. I believe a recent update disabled the controller binding by default.
  4. Like
    PeterU got a reaction from gouliouras in LSPDFR not launching   
    I have compared the trace you provided in PM to a similar trace when I launch RagePluginHook.
     
    It appears that RPH is not detecting that you have read the disclaimer that appears on first launch, thus is not even getting far enough to attempt to launch GTA.
     
    This itself isn't the problem, but it implies that there is a problem with RPH being able to render its screens at all, before it even starts trying to launch the game or anything.
     
    There are a few possibilities I am seeing from the trace:
     
    Could you disable RivaTuner or the MSI AfterBurner software if this is installed and try again? Could you disable NVIDIA ShadowPlay if this is running and try again?  
    The final line of the trace shows that a Windows Error report was attempted to be saved. Could you open Event Viewer from Start > Windows Administrative Tools. Look under Windows Logs > Application and click Find on the right. Search for RagePluginHook for any entries that may give us further details.
  5. Like
    PeterU got a reaction from idklol37 in LSPD:FR crashing after going on duty   
    It will be necessary to see the RagePluginHook.log file in your GTA V folder to have any details of what has gone wrong. Please post this in a spoiler tag.
  6. Like
    PeterU got a reaction from Maxmov in How to run GTA:O with LSPDFR installed?   
    The best approach is to maintain two copies of the game folders and swap between them depending on whether you want to play GTAO or LSPDFR etc. Albo1125 has a great video on how to do this.
  7. Like
    PeterU got a reaction from Stickmangames0 in Computer+   
    As with any plugin update, download it from this site and copy the files in the downloaded package into your GTA V folder as the instructions will say.
  8. Like
    PeterU reacted to godwarrior199 in not loading when going on duty   
    thank you so much it   fir the  problem 
     
  9. Like
    PeterU got a reaction from Kalleboston in Question about game files   
    The 'common' files that many mod authors release allow them to avoid writing code that does the same thing and including it in multiple different plugins.
     
    In general, you can replace these files when adding a new one that also includes it — just make sure that you do not replace a newer version of the "common" file with an older version. You can check version numbers by right-clicking the file, choosing Properties and going to the Details tab.
  10. Like
    PeterU reacted to BQCOM in RAGE loading and loading   
    Thats it! Thank you.
  11. Like
    PeterU reacted to JBuzz826 in Frame drop when approaching suspect during traffic stop   
    +1 to the above. I had keep calm installed and it caused many lags. I couldn’t even get it to run smoothly. I have realistic speed radar and lspdfr 0.31 and Albos plug-ins and a few callout packages. Mainly Tacco and Wilderness and PeterU Callouts. 
     
    @PeterU thanks for developing a great callout Pack by the way! I love responding to all of them. Keep up the great work. (I know this is off topic but wanted to publicly thank you.)
  12. Like
    PeterU got a reaction from Jacrispyxd in Help with going on duty   
    Does nothing at all happen on F4, or does the game pause/resume when you press it? This will help us know whether the RPH console is working at all, or if you just can't see it.
  13. Like
    PeterU got a reaction from MikeVidlak in error   
    Please also check that Windows 10's "Game Mode" is switched off in the Settings app.
  14. Like
    PeterU got a reaction from President Shadow in Hurricane Harvey support drive and matching donations   
    I'm very happy to support this effort and have made a $25 donation. It's wonderful to see an opportunity to bring our communities together to make a difference and I hope others will be able to contribute what they can.
  15. Like
    PeterU got a reaction from FirstThirtyMinutes in Hurricane Harvey support drive and matching donations   
    I'm very happy to support this effort and have made a $25 donation. It's wonderful to see an opportunity to bring our communities together to make a difference and I hope others will be able to contribute what they can.
  16. Like
    PeterU got a reaction from PNWParksFan in Hurricane Harvey support drive and matching donations   
    I'm very happy to support this effort and have made a $25 donation. It's wonderful to see an opportunity to bring our communities together to make a difference and I hope others will be able to contribute what they can.
  17. Like
    PeterU got a reaction from Kallus in LSPDFR , crash after all plugins load ! pls help   
    It looks like you haven't installed all the components needed for the Police Partner mod.
     
    Try installing the latest DarkAPI and try going on duty again.
  18. Like
    PeterU got a reaction from VioletHell in LSPDFR , crash after all plugins load ! pls help   
    It looks like you haven't installed all the components needed for the Police Partner mod.
     
    Try installing the latest DarkAPI and try going on duty again.
  19. Like
    PeterU got a reaction from Starmix in British Policing Script crashes my game   
    Please provide a RagePluginHook.log file. Without this, we won't be able to find out what exactly is causing the crash.
  20. Like
    PeterU got a reaction from ToastinYou in Would someone mind sharing their update check code?   
    An update to my update checking mechanism. Now I run the actual HTTP requests inside a non-GameFiber Thread, which means the game doesn't drop frames while we wait for the HTTP response.
     
    https://gist.github.com/LSPDFR-PeterU/952de66a4f17b838d3870bdaabb6c43b
  21. Like
    PeterU got a reaction from PsiLance in Lspdfr+ Statistics error   
    It looks like something is corrupt in your LSPDFR+ statistics file.
     
    Please rename GTA V folder\plugins\LSPDFR\LSPDFR+\Statistics.xml to something else (e.g. Statistics.old). Then start the game again.
     
    Does this still occur?
  22. Like
    PeterU got a reaction from Vaskulis in [Fixed] Computer+ API check crashing   
    Are you able to share the code for the Computer+ integration wrapper class you have?
     
    Do you have any references to ComputerPlus or ComputerPlus.API anywhere other than in the wrapper class?
     
    It sounds like there is a reference to the ComputerPlus or ComputerPlus.API namespaces that is outside the wrapper class, which would cause the system to try to bind to that assembly when it is not there.
  23. Like
    PeterU got a reaction from ToastinYou in Lspdfr+ Statistics error   
    It looks like something is corrupt in your LSPDFR+ statistics file.
     
    Please rename GTA V folder\plugins\LSPDFR\LSPDFR+\Statistics.xml to something else (e.g. Statistics.old). Then start the game again.
     
    Does this still occur?
  24. Like
    PeterU got a reaction from ToastinYou in [Fixed] Computer+ API check crashing   
    Are you able to share the code for the Computer+ integration wrapper class you have?
     
    Do you have any references to ComputerPlus or ComputerPlus.API anywhere other than in the wrapper class?
     
    It sounds like there is a reference to the ComputerPlus or ComputerPlus.API namespaces that is outside the wrapper class, which would cause the system to try to bind to that assembly when it is not there.
  25. Like
    PeterU got a reaction from tboes in Callout Manager error or something wrong with callouts   
    The way that the core LSPDFR callout system works is that there are a handful of set callout priorities from "low" to "always" if I recall correctly.
     
    Based on those priorities, LSPDFR picks a weighted random callout from the available callouts and starts it. However, there are plenty of reasons that the callout might "refuse" to run after being chosen. My callouts, for example, will decline to run if you are too far away from a spawn point for that callout, among other reasons.
     
    When you use Callout Manager, it force triggers the callout you choose rather than LSPDFR's random system. If LSPDFR picks a callout randomly, and that callout declines to run, typically you'll never even realize, as no message is displayed!
     
    So usually, this will be why Callout Manager says it "fails" to start the callout — the callout has declined to continue for some good reason. If you're curious, press F4 to bring up the RPH console. I always try to leave a message in the log explaining why the callout will not start on that occasion. Hopefully other developers do too!
×
×
  • Create New...