Suicide machine

Yeah, I had the same with Red Faction 2, except - new patch is not increasing FOV, the game scaling is just like my old widescreen hack Vert-, except my old hack didn't cause any issues with terrain rendering, so it must be something new they added - might be some functions they patched they assumed were for UI scaling, but values were used more broadly (possibly something like reading a variable embedded in a structure and they just overrode the way such variables are being loaded - would potentially explain why there are some reports of sensitivity being lower in vehicles as well). But then, that'd still imply they don't have a source code and whilst the functions and calls are utter mess in new executable, many changes seem to actually point that they do and just didn't do a clean release build. It would also be surprising to see them restore online functionality with just partial disassembly.

Today (May 1, 2020) both GOG and Steam versions of original Star Wars: Battlefront (not the EA's one) got updated to a version numbered simply as 1.3.5 (4). While the switch from long dead Gamespy to GOG Galaxy is very much appreciated, it's not the only change made. New patch also adds French, Italian, German, Spanish languages to choose from and improves audio using OpenAL. Finally the patch also reworks widescreen support, as the previous "hack" introduced on July 10, 2019 was quite questionable at best (something I wrote about on my GitHub blog). While not mentioned in patch notes, it seems steps were taken to negate issues with vehicle physics glitching out when running the game above 60fps - but a more in-depth testing is required. So far, so good, right? Well - not really. As it turns out, while some of the new scaling behaviours are indeed good (especially when it comes to menus) , they seemed to have unintentionally broken the draw distance. Here are some examples: Tatooine: Hoth: From a limited testing I've done, some maps don't seem to exhibit issues with draw distance, but it's curious nevertheless this hasn't been caught before release. If I were to guess, it might as well turn out that one of the changes made now multiplies (by values lower than 1) or divides LOD of terrain, here is what happens if you set minimum LOD in game settings: Normally this terrain is visible (although the draw distance is still noticeable shorter than on identical settings on version 1.2 of the game). Either way, let's just hope this time, the patch fixing it will take less than 9+ months to be released. Note: For screenshots my old widescreen fix was used to provide the same 16:9 aspect ratio as with new 1.3.5 patch.

It can also bring every existing card to its knees if used on bigger scale as Minecraft RTX proves, where even with insane optimisations and upscaling to 1080p from lower resolution using DLSS 2.0, RTX 2080 barely manages to keep itself above 60fps (rendering natively it gets crushed with average FPS being 50 and min 99th precintile being 38). So yeah, we're most likely looking at another limited use of raytracing - my guess is reflections and maybe some sort of additional enhancements to Crytek's global illumination. Anything above it seems already heavy for RTX accelerated raytraying with something at complexity of Crysis and already pretty much near impossible to achieve with Crytek's hardware agnostic RT.

Jitterdoomer is now banned... not because of this comment though, although his behaviour did influence the final decision.