• Ooper

    • Post #13

    Some people still use 469b because of mouse feel, I change mouse sens all the time so don't feel anything different on d3d9, opengl, vulkan, d3d11, icb11, d3d12, if I stuck to the same sens and fps limit maybe I would, but actual performance is worse on older patches.

    • On Linux I play OpenGL with 750fps limit. If you want 200+mb demo files per 20 min game
    • On Windows I was using D3D11 469e at 390fps limit, but been playing last few days on ICB11 with 4K downscaled to 1080p with a 241fps limit via nvidia drivers.
    15 days later

    Ooper Thanks. I downloaded and installed this morning. Runs great without any problems so far.

      hey guys question any problems with the new version and ace?

        • Ooper

          • Post #17

          No, the public releases are fine for ACE they are whitelisted, it's only the private test builds that ACE will kick you for hence one of the reasons those ones are not public, test builds are private until tested enough that they are stable for the public release.

          • Jacey

            • Post #18

            Hellcat454

            I have it installed and i still can play on the server, no problems!

              "mutate ace crosshairscale x.x" is not working on this version...

              Use the crosshair scale in the normal UT HUD options, it's near the bottom, if you drag the window off to the side you can see the changes in real time.

                Ooper yeah but.. I use a personalized crosshair, that requires further scaling than the one provided by the UI..

                    • Ooper

                      • Post #23

                      Ann0ying You can adjust it further by editing CrosshairScale=1.200000 in User.ini in the block [Botpack.ChallengeHUD]

                      Tried a stupid value like 7.2 and it looked massive, so you should be able to do lower values as well if wanted

                        • jerc

                          • Post #24

                          I think its 0.5

                          4 days later

                          If anyone having problems with new patch and mouse don't use direct input.
                          I switched to raw input? and it's working fine now.

                          • Ooper

                            • Post #26

                            Microsoft has said for at least 14 years that direct input is not recommended anymore, it was only used because there was no raw input in UT until 469 or XC_Engine.

                            Write a Reply...