- Fixed bug where mouse cursor was visible when entering a map and not using DirectInput.
- Fixed bug where you would be pointing at the sky and wildly spinning when not using DirectInput.
- Fixed bug where key up events were not being sent for mouse buttons when not using DirectInput.
- Added vertex cache optimization for MDL files.
- Fixed lagged keyboard when DirectQ is not the active application.
- Fixed bug where MP3 music may occasionally loop after 1 or 2 seconds instead of playing the full track.
- Added capability to stream media container files from the internet.
- Fixed bug where a TGA texture may occasionally fail to load correctly (e.g. top skybox in 5 Rivers).
I haven't included a "Windows 98 build" this time, but I may add one at a later date if there is sufficient demand.
Some of the 1.8.4 work is included in this, but only a very very small part. I like giving these advance previews of what's to come, but I can't go too far with it as some of the underlying systems have changed quite radically and the code I've included here is already starting to diverge from the main 1.8.4 codebase.
6 comments:
Nice, the "lagged keyboard when DirectQ is not the active application"-thing was getting on my nerves ;)
Nice Release.
sound,music,input,all working great.
and performance is still superb.
Sound skipping is all but gone. Nice work.
..Hello! I've been busy preparing for the birth of our 1st son a few weeks ago. Tonight has been the 1st time I've really had to play with DirectQ since version 1.8.2. So far 1st impressions aren't great only for the fact that 1.8.3b & c crash seconds after running the executable. With out going to crazy I just removed the pk3's & anything other than some png, jpg, & tga texture, model, & hud replacements. Still crashed bad. I guess no one else has this issue or at least not informed you publicly. I'm running 1.8.2 just fine with Win7 32bit, Mobile Intel(R) 4 Series Express Chipset Family aka GMA 4500MHD with driver version 8.15.10.2082, yadda yadda yadda.. I thought it might be a content issue, but after putting it in a fresh dir with nothing but the exe's & the id1 folder with pak0 & pak1 v1.8.3b & v1.8.3c crashed as before, but 1.8.2 ran like a champ. I wonder what would have changed that much to make it crash like that. Hmmm...
Might be a D3D issue; there was a recent release that jumped to a new version of the SDK and it seems that it needs an update. I'll try get this resolved for the next one.
I do most DirectQ work on an identical setup to yours so that's the first place I'd look.
Congrats on the son, by the way! :)
..Thank you! He is awesome! Also thank you for the info. I will try grabbing the latest DX install in between feedings and diaper changes and see if it floats so to speak! ;-)
Post a Comment