A couple of issues with DirectQ

[Ezerhordren]

Sup guys, I don't know you, but i've had the weirdest bugs with version 1.8.8

First, some places seems to go black for no reason, like sometimes are walls, ther doors, other is health or ammunition packs, etc... there is a black bit instead of a texture.
Also, i have a weird mouse lag, let's say I move the mouse 5 times, 3 moves in real time and the last 2, are done very slowly, and I can't do anything to move, shoot or whatever... every now and then, the mouse goes slowmotion and I die,cuz I can't move.
I tried using different mouses (different brands) also tried the same mouse on other pcs and/or games and no problems at all...

what can be happening?

[Spike]

somewhere in your windows/driver settings there should be an option for the maximum number of 'prerendered' frames. reduce that number and it should reduce 'input' lag.

walls spontaneously going black is something you'll have to get mh to fix - chances are, d3d is randomly deleting textures.
I take it you're using winxp or earlier?

[Ezerhordren]

woah, you guys know your stuff! And yeah, windowsXP SP3.. I'll try your advice, and Ill tell you how was it!
Thanks for the help tho

[MH]

First, some places seems to go black for no reason, like sometimes are walls, ther doors, other is health or ammunition packs, etc... there is a black bit instead of a texture.

Are these textures ones which would normally have fullbright colours on them? Like say the arrows pointing to the e1 hall in the start map, or the red lights on a slipgate?

If so (or even if they're not) I'd be interesting in knowing what your video hardware is. Might be a driver bug, might be a DirectX bug, might be your hardware is old and dying, you might be overclocking, might be any one of a number of causes.

Also, i have a weird mouse lag, let's say I move the mouse 5 times, 3 moves in real time and the last 2, are done very slowly, and I can't do anything to move, shoot or whatever... every now and then, the mouse goes slowmotion and I die,cuz I can't move.
I tried using different mouses (different brands) also tried the same mouse on other pcs and/or games and no problems at all...

what can be happening?

I've identified a possible cause to this and it should hopefully be fixed in the next one (real soon).

[Ezerhordren]

Are these textures ones which would normally have fullbright colours on them? Like say the arrows pointing to the e1 hall in the start map, or the red lights on a slipgate?

If so (or even if they're not) I'd be interesting in knowing what your video hardware is. Might be a driver bug, might be a DirectX bug, might be your hardware is old and dying, you might be overclocking, might be any one of a number of causes.



I've identified a possible cause to this and it should hopefully be fixed in the next one (real soon).

Sup MH. Sorry to be a pain in the ass, but this is the first time I found these kind of bugs in DQ. My hardware? well I've tried this version (including the betas) in 2 different hardware conf. the first is old and dying it's an intel 945G I think (I recall a conversation we have long time ago and you toldme DQ was being developed in that hardware?) I have the latest drivers, the latest visualc++ and directx upgrades (Im a game freak, Im always upgrading my shit). But I've also tried it in a newer hardware, I have a gygabyte m.board h55 with a core i5-650 and a nvidia GT240 1gb ddr3... and it has the same problem! missing textures and mouse lag. also the weird thing is, this happen only in original textures, because Im using quake reforge textures (ONLY IN BAD GUYS) and this NEVER happen on those textures. Im also using the same directx version in both machines(Directx 9.0c jun2010). and I have all the visualC++ runtime libraries. 2008 and 2010 x86 and x64 (I have winxp 32bit on my laptop and windows 7 x64 in my desktop) and still the same problem.


also, this only happen (at least so far) when I shoot a grenade to someone, or I get shot with a grenade.. the explosion effect triggers this bug. whenever i hit something or ogres hit me. Sometimes it goes to normal when I hit someone or someone hits me back... and then it happens again but different textures are missing, sometimes walls, doors, (never floor) or light casted on some textures (like the light is missing and is just a flat black "shadow"). It's really weird... how can I take screenshots to show you what happen? it would be easier that way for you to see what Im talking about I think


thanks for the time!!

[MH]

F12 should normally take a screenshot, same as any other Quake engine. You'll find them in "screenshots" under ID1.

The 945 is actually quite alright, I run fairly regularly on one so I can be certain that it remains supported. I also run regularly on an NVIDIA very similar to yours. I generally only ever use the original textures too, so I'm really puzzled at what could be causing it. Some screenshots would be great I think.

[Ezerhordren]

http://i199.photobucket.com/albums/a.../Quake0013.png
http://i199.photobucket.com/albums/a.../Quake0012.png
http://i199.photobucket.com/albums/a.../Quake0011.png
http://i199.photobucket.com/albums/a.../Quake0010.png
http://i199.photobucket.com/albums/a.../Quake0009.png
http://i199.photobucket.com/albums/a.../Quake0007.png
http://i199.photobucket.com/albums/a.../Quake0014.png

well, i think I left a very important detail behind... these bugs happen only on 1.8.8(and betas)did a complete run trough episode 1, on DQ 1.8.7 from e1m1 to chton.. not a single bug.

[Spike]

#9 is a puzzler.
#13 and #14 are generally both black anyway.
if you use r_dynamic 1;gl_flashblend 0 (not sure on the directq cvar names, those are for glquake) and you shot a shotgun next to those walls or a rocket at them, do they suddenly light up properly, or do they stay dark?

[Ezerhordren]

#9 is a puzzler.
#13 and #14 are generally both black anyway.
if you use r_dynamic 1;gl_flashblend 0 (not sure on the directq cvar names, those are for glquake) and you shot a shotgun next to those walls or a rocket at them, do they suddenly light up properly, or do they stay dark?

Yeah, when I shoot a rocket or a grenade explodes nearby, yeah they lit again, and then other places goes dark... and so on. Should I post how is my DQ configured? as in, copy/paste the directq.cfg ? or take a snapshot at the config menu inside directq??

[MH]

It's looking like bad LIT files to me actually. Try moving your LIT files off to another location temporarily and see if you get the same result or if things suddenly go right.

[Ezerhordren]

It's looking like bad LIT files to me actually. Try moving your LIT files off to another location temporarily and see if you get the same result or if things suddenly go right.

I only had litfiles for episode 1 maps, i send them to the recycle.bin and the problem was gone!! (altough the levels looks a little less flashy). But then on episode 2 wizard's manse, the problem returned out of nowhere. I checked the map folder again, and no, no lit file. At all! (also, im not playing 1.8.7 when I deleted the files switched to 1.8.8 test 2)
So I don't know what the hell it's goin on. Because even with the litfiles, 1.8.7 had no bug.

[MH]

Curioser and curioser. I found the cause of the mouse bug by the way and just fixed it earlier today. I'd like to try find the cause of this one too before I release an update.

[R00k]

I only had litfiles for episode 1 maps, i send them to the recycle.bin and the problem was gone!! (altough the levels looks a little less flashy). But then on episode 2 wizard's manse, the problem returned out of nowhere. I checked the map folder again, and no, no lit file. At all! (also, im not playing 1.8.7 when I deleted the files switched to 1.8.8 test 2)
So I don't know what the hell it's goin on. Because even with the litfiles, 1.8.7 had no bug.

Maybe start with a duplicate test install oh quake with /id1/pak0.pak and pak1.pak just install DirectQ fresh then test. If nothing, add your directq.cfg file in, then add paks bak in until you get the bug again. U may even have some .lit files in a pk3 or something you missed.