News | Forum | People | FAQ | Links | Search | Register | Log in
Fitzquake 0.80 Released (finally!)
New in this version: map loading is 4x faster, you can change video modes without restarting, cvar control of anistropic filtering, refresh rate, and vsync, cvar control of max_edicts, r_showtris support, and a typical long list of bugfixes and optimizations.

Go! http://www.celephais.net/fitzquake
First | Previous | Next | Last
 
YES. Awesome, thx! 
Willem 
I don't have any real solutions for you, but I can suggest some things that you've almost undoubtedly already thought of.

The version I have won't save the following values into the config file:

r_shadows
scr_conalpha
scr_conspeed


Try putting the desired values in autoexec.cfg, or create your own seperate .cfg file and exec that via autoexec or the console.

Also, is there a way to get the crosshair to scale up? I want to run a super high res but the tiny crosshair taunts me with it's smallness.

I don't think there's a way to do this in standard Quake (I think there is in QW). I'm pretty sure there's a way to set the console/hud resolution independently of the game resolution (-conwidth?), and this *may* scale the crosshair along with it?

Of course, the real answer is "be a man and don't use the crosshair" ;)

I'll go investigate this conwidth thing, since I'd like to play around with it anyway (can't read text printed to the screen without squinting and leaning forward, or opening the console afterwards, because the text is so fucking small...) 
OK, Scratch That 
It's scr_conwidth in game, and it seems to only affect the console text itself. So if you're running at 1280x1024 and set scr_conwidth to 640, the console text would be as large as if you were running in 640x480.

It does not scale up the crosshair or hud elements though.

It doesn't even scale up text printed to the sceen. I was really hoping it'd do that so I could actually read the text in Evil Exhumed without having to open the console afterwards to see what was said. Kinda spoils the intended effect. :( 
RTFM Fribbles 
Ok, so I found the answer *I* wanted (scr_menuscale will scale the menus, including centerprint text, so I can read the text now, yay).

Willem, I still haven't found a way to scale up the crosshair size. The only thing I can suggest is to modify your conchars and change the graphic used - you still won't be able to scale it up in game, but you could make it something more visible perhaps. 
Scr_sbarscale 
does intermission centerprints and the hud, but not the crosshair. 
I Can Settle This... 
there isn't currently a way to scale crosshair, nor fps counter nor scr_clock readout.

Also, centerprints should go with the menu scale, as far as i remember. 
 
Yep, I've got everything exactly how I want it except for the crosshair. Thanks all! :) I guess consider that a feature request for the next version - scaling crosshair, plz! 
I Have Found A Solution For You 
Dunno Whether It Already Exist... 
... but I really think it would be good manage water and glasses transparency differently... I guess it would requires special stuff as glasses are "water-based" textures, am I right ? 
Go Use Darkplaces Or Something 
and leave your shiny gubbins out of fitzquake 
JPL: 
that's pretty much solved with per-entity alpha 
 
(comming soon!) 
Metlslime 
OK, thanks ;)

I have to experiment now :) 
Glitch Noted In Malice. 
In the Malice TC I found that the Probe item's functionality is broken within FitzQuake 0.80. 'Fire' is bound to move the probe forward, but doesn't actually do anything. The functionality's completely unbroken in WinQuake and GLQuake. Thanks! 
 
hey, just wondering if Preach's hacked version of fitzquake with the model interpolation is up anywhere? The link he posted is down now. Cheers! 
Here 
Ah 
thanks negke, that's gonna come in handy 
Must Be On Quaddicted.COM 2 
 
yup 
Developer 1 
I want to use developer mode to make sure there are no items falling out the map, monsters in walls etc. but when I enable dev mode a number is printed every frame to the console, which is a big pain in the ass since it shoves all the useful information printed at map load time off the screen. I can pause the game quickly to see the data I want, but I'd rather have a way to disable the printing of the number altogether. What is it anyway? millisenconds per frame?

p.s. is a new version of FQ still in the works? 
This Is In Fitzquake? 
i've run in developer 1 a lot and never seen that.

is it a mod you're using that's got some debug text? maybe you can disable that? 
Some Mods... 
do that, especially SP mods. The same problem would occur in any engine that hasn't changed the behavior of that cvar 
P.S. 
yes, there is a new version of fitzquake in the works, and now that my most recent project at work has shipped, i should be able to get it together for release. That is, once my week in seattle for christmas is finished. Unless it keeps snowing and i'm trapped here forever! 
Great 
looking forward to that mp3 quake cd rip support ;)

Of course, FQ is nearly perfect as it is, so I'm not expecting too much new awesomeness in the new version, though I'd love to be surprised by cool shit, and somehow making ATi cards work properly in fullscreen mode would make me happy, since there is some weirdness on my new pc I haven't managed to fix :( window mode runs fine though.

p.s. the mod in question is Quoth. Odd that you haven't seen it, Necros. Maybe I am the only one affected :( 
Counter 
Yeah, that's the counter for number of particles spawned by the particle fields most likely, thought I'd caught all of those leftover dprint messages which aren't helpful for mappers. Ah well...

I was going to suggest the temporary removal of the particle spawnflag from the finc_togglewalls. But since it's Christmas, here's a progs with that line commented out:
http://www.btinternet.com/~chapterhonour/progs-dprints.zip
Replace the progs in pak2.pak with this.

DISCLAIMER: This hotfix hasn't been tested and although it's really unlikely, it may not behave exactly as 2.1 did. Only install this fix if you are experiencing the specific problem blah blah. 
First | Previous | Next | Last
You must be logged in to post in this thread.
Website copyright © 2002-2024 John Fitzgibbons. All posts are copyright their respective authors.