Roane County, Tennessee, USA 19.3.1

Turn Reflection resolution all the way down, or turn off the mirror reflections. See if this helps. Also, shadows are a performance hit. This is a full game world in a pre-release game that doesn't quite have all it's open-world features completed yet- so performance can be hit or miss on systems near the minimum requirements for the game. Please post your full system's specifications to the discussion forum as we value your opinion on the map.
Please keep in mind 3400~3600mb (about 3.5gb) of VIDEO memory is required for high texture detail. If your video card has only 2~3gb, use medium or so, that will help substantially. Performance should get better (even if only slightly) in future versions of this map and/or game - not worse. Thanks for taking the time to review --Cheers

This was originally a Proof-of-Concept style 'large map test', it was only a test. This was supposed to be deliberately-over-the-top, more a means to stress-test the game engine, to see just what this simulator could do before it gave up the ghost, than to be a real purpose-built-map. A bunch of folks egged me on to release it as I was building this in the spring. If they do release tiled terrains (that would be awesome), this map will be re-worked as needed. As more and more streaming optimizations are put in, it will run better, too. This runs beautiful on my end, sans a few under-optimized spots here and there that go down to 30~40fps (vs 100~140+ fps). What it lacks in a pothole simulator, it plenty makes up for in sheer size. The odd part is I actually have more issues running So-Cal Interstate (my last map before this), than I do this one and that one has no trees/signs/rocks etc! This map will use 3~3.6gb of vRAM (Video memory, on the video card) and around 6~7 gb of system RAM shortly after load, additional GB's of page file use may be present though. I tried to keep ram use civil despite map size.
In the future, our PC's will run this even better, and more people will meet the system requirements. Considering the game isn't officially 'finished' yet, I will not worry on it for now, about performance issues.
To end on the most positive note, I really appreciate the critique especially from another mapper (you make awesome pro & FUN maps - keep it up!), so feel free to chime into the discussions if you have more input. To everyone else, I encourage you to try out his maps!

Good video card, enough memory to run the map, maybe your pc isn't so SPUD-worthy as once thought - always a good thing! A lot of effort has gone into streamlining assets and making sure I can re-use them plenty of times otherwise this would be a 10gb download and impossible to run. You also most-likely DO already have proper video-quality settings on your computer, so that the poor thing doesn't go up in smoke either tee-hee. Well anyways, always nice to hear something good for a change, right? Look for updates in the future.
Thanks for taking the time to write in --Cheers!

Yeah I had to drive to Knoxville (past the edge of this map's east side by 20 minutes), from an area technically WEST of this map's location. So I had to go drive through this map technically to get my Rx 480 8gb video board. Was like... gosh this is familiar... hey wait a minute, I am driving in my @#$%ing map... heh. Was a very strange feeling! Had to do it again a few weeks later when a fan went south while it was under carry-in warranty yet. Ugh. Got to get some pointers while I was passing through though. Always fun when you can drive someplace you've been inside a video game. The street layout is 98% accurate most times, and the map is about like a 9.4:10 scale - so that it fits comfortably in the 8gb system ram footprint. Glad to hear from another local - we have a few!
--Cheers!

Thanks. I totally understand your sentiment about big maps being just bland miles of nothing. While that's great for blasting through in a fast car - or maybe flying over top of, it would get boring fast. I couldn't afford object-wise to make it super-dense population nor did the real-terrain-recreation call for any dense population other than a few small towns in rural America. I will be filling in more detail as time goes by. Look for a new version after the next game-version-update, I am hoping to include missions in the next version (no promises, but they'll be in eventually). Join in on the discussion page if you'd like to see a certain race, or something special added in (that goes for anyone else reading this, too). Work is slow but steady so no worries! --Cheers.

That's not a bug with my map, it's the game engine. The water rendering gets much less accurate as you get further away. This also happens in some other games, too.
NO cars are supposed to keep floating, unless it's a boat, or something similar. The older version of the map had somewhat-more-dense water settings than should have been. However, this being said, the car will hydroplane over the water a bit if you're going fast enough. The vehicle sinks when you lose enough momentum.

Lower the REFLECTION RESOLUTION (for your car's mirrors) to something less than half, this should considerably increase your FPS. I have an Rx 480 8gb here and yes there's a few spots that get a bit of an FPS drop. I never noticed the FPS drops when I have the Radeon 7850 2gb, but it was much more noticeable with the newer card. As the game gets updates and the map does too, expect things to get better, not worse (with the exception of very select places like downtown Rockwood that's not finished yet, fps may drop a bit there with all the buildings when it's completed). Turning off anti-aliasing might help FPS but not as much as the 1st thing I mentioned with mirror reflection resolution. Other users have reported turning off shadows helps (or turning them down) but I feel that's a bit drastic for a 980 video board. Overall I am glad you enjoyed it and look forward to the next update that should be out in December sometime. The map update will trail the game version update by a week or two.

Special attention was paid to the AI working properly on this map, hours and hours and hours to be factual. It's possible it was DAYS of time but it's never too much to ask for the fun car-chases that result. While I can't keep the AI from driving the wrong way, it DOES work fine and follow the road perfectly 99.8% of the time. If you find any issues with it where it consistently gets stuck or drives off the road give a shout in the discussion forum, with a screenshot or two I can have a look-see at it.
--Thanks for writing in & Glad you like it.

I had a Radeon 7850 2gb that got a steady 24~52 fps before I bought an Rx 480 last month, consider upgrading the card in the near future as other new games have higher requirements.
Also, consider playing full screen with the Vsync off.
Use low detail if possible. Turn shadows off possibly, and also, turn off reflections, that card is not powerful enough and they hit hard on a map this size. SSAO and AA should be turned down to minimum or off.
I hope this helps. A full detail game-world like this tends to really show off what this game can do / can be but can really hurt performance on lower-end mainstream video cards. That having been said, the rest of your PC is great for this game and you should have great performance otherwise especially if you have an SSD.
--Thanks for writing in, performance shouldn't get any worse in the future with updates, it should only get better.

That's close to my specs (different video board though), you should get pretty good performance with that once it's all loaded into memory.
The vibrating car/physics jittering is merely visual, it doesn't affect the crash physics at all. This is a large-map issue with the game engine (this is a pre-release game, too), once you get 5~10+ miles of the center of the game-world. You won't notice it when you're going fast, though.
--Thanks for writing in.

Shaking cam/car is VISUAL ONLY and does not affect physics. It happens when you get 6~10 miles from the world center of 0,0,0 in ANY Torque3d engine game with physics (Beamng.drive is made from Torque3d). This is a known issue on my end (it's the game engine, not my map).
Your GTX 960 is memory-bandwidth restricted, consider looking at your graphics options and turning down mirror (reflection) resolution, faces per update, detail distance, or lastly, setting texture detail to medium.
This is a very high-texture-detail map. It does most certainly use up 3550mb of that 4096mb of texture memory you have!
This is a cutting-edge map (beta) on a cutting edge (pre-release) game, it may not run perfectly - this is known, but there are some tricks, like turning off Vsync in fullscreen mode, turning down anti-aliasing, SSAO or HDR settings (or turning them off if it's all that's allowed).
Watch your fps (enable it in Steam overlay!) and mess about with options a bit. Some FPS drop is normal in very 'busy' areas like Harriman downtown (you can spawn there, do so to adjust FPS).
-Thanks for writing in and enjoy the map!