Video wird geladen...

Video konnte nicht geladen werden

Zur Startseite

day ???/??? ascii art generation i have successfully added a performant terminal rendering pipeline! frames are rendered as and when they are decoded now (what you see in the video is real time) here's the opening to Serial Experiments Lain on wezterm. 60 fps, locked. with zero hiccups. enjoy...

34,389 Aufrufe • vor 1 Jahr •via X (Twitter)

11 Kommentare

Profilbild von ronin
roninvor 1 Jahr

made with zig, multithreading, and a decent amount of time

Profilbild von gooby
goobyvor 1 Jahr

Could you render webpages somehow so you could browser the web in the terminal lol

Profilbild von ronin
roninvor 1 Jahr

@yacineMTB was able to do this using chrome debugging protocol and he was scrolling x on his terminal lmfao

Profilbild von noah
noahvor 1 Jahr

Do jujutsu kaisen intro

Profilbild von ronin
roninvor 1 Jahr

which one

Profilbild von 0xECS ⎊
0xECS ⎊vor 1 Jahr

this is insane work bro what did you do to make it so performant? encoding algorithms etc. been wanting to make a real time encoding engine myself and then make a TUI video streamer for different video streaming websites😂

Profilbild von ronin
roninvor 1 Jahr

this is specific for the terminal rendering: >multithreading >framebuffer with a bit of added latency to render smoothly >minimal heap allocations it's all on the cpu! i'm going to learn gpu stuff soon

Profilbild von (infinite-jes)
(infinite-jes)vor 1 Jahr

did you post the code yet?

Profilbild von ronin
roninvor 1 Jahr

its been up!

Profilbild von khyro
khyrovor 1 Jahr

fuck it, i am going to start hating on you now, you too good

Profilbild von ronin
roninvor 1 Jahr

bro 😭

Ähnliche Videos

In my previous post about the #Nioh3 demo, I mentioned that when the game isn’t consistently holding 60 FPS or 120 FPS, several issues can show up. Here’s a clearer breakdown of what's going on. The main reason is that the game speed and physics are tied to the frame rate. When you enable the 120 FPS cap, the engine start overreacting and pushes CPU usage very high, even if the game is still running at around 60 FPS (as shown in the first example). In the second clip, you can see the uneven, jittery camera movement I mentioned before. Notice how much smoother 60 FPS and 120 FPS look compared to the unlocked side. Also, camera movement at 60 FPS is slightly faster than at 120 FPS. In the third clip, player movement is slower when the frame rate is unlocked. This doesn’t happen all the time, but it shows up often enough to be noticeable. Because of how the Katana Engine behaves, the game is clearly designed around 60 FPS. Running at 120 FPS is possible, but it’s only recommended if your system can maintain that target almost all the time, which isn’t easy to achieve. There’s also an alternative workaround where you select the 60 (locked) option and enable Frame Generation (DLSS or FSR 3), as shown in the last clip. The downside is that DLSS Frame Generation tends to show the same stuttery look as when the frame rate isn’t holding a fixed target, likely due to Reflex keeping the frame rate slightly below target. FSR Frame Generation, on the other hand, looks much smoother and works better here.

BenchmarKing

17,820 Aufrufe • vor 6 Monaten