Roane County, Tennessee, USA 19.3.1

Thank-you for your efforts.
You may attach corrected DAE's to the forum and when I have time to update this map a bit I can check them out and add them in.
You will be credited when they're used. Thank-you and glad you can enjoy the map.
The issue with the rails is that all the placement is done using float numbers, e.g. rounded numbers, not medically precise. Everything in this game that has to do with physics, locations, etc, is all done on the math floating point unit / processor, so there's always a little variable to this. This causes misalignment that gets progressively worse the further you get from Rockwood (the center of the map is just south of Rockwood and a little bit east, there's a mark on the map actually where this is).
So sometimes you have to check it out before you load the map as sometimes things move an inch or two here or there.
Again, thanks!

I can't fix the screen shake, that's just the price you pay for being 'the biggest map'.
The further you get from the center, the larger the rounding you get on float numbers. Float numbers are just that - rounded imprecise math - but it's very fast. This is the only way current PC's can do physics reasonably. The further you get from the map's actual center (south of rockwood), the more it'll shake. So while you won't notice it in Rockwood, if you drive out to Kingston by the interchange, your car will look like it isn't running right. That said, either drive an old beater, or try to ignore it. It's just part of the show (and I can do nothing about it).
Do try to enjoy the map though. I'll have time to update it some day.

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.