Can you nomip the crosshair in OSP?

[dzjepp]

Hey gang,

Which cg_nomip value, if any, will nomip the crosshair?

Thanks.

[DRuM]

Your crosshair needs nomip?

[dzjepp]

:/

[Cooldown]

Enter the following in the console:

/r_textureMode "GL_LINEAR"

OR

/r_textureMode "GL_NEAREST"

Good Luck and Happy Fragging!

[in4me]

:icon23: I don't know so plz enlighten me as to what it does. :icon31: thanx CoOldown fixed cd-key issue, one server that i couldn't join.

[Cooldown]

:icon23: I don't know so plz enlighten me as to what it does. :icon31: thanx CoOldown fixed cd-key issue, one server that i couldn't join.

I believe what dzjepp is referring to, is that his crosshair blurry when using r_picmip 5 or a similar high value. You can fix it by altering the texture filter setting, r_textureMode. The most common values are:

(low quality): GL_NEAREST
(good quality): GL_LINEAR_MIPMAP_NEAREST (bilinear filtering)
(great quality): GL_LINEAR_MIPMAP_LINEAR (trilinear filtering)
(good quality): GL_LINEAR

In case you don't know, filtering is somewhat like anti-aliasing, except for textures. You can see what the game looks like without filtering by setting r_textureMode to "GL_NEAREST". It's pretty ugly, and everything is very "pixelated" or "blocky".

The default is bilinear filtering, and this will give you the best performance, and pretty good quality. For "best" quality you can use trilinear filtering, although there might possibly be some dip in FPS.

There's one problem with bilinear and trilinear filtering; both of them make your crosshair blurry. Personally I like to use a small crosshair, so this really annoys me because when the crosshair is blurred, I can barely see it. So, if this happens with you, then I'd suggest using GL_LINEAR or GL_NEAREST.

I hope I answered your question!

[dzjepp]

Hey thanks mang, I knew about using GL_LINEAR_MIPMAP_NEAREST and all that (what I had) but I didn't know you can just set a single value of GL_LINEAR or GL_NEAREST. Well I tried both and woah, it's a lot sharper. Actually aside from having blockiness in GL_NEAREST, it still looks damn sharp (there is no 'bluriness' when you go farther away). GL_LINEAR is the same, but the textures are filtered of course. Setting Trillinear fltering via the menu will not yield this sharpness however, since it set's it at GL_LINEAR_MIPMAP_LINEAR. I wonder why id didn't input GL_LINEAR somewhere under easy reach, because back then it would showcase the game quite nicely.

EDIT: Actually is this just enabling anisotropic filtering or what?

[dzjepp]

One small thing, I'm having a problem getting the cvar to stick (using it inside of autoexec.cfg). :/

[dzjepp]

Strangely enough, r_texturemode IS already at GL_LINEAR in the OSP q3config.cfg, but when I launch the game it goes back to Billinear. wtf

[Oeloe]

How do you start up Q3 with OSP? With a proper shortcut that has +set fs_game osp in the command line? Most game browsers like ASE do this automatically. If you use the mod menu inside Q3 to select OSP, autoexec.cfg will not be loaded if you put that file in quake 3 arena\osp.

I'm not putting up with butt-ugly gl_nearest textures just to make my chrosshair slightly less blurry btw. I just tweaked the crosshairsize so that the blurriness is minimal. I use the dot (cg_crosshairtype 7), so it's not that noticeable anyway.

[dzjepp]

I mostly use ASE to launch the game, but yeah, when I test things I launch from an osp shortcut.

[Cooldown]

Strangely enough, r_texturemode IS already at GL_LINEAR in the OSP q3config.cfg, but when I launch the game it goes back to Billinear. wtf

Do you have one autoexec in your baseq3 folder or do you have autoexecs in each of your mod folders? Make sure there's only one r_textureMode entry in each of your configs and that it is set to GL_LINEAR. Try deleting your q3config.cfg files and allowing your autoexec to create new ones OR simply re-execute your autoexec.cfg in-game (/exec autoexec). You can also add +set r_textureMode GL_LINEAR to your shortcut(s): Right-Click on shortcut Properties Target Field.