[Bug-Pc] The map loading bug returns from The Crew 1 albeit nerfed
During the whole lifespan of The Crew 1 there was a major bug that only affected a limited number of players across a large variety of hardware and software configurations.
After driving some distance in either freeroam or in some races, the map textures would be very low resolution and some things like trees would not spawn. If one would drive into it, the car you were driving would instantly stop with the engine at full rev. No inputs would be read after driving into the messed up zone. However the game wouldn't be frozen solid, ai racers would drive on unaffected. Furthermore. you couldn't fast travel more than a certain distance otherwise you would be affected by the but as well. This could cause you never to leave the loading on the minimap. The system I am currently using was affected by this bug, to get around this I would dual boot into another os. After driving around in the crew 2 I randomly got hung during the end of the Mississippi boat race. I though perhaps I was stuck on some sandbar as I would've gotten similar visual and audio feedback. However when I let off the throttle, it stayed at 100% power. After this I started doing some testing to see where else I can get affected by this bug. The only other event I've had it in is right at the end of the xtreem series 2 race by cutting though the swamp right at the end before the finish line. However, much like in the crew 1 if you travel far enough in free roam, you will be affected by it. Flying a plane from the house in miami to seattle I got hit with it twice and I didnt even finish the flight. Once was a bit west of armadillo and another mid way across the grand canyon area. In regards to the minimap, most of the times it seems like I can teleport places without issues, though sometimes it takes quite awhile. First person areas are different, traveling to those with cause a infinite loading screen, though when the game is restarted I will be placed right into the one I was attempting to travel to. Entering them from the main world in free roam works fine. As I stated in the title the bug has gotten a major nerf in the crew 2. In the crew one once you were stuck you couldn't do anything except restart the game. In the crew 2, one can simply go into the main menu and exit. This seems to re-load the world around you correctly, allowing you to continue. Going into the map straight from the main menu does not fix the bug and leaves you at a never ending loading screen. I've not tried the video or photo editor. As always if any more info or testing is needed I'll be happy to provide it
Images for reference
https://imgur.com/a/FH012Ik
Pc Specs
Amd R7-1700
32GB Ram
Vega 64
1 tb SSD w/ Windows 10 ( Bug affected install )
128gb M.2 SSD w/ Windows 7(Unaffected with bug in Crew 1, Crew 2 untested)
5 by 1 1080p Eyefinity at 5400x1920p
1 people found this helpful