From 77eb8dba8a6a7730dc90983566287b9157237c0d Mon Sep 17 00:00:00 2001 From: Jonathan Coates Date: Tue, 20 Oct 2020 15:32:15 +0100 Subject: [PATCH] Created Monitor renderers (markdown) --- Monitor-renderers.md | 20 ++++++++++++++++++++ 1 file changed, 20 insertions(+) create mode 100644 Monitor-renderers.md diff --git a/Monitor-renderers.md b/Monitor-renderers.md new file mode 100644 index 0000000..269bb81 --- /dev/null +++ b/Monitor-renderers.md @@ -0,0 +1,20 @@ +One of the most FPS intensive parts of CC: Tweaked is its monitors. In order to reduce lag as much as possible, while remaining compatible with other mods, we provide two ways to render monitors. + +These can be changed through the `monitor_renderer` option in the `computercraft-client.toml` config file. + + - **Texture buffer objects (TBO):** This uses texture buffer objects and a custom shader to render the monitor. This is extremely fast, but not work when using Optifine or on older graphics cards. + - **Vertex buffer objects (VBO):** This is a more traditional renderer using vertex buffers. This is somewhat slower than TBOs for normal rendering, and significantly slower when monitors update. However, it is compatible with everything. + - **Best:** This is the default. It will use TBOs if the graphics card supports it, falling back to VBOs if needed. + +A more technical description of the various backends may be found [on this blogpost][blag]. + +## Common problems + +### Monitors are partially white/transparent with shaders +When using shaders, monitors may appear incredibly pale or transparent: + +![A transparent monitor](https://user-images.githubusercontent.com/4346137/80976751-b7f88480-8e1b-11ea-9637-e5649de918a3.png) + +This is a problem with how shaders work with the TBO renderer. Switching to the VBO renderer should fix it. + +[blag]: https://squiddev.cc/2020/05/08/monitors.html "An optimised monitor renderer" \ No newline at end of file