Daniel Gibson
Daniel Gibson
Why do you think that would be better? I thought it would be best to let mappers specify that so the user doesn't have to change a cvar between playing...
Yeah, I think the trick is to set com_fixedTic back to 0 :-P At what refreshrate did you play? https://github.com/dhewm/dhewm3/issues/248#issuecomment-530482578 also mentions problems (flickering particles; maybe the same as yours?)...
I can't reproduce this, do you have godmode on or something like that?
Can you try if this by any chance is fixed with the new Carmacks Reverse code? I'm not super optimistic about it, but it's worth a try..
Yeah.. thanks for trying though!
Ok, just to write *something* here: ;) The problem is, this kind of change is dangerous - you never know if that 60Hz assumption is hardcoded somewhere without using that...
can't you run your display at 120hz somehow? like, configure the refreshrate in windows or the GPU driver to 120hz?
Yeah, multiple cores were not a thing in desktop PCs in 2004, so it's very single-threaded. (Some servers or workstations had multiple sockets for multiple CPUs, but that wasn't relevant...
why do you think it's 62.5, the constant (`USERCMD_HZ`) is `60`? EDIT: oh, is it because `1000/60 == 16` (in integers) and `1000/62.5 == 16` as well, even without any...
it's a constant so there is no difference in performance in the divide itself; I don't know why they're using int and not float there. Note that this is another...