ainesophaur

If you change the ini to have DPadRight as the open controller binding, do you still have issues

I'm having a hard time understanding it then as you're the only person to report the problem since I added it four versions ago. Can you provide a screenshot of the directory with the path to the peds folder ?

What are you using as your keybinding? I've noticed if you press the pause game button (default is p and escape) while computer+ is running it locks up the game. If you've set your keybinding to the same key then it locks up completely

Your structure should be as follows Plugins\lspdfr\computerplus\backgrounds Plugins\lspdfr\computerplus\images Plugins\lspdfr\computerplus\images\peds Plugins\lspdfr\computerplus\images\vehicles The images folder is a sibling to the backgrounds folder and the peds and vehicles folders are children of images. Please confirm that is your directory structure

There's probably a handful of vehicle and ped images that I couldn't find or were part of a dlc after I compiled the images. We're going to rely on the community to help us maintain the images. Before we switch directions towards 1.3.5.X I'll probably have the beta testers help me compile a list of missing images.

Below is the view of my peds folder. If your path is correct and the content looks like mine, you should see the images.

What was the last version that you used that didn't crash in that manner?

If you're coming from 1.3.4.4 or one of the hotfixes then just the DLL. If you're coming from <1.3.4.4 you'd be better off to replace both and change the ini settings as you wish

I just realized that the previous hotfix introduced the bug where the key press listener wasn't only occurring when the player was in a vehicle. Can you try out ComputerPlus_1.3.4.4_hotfix_e59697a which was just posted? @grizzleftw The reason I set it to none by default was the default prompt for telling you what to press to open would cause confusion for people who didn't have a controller.. but the next release (with arrest reports and tickets) will put back the default of DPadRight along with a check to see if the user has a controller plugged in This has been resolved with ComputerPlus_1.3.4.4_hotfix_e59697a Inside of Plugins\LSPDFR\ComputerPlus\images is a peds and vehicles folder. If those folders contain images then you should be seeing them in game. Those folder images come from the download Additional_ComputerPlusImageAssets.zip

It's complaining that your Plugins\lspdfr\ComputerPlus\backgrounds folder is missing or the requested file doesn't exist in that folder. Did you modify the backgrounds section of the ini file? If so, make sure the filename exists in the above folder. That folder should have been part of the .zip file

I'll have to look into this.. AFAIK nothing in that area has been changed. Can you attach your RagePluginHookLog.txt?

@SHERIFF/EMS/FIRE @Giomig24 @anters14 @JethroMcCain @devonjones @billiarboy @minddriver @DutchXarms Fixed :)

@Anters, @Giomig24, @SHERIFF/EMS/FIRE can you let me know what you had in your KEYBINDINGS section so I can test it tonight? As much as I like to, I really don't feel it'll provide enough worth as much as it'll cause more support issues. Here's why.. When the game is paused, we're able to exclusively continue our plugin logic while halting others from receiving key presses.. Example, when the game is un paused and c+ is running pressing X will force a call out or pressing shift will cancel the traffic stop. I'm actually going to add a warning dialog the first time the user unpauses the game.. As much as I feel like the warning hurts user experience (in cases like yours where you want it to always be unpaused), I have to always keep in mind there are new LSPDFR and Computer+ users. The confusion from unpausing the game and keybindings from other plugins will cause an overwhelming amount of support requests when users are unaware of the consequences. I may reevaluate my stance on it in the near future, but I at least wanted to let you know my reasonings. After further testing, it seems keypress events still do go through. This request may be considered more in the future.

For everyone having issues with the latest beta opening, try to delete the entire KEYBINDINGS section of your config and reload the plugin. It should warn you that your config is invalid and should then use the previous logic to open (holding the same button as the regular computer) -- if it works, let me know. I'll investigate more tonight.

Since this seems key bindings seem to be an important feature, I'll look at pushing it out before arrest reports.

@Singleton , @Kilyin next version will allow for you to change it