Izzy's Old Account
so I implemented multiple virtual terminals per display in the PsychOS terminal emulator layer if I use a T3 GPU instead of a T2 GPU, the screen it's attached to gets 12 vtys it's pretty silly haven't implemented the DEC extensions for copying data between "pages" yet but I might later. also the area fill control sequences.
Izzy's Old Account
Reply to @[email protected]
while it would be interesting to implement something that runs on the screen only and acts as a task manager/debugger, I'm not confident I can reasonably do that. that's okay though. this is pretty useful nonetheless.
Izzy's Old Account
Reply to @[email protected]
Shout-out to @asie@mk.asie.pl who fixed a synchronisation bug in OC that was preventing this from working in-game and stopped me pulling all my hair out. Now I have it running in-game, see the attached video for a demonstration
for my next trick I'll allow multiple physical displays on one GPU
Izzy's Old Account
Reply to @[email protected]
real talk I'll probably do some more bullshit with different size vtys on T2 and 3 displays. If you run them at lower resolutions you get non-displayed but drawable areas; this means if you run a T3 display (160x50) at T2 resolution (80x25) you get the equivalent of 3 more screens of VRAM.it would also be interesting to play with allocating one less line as the drawable area and having a status line with like, time, memory, number of processes. this would give me just enough VRAM wiggle room to allow swapping out an extra screen one section at a time. with a T3 GPU, using 80x24 displays instead of 80x25 displays gives you half a screen worth of free VRAM, which could be used to store half the screen, which would then be drawn over with the terminal you're switching to, then that section of VRAM would be drawn into from the half you saved, and the process would be repeated for the other half. this would mean doing ... 4 bitblt calls instead of 2, but only 2 of those would actually relate to the screen