PNWParksFan

Come on people, do a least a little itty bit of research for yourself when you hear a claim like this, and don't jump to conclusions. The EPA is not banning "all car mods", and they're certainly not banning you from putting dumb-looking bling on your crappy 90's honda. Even the car industry lobbying site which first reported this clearly stated in their article that the new regulations would apply only to modifications which convert street-legal cars to racecars and which affect the emissions control system (e.g. the catalytic converter, OBD II computer, etc.). In fact, even that claim (which again, was never to ban all mods!) is mostly false according to snopes. No new ban would be implemented at all; the EPA is simply clarifying the language which defines the distinction between a "motor vehicle" and a "non-road vehicle", for existing laws which already prohibit these types of modifications.

The default LSPDFR Backup.xml file will be unaffected. There will be an additional CustomBackup.xml file which will let you customize any area in great detail. If no entry is found in the custom file for a certain area, then it will default to the LSPDFR backup.xml.

It is an additional menu which is functionally equivalent to the default menu. You can either configure it to a different key/button so that you can still use the default LSPDFR backup menu if desired, or you can override the default menu and only use the custom menu. At this point I think we're good on testers, as it's nearly ready for release. I'll let you know when I'm developing future updates if you'd like to help test new features later on.

There's at least one tahoe, several explorers, an F150, and a suburban all floating around. Browse the vehicle models download and you'll find some options.

Thank you very much to all the beta testers who have been helping get this ready for release! I'm planning to get the first public release up by the end of February. Nearly there... just a bit more testing to do, documentation to write, etc.

You've got the right idea for what I'm looking for. I agree that it seems it may not be possible. Major vehicle nodes still seems to pick up points on unnamed roads, so that doesn't work. Using the asphalt filter is effective, although there are a handful of named dirt roads out in the Senora Desert and Raton Canyon areas (and possibly elsewhere too). I'll just have to make do with this combination of natives to do a best approximation. If anybody can figure out a reliable way to actually figure this out I'd be thrilled to hear!

I see that my question wasn't entirely clear. Here's an image to illustrate what I'm talking about: The issue is that both the RPH World.GetStreetName and the native GET_STREET_NAME_AT_COORD return the name for the nearest street that has a name, but that street may actually be quite far from the point of interest (for example, the purple X in the image above). You can't just use GetStreetName because you may not even be on a street at all. You also can't just check for IS_POINT_ON_ROAD because many points are on roads which are unnamed, like the red/blue X shown in the image. If you try to get the name at the red X, you get Great Ocean Hwy. If you try to find the next position on street, you get a point basically right next to it on the same unnamed road, which will also tell you the name is Great Ocean Hwy, even though you aren't on the highway at all. What I'd like to be able to do is determine how far away the nearest named road is from a given point, and what the name is. I can figure out how far away the nearest road is, and I can figure out the name of the nearest named road, but those two roads may not be the same because of how many unnamed roads there are.

World.GetStreetName returns the name of the nearest named street, but does not indicate how far away that is, or if a closer road exists which is unnamed. I'd like to be able to detect if a Vector3 location is on or near a road with a particular name - and ideally be able to tell how far away they are from the nearest point on the nearest named road. Using the native IS_POINT_ON_ROAD you can tell if the location is on a road, but that returns true if the point is on any road (or even dirt path). Using GetStreetName always returns a name even if you're in the middle of the desert far from any roads. Using GetNextPositionOnStreet and checking the distance from the point of interest to that point helps if the next position is on the named street, but if you're on an unnamed street then the next position is often also on the unnamed street and you're back to the same issue. So, does anybody have suggestions for a reliable way to detect the nearest named street, and how far away a given point is from the nearest named street?

Got it. That makes sense, I just wasn't sure which was which. IMO the naming is really unintuitive. Is there any way to contribute edits to the RPH documentation? It would be some enough to describe what you just said in the docs to clear it up for future developers.

So, what does "right now" vs. not "right now" mean in the context of IsKeyDown and IsControllerButtonDown?

I believe it's case sensitive. In at least one place (maybe more) you have <vehicle> when it should be <Vehicle>. Also, in the future, please use code formatting (the <> icon in the editor) and collapse using the eye icon, so it doesn't fill up the whole page with text from your file.

Yup, I did end up using the AutoItX3.dll solution.

I'd like some way to send keystrokes to the game. I tried using SendKeys as built-in to C#, but it doesn't appear to actually register with Game.IsKeyDown. Is there any other way to emulate a user pressing a key in-game?

Perhaps we could just put an updates.ini file in the LSPDFR plugins folder with one entry, and all plugin authors could check that file to see if updates are enabled. That would let users only have to make the choice once to allow or not allow auto-update-checks, instead of having to modify it in every single mod's INI file.

Shared plugin resources of some type must be possible, see @albo's albocommon.dll for example.

Good suggestion to look into the issue of going on/off duty possibly creating multiple menus. I'll check into that. Thanks for the feedback guys.

The fleet: