you will never achieve the exact same feeling in both games

Not really sure, for me it is the same.

in q3 i can easier turn around by one abrupt(or fast) movement.

yes )

Which mod were you using; osp or cpma?

osp

Ah :)

I understand exactly what you are referring to now. I found my osp mouse settings did not cross over at all; am completely different feel.

I would suggest just trying to find a new equivalent that feels similar; it will involve a lower sensitivity and accel most likely.

I do have one tip that you could try.

Input your osp mouse settings into ql.

Then, slowly raise m_filter by 0.1 increments until you find it feeling as close to your old settings as possible.

My (with no proof) theory is; OSP for w/e reason(s) has quite a bit of either input lag or input filtering/smoothing. Have never played baseq3, but cpma, ql and q4 all have very similar mouse "feel". As such, I think it's an osp thing.

I have no real basis for this claim (would love to hear from someone who is in the know about this), yet this seems to make sense to me at least. I tried my old osp settings in ql, and increased the m_filter in increments and did find that it made it feel rather close/similar to as osp, but still not quite right :(

Regardless, good luck with your settings conundrum :(

I have no real basis for this claim

/bangs head on table... maybe stfu then until you do?

Rofl.

I was honest. You are getting angry at me for attempting to explain the difference in input feel from prior experience to try and help another user?

Why? There is no bad intent on my end; why are you irritated about something trivial like this?

without giving any proof, what you wrote might be you imagining things and then it's pretty bad advice, wouldn't you say?

try to have atleast some basis for your claims when replying to someone searching for help.

eg.:
1) to quote lorfa:
[i]m_filter 1 turns on mouse interpolation which adds extra frames in between your mouse movements resulting in a smoother feel/appearance.

The original purpose was designed for ps2/serial mice that used 40 hz, in which case m_filter 1 was _much_ smoother than m_filter 0. It has been kept all this time even nowadays when we have 500-1000 hz usb polling rate. Even so it still produces a noticeable difference in feel that some people like.

The range of values actually goes from 0 to 33.[i]

tl;dr you can not "lowly raise m_filter by 0.1 increments".

2) "OSP for w/e reason(s) has quite a bit of either input lag or input filtering/smoothing."
you are talking out of your ass so hard i can't even disprove your bs :)

More than anything, it's the fact that you feel the need to be patronising that is irritating.

I'm well aware in how to document my findings and build a case for a certain argument referencing materials, articles and other resources to back up my claim. I did plenty of this during my university days.

I jotted out a quick post containing my thoughts on the matter, and how they could help the op. I have no intention to reference on esr, nor ever will, for your benefit.

You are correct; I could have bothered to find basis for w/e claims I intend to make. I don't want to nor feel the need to; whoever reads it can extrapolate what they want from it.

The op may find something useful, maybe not.

You found something to correct, and got right onto it.

It's your choice to critique in that manner. I consider it being anal about something trivial on an internet forum.

tl;dr I'm not going to reference everything I claim on esr. deal with it.

Thanks a lot for your answer, m_filter not help:(
Even i try cl_mouseaccel it's different.

QL has standard com_hunkmegs "96"

where quake3 has "56"

that alone makes much difference for me.

other than that, you should go to the map you play most and move around..aim around..this way you can tell if you need things slower/faster. for me it works.

when i came from q3 to ql..i lowered my FOV and set my accel/sens lower.

com_hunkmegs specifies the amount of RAM quake is allowed to allocate (and reserve) for itself, with min/max being 56/192. it has zero to do with mouse input.

sens shouldn't be different inbetween q3/ql, but coming from osp the op will experience fps independent physics in quakelive which might be the culprit. other than that ql properly supports widescreen now and something about in_mouse -1/1 changed, afaik.

if i were the threadstarter i'd start from scratch with in_mouse 2 (raw input) and m_cpi 800.

if you didn´t notice thus far that com_hunkmegs has a big impact on mousefeel and most likely it can even be quantified. i´d put it like this.

com_hunkmegs -> higher value makes for smoother feel and accel feels stronger.

just be quiet and stop your raging. if you don´t feel it..not my trouble.

i try to make same com_hunkmegs.
in q3 i have 50
in ql 96
so i type in ql com_hunkmegs 50 and con write me:
com_hunkmegs "128" default "96"
latched "50" need restart
i try in_restart net_restart vid_restart and nothing change about mouse:(
but big thanks to you for help

in_restart

also, this is the first thing that comes up in google searching "quake live in_restart"
http://www.esreality.com/post/2145444/in-restart-com-hunkmegs/

thats my thread. funny that it has no real use for someone who cares about in_restart at that moment ..most likely.

vid_restart works for me. it might still say latched.

i have to say that maybe for new mice it might not do as much or whatever. i have old stuff and can feel a big difference from this

otherwise change it in the config of course.

com_hunkmegs can only be changed in QL from 128 to 96 with a trick.

Other than that it is stuck at 128 and cannot be changed. It will only latch. You can verify that it has not changed to the latched value by watching its memory usage in the task manager.

The trick is to use cvar_restart, which will actually change hunkmegs from 128 to 96.

As far as I know it has no effect on mouse input, and there is no reason that it should.

magic

use in_mouse -1, should be the same then if you dont use accel, accel is "fixed" so not the same feeling in ql, for some reason i believe m_filter is very different too, as it now takes intergers and not just boolean.

edit: plus sens could be the same but feeling still off as movement is very different too

i try use in_mouse -1 it's too fast.anyway thanks:)

Just measure 360/cm and ajust sens in ql to achieve the same result. You might want to lower your fov a bit, 110 doesnt feel the same in ql.

You can maintain in_mouse 1 by putting 'seta sensitivity' and 'seta in_mousemode directInput' to your config and make qzconfig read only in order to prevent overwriting (which ql loves to do).

this, easy peasy with no accel

This, sort of.

A nice feature to measure cm/360 is viewpos.

With it it will tell you your orientation in degrees, so you can make a 360 degree turn and compare the values.

Since he doesn't use accel this is a good approach.

in_mouseMode is just a verbose output of in_mouse. It is read-only, and even so changing it wouldn't do anything.

in_mouse 1 should stick on if no autoexec is present. If an autoexec is present, a \writeconfig autoexec is required for it to stay.

Changes to in_mouse during live sessions will require an in_restart to take effect.

If the settings you have in q3/ql are the same then sens should also be. However, the fov might be different if you're not using a regular 4:3 resolution ratio.

In that case: http://kyto.dez.fi/ql/fovcalc/index.php

Try cg_zoomsensitivity 1 and 0.

As far as I'm aware, setting it to 0 reverts back to the old q3 method, and 1 uses a corrected method which actually uses the cg_fov setting (q3 variant used a fix fov of around 91 iirc).

That would only apply when zooming, but yes zoomsens 0 uses the q3 zoom algorithm.

I only mentioned it as I had a quick scroll through his config files, and there were scripts there for a +zoom based config present.

Ofc, you are idd correct :)

Yeah it was worth mentioning good catch :-)

It's just that some people believe that zoomsens affects the normal sens when not-zooming. These people scare me :-)

The kinzu has a sensor problem; it has inbuilt positive acceleration.

Also, it will by default poll on its usb port at 500hz/1000hz.

Both factors will make quite a large difference if you were using a different/older mouse with q3.

Try to use in_mouse 1 in QL, as in_mouse 2 has a slightly different feel.

Just in_mouse 1 ; in_restart

It should stay like this unless you have an autoexec, in which case you will have to do \writeconfig autoexec for it to stay.

As for the other settings they all look the same, including the display refresh, although I would try to check this manually with your displays osd if possible.

I noticed that you have a different r_mode in the q3 osp config than you do in the QL config. Certainly a different resolution would _feel_ differently, but also there's a possibility that the display refresh differs between them.

Other than try to do what was said earlier in this thread, measure the cm/360. If it's off let us know by how much.

Assuming no other influences, sens 7.5, m_yaw 0.016 at 800 cpi should be 9.525 cm/360.