Closed eobet closed 1 year ago
None of the openFPGA cores have settings like that. The way the Pocket is designed, the second FPGA operates the scaler and applies any effects necessary. This functionality is not yet available to openFPGA cores.
It's been a while since I've received advanced info, but when I last heard, this coming Pocket update (supposed to be before the end of the year) will contain the video modes for openFPGA.
In any case, this core is completely out of space; currently at 99% utilization (you're not really supposed to go over ~80). There's no room to add advanced effects or post processing.
@agg23 with Pocket firmware 2.0 you can apparently now enable different CRT effect modes...
Although, I notice that with the default 2.0 Trinitron effect, the screen shrinks compared to what I have edited the video mode to be, so hopefully adding support for these modes will still allow a user like me to stretch the image to maximize the screen usage if they want (but I must admit, I didn't see any scanlines in the Trinitron mode... perhaps the effect is too tiny).
Trinitron mode does indeed have scanlines. It forces integer scaling, hence the smaller picture. I believe the Integer+ mode will come closer to filling the screen.
Yes! I noticed it too. Thank you Adam
On Sun, Jan 7, 2024 at 10:09 AM Adam Gastineau @.***> wrote:
Trinitron mode does indeed have scanlines. It forces integer scaling, hence the smaller picture. I believe the Integer+ mode will come closer to filling the screen.
— Reply to this email directly, view it on GitHub https://github.com/agg23/openfpga-NES/issues/39#issuecomment-1880085471, or unsubscribe https://github.com/notifications/unsubscribe-auth/ATCX6QBMW6G3T2LUUJW2GSLYNK3ELAVCNFSM6AAAAAA7STJQZ6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQOBQGA4DKNBXGE . You are receiving this because you are subscribed to this thread.Message ID: @.***>
Ask a question
The "native" cores have various wonderful video effects, but I don't think this core has any?
Even changing pixel format, resolution and coverage has to be done via a .json file currently...
What are the chances things could be done in this area, like: