Roane County, Tennessee, USA 19.3.1

Use VULKAN, it'll partially get around the draw-call (CPU) spikes you get when using DirectX renderers. DirectX 11 uses a single-core path to send render data to the GPU via the CPU. Vulkan uses a multi-core path to send render data to the GPU via the CPU. This is obviously superior, though how much so is dependent on how far the renderer is along in progress (they're working on it with each version). So sorry about that one, but I learned a lot of lessons - many things good and bad - so that I can make sure Los Injurus doesn't do this too.
This same issue plagued early versions of MS Flight Sim and even Fallout 4 in downtown Boston (especially with scrap mods).
Lag spikes are worst in Harriman by the big bridge, with an honorable mention going to a spot in the middle of Kingston's main commercial row.

Lots of stuff to Explorer, and lots of mountains to Mountaineer too.
So enjoy the Excursion from typical Suburban life and Escape to the wilderness that holds entire Enclaves of trees (and probably, Bugs).
"Heh"

The train feature is a bonus and not really something intended for extended use. The lack of precision in floating-point coordinates (float = rounded) means the tracks can move an inch or two this way or that between run-times of the map (times it's loaded up). So even if I had them perfect, the size of this map + floating point coordinate issues = fail.
Please stick to using the roads only, and only using the tracks to crash trains into cars. Sorry but there's nothing I can do about the trails derailing.
The precision issue is magnified by map size, the larger the worse it is. So the tracks should work fine in Los Injurus if you need to use them badly.
I wish I could have given you a better answer, but this is inherently a limitation of the game engine and nothing I can fix within reason.

The low visibility keeps the FPS up. I wish it did not have to be like this (and in the future, I will re-do the map once Los Injurus is close to done or completely done, to help this), but it must be like this to keep FPS high in such a large map.
Doubling the view distance makes the FPS dive to about 1/2, or less FPS, as the amount of distance is a radius around the player. That mean things in the mirrors, things in-front of you, and things to the sides (what is still in view anyways) are all being drawn 2x as far out. This adds A LOT of work for the CPU (not as much for a GPU oddly enough) due to all the extra render (draw) calls, causing FPS to drop and the CPU usage to spike. Downtown Harriman is already possibly the worst-performing spot on any map in the entire game, and this is the only thing that saves the bacon.
In the future I may be able to remedy this, but it will be after Los Injurus is completed and I will then be porting models from that over to this map as they're more optimized for speed.
--Glad you enjoyed the map. An update to THIS map may be posted Mid-July or so. This date is not set in stone however.

The March 2021 update caused the old 2016-era texture normals (bump mapping) and possibly a few specular mapping textures to break, but the main visible (diffuse/colormap) texture works fine.
So the map works, but the extra texture layers broke due to no longer supporting the old PNG normals. That's alright though, it is over-due for an update and will get it this summer, though it's only going to be a patch for compatibility reasons (not a map progress update).
Do know an update is coming sometime possibly by mid-July.

The shaking is due to inherent limitations of floating point processor operations / design of the game & physics engine. Normally, you don't notice this, but get a few miles out from the center and you'll see a tiny bit of vibration. Go a few miles more and it's a notable shake. Go a few miles more and it's really starting to look like the vehicle is on it's last legs - or is that wheels? Continue for about 100 miles in the same direction away from the world center (which is what matters) and the vehicle will be all over the screen!
Floating point operations are exactly that: a FLOAT, or rounded numbers; not medically precise like an arithmetic logic unit (ALU, a standard CPU core) would put out. Though, that being said, ALU operations take much longer VS FPU operations - which is why we can simulate 2 vehicles per modern 4+ ghz core VS a slide show.
The vibrations are only visual, there is no detriment to the physics engine.
So basically, while you love the map, and I've put thousands of hours into working on it; please do not dock the review over something I have no ability to change/fix/do anything about.
I do appreciate you taking time to review, however.
--Cheers!

Thanks for going the extra mile - literally!
I will check the video out when I have some free time, and a decent internet connection. Thanks again and feel free to make some Los Injurus videos if you have the desire to!

Might be a game engine bug, not my map. Consider setting your resolution to 1920x1080 or 1920x1200 (whichever suits your monitor best), and then trying. That should fix your issue. I will let the developers know of this bug as it's likely not my map.

Thanks - when you want to just drive, or have a good car chase for miles, this is the go-to for it. It's not super detailed, but can't argue with pure road mileage, even if the car seems to vibrate when you get closer to the map edges (it's a limitation that is merely visual and does not affect physics in any way). And to think, I was told this map wouldn't be possible and would never work. Never hurts to try!

FPS drops will happen due to CPU on DX11 games now and then such as:
This game in maps such as Roane County, Italy, West Coast, Los Injurus, and American Road, and some others
Microsoft Flight Simulator 2020
Fallout 4 in downtown Boston areas and other built-up places.
A few other titles also that weren't worth listing.
This happens due to all the different surfaces that need to be rendered, and the fact that every render call the GPU gets must go through the CPU first. DX 11 generally only handles draw calls on a single core of the CPU.
In this game, whenever the map scene hits 4000~5000 draw calls, slowdown can be expected. So lots of complicated different models can cause slowdown without very intense work in optimization.
DirectX12 and Vulkan both fix this by having multi-threaded draw calls pretty much standard.
So while I can't really remedy this at this point, I can plan around it with future maps.
Still, I am glad you enjoy the map and wish you much enjoyment on your relaxing (or invigorating) drives around Roane County.
--Cheers!

They said a map this large couldn't be done.
They said it's too much and would hitch... (streaming improved in game versions 0.7, 0.8, 0.9 and up).
They said there were too many map limitations (object limit at 2048, then raised to 4096, then NO object limit after much badgering by me).
They said the AI couldn't handle it (Limits were raised from 65536 nodes to several times greater, including me finding and removing bugs in the process).
They said it'd require too much (16gb) of RAM to even be playable (I downsized the forest areas considerably lowering the physics collision data footprint of RAM, from 10gb to 5gb avg used at load).
They said it'd be way too slow (so I lowered the draw distance artificially and raised it back later as PC processors became more powerful).
The rural areas are very featureless, boring, dated-looking expanses surely.
But it's here, and it's huge (the largest for the game), and it certainly will provide you a bevvy of driving experience for the awesome price of 0$.
The towns provide plenty of hidden jumps and fun packed in without out-right killing the realism. It's based on real terrain in Tennessee, too.

Don't let anyone stomp out your dreams. If you try hard enough, you can do it. So if you enjoyed this map but want more, check out Los Injurus City Map project, which gets a public update in just a few days.
Thank-you for the kind words, it means so much when maps like this and Los Injurus literally can soak up 5000+ hours a piece and still not be done.

Give it a little time to load in if you don't have an SSD. The terrain doesn't draw in right away but if it's not there and everything else already is, something else went wrong (this map works for others).
If you have 8GB or less of RAM, make sure to close other things out before you load this map (such as web browser, other games, you do not have to close your virus scanner though, leave that one go).
If you do not have a 4GB video card, put the texture details to medium (for 2~3gb video cards) or to low (for 1gb video cards). For video cards with less than 1gb please set the game to 'very low' detail. 'Mesh Detail' can be set by how good your processor is, otherwise left alone (it doesn't help much unless your CPU is very very old). This map requires a 4GB video card to use highest detail textures, and may require even more than that if you have a bunch of cars loaded (I never 100% checked that, but it required 3870mb with 1 vehicle loaded, so it's very close).
If you still cannot load the map, clear cache and try again.
If that does not work, re-download the map; since it is a large download it will quickly show any issues with your internet connection - especially when using wifi. Use a LAN cable while download if you have one (you get often get a short 3~6 foot one at a thrift shop for a pittance).
Get back to me in the discussion forum, with as much info about your hardware configuration as possible, and I will look into it if you cannot get it fixed on your end. Otherwise, the map should be 100% okay.
--Good luck!

I just drove through it the other day when I went to get a new motherboard for my Ryzen computer (I gone-done blew up the PC, thank-you power failure & TN power grid of not-so-good-ness). Is kind of strange driving through my map in real life I will admit. I did know where I was at all times though.
Looks like I have a bunch more random road-repaving sections to add, and a third lane heading from 27 east-bound to Ruritan Rd or Mid-town exit on 40 (I have to check). They're still constructing it, but I'd reckon they finish the real thing before I get it in the map (though it's a likely addition when I have to fix the map next).
The area sure makes a good map though, as it was only supposed to be a open-world concept I spent a few weeks on... Oops!
--Glad you enjoy it!

The AI sure has it's 'idea-light went out' moments, that's for sure, no denying that one bit. I seem to correct it a little more with each revision. I am waiting for the game engine (and the AI brain) to mature a little more before I go ahead and do anything more to it... no sense doing double work that I've already re-done a few times (the map is on at-least it's 3rd AI revision currently).
This map is both a boon to locals, and a major time-sink for anyone who just wants to cruise.
So if you just want to drive around for a while, or speed down streets with AI enabled and find out what happens when you go over the speed limit or run red lights while not going to prison or the hospital, this is a good place to do it.
The crash avoidance skills you learn in this simulation may aid you later in life. They are invaluable. Just remember the big thing - don't panic & don't HAM on the inputs, and you should be much better off. Honing reaction-time down is just as important as both predicting other drivers and always having that 'plan B' escape route if that fails. An experienced driver tries to never put themselves into a position where there's no plan B escape route, too.
I drive an older paid-off Toyota that I fix/maintain myself, so yeah Amen to crash-avoidance... my car will probably be eligible for antique plates before I decide to get another. It's not my dream car, but I'm okay with it, and getting into an accident in real-life isn't my idea of a good time.
--Cheers & Drive safe (in real-life at-least)!

This map is back-burner material while I work on my main project, Los Injurus. When Los Injurus is done, then some of those models will be back-ported to this project and I will pick this mod back up.
This map will only receive maintenance updates to ensure it stays working if it should break, in the time-being until then.
If you should find severe map-breaking or otherwise detrimental bugs, please submit them in the discussion forum so that I can add it to the 'Honey-Do' list over here and get it fixed next time it's required.
--Enjoy the map!