-
Notifications
You must be signed in to change notification settings - Fork 32
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
AMD software support #851
Comments
I already used AMD with this before, also I don’t know how to add support for FidelityFX since I’ve never used it before, also it uses OpenGL, and FidelityFX doesn’t natively support OpenGL, meaning you’d have to use an fork that does add the support for it hey what happens if we talk in this exact comment -Lunar |
yea |
yeah I’m not gonna bother adding support for this (too ambitious and I’m lazy) |
also I love the new design with Issues and the new additions, you can now close as duplicates or create sub issues :0 |
THEY FINALLY ADDED CLOSE AS DUPLICATE????? |
wait |
oh ok you can close as not planned OR duplicate |
yeah, the duplicate one is new |
@SyncGit12 this isn't happening btw, Lime uses SDL 2 (soon SDL 3 if that ever happens), which is built on OpenGL, which OpenFL relies on, and FidelityFX has no support for OpenGL, plus I'd have to port the shaders over from FidelityFX. In short, it's not practical, and it'd take a lot of time that I don't wanna bother spending for something that wasn't made for this game |
what i meant like upscale the resolution and all that not fucking rtx |
oh, then that might be more feasible, but I’d still need the shaders (since it uses shaders to upscale it) so it could take a while |
What feature do you want to get added on the base engine?
AMD software support for JS Engine so it can use FidelityFX
tho this might be not possible
To test your sight, and reliability, please select the option of what should NOT be requested.
Proper credit that was forgotten
The text was updated successfully, but these errors were encountered: