ProQuake 4.00 Zeta

[Baker]

Version updated to 4.00 Zeta (see first post).

To Neil: yes, I'd like to be those in the compile somehow but I don't believe for sure that it is possible.

[R00k]

id suspect that the zlib version in pq just needed to be concurrent, as i think curl calls on it?

You dont need to install Qrack, just rip out the dlls that come with it.. ?
(been about a year since i looked at this so i could be amuck)

[Baker]

The proper dll files are now included in the download. ;-)

[Baker]

I finished a slightly tweaked version and I'll do an update in the morning that loads the skybox and fog from worldspawn to support single player releases like Travail or Castle of the Dark Ages or what not that use fog or a skybox as part of the map.

[Baker]

Mac OSX version of ProQuake 4 Zeta available now:

ProQuake 4: The official continuation of ProQuake

Download: Mac OSX ProQuake 4

Source Code: Mac OS X Source

Unfortunately, it does not yet have the web download capability. Eventually it will, but I am short on time. This was just a quick merge with the Windows version to catch the Mac version up on features but I don't have time to take a in-depth look at what it didn't like about the download code.

It does have the ability to load Half-Life maps and load 512 x 512 skyboxes that are common with single player maps like Travail and such, and alpha brush support for stuff like Forwards Compatible.

[R00k]

Baker, ive used the same precache webdownload routine for bsp as i have for sounds, I havent tested it fully, but hopefully sounds will be now downloaded as well

[Baker]

Haha, I have cl_web_download working for OS X.

Well ..

For Intel. Not for Power PC Macs. I have no clue how to compile in Curl into the project such a way as to create both the x86 and PowerPC binaries (to create a "OS X Universal build").

[Baker]

ProQuake 4 Intel Mac w/Web Download:

http://www.quakeone.com/proquake/Pro...ebDownload.zip

[Team Xlink]

Hey, Baker, do you know if it is possible to do this all in the source code without any of the .dlls? .dlls are more platform dependent.

[Baker]

Quakeworld has had map/model/sound download as part of the protocol from the server for ages. And it is platform independent (but not quite as fast).

/Yes, Quake is a mess isn't it? And I agree. Why can't one engine have it all. Supposedly DarkPlaces is that engine except it has a huge footprint and doesn't even run on a great many Windows machines let alone consoles and so forth [although some of the code in DarkPlaces is absolutely killer and several dozen of the ideas in the DarkPlaces code are thought provoking --- little consolation to someone whose machine can't run it for an unknown reason].

[Dreadlorde]

I'm having problems with alt+enter: it doesn't work. Whenever I try it I get a message saying "Switching between windowed/fullscreen mode is locked". I have cl_key_altenter set to 1 in my config.

p.s.
Do you plan on adding support for higher screen resolutions?

[Baker]

I'm having problems with alt+enter: it doesn't work. Whenever I try it I get a message saying "Switching between windowed/fullscreen mode is locked". I have cl_key_altenter set to 1 in my config.

p.s.
Do you plan on adding support for higher screen resolutions?

Is this on Windows with the glpro400?

If yes ...

1. Did you add anything to your command line like -bpp or -window?
2. Are you in fullscreen trying to go to windowed or windowed trying to go to fullscreen?

glpro400 can't switch bpp (eventually it will, but I'd have to have it clear all the textures and reupload to do it right) so if your desktop is 32 bpp and you used -bpp 16, fullscreen switching is disabled.

If you used -window in the command line, I have ProQuake generally assume that command line parameters trump all to avoid problems where someone has put something conflicting in their config.

p.s.
Do you plan on adding support for higher screen resolutions?

I run ProQuake on my laptop in 1400x 900 resolution. Did you add command line parameters to specify a video mode? ProQuake 4 doesn't need command line parameters for hardly anything because it has a video modes menu and is mostly intended to be run without any command line parameters.

[Dreadlorde]

Is this on Windows with the glpro400?

Should have mentioned that, I'm using d3dpro400.

1. Did you add anything to your command line like -bpp or -window?

-window starts in windowed mode.
but now I can't change to fullscreen, I get the locked error from before. -bpp gives the error 'Specified video mode not available.'

2. Are you in fullscreen trying to go to windowed or windowed trying to go to fullscreen?

Both.

I run ProQuake on my laptop in 1400x 900 resolution. Did you add command line parameters to specify a video mode? ProQuake 4 doesn't need command line parameters for hardly anything because it has a video modes menu and is mostly intended to be run without any command line parameters.

Where is this video modes menu? All I have is Advanced Setting and Customize controls. I just remembered I can set -width and -height from the command line, and it works.

One thing I found odd is that the menu doesn't scale like in WinQuake when you're at a higher resolution. If you don't get what I mean I can post some screen shots later. Just found it odd.

[Baker]

Should have mentioned that, I'm using d3dpro400.

-window starts in windowed mode.
but now I can't change to fullscreen, I get the locked error from before. -bpp gives the error 'Specified video mode not available.'

Both.

Where is this video modes menu? All I have is Advanced Setting and Customize controls. I just remembered I can set -width and -height from the command line, and it works.

One thing I found odd is that the menu doesn't scale like in WinQuake when you're at a higher resolution. If you don't get what I mean I can post some screen shots later. Just found it odd.

Ah!

d3dpro400 must use width/height/bpp command line parameters and doesn't support ALT-ENTER switching (because the d3d wrapper from d3dquake loses the "surface" if I try to destroy and recreate the drawing context and then crashes).

There are a few other things like optional fog that d3dpro doesn't support either.

As for the console scaling, vid_consize controls the scaling and it defaults to automatic scaling. Play with settings vid_consize -1, 0, 1, 2, 3 and maybe 4.

Long story short, by default ProQuake 4 for the GL/D3D version uses "intelligent" console sizing to prevent microscopic text (i.e. do you want text so small in 1600x900 that the console is literally over 100 characters across?) but you can get back to the traditional sizing playing with vid_consize.

[MH]

Ah!

d3dpro400 must use width/height/bpp command line parameters and doesn't support ALT-ENTER switching (because the d3d wrapper from d3dquake loses the "surface" if I try to destroy and recreate the drawing context and then crashes).

There are a few other things like optional fog that d3dpro doesn't support either.

Pretty sure I can fix both of those for you.