-
Notifications
You must be signed in to change notification settings - Fork 24
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
Performance? #12
Comments
Hi, first of all thanks for compiling and running fhDOOM on your Linux/Intel system. It's been a while since i tested fhDOOM with Intel drivers, so i am glad it runs at all :) The next release focuses on several new features and improved image qualtity. That comes at the cost of performance and the snapshot you compiled already has a lot of that. The good news is, there is still alot of room for optimizations. As soon as i finish the next release, i will focus on performance again. The are a few things i want to try out for shadow maps (because that is the bottleneck on typical Windows/AMD/nVidia systems), but i also have ideas to optimize geomatry handling, draw calls, shader updates and load times. |
That's good to know. Maybe a 64bit version could help? :) I'm excited about the potential future of fhDOOM. I have been working on a mod for a while now, but it's progressing slowly due to the lack of available quality documentation. The idea is to do for Doom 3 what Brutal Doom did for Doom, if you get my drift - and I'd be happy to target fhDOOM if I know it is actively and enthusiastically maintained :) |
Hi there,
I suppose this isn't really an issue, but wanted to ask regardless.
Your latest push fixed my compilation problem, I can now compile and run fhDOOM (thanks)
However performance is rather bad on my machine, I've disabled things such as soft shadows which definitely helps but it's still nowhere near as fast as dhewm3 on my machine (x64 Kubuntu, running on an i5 with Haswell chipset, Intel HD4600 gpu, 8Gb ram), less than half the framerate :/
Are there other fhDOOM-specific settings I need to mess with? If not, is there room for optimization?
Thanks once again for your hard work
The text was updated successfully, but these errors were encountered: