The two fixes should not be confused
Capcom’s published update summary says 1.042.00.02 takes measures against frame-rate drops in some environments after 1.042.00.01. The earlier August 7 entry separately fixes a Render Scaling setting that was not applied. These explain the intent of the patches; they do not establish a universal percentage improvement.
Use a comparison you can repeat
If you want to know whether a patch improves your own session, record the game version, device specifications and relevant graphics settings. Compare a similar route or scene under the same conditions. A different weather effect, busier encounter or altered render setting can change what you see without proving that the patch caused the difference.
Begin by checking whether the intended setting is actually applied. Then change one thing at a time. A long list of “optimisations” applied together makes it difficult to isolate the useful change and difficult to undo the ones that did not help.
A support report needs context
Keep the exact problem, the version where you first noticed it, the current version and a short reproduction path. Distinguish a crash from low average frame rate or intermittent stutter. Those are different symptoms, even if a casual description calls all of them “lag”. Include only information needed by the official support process, not account secrets.
Keep expansion news separate
The 2027 Ascendance announcement does not answer whether a present-day PC patch resolves a problem on your hardware. Read the current update notes for that question, then the expansion guide if you are deciding whether to return for new content. JKOOK GAME has not benchmarked this patch; its role here is to explain the documented change and a useful way to check your situation.