I've just released the first release candidate of dhewm3 1.4.0, a sourceport of the "old" (non-BFG) Doom3: https://github.com/dhewm/dhewm3/releases/tag/1.4.0_RC1UPDATE:1.4.0 is out, see https://github.com/dhewm/dhewm3/releases/tag/1.4.0UPDATE2:1.4.1 Release Candidate is out, see https://github.com/dhewm/dhewm3/releases/tag/1.4.1_RC1 - please test!I provide Windows binaries there, if you're using Linux or OSX you have to compile yourself, but that shouldn't be very hard either.
Some features of dhewm3 vs the original code:
- 64bit port
- OpenAL for audio output, all OS specific audio backends are gone
- OpenAL EFX for EAX reverb effects (read: EAX on all platforms)
- Better support for widescreen (and arbitrary display resolutions), more resolutions can be configured in the menu
- The mouse isn't too fast in menus at resolutions > 640x480
- The console can be opened with Shift-Escape, regardless of your keyboard layout
- SDL for cross platform low level OS support, OpenGL and input handling
- A portable build system based on CMake
- (Cross-)compilation with mingw-w64
- Lots of other bugfixes I forgot
If you test it I'd be glad about feedback (both problems and "I use operating system $XY and it works!") :)
So far it has been tested mainly on Linux, and I did a bit of testing in Windows XP and Win7 - so I'd be especially interested in Win8 and Win10.
OS X would also be interesting.
Thanks a lot!
Tested on Windows 10, missing LIBEAY32.dll and SSLEAY32.dll :(
hmm seems to have something to do with openssl, probably used by the bundled libcurl
I uploaded a new .zip with a libcurl that doesn't use openssl, can you try again? :)
That worked. I played through a new game a little bit, very cool being able to use EAX reverb, last time I was able to play the game with that was when I first got it and had an Audigy 2. So, yea, everything seemed to work fine now, or at least during my brief little playthrough.
Great, thanks!
Tested on Windows 7 64-bit Ultimate SP 1. Great to hear EAX reverb in the game for the first time. It's not perfect but some scenes sound pretty neat with it. Good work!
I did come across this error though when fighting the cyberdemon.
(http://i.imgur.com/BUWhWSP.png)
Hmm interesting. Was this with the binaries I provided or did you compile yourself? If so, what compiler, did you create 32bit or 64bit binaries, ...?
(I did a Release build so I'm surprised there's an Assertion)
Anyway, this looks like a Bug, I'll try to reproduce it, thanks!
Nope I didn't compile the source, just using the binaries that came with RC1.
Finally :) Congrats on the release !
By chance, do you have Windows and MSVC, caedes ?
Yes I do have Windows and MSVC (even though I do almost everyting on Linux with Eclipse).
The binaries I released were built with MSVC2010 Express.
So far I haven't been able to trigger the assertion (despite beating the Cyberdemon several times), did you do anything "special", Phrozo? Does it always happen for you?
What happens right before the assertion crashes the game? (Like, does it happen when you're hit by a cyberdemon rocket or when you kill an imp - with what weapon? - or ...?)
Furthermore: What CPU do you have in your PC? Also, when starting the game, can you go into the console and scroll up to the beginning of the messages?
It should say something like
32112 MB System Memory
found interface lo - loopback
found interface eth0 - 192.168.0.101/255.255.255.0
doom using MMX & SSE & SSE2 for SIMD processing
enabling Flush-To-Zero mode
or similar - how exactly does the "doom using MMX & SSE & SSE2 for SIMD processing" look for you?
@caedes: e-mailed you something
Hey Caedes,
Running Win 8.
I installed it into my patched doom 3 install folder (not steam) and I got this warning in the console:
WARNING: unknown event 770
Apart from that, just tested a little survival map I'm working on, everything worked great. Thank you for this.
Does this have the fix for Microstutter?
Edit: This doesn't seem to have any Microstutters at all!
Quote from: caedes on October 04, 2015, 02:30:32 PMSo far I haven't been able to trigger the assertion (despite beating the Cyberdemon several times), did you do anything "special", Phrozo? Does it always happen for you?
What happens right before the assertion crashes the game? (Like, does it happen when you're hit by a cyberdemon rocket or when you kill an imp - with what weapon? - or ...?)
Furthermore: What CPU do you have in your PC? Also, when starting the game, can you go into the console and scroll up to the beginning of the messages?
My CPU is an Intel Quad Core i5 750.
Here is from stdout:
dhewm 3 1.4.0 RC1.1304 windows-x86 Oct 3 2015 19:18:01 using SDL v2.0.4
4096 MB System Memory
Winsock Initialized
Found interface: {BCB5F415-40A5-4B00-907B-06861BDE4C2A} Realtek PCIe GBE Family Controller - 72.175.114.228/255.255.252.0
Sys_InitNetworking: adding loopback interface
doom using MMX & SSE & SSE2 & SSE3 for SIMD processing
enabling Flush-To-Zero mode
enabling Denormals-Are-Zero modeBut I sometimes get this in console:
WARNING: alEffectf(AL_EAXREVERB_LATE_REVERB_DELAY, 0.100) failed: 0xa003I had some cheats on when the event happened but nothing out of the ordinary. I haven't been able to reproduce it as well.
When I boot up the game (unzipped the dhwem to it's own folder & copied just the pak00* files over) I get "WARNING: unknown event 770" in the console. I thought it might be because it has EAX enabled by default & I don't have a card that supports it. I disabled EAX/surround sound & exited/reloaded game, still happens.
So far, besides that, loads up a new game ok. Win 10-64 bit, AMD Phenom 8350, AMD 7850 GPU.
Quote from: Phrozo on October 05, 2015, 12:27:10 AM
I had some cheats on when the event happened but nothing out of the ordinary. I haven't been able to reproduce it as well.
Hmm I guess I'll just ignore that bug for now.. I'll keep the issue on our bugtracker open (https://github.com/dhewm/dhewm3/issues/122) but until someone finds out how to reproduce it there's nothing I can do about it :-/
Again, thanks to everyone for testing!
the "WARNING: unknown event 770" message can be safely ignored. it's just an event SDL2 sends when a window gains focus (is created/comes back vom background) that dhewm3 doesn't handle.
I'll supress it in the release version.
1.4.0 is out, thanks to everyone for testing!
https://github.com/dhewm/dhewm3/releases/tag/1.4.0
Quote from: caedes on October 09, 2015, 11:39:14 AM
1.4.0 is out, thanks to everyone for testing!
https://github.com/dhewm/dhewm3/releases/tag/1.4.0
Congrats!!!!
Hi, Thanks for your work on this project. I was giving up hope on play Doom 3 decently on mac. I´ve just learned of it and compiled it right away.
My specs are:
Mac Book pro 13'' late 2011 8GB ram OSX: 10.11.2 (El capitan)
In the readme says that I need to point to the soft Libs of OpenAL before compiling on OSX but in my case it was not necessary. I´ve installed all the dependencies using mac ports, including the soft version of OpenAl and then just compiled it with no issues.
So far the game is running flawlessly on my mac (although I´m just starting the game). I´ll gladly test the mac version and report back on the git hub page.
I have a question: Is controller support planned in the future?
Thank you very much
Thanks for testing, marcosot, I'm glad it works great on Mac, too :-)
I currently have no plans for controller support, but I'd accept pull requests/patches, of course.
I just released 1.4.1 Release Candidate 1: https://github.com/dhewm/dhewm3/releases/tag/1.4.1_RC1
It's only small fixes/improvements, but please test anyway!
- Fixed some rare crashes due to assertion errors (hopefully) including the one reported by Phrozo
- AZERTY Keyboards, as used in France and Belgium, should now work (the row of keys with 1...9, 0 is now usable)
- A crash (at least on FreeBSD) when loading Resurrection of Evil's last level is fixed
- Compatibility with Microsoft Visual Studio 2015
- Video resolutions in menu now sorted, added 2880x1800
- Support for up to 8 mouse buttons (on Linux this needs the not-yet-released SDL2 2.0.4 or recent code from their hg repo)
Thanks in advance for testing! :D