MightyPirates
IDEA Support to additional GPU VRAM
In my calculations, I want to make a fast-refreshing screen, and for this I calculated that a double buffer for 160x50 would require 125 KB of RAM, but I don't want to keep it in the RAM where the processor works, because there is a GPU for this, but I found out that only 3200 bytes are available for all GPU levels. Can you change this somehow? Or where can I change this in the config? I edited the lines in gpu {} in the application.conf section, but that didn't solve my problem.
How did you get to this result ? Anyway, this option already exists, the issue is invalid. You can find the config option at the bottom of the config file.
Maybe you misunderstood, but I mentioned that this did not solve my problem; only 3200 bytes of VRAM are free at all GPU levels.
Maybe you misunderstood, but I mentioned that this did not solve my problem; only 3200 bytes of VRAM are free at all GPU levels.
Can you give me the test.lua script so I can reproduce on my side ?
I also noticed a bug: if you increase vramSizes and turn away from the screen, the output disappears, and even if you break it and put it back, the only thing that helps is restarting the computer.
Code:
local component = require("component") local gpu = component.gpu
-- Всего VRAM (не включая экран) print("Total VRAM:", gpu.totalMemory())
-- Свободное VRAM print("Free VRAM:", gpu.freeMemory())
Is it possible to get the full 24-bit color palette by changing the configuration? Or is this not implemented?
Maybe you misunderstood, but I mentioned that this did not solve my problem; only 3200 bytes of VRAM are free at all GPU levels.
Can you give me the test.lua script so I can reproduce on my side ?
Sorry for jumping to conclusions. I played around with it a bit more, and the VRAM really did increase. Now the level 3 GPU has 125 KB, which will greatly simplify the creation of my engine for this mod :D
well then that issue can be closed I think, unless the functions' implementations still have flaws somehow
well then that issue can be closed I think, unless the functions' implementations still have flaws somehow
Could you check the bug I mentioned above? When I increase vramsizes the monitors of some sizes sometimes stop showing the picture if I turn my back or move away for a couple of chunks. Maybe it's because I have the server on hdd and sometimes lags tps, and it affected the monitors
no that sounds more like faulty culling to me for the "move away" part I think there an option to fade the display out if it was more conservative there would be more tiles drawn and more performance loss, but heh it's in your peripheral vision/far away anyway so why worry
I meant that at some random moment on a large monitor, the picture just disappears right before your eyes when you’re literally standing 1–2 blocks away from the monitor, and it only shows up again after restarting the PC. If you revert the changes to vramsizes in the config, this bug goes away. Also, some kind of error shows up in the chat and asks to send it to support, something like “failed to transform classes”.
also, I saw that you were using TLauncher, please use another launcher as this one has spyware allegations and shady origins As for transformer errors, I don't really know, could be a mod conflict or something (though even for me these Forge features are strange)
also, I saw that you were using TLauncher, please use another launcher as this one has spyware allegations and shady origins As for transformer errors, I don't really know, could be a mod conflict or something (though even for me these Forge features are strange)
No, it's not a tlauncher. Only the name remains; it's an open-source legacy launcher.
Is this normal? The server with 4 GB of RAM worked for 17 days, and then suddenly crashed.