johnclark1102

Microsoft confirms that GFWL will continue. http://www.ign.com/articles/2014/06/30/microsoft-confirms-games-for-windows-live-will-continue

Most "clans" generally prohibit the distrubution of their materials outside their group. In many cases, these packs contain exlucsive content that was created by the members of the group, for the members of the group. In almost all cases, they contain content that is freeware and publicly available on websites like LCPDFR.com and others, simply with a custom livery on it. I suggest you check out the link that SCSDeputy posted and find some cars in there that you like. There are several packs of cars available there that are quite good.

It's somewhere in data/maps/east Unfortunately, I'm not going to get any more specific than that. It took me weeks of searching through every single map file to find it; but the hunt is part of the fun, and putting in the work is the best part of the reward. Keep looking and you'll get it; it's out there, waiting to be found.

LMS, after some further testing it appears that this command is at least partially working. LCPDFR now always responds to my keyboard inputs, even though the on screen prompts are showing the conroller buttons. Previously, if the controller buttons were shown on screen the script would only respond if I used the appropriate controller button.

Thanks. After testing again with the line in the main section, I can confirm that it is not working for me. Looking forward to an update in the future; thanks again for looking into it!

Thanks for the response! So far I haven't been able to get this feature to work. Could you provide some guidance on where the line is supposed to go in the .ini file, or what other steps need to be taken to enable this feature and I'll try it again? I've just been trying it in random sections of the .ini file so I'm not even sure if I'm setting it up correctly.

I hate to bump a topic, but I've been looking all over the forums and haven't found anyone else talking about this new feature to force the keyboard inputs and I haven't had any luck figuring it out on my own. So, I wanted to bump this topic in the hopes that someone who knows how to use this feature will see it before it fades into oblivion. I'm dying to try out 1.0C, but until I get the controller / keyboard conflicts resolved, it's simply not playable for me.

You could just re-install the game. Or install it a second time to a different folder to have as a back up copy; that's what I did.

No worries, I'll wait for LMS to come along and provide his insight while I keep working on figuring it out. Thanks again!

Thanks for the help. I tried adding it to the "Main" section of the config and it didn't work. I'm going to try adding it to some other areas but, I also thought it might benefit others here to have some guidance on how to enable this feature since the .ini file hasn't been updated. Where are we supposed to be adding this line to make it work? Does it even matter where in the .ini we put it? "AlwaysForceKeyboardInput=True" Or is it just: "AlwaysForceKeyboardInput" Without the need for a true / false? I couldn't find any information about this new feature in the documentation; the only mention I've been able to find for it is in the patch notes so I'm just not sure how to take advantage of this new feature.

So, I was very excited when I saw in the patch notes for 1.0C that controller input can be disabled now, by using the "AlwaysForceKeyboardInput option in the configuration file". Well, I cannot find this option in the configuration file. I've looked through every line, I've used CTRL+F to try and find it, and I can't seem to locate it. I've tried using the automatic install, and the manual install. Does anyone know where can I find this option in the configuration file?

Most of the agencies where I've lived do not use traffic advisors. They almost all do have some sort of amber lights facing the rear of the car though, whether a simple amber flasher in the rear window or something integrated into the light bar. I believe State law here requires all public service vehicles display some sort of amber to the rear. I actually did some research on lighting packages recently and found a traffic study that showed that drivers slowed down noticeably for multiple colors like a mix of red / blue / amber, more so than if any one single color was used. The study was conducted by placing a stationary light display in the shoulder featuring different light configurations, colors, and patterns, and an observer was monitoring traffic speed on radar and visually monitoring lane changes away from the light display. Volunteers were also polled via survey about their opinions of certain light colors and their meanings. The conclusion of the research team was that a majority of drivers associate amber lights with tow trucks or other civilian service vehicles, red lights with fire or medical vehicles, and blue lights with police vehicles. The poll also determined that drivers most often assumed a severe incident had occurred, and slowed down and moved over more frequently when they saw a mix of light colors and patterns. The same study also showed that amber alone showed almost no decrease in driver speed or change in behavior, where as use of red and/or blue resulted in driver speed reductions and lane changes away from the lights, and a mix of all 3 colors resulted in the greatest speed reductions and lane changes. So, the research study determined that a mix of different light colors can give drivers the impression that there are multiple vehicles from various sources on the road, and that motivates more drivers to slow down or move over, thus a mixed combination of various light colors and patterns was recommended as optimal for safety. The study was conducted by the Texas Department of Transportation some years ago when they were equipping the DOT vehicles with new lights, which now use a standard amber / blue configuration on all DOT vehicles instead of their previous all amber configuration. Long story short, everyone has an opinion on light colors and uses. Ignoring the research I've done and the traffic study I've found, my opinion has always been that traffic advisors are pointless and there are better ways to use lights on vehicles. If you want to make a vehicle without one, then go for it.

I use .95 because it's more stable in multi player which is the only way I use LCPDFR. I'm dying to take advantage of some of the new features in 1.0, but testing and experience shows that we can play multi player games a lot longer with .95 at this point. I'm sure there will be more updates to 1.0 in the future and maybe those will be a bit better for multi player, but as the LCPDFR team has said several times, it's not designed for multi player. Unfortunately, that means that most of the new features implemented with 1.0 are counter productive to the way I use the mod. I used .91 for a long time after .95 came out too so, that's just how it goes some times. I'm hoping one day to be surprised by a multi player version of LCPDFR, but only time will tell. Maybe one day I'll take up scripting and learn how to do something like it for multi player the way I'm learning how to use zModeler to make cars. All I need for multi player is the ability to conduct traffic stops and interact with peds. I don't need the radio chatter, AI backup, AI paramedics, the computer system, the quick action menu, or a majority of the other functions LCPDFR brings to single player. A simple bare bones script with traffic stops and AI ped interaction is all that is needed for multi player. Until fortune smiles my way and that day comes, I'm happy with .95 and possible future versions of 1.0 with more stability in multi player, and I'm very excited for all my single player brothers out there that have such an awesome mod like LCPDFR to help make their experience a bit more fun.

I'm sure they have. People like Sam and his team don't really ever stop working on improvements and upgrades. As soon as they finish something, they end up thinking about all the things they had wanted to do and how they can do it better next time and it always leads to long nights of combing through project files trying to get it right. That's the problem with being a creative person; I know from experience... I'm confident they are still working on the next version, while also still trying to field support requests and manage the LCPDFR community as a whole. We'll see an update as soon as they are done tinkering and feel like they've made enough changes to warrant a new version, and have had enough time to test and assemble the new version.

I haven't noticed any issues on my computer, but I am running a high end machine so maybe that helps. I did some searching and it looks like you cannot just downgrade. The only way I can think of to use an older version would be if you happen to still have the original install for that version, or can find it somewhere online, then uninstall 2.2.6 and install 2.2.4. I wouldn't personally trust any download links for an older version though, unless they come from a reputable source, which will be hard to find for zModeler I'd think.

What's wrong with 2.2.6? I've been using it since I started modeling and it works fine.