proquake (or qrack): multiple network interfaces + qrp

[killingtime187]

hi all -

1. i have a machine with multiple network interfaces (no, i can't disable the others as they're active while i game ). the problem is that the only client that seems to connect through this setup is dp. proquake/qrack says detected multiple interfaces, tries to connect throught the "wrong" one and, of course, fails to connect.

2. this might be a qrack bug, but if i turn on "enhance pointer precision" in windows, run qrack, then exit, the option is turned off again

3. is there a way to use qrp or map textures + r_novis 1 with qrack/proquake ?

right now, the only client that works is dp, but there is one major problem with this client -- my ping doubles (or appears to) vs regular glquake. also, my framerate is all over the place -- mostly high, but sometimes drops to 10! for some unknown reason.

[Mindf!3ldzX]

1)Create a short cut to your quake client (right click it,send to desktop (create shortcut!) FOK,ok it should look like this.



<- TY =PEG=

you need to specifiy which ip to bind to,with -ip 1.1.1.1

ProQuake.exe -ip 1.1.1.1
glQrack.exe -ip 1.1.1.1

2)I used to have to open Qrack, when it opens, I would ALT-TAB out of Qrack,and alt-tab BACK into quake. This is hardly a fix,but it does work, and I used to have to do this EVERYTIME I loaded Qrack.

I still to this day alt-tab my quake client when I first load it, because of relentless problems with Vsync. The alt-tab fixes the issue without over complicating the situation, and I get to Quake that much quicker hah





3)r_novis 1 usage is tied into wanting pretty water in DP? Rook recommends not using r_novis 1,because

r_novis 1 = client draws everything on map,even the shit you(it) cant see.
r_novis 0 = client only draws what the client can see (this is best)

[R00k]

hi all -

1. i have a machine with multiple network interfaces (no, i can't disable the others as they're active while i game ). the problem is that the only client that seems to connect through this setup is dp. proquake/qrack says detected multiple interfaces, tries to connect throught the "wrong" one and, of course, fails to connect.

Are you trying to connect to another server out of your network? Have you tried using the -ip commandline parameter?

2. this might be a qrack bug, but if i turn on "enhance pointer precision" in windows, run qrack, then exit, the option is turned off again

Mouse acceleration is forced off in Qrack, I can create a cvar to enable it.
99.9% of players hate mouse acceleration, and it was getting enabled automatically in windows 7.

3. is there a way to use qrp or map textures + r_novis 1 with qrack/proquake ?

Download the textures here : :: Quake Revitalization Project ::
rename the pk3 file to .zip then copy out the contents to your /quake/id1/
folder this will not work with proquake as it doesnt support external textures.

[killingtime187]

rooook! ... finally talking to you in the forum

yea, trying to connect "out" from behind a nat'd network -- i.e. some internal ip of 192.168.x.x (actually several as i have several interfaces). i will try -ip <ip of interface to inet>, the only issue is that this iface is dhcp and i will have to keep changing the value every time i get a new address.

as for mouse acceleration, well, i've always played with it given that i've always had that option on in windows -- just weird exiting back into windows and my mouse movements are all over the place. lemme have that cvar

the textures ... just extract to id1 or to id1/textures ? also, i like the "see-through" water what's your recommendation here ?

[R00k]

In the pk3 file (renamed to .zip) ther should be a textures folder, just copy that to id1 and it will merge the contents.

[killingtime187]

rook:

installed textures but cannot see super shotgun model. any idea which texture/tga files this is ? i exploded the following into id1\textures:

QRP_item_textures_v.0.73_dp.pk3
QRP_map_textures_v.1.00.pk3
QRP_normalmap_textures_add-on_v.1.00.pk3

[Spike]

programming fix for issue 1.

file net_wins.c, function WINS_OpenSocket:
address.sin_addr.s_addr = myAddr;
becomes:
address.sin_addr.s_addr = INADDR_ANY;

yay! now you can connect to localhost! yay! now the operating system can route packets over interfaces other than the default interface. any ip addresses that it reports will still be the default interface and still be affected by -ip.
R00k/Baker, If you don't change this, you'll never be able to host/connect to ips other than via a single interface. While I accept that a server might want to listen only on a single interface to make it a private game, it must also be expected that this will be rarer than having to use -ip because you're unable to connect to servers on the other interface.
I've stated this before on this forum, so I apologise if it has already been fixed.
This fix won't fix hosting a game on multiple interfaces as a server will report a potentially unroutable IP to the non-default interface - you *can* fix that with routing tables in linux, and its never going to be a problem if you're connecting to either 127.0.0.1 or any hostnames for the local machine - you'd need to fix the network protocol for that, but that's the only thing that would actually need a protocol change. So fix this already!

-ip with dhcp sucks.

[killingtime187]

interesting spike, so long as the client doesn't waste cycles sending the udp packets over "every" interface ideally, it would be great if you can tell it to use a specific network interface rather than it being ip based (as you said, dhcp + that = sux).

in followup to the super shotgun issue on the latest qrack. attached is a screenshot from me on dm.quaketx.com right now.

[R00k]

That sg looks like maybe its an md3?

I was under the assumption that if the "-ip" wasn't specified it fell back to INADDR_ANY

	i = COM_CheckParm ("-ip");

	if (i)
	{
		if (i < com_argc - 1)
		{
			myAddr = inet_addr (com_argv[i+1]);

			if (myAddr == INADDR_NONE)
				Sys_Error ("%s is not a valid IP address", com_argv[i+1]);

			strcpy (my_tcpip_address, com_argv[i+1]);
		}
		else
		{
			Sys_Error ("NET_Init: you must specify an IP address after -ip");
		}
	}
	else
	{
		myAddr = INADDR_ANY;
		strcpy (my_tcpip_address, "INADDR_ANY");
	}

	if ((net_controlsocket = WINS_OpenSocket (0)) == -1)
	{
		Con_Printf ("WINS_Init: Unable to open control socket\n");

		if (--winsock_initialized == 0)
			WSACleanup ();

		return -1;
	}

[killingtime187]

what's a md3 ? how do i fix it ? all the other weaps look fine.

[killingtime187]

by the way, in regards to using a specified interface rather than an address, for windows, here is the code to get the adapters and their address (i would configure, via some config var, iface = "Local Area Connection 1"):

IP_ADAPTER_INFO structure (Windows)

for linux, here is the code:

Adam Pierce Enumerating Network Interfaces on Linux

for linux i guess i would select iface = ethx and the client will automagically grab and bind to the "current" address in both cases.

how about my ssg model ? how do i fix ?

[killingtime187]

by the way, confirmed -- qrack gives me MUCH BETTER ping than dp -- cuts it in HALF actually! so, there is something not quite right with the dp net stack (although it doesn't have the problem with multiple interfaces).

[killingtime187]

found the problem with the ssg display. it's pak1.pak from qrack site -- remove it, get back "old" models, but ssg shows up again.

[Mindf!3ldzX]

Darkplaces works just fine, when you bang every bell and blow on every whistle (Bells & Whistles Broseph!) , its going to slow your PC down,which also slows down your PING! I dont know how or why , but how many FPS your getting is tied to what your ping will be.

Most server I ping 70ms-80ms at when I use Vsync (very low fps,60-75max) on any client,almost any server.
If I unleash 500-1000 FPS I can damn near cut my ping in half (40ms-50ms)

DarkPlaces isn't about going fast,its about looking good and being a heavily modification friendly gaming engine. It just so happens that looking good and going fast go against each other. Anyone using RTLIGHTS knows this I only get 60-70FPS max when using RTLIGHTS and other shit turned on.

Qrack is bred for online multiplayer gaming, and the two engines are definately miles apart for what the overall goals for each author's respective engine.

IMHO,
Qrack is for someone wanting snazzy graphics without losing the multiplayer capabilities!

[killingtime187]

that's interesting mind, but i get over 200fps with dp and 80 ping, whereas with qrack, i get 100-150fps, but 50 ping. of course, im assuming that the fps and ping printouts are legit and aren't fudged or off in some way.

if you have a few mins, can u try this simple test ? --> extract latest qrack + the two additional pak files -- i.e. pak1.pak (models/textures) and pak2.pak (skins) and see if you can view ssg ? looks like this model is messed up. as i just posted, i removed the additional files and the orig q1 ssg showed up fine.