The saved background image is blitted to the screen.
Then, the offset for the credits is incremented.
Proceed with 2. until a key is pressed
So there's three spots where the screen offset based on screen size has to be taken into account. I forgot one.
This is all fixed now, highscore list displays properly as well, and I have added a simple movie playback function cycling through all available game movies.
I have two different source code archives, one of which probably does not contain UDP/IP code.
I have been working on UDP/IP comm today, but not gotten far. Somehow I cannot bind a socket to an IP address.
Most of what I've seen in D2X coding style wise made my hair raise. Bloody amateurs who think they're cool because they can tinker around in some OpenGL code.
The menu function is several 1000 lines. The guy who has coded this must have never heard of functions, or function arguments, or reusable code.
Diedel wrote:The next thing I'd really love to implement is playing via direkt UDP/IP connection (i.e. the servers makes his IP address known to all clients who enter it in their multiplayer screen and thus can connect directly to the server over the inet w/o the help of KALI).
Well I hope you'll be able to implement that into D2x! That would be great! Be cool to setup a dedicated server to play on!
Good luck and I hope you can make that work.
Guess I shouldn't have used the word "dedicated". lol
All i ment was that on one PC I can start a game (non Kali) and from another join it. Plus give out IP for others to join. EDIT: *thinking to self.. whats the point in doing that?* Thats all I ment. Sorry Ferno and Diedel.
Just makes me think back when D3 first came and you could do the P2P IP games and my Brother-n-law was playing a lan game with friends. I knew his IP so I joined the game from my house. He was surprised when I showed up in the game!
Diedel.
Bug of some kind. D2x-w32 v1.10:
Tryed to go through an illusion/door and you can't now.
Test it urself and see if this happens to you?
Thanks.
What mouse do you use?
Mine is the Logitech Mx 700 cordless Optical Mouse and keyboard (Logitech® Cordless MX� Duo).
Just wondering if it has something to do with the optics or what? Either way. I've tryed over and over. Still won't set L/R.
Something I've noticed in the last few versions, the fusion cannon shots are almost transparent, and frequently are not even visible against a light texture background.
Also, do you have any listing of all the new d2x.ini file parameters and what they do? like "-minturnrate X" what is the number range and what does it do?
Thanks for all the fixes so far, 1.0.13 is playing nice!
Hummmm... I got v1.0.13 and the mouse movement is still not setting right. I still only get F/B to set. Can you please look into this? I have no idea why this is.... Lehm is having same prob. So I'm not the only one.
Just so you know. I have no other joysticks pluged in when trying to set mouse axis.
Thanks
I don't have this problem, so I cannot look into it. I just tried it again. I only need to move the mouse fast enough (not very fast, just not slo-mo).
Diedel.
I'm geussing that you don't play D2x in FULL screen do ya? If not try and set mouse axis in FULL screen mode. I play in FULL screen mode and when I unchecked FULL screen and set it to 800x600. I was able to set mouse axis F/B and L/R then. It seems to be only a prob when in FULL screen mode. So try that please and see if you get same prob in FULL screen mode.
Thanks
One thing that I liked about D1x was the ability to assign certain weapons to certain joystick keys. IE: lasers could be assigned to button 5, Vulcan could be assigned to button 6, etc.
the only think I could probably do was to bind a weapon toggle to a joystick key (like pressing a certain button will change the current weapon to lasers), but not have the weapon immediately fired - that would be a cheat.
the only think I could probably do was to bind a weapon toggle to a joystick key (like pressing a certain button will change the current weapon to lasers)
Ugh... redrawing bug is still present in some form. (1024x768 resolution if it helps any.)
Start up a level - any level, it doesn't matter. Then exit, and hit the 'New Game' option again. Scroll the list with the arrow keys, and things will become very difficult to see.
Midi support in newest build picks title song when disabled and re-enabled in game, instead of the level's MIDI file. (At least it does for custom MIDIs...)
In addition, I have a suspicion D2x doesn't handle object bitmaps properly.
Hi there, I was very very suprised about development of D2X-win32 in the year of 2005 - just AMAZING!
There is one great BUT - I'm standing in the queue with those who have problems with crackling and shattered sounds. I've tried many D2X builds and the sound is quite smooth in them (even when using same SDL library as d2x-win32 uses!).
HW: GeForce Ti4200 (this bug was reported also by someone with Radeon), Soundblaster Live 1024 (maybe??), chipset VIA KT266A. All drivers most recent (and working well in all game titles).
Try adding "-sound11k" or "-sound22k" (without quotes) in your D2x.ini. It can be found in the D2 directory. Only try them in one at a time, having both in the .ini file might cause conflicts.
See if that clears up the crackling. Make sure you have the latest D2x-w32 (v1.1.11) with the SDL provided in that. If you already have an existing D2x.ini file in your D2 dir do not overwrite it with the one provided in the zip file.
Tyranny: thanks for hints.
a) i have already fiddled with samplerate before - crackling is not cleaned up - it can be just somewhat "covered" in overall low-quality 11k but it's still there.
b) I'm always doing clean "unzip" to my old DOS D2 not to have anything mixed..
can you get more specific about "object bitmap rendering faults"?
Tyr,
though it acts the same from the outside, a midi device is technically different from a redbook audio device (even if the device is just a piece of software).
I got the code from icculus.org and didn't write it myself, but I've understood it good enough. I have played around with that code for hours yesterday and queried the availability of midi device volume control on my computer (Audigy 2, not the worst sound hardware I'd say), and there wasn't volume control.
You can however always turn midi sound completely off and on in the sound menu when chosing the lowest volume or a higher one.
I really cannot tell why sound is so bad on certain systems. I have never experienced problems. There is some slight static during sound playback (esp. explosions), but it is only noticeable when I pay attention to it. As far as I can tell I am using the same sound code the "official" d2x project does (arch\sdl\digi.c), so I am clueless about what's going on (wrong) here. I will pursue this matter and maybe find something out. I have asked Bradley Bell to help me with this, but gotten no reply so far.
I have heard many things about the coding style of the Descent X programmers, most of them not good.
