 News | Forum | People | FAQ | Links | Search | Register |
Log in |
|
|
On the
Keeps coming back this one, and hmap2 isn't very robust. on second thought...
seems like the elapsed time output stuff is broken? Light: 0.0%, Elapsed: 0:00 Light: 0.0%, Elapsed: 0:00 Light: 16.3%, Elapsed: 0:00 Light: 28.2%, Elapsed: 0:00, Left: 1:00, Total: 1:00, 24% Light: 41.1%, Elapsed: 0:00, Left: 0:00, Total: 1:00, 39% Light: 72.2%, Elapsed: 0:00, Left: 0:00, Total: 0:00, 81% Light: 92.0%, Elapsed: 0:00, Left: 0:00, Total: 0:00, 92% Light: 99.3%, Elapsed: 1:00, Left: 0:00, Total: 1:00, 98% Light: 100.0%, Elapsed: 1:00, Left: 0:00, Total: 1:00, 100% Light: 100.0%, Elapsed: 1:00, Left: 0:00, Total: 1:00, 100% done in 60.771000 seconds looks like it was rounding off the numbers. also, how do you use _color with sunlight? tried sticking that in world, but no luck. _color with sunlight is an exercise for the future. ;)
The time counter is no longer reliable since I multithreaded it, but it still gives a reasonable approximation. about the time counter, that's not what i meant. if you look, you can see that the tool is only displayed minutes and floor'ing the seconds, even on the elapsed time.
please get rid of 'press any key...' pause at the end of light processing. it's downright annoying and serves no purpose. at the very least add a switch to disable it. even just hooking it into -nowarnings.
on re-reading, my posts sound rather negative.
sorry about that, the multithreading is going to be a great time saver and i'm quite excited about that. :) This tool applied coloured lighting to one of my current projects which has 104 lightmaps, and over 60'000 vertexes and marksurfaces. Its a benchmark in Quake1 lighting tools. Coloured lighting on massive maps with extra4 etc. It auto-detects if you are using RGB "1.0 1.0 1.0" or "255 255 255" colourscales, too, which is cool.
what does it all have to do with fitzquake sdl version beta? ;)
Hmmm... something or another ;> I got another report of brightness failing too.. So the gamma feature is probably worthwhile. But in my experience, a gamma slider shouldn't be placed beside the brightness one. I'd like to have a GL Options menu (just above the Video Options menu), and put the Gamma slider in this sub menu. Any extra GL menu items can also be placed here. if it's a GL option or not. To them, it's all video related, so that's where it should go. Maybe split the video menu into resolution / bpp options and other options like brightness / gamma / etc
but the quake brightness slider IS gamma. It has always been directly linked to the gamma cvar, way back to dos quake, and the gamma cvar has always controlled basically the same gamma ramp function that we are doing with hardware gamma in fitzquake/etc.
"idgamma" is different, i only assume that it implements additional contrast/saturation controls since people who use it complain about how things look without it. Here's some link for a recent tyrquake fix.
http://www.disenchant.net/git/?p=tyrquake;a=commitdiff;h=ed46d97c106471672c571eebd51dedc0508e1225 @Than This seems to work for some people.
Download the source and patch tar xzf SDL-1.2.14.tar.gz cd SDL-1.2.14 patch -p1 <libsdl-new_gamma_ramp_support.patch Remove your old libSDL somehow, or "configure --prefix=/usr" will overwrite libs in /usr/lib configure && sudo make install sudo ldconfig quakespasm Does FitzQuake SDL automatically properly keymap a keyboard
From the code, I am guessing it does but I don't have an easy way to verify this. do that, but it would have required replacing Quake's own keyboard codes with SDL codes throughout the entire codebase, and I didn't want to do that way back.
I do think it should be done though, and maybe I'll convince the QS guys to let me fix this in QS.
|
|
| You must be logged in to post in this thread. |
|
| Website copyright © 2002-2024 John Fitzgibbons. All posts are copyright their respective authors. |