been 2 hours, still no comments?...
nice find

Nice find :D Gotta try!

http://wadle.co.uk/cnq3-145.zip if you wanna try it, looks like this'll be the version that's released.

thank you dear sir.

As long as the spectator bug isn't fixed, CNQ3 is just as much of a pain in the ass as iOQ3 to run servers for a competition with GTVs.

But it's still cool to run client side : ]

Never ever heard of that bug? Care to explain it instead of just hoping it'll get fixed?

There is already a thread on promode.org/forum. It's been there for a long time now I guess.

http://www.promode.org/forum/viewtopic.php?f=17&t=4323

Oh that, sorry I didn't think it was specific to CNQ3.

It's not

It's specific to any engine based on id's source code. This infection is in blood of any quake3 'surrogate'.

Are you sure about that? Or is it just engines derived from ioq3?

Absolutely sure!

http://promode.org/forum/viewtopic.php?f=17&a...bug#p42677

much worse yet barely ever discussed

that's cause no one cares about vq3 :)

yes.. this specbug is always ruin GTV broadcasting when you need to reconnect 10 different rooms :E

Raw mouse input?

Only if there will be source code somewhere...

my point was i want a RawQuake intergrated version of cnq3145

untill then i will use RQ w/ cnq3143

And my point was that this is possible, but I need sources for CNQ 1.45 :)

You should make a new raw input version as soon as you can 'cause many players have already gotten used to it including myself \o\
P.S. It would be pretty nice if you make something like that for q4 executable :3

For both cases I need source code... And for Q4 it is scheduled to be released either on late 2010 or never. :(((

hmm... i MAY change my mind about this.

like i said way back, raw is a placebo, but it IS "nicer code" than DI. what's always stopped me is that i *know* we have players on w2k still - but they ARE an absolutely tiny fraction, and the option of MSG mouse input would still be there for them - and i don't know how many are using that anyway.

it figures, since i finally cleaned up the clusterfuck of the original DI init during 1.45. :P

i'll sleep on it, but my gut feeling right now is that i probably will switch. it helps that i deleted the DX SDK over the weekend when i was cleaning up, oops. :P

Waiting for linux version!

Very nice dynamic lights!

n1... fps drops due to cpma bots is fixed :)

Really? I don't think that was intentional if it did.

Anyone else having quake suddenly alt tab out in the middle of a game with cnq3 1.45?
Apparently this is a problem somewhere else. Since other applications suddenly does it too hm.

get tweakui (ms site) and check the box that says "don't let shitty apps randomly steal focus"

Ahh thanks :)

using r_mode 1 and using a 4:3 resolution. now i cant get into fullscreen anymore

r_mode -1?

it says in the changelog:

r_mode 1 = custom resolution, as before

will give -1 a try tho

You probably have r_displayrefresh 125 but only a 120 mode available so it fails to windowed. Not the most user friendly way of doing it I know.

ah, thanks, displayrefresh 60 does the trick!

either liam's changelog is a bit out of date (i tend to not clean up the language until the last minute) or you missed it (or both :P)

chg: hardcoded r_mode garbage and modelist removed:
r_mode 0 (default) = current desktop resolution, depth, hz, etc
r_mode 1 = custom resolution etc
note: r_mode 1 WILL NOT tolerate invalid r_displayRefresh values any more

"r_mode 1" is actually "r_mode anything-that-isn't-zero" - it should really be called "r_custommode" or sthing, but that seems overly nitpicky/pointless/annoying. :)

--

i doubt you need to set displayrefresh 60: just leave it at 0. if you're on a shitty lcd (and all lcd's are shitty) you probably don't have a choice, so you'll get 60 as the default anyway. indeed, since you clearly ARE on an lcd, you should probably just use mode 0. :)

i agree it's not "user friendly", but here's the thing: loose code / design causes problems FOREVER; making people actually get their configs RIGHT is a one-time deal.

if you have r_displayrefresh 125 but only a 120Hz mode, idq3 will give you *60*Hz, and you'll never know unless you use vsync+drawfps / OSD / etc. that sucks donkey balls. if cnq3 accepts your settings, you know you GOT what you said you wanted, instead of something random that may be absolutely crap.

the engine has no business lying to the user, EVER. if you asked for 1000x800 and it just gave you 640x480 and pretended everything was fine, would you accept that? :P
(and that would STILL be better than lying about the refresh rate, since at least low rez doesn't give you headaches).

even on Shitty Monitors, it's important for the engine to be honest, since some of them can apparently do ?75?
at low rez. that may be trivial compared to the 120/60 difference on a real monitor, but it's still the Right Thing to do.

--

for the most part though, r_mode 0 is the "important" one: with so many people stuck on ubershit short-height lcds these days, and having more than enough graphics horsepower to play at their native rez, it's a lot easier for both them and us to just use mode 0.
the mode list was a poor decision even a decade ago, but the idea of welding 50 *more* random resolutions into it, and continuining to do so indefinitely, is sheer stupidity.

thanks for the answer.

i read the part about displayrefresh but i somehow disregarded it, not making the link between the failing fullscreen and displayrefresh.

i have no issues with the way its being set now.

i've been using custom 1400:1050 as a resolution because i hate the 16:9 format.

any ideas where i can find that mentioned server cnq3 1.44?
no problems using the 1.45 as client just fyi