A handful of players attempting to start the Command and Conquer Remastered version had noticeably refresh rate per second (FPS) drops while playing. The issue can occur during a match, but some have reported that it occurs immediately after launching the game and soon after they receive a hard game crash preventing them from playing. Because it's a remaster of the game, there are a handful of cheats for you to try out.
Some players declined the settings or ran the game in a different windowed mode. This works for some, but others have reported that any attempt to change the game from full screen to window causes the game to freeze further. You may need to play the game in a different resolution, such as a smaller one. and optimized, rather than the modern 1920 × 1080 resolution, or even greater.
Your next choice is to go to the options settings and try changing the v-sync configuration to turn it off. Disabling this feature may make it easier to read. You might want to play around with one of the graphics settings to see if that tries to help you with stuttering or freezing issues.
In addition, you go directly to your graphics card panel on your hardware to disable 3D options. Because Command Conquer Remastered is an older game, some of the higher quality settings might make it worse. Turn off one of the 3D options, then even turn off v-sync from this section if you have more options to choose from.
If you continue to have issues, your next choice might ask you to check the game files in the Steam directory by right-clicking the game in your Steam library and choosing properties. From there, go to the third tab and choose to check the integrity of the game. It will take some time to load all the files, but after that try to reload them into the game. One last option is to uninstall the game, to give it a fresh install and restart your hardware.
You can always contact the EA Support Team for further assistance if you continue to have issues. Many people in the Steam community threads have experienced FPS issues, which means the developer may need to release a fix. The more the support team hears about it, the faster the developer can try to fix it.
