Recientemente hice el test de Ingles de https://www.cambridgeenglish.org/test-your-english/ en el cual obtuve 21 preguntas correctas de 25... y me puso "Nivel A1"...
Eso me puso en duda, así que le pregunte a GEMINI que me hiciera un test para medir mi nivel "real" y GEMINI dice que soy C1.
Do you remember back in the 90s, kids spread a rumour worldwide about "Holding Down + B increases catch rate" ??? It's true. Always works for me.
Don't mind me, just catching my TM Slave.
Ya di el viejazo. Extraño las tardes de retas de Tekino después de la secundaria.
Not perfect but does bring memories.
Not trying to spam, but can't edit a ful video without showing a vertical video in horizontal format and viceversa. So please excuse "double posting".
This video shows the current LCD Module of the shader.
LCD Flare, Shimmer, Polarizer and Drop Shadow reacts to Gyro Sensor if your device has it.
Otherwise, parameters works but won't react to device movements.
Managed to decrease the GPU demand for the entire Glow + Phosphor Decay/Trail feature.
Now it runs fine in Samsung Galaxy A03 as well as in my puny 2015 notebook.
Shader for #RetroArch "Merge" TEST.
It merges "LCD Master" + "CRT Master" + "Phosphor" each module with their respective Toggle, Patameter and Control for their respective features. Each "part" is it's own shader, except this "Merge" is literally all of them in 2 pass Shaders: "Merge.slang" + "Phosphor.slang" sharing one "Merge.slangp".
I tried to get the Phosphor Decay script as a single pass but the phosphor decay effect dies as a single psss.
LCD Master Part:
CRT Master Part:
Image Adjustment Part:
I still have to attack two minor bugs, but overall every single parameter has it's on/off toggle switch and can be stacked with each other.
Tests indicates that runs fine in:
[PC]
- Windows 10 Intel N3700 / d3d11 Driver
- Windows 7 Intel i3-2120 / d3d10 Driver
[Android]
- Samsung Galaxy A03 / Vulkan
In android though, the Glow effect introduces minor input lag and audio stutter... but at low amounts, my Mali G57 bears the effect.
Been working on this for over a week now.
Finally have the "Glow Decay" effect done!
It simulates the CRT "Phosphore Decay" in which CRT's over-estimulates sprites in dark backgrounds and leaves a trail behind that slowly fades out.
Note: My screen recorder is not capturing the CRT Masks fine, in video looks like colors are bleeding, in my VGA monitor I'm not seeing such bleed.
This is an attempt to further improve my shader "LCD Master" which currently sits at version 15. Everytime I add a new feature and doesn't break, I make a copy, hence a "version" and continue working on it, if it breaks, fall back to previous.
Currently struggling a lot with a "CRT Bloom" which I very vividly remember seeing in an old Samsung CRT VGA Monitor back in the 90s when using Windows 98.
The current "Bloom" I have is heavy for my potato and doesn't even look remotely right... but having the Curvature + Phosphor Masks in my potato is a massive win... usually, recording adds another layer of CPU performance drop... but honestly, my shader's Curvature + Phosphor Masks are not harming emulation at all (only if I record) and if i'm honest, my potato struggles a lot even with the "CRT-Potato Shaders"... so I pat myself on the back.
Also experimenting with a "Dither Blur" parameter to merge neighbour pixels that some games uses to create tones that aren't there.
Me pasé desde temprano haciendo mis Dynamics y Presets.
Ya perdí la práctica!
Still working out the "Flare/Shimmer" effect. It reacts to Gyro Sensors.
Trying to recreate what I see in my GBC...
I ran into memory issues this week. Removed some features, merged some... this is in order to:
- Optimize the shader to work in "low end" devices.
- Have more memory for future features.
Test done in Samsung Galaxy A03.
Me presento, soy nuevo y me gustaría hacer "amigos".
Soy Juan, de México, vivo en CDMX, Iztapalapa, tengo casi 33, y llevo dibujando "seriamente" desde el 2014. Autodidacta, y ya casi no dibujo por andar "estudiando" programación.
Nota: La tercera imágen fue hecha con "Colors 3DS".
Regalito: Pinceles para Autodesk Sketchbook (https://gbatemp.net/threads/menamorarte-thread.663961/)
Saludos.
Update of my Custom Shader "LCD Master" for RetroArch Android, using Vulkan as Video Driver.
It's an optimization/improvement + new "shimmer" effect update. Still working on it.
Gameplay recorded in Samsung Galaxy A03.
PS: Excuse touch controls 🤕
https://www.youtube.com/watch?v=p0TYmkHt5lw
Since some users asked for it, I've updated my original script by adding a scale and move by 10 option + added a new parameter to the generated overlay.cfg in order to make things easier for the user.
Download: https://ko-fi.com/s/ae711d2fc1
This software was developed from scratch and was made it to aid myself in the creation of Input Animated Overlays for RetroArch as I find the process entertaining.
It's designed with simplicity in mind, and is as easy as adding your background.png, clicking "+ New Item", choosing the shape (rect or radial), dragging it to the right position, scaling it and moving it in with the arrow keys on your keyboard, zooming-in with mouse scroll wheel for perfect placement, adding the parameter/name of the input, and clicking "Save Overlay .cfg" to generate a readymade .cfg file which will need minor adjustments with any text editor such as adding parameters to your analog sticks or checking that every input has the correct identifier.
Finally made it a reality. The old software was too outdated in my personal opinion.
It handles Rect and Radial buttons and I've added a Zoom In/Out function, plus moving items with Direction Keys and Button Combo:
- Ctrl + Up = Scale Up Item
- Ctrl + Down = Scale Down
- Ctrl + Right = Make Item Wider
- Ctrl + Left = Make Item Narrower
Also a "Copy Paste" function to get consistent Items, for instance, when making Face Buttons that needs the same dimensions.
Nice!
Will do other colors.
I AM NOT A BOT AND I'M POSTING THIS AS CLEAR AS POSSIBLE IN MANY DIFFEREN SUB REDDITS. PLEASE CONSIDER READING BEFORE DELETING MY POST!
I've been working in a custom Screen Recorder that is adressing my own issues... since all the alternatives where either bloated or simply made my recording process laggy due to me not meeting the minimum hardware requirements... I decided to tackle the issue myself and this is how "Papalotl" was born.
Papalotl has been in active development since March 6th 2026... and up until the time of this post, Papalotl is at version 3.2.2... (currently debugging it)
It began as a simple Screen Recorder, "Papalotl v1" that in personal tests in my modest hardware (Windows 7PC, Intel i3-2120, 6GB RAM and NO GPU) outperformed my copy of Wondershare Filmora.
Where Wondershare Filmora achieved 11FPS, at the Lowest Quality possible... Papalotl reached a smooth 60FPS: https://www.facebook.com/reel/933609092855386
Then, I decided it needed Audio Capture... and that's how Papalotl v2 was born: https://www.facebook.com/reel/1623774778842065
Then... I began to debug the v2, and couple bug fixes and optimizations later, I landed at 2.2.5: https://www.facebook.com/reel/1023566780618277
This version came with two new capture methods:
Timelapse Mode: https://www.facebook.com/reel/1517095070097228
Snapshot Mode: https://www.facebook.com/reel/2375021109649193
Then... I decided to try and optimize this version because I was noticing stuttering in some tests... and after bug fixes and further optimization, the current Papalotl v3.X branch was born which is a totally different capture method from 2.X.X: https://www.facebook.com/reel/1508045680853486
Now... I'm currently optimizing the v3.X branch, and I've split Papalotl into two versions:
Lite and Pro.
Papalotl 3.2.X LITE - Outperforms all previous versions and it's hardcoded to be capped at 720p IF IT CAN'T GO FURTHER THAN THAT DUE TO CPU CONSTRAINS: https://www.facebook.com/reel/1557195099320771
Papalotl 3.2.X PRO - Outperforms LITE by eliminating such constrains, and it literally "chooses" the best case scenario depending on what you're recording. Needs a lot of testing since, it's literally using capture methods that might / might now work depending on task... and it's not because it's broken, but because it is meant to do that by eliminating hardcoded constrains that LITE version has implemented.
Current Papalotl v3.2.2 LITE can record Dolphin, at a stable 30FPS with occasional Framedrop without compromising Quality, in theory, PRO version should outbeat LITE in terms of Video Quality Output
This Papalotl v3.2.2 LITE test is:
Dolphin - Twilight Princess
Papalotl set to: 720p, 30FPS, LOW Quality Mode, Fullscreen Capture: https://www.facebook.com/reel/1379165307399971
NOTE: I've implemented a "Pause / Resume" feature into my code since 3.2.1... it's buggy right now and it's literally the last thing I need to fix to release Papalotl 3.2.2 LITE and PRO versions.
The changelog is basically this:
- Papalotl v1 outperformed OBS and Wondershare Filmora in my tests.
- Papalotl 2.0 outperformed 1.0.
- Papalotl 2.2.5 outperformed 2.0.
- Papalotl 3.1 outperformed 2.2.5.
- Papalotl 3.2.1 outperformed 3 1.
- Papalotl 3.2.2 outperformed 3.2.1.
And you can try Papalotl v1 for free right now: https://ko-fi.com/s/5fa602d9a5
With the option to upgrade to Papalotl v3.2.2 once I debug the "Pause / Resume" function.
Papalotl 3.2.2 will remain as a Portable App also... BUT you'll have to get FFMPEG.exe in order for it to function, it just needs "ffmpeg.exe" right next to the "Papalotl 3.2.2.exe" or both in the same folder for it to work.
Papalotl 3.2.2 won't be free.
I AM NOT A BOT AND I'M POSTING THIS AS CLEAR AS POSSIBLE IN MANY DIFFEREN SUB REDDITS. PLEASE CONSIDER READING BEFORE DELETING MY POST!
I've been working in a custom Screen Recorder that is adressing my own issues... since all the alternatives where either bloated or simply made my recording process laggy due to me not meeting the minimum hardware requirements... I decided to tackle the issue myself and this is how "Papalotl" was born.
Papalotl has been in active development since March 6th 2026... and up until the time of this post, Papalotl is at version 3.2.2... (currently debugging it)
It began as a simple Screen Recorder, "Papalotl v1" that in personal tests in my modest hardware (Windows 7PC, Intel i3-2120, 6GB RAM and NO GPU) outperformed my copy of Wondershare Filmora.
Where Wondershare Filmora achieved 11FPS, at the Lowest Quality possible... Papalotl reached a smooth 60FPS: https://www.facebook.com/reel/933609092855386
Then, I decided it needed Audio Capture... and that's how Papalotl v2 was born: https://www.facebook.com/reel/1623774778842065
Then... I began to debug the v2, and couple bug fixes and optimizations later, I landed at 2.2.5: https://www.facebook.com/reel/1023566780618277
This version came with two new capture methods:
Timelapse Mode: https://www.facebook.com/reel/1517095070097228
Snapshot Mode: https://www.facebook.com/reel/2375021109649193
Then... I decided to try and optimize this version because I was noticing stuttering in some tests... and after bug fixes and further optimization, the current Papalotl v3.X branch was born which is a totally different capture method from 2.X.X: https://www.facebook.com/reel/1508045680853486
Now... I'm currently optimizing the v3.X branch, and I've split Papalotl into two versions:
Lite and Pro.
Papalotl 3.2.X LITE - Outperforms all previous versions and it's hardcoded to be capped at 720p IF IT CAN'T GO FURTHER THAN THAT DUE TO CPU CONSTRAINS: https://www.facebook.com/reel/1557195099320771
Papalotl 3.2.X PRO - Outperforms LITE by eliminating such constrains, and it literally "chooses" the best case scenario depending on what you're recording. Needs a lot of testing since, it's literally using capture methods that might / might now work depending on task... and it's not because it's broken, but because it is meant to do that by eliminating hardcoded constrains that LITE version has implemented.
Current Papalotl v3.2.2 LITE can record Dolphin, at a stable 30FPS with occasional Framedrop without compromising Quality, in theory, PRO version should outbeat LITE in terms of Video Quality Output
This Papalotl v3.2.2 LITE test is:
Dolphin - Twilight Princess
Papalotl set to: 720p, 30FPS, LOW Quality Mode, Fullscreen Capture: https://www.facebook.com/reel/1379165307399971
NOTE: I've implemented a "Pause / Resume" feature into my code since 3.2.1... it's buggy right now and it's literally the last thing I need to fix to release Papalotl 3.2.2 LITE and PRO versions.
The changelog is basically this:
- Papalotl v1 outperformed OBS and Wondershare Filmora in my tests.
- Papalotl 2.0 outperformed 1.0.
- Papalotl 2.2.5 outperformed 2.0.
- Papalotl 3.1 outperformed 2.2.5.
- Papalotl 3.2.1 outperformed 3 1.
- Papalotl 3.2.2 outperformed 3.2.1.
And you can try Papalotl v1 for free right now: https://ko-fi.com/s/5fa602d9a5
With the option to upgrade to Papalotl v3.2.2 once I debug the "Pause / Resume" function.
Papalotl 3.2.2 will remain as a Portable App also... BUT you'll have to get FFMPEG.exe in order for it to function, it just needs "ffmpeg.exe" right next to the "Papalotl 3.2.2.exe" or both in the same folder for it to work.
Papalotl 3.2.2 won't be free.