Lumion Won’t Use My Full GPU: Troubleshooting Performance for Arch-Viz
Before assuming the card is broken, check what Lumion is actually doing, because low GPU usage usually has a mundane cause. In the editor, Lumion caps its framerate to your monitor’s refresh rate, so seeing the GPU at 40 or 60 percent while you navigate is normal, not a fault. The reading that matters is during a final render: if the GPU still sits low then, the usual culprits are a CPU bottleneck feeding it too slowly, Lumion running on the wrong GPU (the integrated chip on a laptop), or a power or driver setting holding it back. Each has a specific fix, and almost none of them is a dead card.
First, is it even a problem?
Plenty of people panic at a GPU usage number that is behaving exactly as designed. While you move around the editor, Lumion only needs to draw enough frames to match your screen, usually 60 a second, so once it hits that it stops pushing the card harder. That leaves the GPU well below 100 percent, and that is fine. The number worth watching is during an actual photo or movie render, when Lumion should be working the card hard. If it maxes out there, nothing is wrong. If it stays low during a real render, then you have a bottleneck to find.
The usual causes, and how to fix each
When the GPU genuinely will not engage during a render, it is almost always one of these. Work down the list, since the first two catch most cases.
| Symptom | Likely cause | Fix |
|---|---|---|
| GPU low, CPU pegged near 100% | CPU bottleneck feeding the GPU too slowly, often a very heavy or unoptimized scene | Optimize the scene; a faster CPU helps, but lighten geometry first |
| Wrong GPU shown in use (laptops) | Lumion is running on integrated graphics, not the dedicated RTX card | Force Lumion onto the dedicated GPU in Windows graphics settings or the NVIDIA control panel |
| GPU never ramps up fully | Power plan limiting performance, or laptop on battery | Set the power plan to maximum performance and plug in |
| Stutter rather than low usage | VRAM full, swapping to system memory | Lighten the scene or use a card with more VRAM |
| Low usage after a driver update | Driver glitch or wrong driver version | Clean-install the current studio or game-ready driver |
The wrong-GPU one catches more laptop users than any other. A gaming or mobile workstation laptop has both an integrated chip and a dedicated RTX card, and Windows sometimes hands Lumion the weak integrated one, so the powerful card sits idle while you wonder why performance is poor. Forcing Lumion onto the dedicated GPU in the graphics settings often transforms it in one step.
When the card is just not strong enough
Sometimes the GPU is being used fully and the performance is still poor, which is a different message: the card is the limit, not a misconfiguration. That is the case the laptop-throttling and slow-render articles deal with, in why Lumion is slow on a laptop and why one GPU is not enough. Here the answer is genuinely more GPU, either an upgrade or a rented machine, rather than a setting.
A cloud machine is also a clean way to sidestep the configuration problems above entirely. A rented Windows server has one dedicated RTX 4090 and no integrated chip to confuse things, no laptop power throttling, and 24GB of VRAM so swapping is not an issue. Because Lumion is real-time, this is a rented machine rather than a render farm, since the per-frame farms, GarageFarm, RebusFarm and Fox, cannot run Lumion. iRender is the service I use for it, with a dedicated RTX 4090 that engages fully on every render, your own Lumion install, and a free trial to compare against your local machine. It is RTX 4090 rather than the 5090, you handle the first setup, and the per-hour meter runs until you shut down.
Card is fully used and still too slow? That is a hardware limit, not a setting. Render Lumion on a dedicated RTX 4090 through iRender, where the card engages fully every time, with a free trial to compare against your machine. → Try iRender for Lumion
FAQ
- Why is my GPU usage low when running Lumion?
In the editor it is usually normal, because Lumion caps its framerate to your monitor’s refresh rate and stops pushing the card once it hits that, leaving usage below 100 percent by design. The number to watch is during a final render, when Lumion should work the card hard. If usage stays low then, you have a bottleneck: commonly a CPU limit, Lumion running on integrated graphics instead of the dedicated GPU, or a power or driver setting holding the card back.
2. How do I force Lumion to use my dedicated GPU?
On a laptop with both integrated and dedicated graphics, open Windows graphics settings or the NVIDIA control panel and assign Lumion to the high-performance dedicated GPU. Windows sometimes defaults Lumion to the weak integrated chip, leaving the powerful RTX card idle. Setting it explicitly to the dedicated card, plugging in, and choosing a maximum performance power plan often fixes poor Lumion performance in a single step, since the strong card finally does the work.
3. Is low GPU usage in Lumion always a problem?
No. While you navigate the editor, Lumion only renders enough frames to match your monitor, so it intentionally runs the GPU below full to avoid wasting power, and a reading of 40 to 60 percent there is expected. It is only a concern if the GPU stays low during an actual photo or movie render, when the card should be fully engaged. So check usage during a real render, not while moving around the editor, before assuming something is wrong.
4. Why is my CPU maxed but my GPU idle in Lumion?
That points to a CPU bottleneck. Lumion needs the processor to prepare and feed the scene to the GPU, and a very heavy or unoptimized scene can keep the CPU so busy that the GPU waits for data, sitting underused. Optimizing the scene with lighter geometry and sensible textures usually eases it, and a faster CPU helps in stubborn cases. Renting a cloud machine with a strong balanced configuration also avoids the bottleneck if your processor is the weak link.
Related post: Lumion Keeps Crashing on Big Scenes: Causes and Fixes for Architects
