Referencing the latest "tracking the engine upgrade" post:
The point of this thread is to discuss issues brought up by Matt related to the launch of the public 2.1 beta.
I will summarize relevant portions of the post, in case you did not read the full thing.
Current testers of the new engine beta expressed the following concerns:
Input lag from Windowed Fullscreen (Exclusive fullscreen was removed due to lacking DX12 support)
Visual and audio bugs
Doors getting out of sync with the server and showing open when they are closed or closed when they are open
Issues with Field of View and mouse sensitivity in Marksman mode. The more zoom, the more problematic this becomes.
Possible bugs in the UI that are slowing down FPS
Issue with stutters that was cleared after rebooting
Removal of 1024x768 resolution (UI screens show more information, leading to this resolution being removed)
Matt further states:
"My personal feeling is to launch the Beta as soon as the content migration (porting new content from LIVE to the 2.1 beta) and crashes are fixed. Then iterate on Windowed Fullscreen and other bugs.
But I've also been told that the first impression is everything, and to some extent I believe that. But I feel like that would apply more to the APB 2.1 full launch and less to the Beta."
Boiled down to something a little simpler:
Launch the open beta early with visible issues, or wait longer until those issues have been fixed and then launch the open beta.