DirectInput

[Shambloid]

Quick question, I buckled down and got a new mouse (Razer deathadder) and was wondering what the use of the DirectInput command in Proquake was. It seems to me that it causes it to drops inputs, mostly when doing multiple inputs like for an rj, with the combination of looking down quickly and pressing shoot and jump simultaneously. Anyone else have these kind of experiences or know the advantage of using directinput??

[Baker]

I use DirectInput because Windows uses your screen aspect ratio to "taint" the mouse. If you are using, say, 1280x1024 resolution, this is a 4:3 aspect ratio which Windows corrects the mouse input. But that makes it so moving the aim up/down is different than left/right.

Try typing m_rate 125 in the console and see if that helps with the dropped inputs problem. Let me know, I am interested in this.

Phenom has mentioned your observations and does not appear to have them with Qrack, and Qrack uses a default of 125 I believe.

/Note: I need to make m_rate save to config in ProQuake. If this helps, you will need to type m_rate 125 in the console every time you start Quake since it doesn't save. I will have a new release where it saves by the morning.

[Shambloid]

Thanks for the help, and yeah, I quickly tried out qrack (with the -dinput command) and it works fine, the multiple inputs that is. But for proquake, the m_rate command is not recognized for some reason (on 3.5 and 3.95). Is it some other command??

[Baker]

I noticed that m_rate isn't actually available when using the client.

It's in the source, it just isn't exposed to the user. So ... I have 2 things to do. I'll make m_rate so it works in the console.

I'm glad you aren't having the problem in Qrack. I'll see if I can determine the reason Qrack behaves nicely with that and ProQuake doesn't.

Check back tomorrow and I'll have a new version of ProQuake with the changes. Then let me know if this resolves your problem.

[Shambloid]

Alright, will do. Thanks alot Baker.

[Baker]

I was wrong about this.

You have to add -m_smooth to the command line for m_rate and m_showrate to have any impact.

I tried this out and I have to say using -m_smooth feels terrible to me, but that's just my opinion and some people like it.

If you want to try -m_smooth you can use the m_rate <#> (like 60 or 125).

[Shambloid]

Alright, when I get back to my comp I'll check that out. Curiously, does that mean in qrack -m_smooth is by default enabled, allowing me to use the m_rate option?? I'd rather not have mouse smoothing since that introduces lag, of which I would probably never notice, but I need my peace of mind

[Shambloid]

Ok, I tried out the -m_smooth command, and sure enough it worked, but my console kept spamming the message "serve wheel" (which is apparently the same problem Phenom had). I should note that I couldn't try out the m_rate command (not that it mattered) as the as the serve wheel message spamming wouldn't let me. I'm going to mess around with my mouse driver and see if I can get it to work properly.

[Shambloid]

Yeah, no dice, same thing after I unistalled the razer drivers (which apparently was recommended for the razer deathadder to fix something with the middle scrolling mouse button). I'll probably stick with qrack for now. Also, qrack seems to give me alot more viewing space on my widescreen monitor, proquake shows less overall screen than a 4:3 ratio for some reason, like it just cut off the top of a 4:3 to make it widescreen.

[Baker]

That serve wheel annoyance was fixed a while back.

Use ProQuake 3.99h (download) instead of ProQuake 3.95.

There have been numerous little update releases since 3.95 and will continue to be until 4.00 is reached (4.00 = no known bugs with every feature/improvement on a list I have are in it and a couple of weeks of testing + thorough documentation).

Yeah, no dice, same thing after I unistalled the razer drivers (which apparently was recommended for the razer deathadder to fix something with the middle scrolling mouse button). I'll probably stick with qrack for now. Also, qrack seems to give me alot more viewing space on my widescreen monitor, proquake shows less overall screen than a 4:3 ratio for some reason, like it just cut off the top of a 4:3 to make it widescreen.

If you use the same resolution AND the same refresh rate in both ProQuake and Qrack, the results should be identical. I think you are using a different refresh rate in Qrack than ProQuake ... just a guess.

If video code in ProQuake is almost a mirror image of Qrack's.

Type vid_describecurrentmode in the console and it shows videomode width, height, bits per pixel (aka color depth) and refresh rate. Of course, it also shows in the video modes screen.

/Just information for clarity

Again, thanks for all of this info. I will need to find out about m_smooth works and see if Qrack uses that by default.

[Shambloid]

Hey, I tried out the 3.99 and it works fine with the m_smooth. I don't know if this helps, but I found out the with directinput (and not using m_smooth) the game works just fine using a 125 hz usb polling rate (razer deathadder mouse). Bumping it up to 500 hz gives me some occasional skipping problems, and 1000 hz makes you miss all rocket jumps.

I'll check on the widscreen thing and get back to ya. Thanks