Software renderer: Difference between revisions
Jump to navigation
Jump to search
SirYodaJedi (talk | contribs) mNo edit summary |
Thunder4ik (talk | contribs) m (→top: clean up, replaced: {{goldsrc → {{gldsrc (2)) |
||
Line 1: | Line 1: | ||
{{stub}} | {{stub}} | ||
A '''software renderer''', such as those available in {{ | A '''software renderer''', such as those available in {{gldsrc|2}} and {{idtech2|2}}, uses the CPU to render 3D geometry, instead of a GPU. A 3D application using a software renderer can be considered to be running in '''software mode'''. | ||
The GPU is still used for processing the 2D image generated from the software renderer, but no 3D hardware is used. | The GPU is still used for processing the 2D image generated from the software renderer, but no 3D hardware is used. | ||
{{todo|Explain more about {{ | {{todo|Explain more about {{gldsrc}}'s software renderer, its limitations, and its advantages. | ||
* Overbright lighting on MDLs (instead of only map geometry) | * Overbright lighting on MDLs (instead of only map geometry) | ||
* Water ripple effect | * Water ripple effect |
Revision as of 13:25, 4 January 2024
A software renderer, such as those available in GoldSrc and
id Tech 2, uses the CPU to render 3D geometry, instead of a GPU. A 3D application using a software renderer can be considered to be running in software mode.
The GPU is still used for processing the 2D image generated from the software renderer, but no 3D hardware is used.
Todo: Explain more about
's software renderer, its limitations, and its advantages.

- Overbright lighting on MDLs (instead of only map geometry)
- Water ripple effect
- Lack of texture filtering
- 256x256 texture limit
- Lower limits
- Overdraw from func_detail
- Custom mipmaps are possible