LukeD

Try running the game, the diagnostic tool isn't reporting any problems.

They may well try, in truth. I haven't a fucking clue. I'm not one of them lol. they might blow up a post box and laugh at their evil deed, all those poor poor brits who won't get their post. I genuinely haven't the slightest clue. Does she have good security...oh, only the Queen's Guard and the Queen's Life Guard along with the rest of the armed forces that swear an oath to her....I'm pretty certain if an attempt on the queen's life was known to occur or did occur she'd be alright. I mean the woman lives in 6 different houses so you know. You gotta pick the right house first :P

Just for the record, we monitor and prevent. Approximately 600 people are known to have left the UK and gone to countries where extremist groups are. If they are known to the government they get put on a watch list. Those on that list are barred from travelling to the UK, 2 of those involved in the attacks in France we're already on that list and would have been prevented from entering the UK. Also, regarding your quote. I think you'll find he said the following: "Strikingly, working with our partners, we have stopped three UK terrorist plots in recent months alone. Deaths would certainly have resulted otherwise. But we cannot be complacent. Although we and our partners try our utmost we know that we cannot hope to stop everything." The part you're cutting out is the fact we stopped 3 attacks recently, something which you appear to feel is not effective enough? If you go to the source of that quote above you'll also read that for every 1 attack that gets through we've stopped 3 or 4 other attacks over the past decades. Is that not good enough either? I mean we're talking a 1 in 4 chance of failure. That's a 75% success rate of stopping acts of terrorism. The part you're drawing the most attention to is that we can't stop everything. But think for a second at what you're getting annoyed with. Nobody in the world can stop everything from happening. I agree we should try to do more, I agree a more proactive stance should be taken by all. I agree that these extremists need to just be removed rather than try to control them. But it's no good deploying the army into a country to cut down the extremists and then say "oops" when you cause more problems and possibly start a war.

It is compatible yes. You NEED 1.0d to run Callouts+ 0.6. If you had 1.0c, the plugin wouldn't be able to find certain API features and would crash instantly. Just the same as how you can't run Callouts+ without LCPDFR 1.0 installed, it's a plugin not a unique script. It depends on LCPDFR. Now, on to these errors of yours. Both of the errors I read are from the breakdown callout and the barrier feature. These were reported by another user a few days ago, so I've already had chance to fix them. The new release shouldn't be too long now. I'm sorry you're having a few problems, I am working on these round the clock I promise. The best thing you can do to help reduce or prevent the crash you get is to not use the barriers until 0.6.1 is out. From my testing it's the barriers which are causing the issues not the callouts, but I've applied some more safety mechanisms into the callouts too. 0.6.1 should address the barriers issue, but it will also come with a nice new feature that I'm sure you will all like. It will take me a little while to finish the release though, because I'm also in the process of completely rewriting the paramedic, removal team and tow truck. you'll see a significant improvement in these. But that's all I'm telling for now.

I think you made a derp. Error while initializing plugin: Callouts+: Requested value '[' was not found. Show me your ini file please?

Double check what you're doing, it's "reloadscripts" not "reloadcripts" as you put it originally. It definitely works. Oh and it's "callouts+ is" because you're referring to the plugin which is singular. (There ARE multiple callouts, there IS only 1 Callouts+) :)

As the SHDN log file shows: GTA.NonExistingObjectException: Invalid call to an object that doesn't exist anymore! This error is being thrown as a result of the ped in the breakdown callout, the update to 1.0d must have altered something in the loader which I hadn't taken into account. This was reported by another user on my forum thread and has been addressed already and will be available when the next release is done. Thanks for reporting. If you have any other issues, bug reports or things you want to draw my attention to regarding Callouts+ I highly recommend you do so on the >forum thread I have. There is nothing wrong with posting your error log here for the record, it's just that I get notified if someone replies to my forum thread, whereas I don't get notified if someone posts in the support section.

It should do because it reloads LCPDFR which then reloads the plugins. It's also how I get away with not restarting my game every time I change a tiny bit of code :)

Yes they are and I will add this to the user documentation so it's in the next release I make.

So...it's a life simulator? The concept seems nice and if their servers are reeeaaaalllly good and always full of people I can see it being kind of fun. But sadly I can see this being a complete flop in which your money is taken and the project dies. Heres why: 1) Online only, so it relies on the servers being stable and there being enough people. If there isn't enough people you'll be bored for 90% of the time and the remaining 10% will be very fast paced and over within seconds. 2) Unless you get a decent position (like a cop) you're gonna have a shit time. I mean, you own a business so what you stand still for 6 hours, earn money. Drive home then repeat the next day? That isn't fun, no matter how much you roleplay cleaning the floor and counters. 3) Relies on a decent balance of players, it's no good having a server of 100 cops, 2 criminals a 1 store clerk. further, if someone desperately wants to be a cop, they won't stay with a server until they can be one. 4) This is the big one. After a few weeks all the young children who have apparently fucked my mum will be playing, screaming down their £2.99 budget headset they got from a dodgy electrical store in town. whining they got banned/kicked by a shitty admin and failing to roleplay. As will the script kiddies who ruin everyones day. I hate to be the negative guy, cause this does "look" very good. But they're claiming a huge amount of stuff with so far nothing to show for it and people have given money.

I need your ScriptHook and ScriptHookDotNet log files please. The error in the LCPDFR loader isn't reported in the LCPDFR.log file, it's reported in the ScriptHookDotNet log file. Also, yes the plugin is 1.0d compatible, it was built on the 1.0d API.

Fair enough, I would still advise against cheap ones though. I'm not saying go stupidly expensive, but just ensure you are paying for quality and not for brand name. Water and electricity makes me nervous even when done correctly. So I'll stay happy with my 8 fans :)

Yeaaaah, that shouldn't be causing you any issues at all. The line being reported as the cause of the error has nothing to do with the tow truck. I'm in the process of running several upgrades and improving things, so bare with me.

I know nothing about if the card is compatible or not. But "cheap" and "water cooling" are NOT words I would ever put together. If you buy a cheap fan and it's bearings die, you'll gain some heat but you can just replace the fan, job done. If you buy a cheap water cooling system and it leaks, your whole pc is toast. Literally. Cremated horrible toast. As for water cooling in general, it's not necessary unless you strive for a super silent PC, you don't get that much of a boost in cooling from what I know. (but those who have water cooling might give better advice)

If you are using LCPDFR 1.0d, go into the config file and set the following to false: [Main] ... AutoSaveEnabled=True this will disable the new Auto Saving feature that came with 1.0d, and will hopefully improve your performance. If it doesn't, you might have an underlying PC issue.

Hmm strange, I'll take a look through the code later today and see if I can pinpoint the issues. Keep trying to place the barrier in random places if you have the time to deal with constantly restarting scripts, it may be a conflict between scripts. In which case you may well find the issue by trial and error. EDIT: Solved one of the issues with the barrier interacting with the breakdown callout, thus causing a crash. Every other time I placed a barrier it worked fine. Will keep messing with it. In the meantime if you guys can carry on trying to place barriers, each time it crashes for you take note of what crashed (plugin or loader) and tell me what happened prior to the crash.

It seems you did something that tried interacting with the breakdown callout, but it went wrong. Can you tell me exactly what you did leading up to the crash? If I can reproduce it I can fix it.

Update Released!!! Version 0.6 is now available to download! '?do=embed' frameborder='0' data-embedContent>> This version was built on the LCPDFR 1.0d API, so using an outdated version will probably cause issues. Be sure to update. Not much is included in this version, mostly bug fixes. but I included a new callout and some config file changes too. go play, let me know how it runs! :D Oh and HAPPY NEW YEAR :D

Nothing to see here! This topic has been closed by LCPDFR.com staff as it is a support topic concerning an unsupported version of LCPDFR. We do not support old versions of LCPDFR, and recommend you use and download the latest version. If you feel that this topic has been closed in error, please report this post.

Generally speaking when you release an update, you fix bugs and add content. (more than likely in that order too). So yes, any new version of LCPDFR will attempt to improve the stability of the game for you, there is only so much they can do though. So if I were you I would get used to the fact it will never be perfect. Also, don't be worried about any new versions being buggy. Chances are there will be bugs that have gone unnoticed. These bugs get reported, and if possible fixed. Remember in 1.0a, pressing the key for the different light modes crashed the game? Fixed in 1.0b. :)

Spend half an hour messing with graphics settings, see how much my pc melts running it on maximum. Re-complete story in first person. Fail miserably. Have to spend twice as long completing it. Blow lots of shit up. See how long I can last in a police chase in first person. Die lots.

Not true, VAC covers over 300 games including non-Valve titles, a VAC ban can be issued on any account that has evidence of cheating via report or via the VAC system. The ban is not issued instantly upon cheat detection, usually days or weeks after the initial detection. http://store.steampowered.com/search/?category2=8

You can search the Met police website for information, unit specifics I think are published (so you can get a rough idea what different acronyms mean). To be honest though your best bet for vehicles would be to post the ones you don't know and let the UK members give you answers. EDIT: Or do what Lund Said :)

MODERATOR NOTICE Topic moved from Website & Community General to LCPDFR Suggestions.

This has been suggested so many times before, and has been answered too. As Will stated above with his Sam quote, it's very difficult to do. GTA IV's AI is shit to put it bluntly. Trying to get them to perfectly pull in behind the player at ANY position on the map is a lot harder than you think, yes it would be cool, just very difficult. You then also have the issue of distinguishing if you need traffic stop backup or normal backup, adding a unique keybind is a no go given the number of keybinds you already have. Maybe we'll see something from the Dev's that will blow our minds, maybe we'll see a concept. But don't go expecting and getting your hopes up is my advice, this isn't as simple as you would think.