ProQuake 4.93 Test

[Vsevolod]

This works perfect here.
Windows XP 32 bit.

[Baker]

Baker is the server browser in-client based on or using data from the server browser here or no (just want to know for future reference so if I ever make any mods to the code here I know whether it'll break your client or not hah). PM me if you want to discuss tech. stuff outside of this thread.

Yeah, it draws data from QuakeOne.com. I'll send you a private message on the technical details (+R00k/MH/Spike).

[Baker]

This works perfect here.
Windows XP 32 bit.

Well, we have several "server browser works perfect". I wonder why Mindz had an issue on one computer.

[Mindf!3ldzX]

Well, we have several "server browser works perfect". I wonder why Mindz had an issue on one computer.

I have a 100% stripped folder (for testing Direct test builds that I nag MH for) and ima test proquake beta inside that folder, see if it happens again. brbr.......

It's something inside my ID1 folder,probably autoexec.cfg because directq uses directq.cfg and qrack uses its own folder.

I'll start taking peices out / trying / and rinse repeat until I find whats the issue..... and yeah looks like only DirectQ will need that pq_password thing. Baker can I nag you to start including multimonitor / alt tabbing / into your pre-release testing regimine,as that makes or breaks my ability to use a client.

Life is busy and my PC is busier lol,multi monitor is acting weird. if I have a window open on monitor 1, open the probeta I just downloaded , when I close quake it has pushed verything onto monitor 2.


confirmed working, just will need to figure it out.

[Baker]

I have a 100% stripped folder (for testing Direct test builds that I nag MH for) and ima test proquake beta inside that folder, see if it happens again. brbr.......

It's something inside my ID1 folder,probably autoexec.cfg because directq uses directq.cfg and qrack uses its own folder.

I'll start taking peices out / trying / and rinse repeat until I find whats the issue..... and yeah looks like only DirectQ will need that pq_password thing. Baker can I nag you to start including multimonitor / alt tabbing / into your pre-release testing regimine,as that makes or breaks my ability to use a client.

Life is busy and my PC is busier lol,multi monitor is acting weird. if I have a window open on monitor 1, open the probeta I just downloaded , when I close quake it has pushed verything onto monitor 2.

Explain the ALT-TAB thing you are referring to. (is this Qrack only that does it? And what does it do?)

Regarding multi-monitor: I might throw in my "monitor 2" modification and see if that helps you. I'll explain how it works on official release of 4.93 if I am able to include it (my current Windows laptop doesn't support multi-monitor, so I'll have to do it "on the blind").

[Baker]

Polarite: The following .zip includes 2 binaries, a glpro493_a and a glpro493_b.

http://quakeone.com/proquake/glpro493_polarite.zip

I think one of these will solve your keyboard issue, I need to know which one does.

Also: Do have in_keymap set to 0 or 1? I just need to know if you use 0 or 1?

[Polarite]

They both seem to fix the problem.
I use in_keymap "0"

Only noticed 1 different thing :
glpro493_as.exe windows doesn't work.
glpro493_bw.exe windows key works.

[Mindf!3ldzX]

Quake is in fullscreen, alt tab successfully goes to Desktop & returns to just as it was. Proquake is shuffling my background windows all to monitor 2 when opening.

Alt Tabbing out of Quake is a common occurance for me,and thats what im speaking of. Just alt tabbing out of quake with mulitple monitors @ different resolutions. (monitor 1 = 1280x1024 , monitor 2= 1440x900)

I only use 1 monitor for Quake,and during alt tabs, some engines can act wonky. This is just my observation that some engine authors might not be factoring in the prospect that a user uses multi display outputs / facilitate in-house testing on multimonitor setups, checking for alt-tab success.

AMD has eyefinity but I dont have 3 "identical" monitors so it looks shitty,and thats on my end.

Wasn't an error report just a suggestion for future inhouse testing you do.