justdrex @justdrex

Simon Hanus ('27, INTL)🇨🇿⬇️ Backside loaded stance w/ coil/slide step load, Fights for the LP, Violent hands, Rips this one to the left side for the 1B. #PSFallNatty | #Uncommitted | @SimonHanus4 | @CBU_FL 👤 play.ps-baseball.com/player-profile…

I resigned from Anthropic today. I spent the last three years doing pretraining research at both OpenAI and Anthropic. Neither company is acting responsibly. They are racing straight to self-improving superintelligence and gambling with our lives. More thoughts below.

drove past Brno, felt the aura.

Never give up ❤️

@tobysct_ dej mi jednu pls jsem broke

Optimizing CS2 on Nvidia GPU & AMD X3D CPU – Comprehensive Guide Launch Options: Myths vs. Reality Many “tweaks” from CS:GO no longer work in CS2. The Source 2 engine changed what launch parameters are valid. In fact, a Valve developer even stated “Best launch options are no launch options. They are the most used and most tested.”. Many of the old launch flags are simply ignored by CS2. For example: -tickrate 128 – Did nothing in CS2 (the game uses subtick timing now). -novid – Redundant because CS2 has no intro video anyway. DirectX 9 flags like -d3d9ex/-disable_d3d9ex – Unsupported in CS2, which runs on DX11/Vulkan. Heapsize/threads tweaks – Unnecessary; CS2 manages memory and threading internally. Using -threads can even cause instability. Bottom line: Use minimal launch options. In fact, beyond setting your refresh rate and uncap FPS, additional launch parameters are mostly placebo. The only commonly useful ones are: -allow_third_party_software if you use game capture/overlays (beware: might affect trust factor ), -freq or -refresh to ensure the game uses your monitor’s max refresh (e.g. -freq -240), and +fps_max 0 to remove FPS cap (or set a specific cap). Other tweaks typically offer no real benefit in CS2 and can be safely removed for a cleaner startup. Vulkan API and Shader Issues in CS2 Counter-Strike 2’s performance is a work in progress. By default on Windows, CS2 uses DirectX 11. Some players experience severe stuttering on DX11 (especially in online matches, even if offline bots are fine). A proven workaround has been running the game in Vulkan mode via the -vulkan launch option. One user reported that using Vulkan completely eliminated the stutters (making the game playable) whereas DX11 had major frame pacing issues. The trade-off: Vulkan mode might yield slightly lower max FPS than DX11, but the improved consistency can be worth it. If you suffer from inexplicable hitching or input lag, try -vulkan and see if it smooths out performance. (If it doesn’t help, simply remove it – not all systems benefit equally.) However, be aware of current Source 2 engine bugs. Even with Vulkan, certain in-game events can cause dramatic frame drops for all players. For example, many have observed that when a Molotov (incendiary) grenade ignites or is extinguished, everyone’s FPS can nosedive momentarily – sometimes from 240 FPS down to ~30 FPS. These FPS “spikes” happen even if the effect occurs across the map, indicating a shader or particle effect compiling on the fly for all clients. In other words, CS2’s shader caching isn’t fully optimized yet – the first time complex effects (smoke, fire, etc.) are rendered, a hitch may occur. This is a known issue (the game is not in a perfect state ), and Valve will likely patch it. For now, you can mitigate it by using lower Particle Detail (in Video settings) so that smokes and molotov flames are less taxing. Also, set “Effects” to Low to reduce impact. The goal is to minimize how dramatic these effects are on your GPU. Until Valve addresses the root cause, expect that large smokes or mollies can cause momentary FPS drops on any system – it’s not your PC’s fault alone. Flushing the Shader Cache: After big updates or driver changes, it’s wise to clear CS2’s shader cache to reduce stutter. Stale or corrupt shaders can cause constant hitching. To do this, delete the shaders_* cache files in …\Counter-Strike Global Offensive\game\ directories, or simply run Disk Cleanup and purge DirectX Shader Cache. Then verify the game files so that CS2 can rebuild a fresh shader cache. Many players found that doing this (and removing outdated DirectX install files in the CS2 folder) fixed nearly all stutter for them. Essentially, you force the game to compile new shaders ahead of time, rather than during gameplay. System Setup: Windows 11 & AMD X3D CPUs For best results, use Windows 11 (23H2) or newer. Windows 11 has scheduler improvements that benefit both Intel hybrid CPUs and AMD Ryzen X3D chips. The user’s reference build is Windows 11 Pro 23H2 (build 22631.5116) – running an up-to-date OS is important for newest game optimizations (Windows 10 lacks some of these). In particular, AMD’s 3D V-Cache CPUs (like the 5800X3D, 7800X3D, 7950X3D, etc.) rely on Windows to properly schedule threads to the cache-rich cores for best performance. Make sure you install the latest AMD chipset drivers and enable Xbox Game Bar/Game Mode, which on newer X3D CPUs will automatically park the secondary “non-3D-cache” CCD when you launch CS2. This ensures the game runs on the CCD with the extra L3 cache (critical for high, stable FPS). If you have a dual-CCD X3D (e.g. 7950X3D), verify that the Core0/1 (the cache CCD) is being utilized in-game – usually Windows handles this if Game Mode is on. If not, you can manually set CS2’s process affinity to the cache CCD, but that shouldn’t be necessary in most cases. The 3D V-Cache gives X3D chips an edge in CS2’s CPU-bound scenarios, as seen in benchmarks (the X3D CPUs dominate CS2 framerates “effortlessly” in many tests ). With a properly configured system, a Ryzen X3D plus a strong Nvidia GPU is one of the fastest combinations for CS2 right now. Avoid CPU OC/unstable tweaks: It’s generally recommended not to use motherboard “Game Boost” auto-OC features or Process Lasso affinity tweaks with X3D CPUs for CS2. Those can introduce latency or instability. The X3D chips perform best at stock settings (with PBO if you need, but ensure it’s stable) because their large cache is the main accelerator – not raw frequency. Keep your RAM in a stable EXPO profile (memory bandwidth is slightly less critical for X3D, but you still want no bottlenecks or errors). The goal is consistency and low latency, not chasing every last MHz at the cost of potential stutter. Also, consider enabling Resizable BAR (ReBAR) in BIOS for your GPU. CS2 doesn’t natively advertise ReBAR support, but you can force it on at the driver level. On Nvidia RTX 30-series or 40-series, update your GPU VBIOS if needed (Nvidia provided a ReBAR firmware update tool) and enable “Above 4G Decoding/Resizable BAR” in BIOS. Then, using Nvidia Profile Inspector (an advanced tool), you can force ReBAR globally for all games. (In Inspector, set rBAR - Feature to Enabled and apply, etc.) As one community guide notes, CS2 has zero official ReBAR support, meaning the driver may not use it unless forced. Enabling it globally has essentially no downside and can slightly improve throughput and system latency. Many users reported ReBAR helps smooth out frame delivery in various games – and since CS2 moves a lot of data (maps, models) to the GPU, ReBAR might help performance a bit. This tweak is optional, but it’s one reason “Nvidia Profile Inspector is OK” to use – it lets you apply ReBAR or other deep driver settings that the standard control panel might not expose. Just be cautious and only change known flags (like ReBAR or Max Frames, etc.) – avoid obscure “tweaks” that aren’t verified. NVIDIA Control Panel Settings for CS2 To make your Nvidia GPU “CS2 ready,” you’ll want to adjust a few settings in NVIDIA Control Panel (NVCP) for maximum performance and lowest latency: Power Management Mode: Prefer Maximum Performance. This prevents the GPU from downclocking at inconvenient times. It ensures your card runs at full boost clocks during gameplay. CS2 can have fluctuating load (very high FPS in some scenes, lower in others); a fixed max performance mode stops any delay in ramping clocks up. Monitor Technology / G-SYNC: If you have a G-SYNC or FreeSync (compatible) monitor, you need to decide: pure competitive (lowest lag) or smoother visuals. For absolute lowest latency, many top players run with G-Sync off and uncapped FPS, tolerating some tearing for the sake of responsiveness. If you prefer to use G-Sync for tear-free output, enable G-SYNC for fullscreen and disable V-Sync globally (or at least in-game), then set NVIDIA Reflex to On + Boost in CS2. This combo can reduce latency while still avoiding tearing. However, CS2’s Reflex implementation has issues (explained below), so the safer competitive route is often no G-Sync, no V-Sync, uncapped FPS. It really comes down to preference: just know G-Sync slightly adds input latency (a few ms) unless carefully tuned with Reflex, so many avoid it in tournament play. Low Latency Mode (LLM): Off (or at most On). This setting in NVCP controls the frame render queue. In Ultra, it forces 0 pre-rendered frames (lowest possible queue), but many have found that “Ultra” can introduce stutters in CS2. In fact, CS2’s own “NVIDIA Reflex” setting essentially does a similar job. Using both Reflex and Ultra LLM can conflict. One CS2 user noted that NVIDIA Reflex set to On plus having Low Latency Mode Ultra in the driver made the game stutter horribly, and the fix was to turn Reflex off and LLM to a lower setting. Unless you’re highly GPU-bound, CS2 doesn’t benefit much from LLM Ultra. Recommended approach: In-game, set “NVIDIA Reflex Low Latency” to Disabled (or at most Enabled, not Boost), and in NVCP set Low Latency Mode to Off or On (not Ultra). By not forcing ultra-low queue, you might eliminate micro-stutters that occur when the GPU is starved. CS2 is often CPU-bound on strong systems, so the GPU queue isn’t the main cause of latency. Prioritize consistency over chasing the last millisecond. In short, we suggest “No Reflex, no Ultra LLM” for now, given the current bugs. This matches community findings that Reflex in CS2 “sucks” and can actually add input delay or frame pacing issues in its current state. If future patches improve it, you can reevaluate, but many competitive players have Reflex off at the moment. Threaded Optimization: On. This allows the Nvidia driver to multithread its work. By default it’s “Auto”, but forcing it on ensures the driver doesn’t revert to single-thread mode. CS2’s engine is modern and benefits from multi-threading, so there’s no harm leaving this on. (Older Source1 advice to turn it off no longer applies – Source2 is a different beast.) Vertical Sync: Off. This is obvious for any competitive setup. V-Sync adds significant input lag and capricious frame timing. It should remain off in NVCP and in-game. (If you use G-Sync, you might optionally use V-Sync only to prevent tear at max FPS, but that’s a special case usage with Reflex – not recommended unless you know what you’re doing.) Multi-Frame Sampled AA (MFAA): Off. Not relevant to CS2 (which has its own MSAA options), and leaving it off avoids any unpredictable performance hits. Anisotropic Optimization / Trilinear Optimization: These can be On (they have negligible visual impact in CS2 but can save a tiny bit of performance). It’s fine to use quality optimizations globally or per CS2 profile if you want every extra FPS. Setting Texture Filtering Quality to “High Performance” in NVCP is a quick way to enable all such optimizations. Max Frame Rate: Off (no cap) – unless you specifically want to cap FPS to reduce GPU load. Generally in CS2, uncapped or a very high cap is best. A higher framerate than your monitor’s refresh can still reduce input latency, because each refresh the monitor picks the most recent frame from the GPU buffer. For example, on 240Hz, running 400+ FPS yields newer frames on average than running exactly 240 FPS. This results in less input lag and a “clearer” sensation of motion. Thus, do not cap at your exact Hz if your system can go higher – let it run as high as possible (while stable). Only consider capping (e.g. to 300 or 400) if your GPU is getting 99% usage and running hot, or if you want to avoid any potential GPU-side latency when fully maxed out. Otherwise, more FPS = better for competitive play. Preferred Refresh Rate (for CS2 profile): Set to Highest available. This ensures the game uses your monitor’s maximum Hz, especially if you have a 120+ Hz display. (Also double-check in Windows Settings > Display > Advanced that your monitor is actually set to its top refresh rate. Sometimes Windows defaults to 60Hz after a driver update or new monitor.) Shader Cache Size: Keep it at Driver Default (or set a reasonable size like 10 GB if you changed it). Don’t disable shader cache. Having a shader cache helps minimize in-game stutters as effects are reused. If you suspect the cache is corrupted, you should clear it (via Disk Cleanup as mentioned) rather than disabling it entirely. The goal is to let the GPU precompile and store shaders so that you’re not compiling during a match. Finally, update to the latest NVIDIA driver (preferably the Game Ready Driver for CS2, if available). New drivers often include optimizations or fixes for CS2, especially as the game is evolving. Avoid using very old drivers on this new title. A clean install via DDU isn’t necessary unless you suspect a driver issue, but it’s something to try if you have persistent problems. Best Practices: Hardware Connections & What to Avoid Even a perfectly tuned PC can be held back by suboptimal hardware setup. Here are some critical tips for monitor and peripheral configuration to achieve “no jitter, input first, no lag, clear picture” performance: Use a Single High-Refresh Monitor (When Competing): Running multiple displays can negatively impact gaming performance. If you have a second monitor, consider disabling or disconnecting it when playing CS2 competitively. Why? Because Windows and GPUs sometimes have trouble with mismatched refresh rates. In fact, by default many GPUs will synchronize all connected monitors to the same refresh. For example, if you plug in a 60 Hz secondary screen, the system might downclock or sync the primary to 60 Hz as well, effectively capping you at 60 FPS until you manually fix it. This can introduce micro-stutter or lower FPS without you realizing. It is possible to run dual monitors (e.g. 240Hz + 60Hz) by adjusting each display’s settings in NVCP, but any background activity on the second screen can still steal GPU cycles. To eliminate all doubt, it’s best to have only your main 240/360Hz monitor active while playing. This ensures your GPU is 100% focused on pumping frames to that display alone (NVIDIA’s “Single Display Performance Mode” in NVCP can also be enabled ). If you do use two monitors (for streaming, music, etc.), try to keep the second one at least an integer fraction of the first’s refresh (e.g. 240Hz & 120Hz, or 240 & 60) , as this can reduce odd stuttering. And of course, don’t have videos or animations playing on the side while you play – that can cause jitter. Avoid Capture Card Loops on Your Gaming PC: If you use a capture card (for dual-PC streaming or recording), be careful how you connect it. Many competitive players found that having a capture card plugged into their GPU (e.g. via HDMI output) or mirroring the main display to a capture device introduces latency and caps performance. For instance, cloning your 240Hz screen to a 60Hz capture card will force the GPU to output 60Hz for both, ruining your high-FPS experience. Even if not cloning, just having the capture card as an active output can sometimes engage the GPU’s multi-display mode or lower clocks. The safest setup is to keep your gaming PC output solely to your monitor. If you must send to a capture card, use technologies like OBS’s NDI or PCIe mirror with proper config, and ensure the capture card isn’t pulling your primary to a lower refresh. In summary, avoid any unnecessary connections on the GPU that could disrupt its focus on your main monitor. This includes VR headsets, extra TVs, etc., which all make the driver juggle multiple display timing. Connect to the Right GPU Port: This is a subtle but notable tip – use the first (primary) DisplayPort output on your graphics card for your main monitor. On most RTX cards (20-series, 30-series, etc.), the ports have a priority order determined by the firmware. Typically, the furthest right DisplayPort (when looking at the card from the back) is Port #1 – the highest priority. Using that port for your primary monitor can ensure it’s initialized as Display 1 and gets full attention. By contrast, the DP port closest to the HDMI (or the HDMI itself) is often lower in priority. While performance shouldn’t theoretically differ, many users have reported that using the primary DP port yielded a more stable high refresh signal (fewer glitches) and that sometimes the port next to HDMI had quirks (possibly due to shared circuitry or simply Windows assigning it as secondary display). Also, the highest-bandwidth port on newer GPUs might be labeled – e.g. if one DP is 1.4 and another is 2.0/2.1, use the one supporting your monitor’s max resolution/Hz. In short, plug your main monitor into the top-priority DisplayPort. This way you know you’re getting the intended bandwidth and priority (and your BIOS POST and Windows login will appear on that screen by default). It’s a small optimization, but every little bit helps to avoid odd issues. Do not use an HDMI port for your high-refresh monitor unless you absolutely have to – on many GPUs, the HDMI might not support 240Hz or higher at full resolution without subsampling (HDMI 2.1 can, but older HDMI 2.0 cannot do 240Hz 1080p in some cases). DisplayPort is generally the better choice for PC monitors. Use Quality Cables: A bad or marginal DP cable can introduce flicker, jitter, or drop you to a lower refresh without warning. Ensure your DisplayPort cable is VESA certified for the bandwidth (e.g. DP 1.4 or 2.0 certified). If you suddenly see your monitor stuck at a lower Hz or blanking out, the cable could be the culprit. This isn’t directly about CS2, but it affects your “clear picture” and stability. No Unnecessary Background Apps: It should go without saying, but close any background programs that aren’t needed while playing. Especially overlays, RGB software, or “FPS boost” applications can interfere more than they help. Don’t use Process Lasso or other CPU pinning tools unless you have a very specific reason – let Windows and the game handle CPU scheduling, especially with X3D’s special scheduler. Disable overlays like Steam overlay, Discord overlay, GeForce Experience overlay (Shadowplay) if you suspect they cause hitching (they hook into the game and sometimes impact performance). The idea is to have a clean environment where CS2 is the sole focus of your CPU/GPU. Windows Optimizations: Make sure Game Mode is enabled on Windows 11 (it usually is by default; it helps prevent Windows Update or other background tasks from stealing resources during gameplay). Consider disabling Hardware-accelerated GPU Scheduling (HAGS) if you experience micro-stutters – some users report that “on most rigs, HAGS causes micro stutters” in CS2. You can toggle this in Windows Graphics settings. It may help on some systems (and conversely, a minority find HAGS on helps a bit – but try off if you have issues). Also, set your Windows power plan to High Performance or the AMD Ryzen High Perf plan. This keeps the CPU ready at max frequencies (important for reducing input lag). Lastly, if you’re very serious: disable fullscreen optimizations for CS2’s.exe (this can potentially reduce latency in some cases, forcing true exclusive fullscreen). Right-click cs2.exe -> Properties -> Compatibility -> check “Disable fullscreen optimizations.” This ensures you’re not running the game in a pseudo-borderless mode that could introduce a few ms of delay or mouse weirdness. (CS2 should run in true fullscreen if you select fullscreen in-game, but Windows 10/11 sometimes still applies composition unless you disable this). It’s a small tweak, but many competitive players use it. Conclusion By following this guide – trimming useless launch options, using Vulkan if needed, configuring your Nvidia settings for low latency, and optimizing your hardware setup – you’ll set up CS2 to run with no jitter, minimal input lag, and maximum clarity. The combination of an Nvidia GPU and an AMD X3D CPU is extremely powerful for CS2, but only if you let each do its job: keep the CPU fed with proper scheduling, and the GPU unleashed with proper settings. Avoid “snake oil” tweaks that promise magic FPS gains (most are BS in Source 2, as 99% don’t actually work ). Instead, stick to proven methods: clean shader cache, updated drivers, correct monitor configuration, and sensible in-game settings. Remember that CS2 is evolving – patches may improve performance (or sometimes introduce new bugs). Stay updated on community findings with each update. As of now, running Windows 11 23H2 and the latest NVIDIA drivers, with the above tweaks, is the most competitive setup. It prioritizes input responsiveness and frame stability over fanciness. You may not have the prettiest shadows or the fanciest effects, but you will have an edge in reaction time and visual clarity, which is what matters in high-stakes play. Good luck and have fun fragging in CS2! 🔫🎮 Sources: Valuable insights were gathered from community forums and guides , as well as first-hand user experiments. All citations are included for reference. Enjoy your optimized Counter-Strike 2 experience!

Upgrade Your CS2 Timeline📈 Tactics: @mindtr6cks Tricks: @Rylop2 Utility: @genvl288 Analytics: @smartbackwards Podcast: @AllAboutCS2 Game Optimization: @fREQUENCYCS Quick News: @ThourCS2 Updates/Leaks: @gabefollower Mental Game: @MindBodyEsports 👇🏽Share who deserves to be here!

m0NESY’s PC needs a check too 🥶

@kencarson Where is Prague?

@EliteTokensGG @duckkyxxfv @tomlangertl

@EliteFNDivision @EliteScrims @duckkyxxfv @tomlangertl

@OndrejVit_ @Hudl Wow! Incredible! Young talent!

Here are my Youth Bowl X Highlights❗ Down 28-6 late in the third quarter. Found a way to come back and win! 410 passing yards 4 passing TDs @hudl hudl.com/v/2Qn9nQ #hudl

@FortniteGame ???

@NadeKing inferno?

@UbisoftSupport hello, pls fix, ty

You need to understand @CounterStrike that without proper anticheat - Premier fucking sucks, no one gonna grind for rating like in Valorant, easiest way - connect with FaceIT anticheat, hardest way - create much better one

HIM 🇫🇮

Champions

WE ARE THE FIRST CS2 CHAMPIONS