use cg_drawcrosshair 62 and cg_crosshairsize 0.1 to enable |]

#include "ui/menudef.h"

menuDef {
name "Crosshair"
rect 320 240 32 32
fullScreen MENU_FALSE
visible MENU_TRUE

itemDef {
name "Vertical"
rect -0.5 -4 1.6 8
visible 1
style 1
cvarTest "cg_drawcrosshair"
showCvar { "62" }
decoration
backcolor 1 1 0 0.35 //yellow //0.35 opacity
}

itemDef {
name "Horizontal"
rect -3.6 -0.5 8 1.6
visible 1
style 1
cvarTest "cg_drawcrosshair"
showCvar { "62" }
decoration
backcolor 1 1 0 0.35
}

}

what i sthe difference btw cg_drawcrosshair 62 and cg_drawcrosshair 2 ?

cg_drawcrosshair 62 activates custom crosshair

It's what his cvar test value is set to:

cvarTest "cg_drawcrosshair"
showCvar { "62" }

Since cg_drawcrosshair just repeats itself after a while you have the option to use the custom crosshair or not by setting a high value for cg_drawcrosshair cvarTest.

You could use any cvar for a test, even made up ones with seta.

I've used cg_placebo before, for example:

cvarTest "cg_placebo"
showCvar {"1"}

That way whenever cg_placebo is 1 it shows whatever it's supposed to show.

At 800x600 looks odd, like the bottom is cut off.

It's got to jive somehow mathematically with the way QL increases the pixels for each line when going from 640x480 to 800x600.

800/640 is 1.25 so perhaps it is something like every 4th pixel gets an extra in a specific direction (added to the end from the right?).

Still that doesn't explain why it makes the "winged" look. I suppose that would have to involve a pixel getting removed from some n by n square. I'm sure this is bitmaps 101 to somebody but I am struggling with it :-(

exact same amont of pixel on all sides, just checked in paint

At 640x480 or at 1024x768 I'm sure it is. 800x600 behaves differently however.

Here's a photo comparing this:


menuDef {
name "Crosshair"
rect 316 236 8 8
fullScreen MENU_FALSE
visible MENU_TRUE


itemDef {
name "left to right"
rect 0 3.5 8 1
visible 1
style 1
cvarTest "cg_drawcrosshair"
showCvar { "22" }
decoration
backcolor 1 1 0 1
}

itemDef {
name "up to down"
rect 3.5 0 1 8
visible 1
style 1
cvarTest "cg_drawcrosshair"
showCvar { "22" }
decoration
backcolor 1 1 0 1
}
}

Which is just an 8x8 square for the MenuDef that starts at 316 (4 pixels left of center) , 236 (4 pixels above center) with two lines 8 pixels in length and two in width crossing each other.

In the photo the Id crosshair 2 at 800x600 is shown on the right, the custom on the left. Notice that the custom takes up 10 pixels as opposed to 8, and 8 * 1.25 happens to be 10.

As you can see Id's version features some off-color pixels on the ends and 4 extra off-color pixels just outside the center 4 giving it an improved look at a distance.

Good luck trying to make those pixels with a custom hud. I guess it's about as good as I can get, after all when I add in the opacity (backcolor x x x 0.y) the pixels will probably behave oddly anyways.

Maybe the 4 pixels from the center could be added if I can figure out what color numbers they are. What a pain in the ass.

forget about math and go with trail and error, works like a charm \:D/

Aye. Bout the only thing that works really. When I was adjusting Cypher's IEM xhair for my res I tried doing it by reducing everything by half (his 800x600, my 1600x1200). Didn't work.

Just keep adjusting until it looks good, that's the only thing that matters. Don't bother getting hung up on having to use different dimensions for each part. You'll drive yourself crazy.

erh looking at the way HUDs in ezquake work it's because you have 640x480 hud on a 800x600 game and you can't put enough decimals to make a clean conversion.

A. That post was from April 2011

B. Was talking about Quake Live, not ezquake.

C. What decimals, where? The hud works by pixels, the decimal work is done internally by the game where I have no access to it. Probably the best way to do it would be to look through the source and try to determine how exactly it does the scaling, but ya, not really interested enough to do that. Otherwise like palatka said, trial and error :-/

I was comparing it to ezquake as the hud canvas so to speak is 640x480 in quake live, where as in ezquake you can change that canvas with vid_conwidth and vid_conheight to half or equal your resolution making covnverting a hud item basic math.

I'm aware of the age of this thread.

I meant positioning the items on the hud where as an increase of less than 0.1 yields no visible result on the position of the items or pixels on the hud.

try r_texturemode gl_linear_mipmap_linear