Roane County, Tennessee, USA 19.3.1

Free camera is fine, sometimes the steam overlay can cause keys to stick in many games, try tapping shift or tab a few times if it happens, or run the game directly from the exe or a shortcut to the exe, not a steamrun url shortcut or steam interface. consider turning down the reflection resolution some if you need to, as it will drastically affect performance. I have a very similar graphics board (rx 480 8gb) and it's just dandy if you turn down reflection res just a bit.
Thanks for the good words... I am no god, but I surely think the Devs may be. Waited (and have been modding) since the mid-90s for a game like this on PC that was so mod-friendly. Embracing modding is the best thing a dev can do.

Thanks, yes it's quite a monster. If you need to get somewhere fast, inside the (F11 Key) map editor, the camera speed field takes numerical input even in 4 digits, so if you put in like 1000~2000 as a number, it'll take it. This gets you across this monster of a map in seconds. Just remember to hit the slider to put it back to normal speed before you go back out or you'll have issues when you need to move the camera slower (for screenshots or just viewing how much you destroyed the car).

Minimum system requirements for proper operation of this map:
8gb of system RAM, virtual memory in Windows enabled
64bit operating system and 64bit game version running
Good video card to handle plentiful trees and high-res textures
SSD recommended but entirely optional
Intel processor recommended but entirely optional
If your PC can still handle all the newest games coming out, you generally can run this game. For most people, if there's any issue, it's system memory. RAM is very cheap - the cheapest most influential upgrade you can get along with an SSD. Consider buying more RAM as video settings can often be turned down to help this run better.

The only person who has more fun than everyone else playing it is the guy who made it - rest assured with confidence it WONT die - not anytime soon anyways. This map is not yet finished, and work continues. Look for updates once every 4~8 weeks, until this map is complete. I have kept in close contact with the developers of this game periodically while making this to make sure nothing is outmoded during the time this map was being made available. Should something unforeseen occur, also know that I am committed to continually improving this map and fixing any compatibility issues that may arise (though they should not).
Thank-you for the compliments & happy Beaming.

4gb of GDDR5 VIDEO memory = high settings
Adjust reflection, shadow detail/distance, and texture detail accordingly if you have less. Reflection (for mirrors) has a very hard hit on FPS, so I don't have it cranked all the way even for a Radeon Rx 480 8gb I just bought. It takes a 980ti/1070 geforce card to get good reflection detail AND good FPS.
Just make sure you have VIRTUAL MEMORY enabled on your system if you don't have a LUDICROUS amount of system RAM.
Otherwise you should be fine.

Thanks. Please make sure your VIRTUAL MEMORY is enabled when running this map. While you should have no issue with 16gb of memory, please consider the fact that this is a pre-release early access game title with a 'beta' map, so memory use might not be 100% optimized yet. I have seen my 16gb-of-RAM PC here I made this one use 90+ % of memory (up to 99%!) while simultaneously using 24gb of VIRTUAL memory on drive c:. Using Virtual memory on a modern (or even semi-modern) SSD will not noticably lower the lifespan of it, despite old rumours (they're more reliable than hard-drives and have wear-leveling protocols built into the drive). So yes, DO use Virtual memory - look up a google tutorial of this on the internet for your version of Windows. 16~20gb of virtual memory should be enough for almost anyone who's not editing maps pulling all-nighters.

The car will vibrate most near the edge of the maps on the north, east, and west side of the map, as the world-center is actually just slightly south of the actual terrain center. The further you go in a torque3d (Beamng's parent engine) game, from the world center of 0,0,0 coordinates, the more the visuals will be 'less precise'. This is not a bug with the map, nor does it affect the car/crash physics, it's merely visual and it's engine-related. This also happens on @Nadeox1's SSRB map, which is about 50 miles (or 50km) of road-length of long, straight highway, as you can notice. Since this is the largest map in Beamng.drive, you're most likely to notice it here first. Rest assured it's on superficial/visual and does not affect gameplay at all. Thanks for the compliments!

Thanks for the compliments. There's a few bugs, that's why this is technically beta 0.5 (but it's the first PUBLIC beta not limited to the forum thread for it that's rather buried). I will work out these bugs in time, mostly console errors (unfinished unused assets that I will tidy up as I use them more or delete if I don't use them), non-dds textures (just a very few left!), non-power-of-2 textures (railroad crossing light), etc. Most of the glitches I know about but they're being worked on. Feel free to put more detail in the matter on the discussion forum attached. -Cheers!

i7 and a 16gb set of ram is what I designed this on. It will run beautiful once everything is loaded up (this may take a few minutes on a hard drive on the first run, less on subsequent runs). It may get temporarily a little choppy the first time you look around and as you drive the first two miles it may do some loading but by then everything should be loaded up. If I drive north from BURGER WORLD spawn everything usually is fine by the time I've merged on the highway. It's a HUGE map.

Who ever thought a few pickups and an equal or greater amount of couches could be so entertaining for so long, right? There will totally be a bunch of couch hauling missions. This will be both fun and a test of patience, but eventually, when the missions are out, there will be not just that but racing, car chase missions, and escape the corrupt informant missions too!

Ah yes, thankyou. Reflections do nail performance, by as much as 200% the cost to render, sometimes more. Not everyone realizes this, especially on large maps, that just turning reflection resolution down a bit REALLY helps. I have 1080p reflection resolution (or somewhere around that) enabled on water, for the beauty (it isn't the 1990s anymore ya know) of this game & environment to really show. That coupled with mirror reflections being on can really CLOBBER your FPS. Somewhere, there is a balance, that relies on the user to know just where to set the reflection resolution slider. Sometimes it makes the biggest difference on memory-bandwidth constricted (or shader-constricted) cards such as a 750ti or 950/960 nvidia card, where as it won't so much say on an older Radeon 7850 as that has 256bit memory and an okay amount of shaders.
Even my Rx 480 8gb I just bought (was tired of 30fps in my games) after 3 years+ on the old card I had (the 7850 2gb above) still struggles on super-high reflections at times.
Thanks for taking the time for an honest review.

Not only have you read it, you thankfully posted this for everyone to (hopefully) see yet another time. This is always GOOD. Thanks for taking the time to do this. While it undoubtedly will still eventually happen, maybe, somehow, it will help :) Thanks for taking the time to do THAT and try this.

Upwards of approx 1000 hours to make the map - over the last nine months. This was only a proof-of-concept and large-map-game-engine-test for the first 2~3 months until I realized that it worked fine for the most part, and was entirely plausable. After that I put considerably more effort into it and opened it up to alpha, and then beta-testing.