-
Notifications
You must be signed in to change notification settings - Fork 396
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
port Chocolate Doom #4149
Comments
Chocolate with a backup using Crispy? |
The "limit-removing enhanced-resolution" part scared me in Crispy. |
My old list had PrBoom+, which is now inactive. Though I'm guessing the choice of Chocolate Doom is because it doesn't have many enhancements, whereas PrBoom+ does. |
Not only does prboom+ have insane amount of enhancements that nobody wants to adapt to our needs, it also has insane amount of dependencies that have to be ripped out. Dunno if libretro already simplified it tho. |
Honestly dsda-doom is probably a better replacement over PrBoom+. |
The only theoretical benefit of prboom is that they already made it build as a headless shared lib. Dunno how hard it'd be to turn chocolate or that dsda thing into that. Maybe not too painful, we just need to look how libretro grabs the data from the core, how it sends back inputs, and how it advances frames. May appear to be kinda universal across all ports. I feel whatever is the closest to vanilla, would be the easiest to support due to lack of feature creep. |
https://github.com/chocolate-doom/chocolate-doom
The most accurate of the source ports.
Can't tell if it even has threads, but it seems to need to be detached from frontend and turned headless.
The text was updated successfully, but these errors were encountered: