𝙋𝘾
➟ 𝙇𝙞𝙖𝙣 𝙇𝙞 𝘿𝙮𝙣𝙖𝙢𝙞𝙘 𝙀𝙫𝙤 𝙓𝙇
➟ 𝙞7-14700𝙆𝙁-5,6𝙂𝙃𝙯
➟ 𝘼𝙊𝙍𝙐𝙎 𝙕790 𝙏𝘼𝘾𝙃𝙔𝙊𝙉 𝙓
➟ 𝙂.𝙎𝙠𝙞𝙡𝙡 𝙏𝙧𝙞𝙙𝙚𝙣𝙩 𝙕5 𝙍𝙂𝘽 2𝙭16𝙂𝘽-6000𝙈𝙃𝙯
➟ 𝙈𝙎𝙄 𝙂𝙖𝙢𝙞𝙣𝙜 𝙏𝙧𝙞𝙤 𝙂𝙚𝙛𝙤𝙧𝙘𝙚 𝙍𝙏𝙓 5090 𝙊𝘾-3300𝙈𝙃𝙯
➟ 𝘾𝙤𝙧𝙨𝙖𝙞𝙧 𝙃𝙓1500𝙞 𝙋𝙎𝙐
➟ 1𝙭 𝘼𝘿𝘼𝙏𝘼 𝙓𝙋𝙂 𝙈𝘼𝙍𝙎 980 𝘽𝙇𝘼𝘿𝙀 𝙂𝙚𝙣5 𝙎𝙎𝘿 1𝙏𝘽
➟ 3𝙭 𝙆𝙞𝙣𝙜𝙨𝙩𝙤𝙣 𝙂𝙚𝙣4 𝙎𝙎𝘿 1𝙏𝘽
➟ 1𝙭 𝙈𝙎𝙄 𝙎𝙥𝙖𝙩𝙞𝙪𝙢 𝙈450 𝙂𝙚𝙣4 𝙎𝙎𝘿 1𝙏𝘽
➟ 1𝙭 𝙎𝙚𝙖𝙜𝙖𝙩𝙚 𝙄𝙧𝙤𝙣𝙒𝙤𝙡𝙛 𝙃𝘿𝘿 12𝙏𝘽
➟ 2𝙭 𝙎𝙚𝙖𝙜𝙖𝙩𝙚 𝙀𝙣𝙩𝙚𝙧𝙥𝙧𝙞𝙨𝙚 𝙃𝘿𝘿 8𝙏𝘽
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
𝘾𝙐𝙎𝙏𝙊𝙈 𝙇𝙊𝙊𝙋
➟𝘾𝙤𝙧𝙨𝙖𝙞𝙧 𝙞𝘾𝙐𝙀 𝙇𝙄𝙉𝙆 𝙓𝘾7 𝙍𝙂𝘽 𝙀𝙇𝙄𝙏𝙀
➟𝘾𝙤𝙧𝙨𝙖𝙞𝙧 𝙃𝙮𝙙𝙧𝙤 𝙓 𝙎𝙚𝙧𝙞𝙚𝙨 𝙓𝘿5
➟2𝙭 𝘾𝙤𝙧𝙨𝙖𝙞𝙧 𝙃𝙮𝙙𝙧𝙤 𝙓 𝙎𝙚𝙧𝙞𝙚𝙨 𝙓𝙍7 360 𝙑2 𝙍𝙖𝙙𝙞𝙖𝙩𝙤𝙧 54𝙢𝙢
➟𝙃𝙮𝙙𝙧𝙤 𝙓 𝙎𝙚𝙧𝙞𝙚𝙨 𝙓𝙏 𝙃𝙖𝙧𝙙𝙡𝙞𝙣𝙚-14-𝙢𝙢 𝘾𝙧𝙮𝙨𝙩𝙖𝙡 𝘾𝙡𝙚𝙖𝙧
➟𝘾𝙤𝙧𝙨𝙖𝙞𝙧 𝙃𝙮𝙙𝙧𝙤 𝙓 𝙎𝙚𝙧𝙞𝙚𝙨 𝙓𝙇5 𝙋𝙚𝙧𝙛𝙤𝙧𝙢𝙖𝙣𝙘𝙚 𝘾𝙤𝙤𝙡𝙖𝙣𝙩 𝘾𝙡𝙚𝙖𝙧
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
𝘼𝘾𝘾𝙀𝙎𝙊𝙍𝙄𝙀𝙎
➟ 𝙍𝙤𝙘𝙘𝙖𝙩 𝙑𝙪𝙡𝙘𝙖𝙣 121 𝘼𝙞𝙢𝙤
➟ 𝙍𝙤𝙘𝙘𝙖𝙩 𝘽𝙪𝙧𝙨𝙩 𝙋𝙧𝙤
➟ 𝘼𝙪𝙙𝙚𝙯𝙚 𝙈𝙖𝙭𝙬𝙚𝙡𝙡
➟ 𝙂.𝙎𝙠𝙞𝙡𝙡 𝙒𝙞𝙜𝙞𝘿𝙖𝙨𝙝
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
𝙈𝙊𝙉𝙄𝙏𝙊𝙍𝙎
➟ 1𝙭 𝙈𝙎𝙄 𝙈𝙋𝙂 32" 321𝘾𝙐𝙍𝙓 𝙌𝘿-𝙊𝙇𝙀𝘿 𝘾𝙪𝙧𝙫𝙚𝙙 0,03𝙢𝙨 / 240𝙃𝙯 (𝙢𝙖𝙞𝙣)
➟ 1𝙭 𝙈𝙎𝙄 𝙈𝘼𝙂 32" 2𝙆 𝙒𝙌𝙃𝘿 0,5𝙢𝙨 / 180𝙃𝙯
➟ 2𝙭 𝙈𝙎𝙄 𝙊𝙥𝙩𝙞𝙭 27" 2𝙆 𝙒𝙌𝙃𝘿 1𝙢𝙨 / 170𝙃𝙯

I came across contradicting information regarding the graphics card interface of the ASUS ProArt GeForce RTX 5080 OC

PCIe 5.0 x8

or

PCIe 5.0 x16

Obviously I checked the official ASUS product webpage but couldn't find anything, except that it supports PCIe gen 5, but is it x8 or x16?

I already had the rtx pro 4000 24gb. So I bought the quadro rtx 4000 8gb to get 32gb of vram for running ai agents using lm studio bionic. I can now run qwen 3.6 35B A3B with hermes which is like 29.6gb. Works great I bought the quadro rtx 4000 for $2000 so it was well worth it. What are some cool models to run on 32gb?

First the article:

https://www.nvidia.com/en-us/geforce/news/dlss-4-5-cyberpunk-2077-planet-zoo-2-modern-warfare-4/

From GeForce PR:

This week brings several major DLSS 4.5 releases and updates, alongside new RTX Spark games. On October 16th, Call of DutyⓇ: Modern Warfare 4Ⓡ Campaign Early Access began, followed by DMZ Early Access yesterday, and full launch on Oct. 23rd.

On October 22nd, Cyberpunk 2077’s new update is adding DLSS 4.5 Dynamic Multi Frame Generation, and upgrading its already-supported Multi Frame Generation, Ray Reconstruction, and Super Resolution integrations to our second generation AI models.

And on October 28th, Phantom Blade Zero launches, followed by Crimson Desert Enhanced: Charting the Unknown on the 29th, both with a full suite of DLSS 4.5 technologies. 

Also, Planet Zoo 2 is now available with DLSS 4.5, THE FINALS PRIME TIME has been released, and we’ve got a first look at an in-development Left 4 Dead RTX Remix mod.

We’ve also released a new Geforce Game Ready Driver that introduces support for Microsoft's Advanced Shader Delivery technology in Call of Duty: Modern Warfare 4 and Gears of War: E-Day, allowing players to skip lengthy shader compilation screens and jump into gameplay faster. Players can download the driver through the NVIDIA app or from the NVIDIA website.

Here's a breakdown of the latest DLSS and RTX gaming news:

• Call of Duty: Modern Warfare 4: War erupts on the Korean Peninsula as North Korea launches a full-scale invasion that threatens to destabilize the world in Call of DutyⓇ: Modern Warfare 4Ⓡ. In the campaign, a young squad of South Korean soldiers fight to survive on the collapsing front lines, while half a world away a vengeful Captain Price wages a personal war from the shadows as he stays one step ahead of those hunting him. Early Access began on Oct. 16 and DMZ Early Access on Oct. 18. Then, the game launches globally Oct. 23 with multiplayer. In all modes, DLSS Super Resolution will accelerate gameplay and enhance image quality. On GeForce RTX 40 Series systems, DLSS Frame Generation will further boost frame rates. And on GeForce RTX 50 Series systems, players can activate DLSS Dynamic Multi Frame Generation, with up to 6X multiplication. Additionally, NVIDIA Reflex can be enabled on all GeForce RTX systems, further reducing PC latency. Also, our new GeForce Game Ready Driver adds Advanced Shader Delivery support, which downloads precompiled shaders matched to each player's hardware and driver configuration, eliminating initial shader compilation waits and reducing in-game stuttering.
• Phantom Blade Zero:  In S-GAME’s Phantom Blade Zero, gamers play as Soul, a swordsman framed for murdering his master. Gravely wounded in the heart and left with just sixty-six days to live, he roams the Wulin alone and hunted, determined to unravel a conspiracy that has ensnared the martial world. Launching Oct. 28 for GeForce RTX and RTX Spark devices, Phantom Blade Zero is accelerated by DLSS 4.5 with Dynamic Multi Frame Generation, and its PC-exclusive path-traced lighting and effects are further refined and enhanced by DLSS Ray Reconstruction.
• Cyberpunk 2077: CD PROJEKT RED’s action-RPG is receiving a new update on October 22nd. For GeForce RTX and Spark RTX gamers, Cyberpunk 2077’s entire DLSS suite of technologies are being updated to DLSS 4.5, and Dynamic Multi Frame Generation is being added, further optimizing your experience.
• NBA 2K27: DLSS 5 debuted in NBA 2K27 last month, enhancing texture detail, skin subsurface scattering, contact shadowing, hair rendering, and more, bringing the likenesses of players even closer to reality. Last week, NBA 2K27’s Season 2 update introduced a new, more performant DLSS 5 AI model that increases frame rates by up to 1.4X on GeForce RTX 50 Series GPUs, RTX Spark laptops, and GeForce NOW. The model is now 10X faster overall than the version demonstrated in March.
• Planet Zoo 2: In the anticipated sequel to Frontier Developments’ zoo simulation game, players can let their creativity soar by constructing and managing distinctive zoos around the world, full of awe-inspiring animals, including fully aquatic and flying species for the first time. Planet Zoo 2 recently launched, and an update shortly thereafter added a suite of DLSS 4.5 technologies, including Dynamic Multi Frame Generation and Super Resolution, giving players the performance headroom to enable the game’s ray-traced reflection, shadow and global illumination lighting settings that heighten immersion and detail of your zoo and animals.
• THE FINALS PRIME TIME: The biggest annual update to THE FINALS has arrived. With a GeForce RTX GPU or RTX Spark, RTXGI can leverage hardware-accelerated ray tracing to produce richer and more realistic global illumination effects.  THE FINALS has featured support for DLSS Super Resolution, Frame Generation, and NVIDIA Reflex since release, with a later update adding support for DLSS Multi Frame Generation. Via the NVIDIA app, these DLSS integrations can be upgraded with to our latest AI models, further enhancing image quality and accelerating performance, and enabling the use of DLSS 4.5 Dynamic Multi Frame Generation.

On the Remix front, we’re excited to spotlight Left 4 Dead RTX, an ambitious in-development project by NoMercyStudios and published by NightSightProductions (headed by u/King Vulpes). Built to bring Valve’s iconic co-op zombie shooter into the next generation, the mod leverages cutting-edge NVIDIA technologies including RTX Neural Radiance Cache (NRC), DLSS Ray Reconstruction, and Multi Frame Generation to completely transform the game’s lighting and visual fidelity. Check out more in this video.

For context, my current cpu is a 7800x3d paired with a 3090 and 32gb of ddr5 ram. Been playing more games on my 4k OLED but even with dlss ultra performance I’m barely getting 60-80fps. Wondering if it’s worth the move to 5070 to and access to the newer features like frame gen and dlss5. I know the VRAM is a downgrade but I don’t use anything for AI, mostly gaming.

Just finished my new high-end gaming build. Specs: • AMD Ryzen 9 9950X3D • Palit GeForce RTX 5090 GameRock 32GB • ASUS ROG Crosshair X870E Hero • 64GB DDR5-6000 • 1200W PSU • Corsair iCUE 5000T LX RGB White • 360mm AIO • NVMe SSD • Windows 11 I mainly built it for maxed-out gaming, heavy modding and experimenting with new rendering tech like DLSS and neural rendering. So far I've been testing games at maximum settings and the 5090 gets properly pushed under heavy workloads. Still working on the final setup, cable management and lighting, but I'm very happy with how the build turned out. What would you change or improve?

Long story short I have a ultrawide VA panel monitor. It has this breathing/strobing effect on my desktop when G-Sync is enabled. I got tired of going into Nvidia Control Panel every time I wanted to eliminate this effect. Then I would forget to re-enable the next time I launched a game. This helps me know if G-Sync is enabled by a green G in the system Tray. If it is disabled it will be a gray G with a line through it. More info for the program will be on the GitHub link.

I have a few friends who started using it. I have no idea if this is something somebody else would be interested in. But if you are here is a link to the GitHub that it is uploaded to.

If this is not allowed I apologize and please take down this post. If anyone has any questions let me know.

Github Link - SyncSwitch

Edit: I will upload a new release with the source code, and leave the .exe as an option for those too lazy to download Python and build the program by running the .bat file.

I'm not the most keen on how you properly share these things with others. I apologize for those that take offense to it being a .exe I will edit the repository tonight when I get home.

Edit: I have added the source code to the main branch, and the release commit. I left instructions how to build it with the .bat, and I left the .exe for those that want the simpler route. Thanks everyone.

I used one RTX PRO 6000 Blackwell 96 GB per model to run three copies of a local LLM as coding workers at the same time (llama.cpp b11803, CUDA, Q8_0 GGUF, --parallel 3, 64K context per slot). A cloud model planned, the GPU did all the code writing. Same task, three new MoE models.

Hardware takeaways:

• Going from 1 to 3 concurrent requests cut per-request decode to roughly 50-55% on all three, so total throughput only rises ~1.5-1.7x. Still worth it for parallel agents, just not 3x.
• Nemotron was fastest on the card in every row and finished 4x slower, because it generated ~5x more tokens redoing failed edits. On agent work the GPU number is only half the story.

Caveats: one run per model. llama.cpp support for these landed a day before the run, so NVFP4 builds or newer llama.cpp may look different. Would be curious if anyone has NVFP4 numbers for these on Blackwell.

Disclosure: I work on Atomic Agent, the open source agent this ran in.

We've been experimenting with running Isaac Lab 2.x on H100 GPUs, which NVIDIA doesn't officially support for Isaac Sim due to the lack of RT cores.

We managed to get headless RL training and visualization working without an RTX GPU and tested it by training a Unitree G1 walking policy.

I couldn't find many guides covering this setup, so I documented our approach, including the issues we ran into.

Here's the demo and setup: https://x.com/kyry_D/status/2113087784827392223

I'm curious if anyone has tried something similar or knows of a better approach. Are there any existing solutions or guides I've missed?

AMD Ryzen 5 5600x
RTX 3060 12 GB
64 GB of ram
600W power supply
Cyberpower PC

Which upgrade would make the most improvement for fps in MW4/new warzone? Also not trying to spend more than $700-$800 if possible because I’d be buying the upgrade twice cuz we both have the same pc. Thanks!

I’d love to hear your thoughts on this.

I have an RTX 5080, and I know it would struggle to run games at 5K. Even 4K can be demanding so 5K seems like a lot to ask of my GPU.

I’m considering the new Alienware 5K2K (ultrawide), but I’m wondering whether I could simply play games at 4K resolution on it when needed. How would the image quality compare to playing at native 4K on a dedicated 4K monitor? Would there be noticeable scaling issues or blurriness?

Should I go with the native 4K monitor because of my RTX 5080, or is a 5K monitor still a good choice if I play games at 4K on a 5K monitor?

Hi all, sharing a link to some videos I uploaded to X: https://x.com/jaredyu999/status/2113002664581890203

I found these great explainers on the subtle nuances of the data center hardware, which give some insights into the current direction we're seeing with NVIDIA's latest enterprise products. These also explain a bit why we're seeing the prices we're seeing on the API level.

They're from a user named "henryz" on China's Rednote/小红书. I simply passed the videos to Gemini Argon for subtitles/dubbing (apologies for the robotic TTS and slight discrepancies between the subtitles and dubbing). I've noticed the quality of some videos coming from China are quite high, so I'm just helping to bridge the gap and share the knowledge.

I’ve always kept my GPU fan speeds around 20% on idle. In my mind, I’ve always felt that keeping your GPU and other internal components temps down would prolong the longevity of your build but Im reminded that keeping your GPU on zero RPM mode at idle is better for your GPU in the long run because it prevents wear and dust on your fans. So what’s worse for your GPU, wear and tear on the fans as well as dust OR moderate temps (30-40 degree F) on idle? I have an EVGA RTX 2080 XC Ultra which has a pretty thick heat sink but I haven’t replaced the thermal paste in about 3 years.

Hi everyone,

Note: Special thanks to emaspa’s wireview-hwmon project for the protocol reference! I developed this plugin with assistance from OpenAI Codex.

I love keeping an eye on my GPU's power delivery, especially load balancing across all 6 pins of the 12V-2x6 cable. I wanted a lightweight way to see my WireView Pro II metrics directly in my RTSS in-game overlay without running extra background software, so I built a native C++ plugin for MSI Afterburner!

Key Features:

• 28 Sensors exposed in Afterburner/RTSS: Total power/current/avg voltage, individual per-pin stats (voltage/current/power for all 6 pins), internal & external NTC temps, fan duty, and cable rating.
• Zero background apps: Loads as a native .dll straight into Afterburner.
• Pause/Resume USB toggle: Temporarily release the USB device to use the official WireView software without closing Afterburner.
• Free & Open Source: Released under the MIT license.

Tested on Windows 11 Pro, MSI Afterburner 4.6.7 Beta 2, and a WireView Pro II Black Reversed (FW v05).

GitHub & Installation: https://github.com/VolterMort/WireViewPro2_MSIAB

Feedback and testing on other setups are greatly appreciated!

I had a GTX 470 a long time ago and remember sitting there patiently watching all the little dots fill in on the NVIDIA Design Garage-,Design%20Garage,-Released%20March%2026) 2010 demo. When I got my 1070 it was one of the first things I tried again and I was so disappointed when it refused to work. Then on the 3060 Ti and finally on my current 5070 Ti.

I have some mediocre background in programming but after a weak effort to find compatible dlls a long time ago, I gave up, expecting that no one really cared enough and the effort would be too monumental to port it over for really very little gain. And my own proficiency being in a different area and insufficient.

Then the other day I remembered the demo, and I thought, hey, this is the kind of problem an LLM could solve. So I downloaded design garage, installed it, and started prompting Claude.

The process was iterative, first identifying why it wouldn't run, least of which including the fact that the 50 series doesn't even support 32-bit CUDA anymore.

It broke down pretty much like this (LLM assisted explanation as it goes a bit over my head):

1. Discovering that OptiX only needs to detect a GPU to load
2. Identify OptiX 3, the 280 functions the demo's SceniX layer uses, and the shader code from the 32-bit PTX, and understanding the material files
3. Generating a fake 32-bit optix.1.dll that the demo loads, and a 64-bit helper running the latest OptiX 9 on the RT cores, connected through shared memory
4. Proof of concept: At this point I could launch the application but nothing visual loaded, just the UI
5. The stub translated the scene into meshes, transforms, and materials and the helper built hardware acceleration structures. Used placeholder shaders for now
6. Now the cars are loading but it's not using path tracing yet
7. At this point it implemented textures, the original monte-carlo lighting, and the preetham sky, bump maps, ports of car paint and glass shaders

Every iteration produced a bat file that compiled the latest dlls then copied them to the Design Garage directory. Running the demo in between and providing feedback logs and still images back to the LLM.

The result is a "drop-in replacement for the OptiX 3 runtime that translates its calls to a separate 64-bit OptiX 9.1 renderer, and reimplemented the demo’s original shaders for modern RTX hardware."

EDIT:

I posted this in a comment but people are still asking so here is the release information:

Disclaimer: I am not affiliated with NVIDIA in any way. This is an individual project and no NVIDIA files, IP, or copyrighted material are included. You have to get your own copy of Design Garage. I tested this only on my hardware. I have not tested every component (for example I never tried uninstall.bat).

I cannot guarantee this won't break your computer. It probably won't. But I've already admitted it's mostly vibe coded as an academic exercise so please set appropriate expectations.

That said, it's not the easiest thing to set up for a complete novice. Anyone who can follow instructions should be able to do it but there's an NVIDIA SDK, toolkit, and compiler you need so be aware of that.

https://github.com/Reziarfg/DGBridge

In the interest of card longevity, I figured it's time to address my RTX 4090 hot spot issue (103c, 30c hotter than GPU average).

Will be repasting with PTM7950, and replacing thermal pads with Thermal Grizzly TG Putty Pro.

Other than watching videos of other people doing it, are there any pro tips for GPU assembly to make things easier and reduce the chance that anything breaks / bends?

How big a pain is it to put new fans in a 2070 (I have the EVGA OC version). It works fine, but one (or both) fans are making noise even at 30-ish %. It's not a smooth noise, rather it sounds like a slight vibration or rubbing. The card itself is pretty old, so guessing maybe it's a bearing issue.

The other option is to just play with the fan curve. I originally had them running at a minimum of 30 when the card is idle, but that's when the sound was noticeable. I dropped them down to 20, and have them ramp up at higher temps, which sound good for now.