Darkplaces help

[Baker]

You'll probably have to ask some of these questions at DarkPlaces IRC.

You'd need to use Pakscape under WINE and find the name/folder of the sounds you want to replace.

There are some sound replacement .pak files available (they go in quake/id1):

http://www.quakeone.com/index.php?in..._view&cat_id=6

[Tom]

Thanks.. I will go on the Darkplaces IRC later.

With the water... when I started quake again the water is not transparent. How do I make it start up trans?

Also.. the add ons dont work. Ive activated them in the mod bit under darkplaces and make a short cut with -rogue at the end but nothing happens.

[Baker]

Yeah, you'll need DarkPlaces IRC.

Since IRC is real-time chat, someone can walk you through things a lot better than in a forum. There is a lot to learn with DarkPlaces, you will have these questions for a week because it has so many capabilities.

[Tom]

Thank you for everything!

[Baker]

Thank you for everything!

No problem :d :d

I *still* don't know everything about DarkPlaces and I've used it off and on for 3 years. :d

[Paradise]

As a general rule, every setting you want to stay permanent you must place in your config.cfg file which must be write-protected. I am not certain if other clients over-write your config.cfg file upon startup. It is the safest bet to do that since many clients like to revert back to their original default settings, over-writing your new settings. Keeping track of what you did and backtracking to do it all over again is both an uncessary pain and a nuissance.

You can also create some little daisy chain files. That is what I do. Let us say you want some settings in MultiPlayer when you connect to a server and you want them disabled when you play SinglePlayer - the best example are speed movement settings - some servers have above 400 pps - pixels per second allowed - and if you are at the lower default speed of 320 pps, you are clearly at a disadvantage. And in SinglePlayer you do want to move at the normal speed, that is unless you are running.

As I was previously saying you can create small text files with specific settings which you can call upon from your config.cfg file with a simple key-press.

For one command you can use a bind, if you want a series of commands, then you must put them in a text file all together to stay each time upon their execution. This is best as you will probably run out of keys on your keyboard from assigning each key-stroke for one specific setting to be executed after another.

And this way it is easier, as you want them all executed at once and not waste the time pressing the buttons and activating them one by one. You can do this by putting those commands within a single text-file and more if needed.

An example:

You want to set the maxspeed to 500 pps when you connect to a server and you want the choice of playing at the default maxspeed of 320 pps in SinglePlayer. Instead of typing that each time in the console for the change to take effect, you can call upon your function to do it for you each time.

bind "a" "sv_maxspeed 500"

Therefore when you press a, your movement speed will change from default 320 pps to to your newly selected 500 pps.

Another example:

You also want to bind some keys that only work on the server and not in SinglePlayer where you have no use for them.

bind "a" "sv_maxspeed 500"
bind "b" "do such and such"

You place both of these in a text file - server.txt - and put it into your config.cfg file the following command to call upon this file to be loaded up into memory and be active from the time onward after you execute it.

bind "c" "exec server.txt"

Keep it mind, when you exit Quake, the commands within server.txt will not stay active for the next time and neither will your config.cfg file will change - which is an extremely excellent thing.

This is an extremely excellent solution for enabling temporary settings for a temporary play session without having to re-edit your configuration file and having to type these into the console everytime you want to activate those specific settings for SinglePlayer and MultiPlayer. You do it once, press this key and this is it! Done!

There is one exception here. Some settings are done from the command line. Most commonly are the graphical resolution settings.

Explaining all these here is difficult, it is best you do some reading on these subjects. There are plently of materials on this site to get you started as well as in the provided documentation alone with the clients you choose to download.

This is an overview, you must really research and learn on your own. I deeply hope you found my tutorial useful and it helped you to get started.

[Tom]

Thanks, I'm starting to understand now

Just one more thing..

My mission packs..
Put them in seperate folders (the pak0.pak file) called hipnotic and rogue.
Darkplaces sees them on the options and when I enable them. It says..

Can not change gamedir while client is connected or severs is running.

How do I get it to work?

[Canadian*Sniper]

Type "disconnect" in the quake console then try. It's basically saying you can't change the mod quake is running while you're running a server. You're technically running a localhost singleplayer server when you're running a demo or playing singleplayer.

[Tom]

still not working....
It lets me enable it. Then loading comes up. After that..what do I do??

[Canadian*Sniper]

Well if all else fails you can just run the mod at the very start when you launch darkplaces on linux. Just put in the command you normally use to run darkplaces but add "-game rogue" at the end of it. Example:

./darkplaces-linux -game rogue

[Tom]

Didnt work :\

Quake opened and normal quake started.
This is what was shown in the terminal after.

CD Audio Initialized


<===================================>

the Necropolis
ioctl CDROMREADTOCHDR failed
No CD in player.
You got the shells
You got the Grenade Launcher
Mesa 7.0.1 implementation error: User called no-op dispatch function (an unsupported extension function?)
Please report at bugzilla.freedesktop.org
Mesa 7.0.1 implementation error: User called no-op dispatch function (an unsupported extension function?)
Please report at bugzilla.freedesktop.org
Mesa 7.0.1 implementation error: User called no-op dispatch function (an unsupported extension function?)
Please report at bugzilla.freedesktop.org
Mesa 7.0.1 implementation error: User called no-op dispatch function (an unsupported extension function?)
Please report at bugzilla.freedesktop.org
Mesa 7.0.1 implementation error: User called no-op dispatch function (an unsupported extension function?)
Please report at bugzilla.freedesktop.org
Mesa 7.0.1 implementation error: User called no-op dispatch function (an unsupported extension function?)
Please report at bugzilla.freedesktop.org
Mesa 7.0.1 implementation error: User called no-op dispatch function (an unsupported extension function?)
Please report at bugzilla.freedesktop.org
Mesa 7.0.1 implementation error: User called no-op dispatch function (an unsupported extension function?)
Please report at bugzilla.freedesktop.org
Mesa 7.0.1 implementation error: User called no-op dispatch function (an unsupported extension function?)
Please report at bugzilla.freedesktop.org
Mesa 7.0.1 implementation error: User called no-op dispatch function (an unsupported extension function?)
Please report at bugzilla.freedesktop.org
Mesa 7.0.1 implementation error: User called no-op dispatch function (an unsupported extension function?)
Please report at bugzilla.freedesktop.org
Mesa 7.0.1 implementation error: User called no-op dispatch function (an unsupported extension function?)
Please report at bugzilla.freedesktop.org
Mesa 7.0.1 implementation error: User called no-op dispatch function (an unsupported extension function?)
Please report at bugzilla.freedesktop.org
Mesa 7.0.1 implementation error: User called no-op dispatch function (an unsupported extension function?)
Please report at bugzilla.freedesktop.org
Mesa 7.0.1 implementation error: User called no-op dispatch function (an unsupported extension function?)
Please report at bugzilla.freedesktop.org
Mesa 7.0.1 implementation error: User called no-op dispatch function (an unsupported extension function?)
Please report at bugzilla.freedesktop.org
Mesa 7.0.1 implementation error: User called no-op dispatch function (an unsupported extension function?)
Please report at bugzilla.freedesktop.org
Mesa 7.0.1 implementation error: User called no-op dispatch function (an unsupported extension function?)
Please report at bugzilla.freedesktop.org
Mesa 7.0.1 implementation error: User called no-op dispatch function (an unsupported extension function?)
Please report at bugzilla.freedesktop.org
Mesa 7.0.1 implementation error: User called no-op dispatch function (an unsupported extension function?)
Please report at bugzilla.freedesktop.org
Mesa 7.0.1 implementation error: User called no-op dispatch function (an unsupported extension function?)
Please report at bugzilla.freedesktop.org
Mesa 7.0.1 implementation error: User called no-op dispatch function (an unsupported extension function?)
Please report at bugzilla.freedesktop.org
Mesa 7.0.1 implementation error: User called no-op dispatch function (an unsupported extension function?)
Please report at bugzilla.freedesktop.org
Mesa 7.0.1 implementation error: User called no-op dispatch function (an unsupported extension function?)
Please report at bugzilla.freedesktop.org
Mesa 7.0.1 implementation error: User called no-op dispatch function (an unsupported extension function?)
Please report at bugzilla.freedesktop.org
Mesa 7.0.1 implementation error: User called no-op dispatch function (an unsupported extension function?)
Please report at bugzilla.freedesktop.org
Mesa 7.0.1 implementation error: User called no-op dispatch function (an unsupported extension function?)
Please report at bugzilla.freedesktop.org
Mesa 7.0.1 implementation error: User called no-op dispatch function (an unsupported extension function?)
Please report at bugzilla.freedesktop.org
Mesa 7.0.1 implementation error: User called no-op dispatch function (an unsupported extension function?)
Please report at bugzilla.freedesktop.org
Mesa 7.0.1 implementation error: User called no-op dispatch function (an unsupported extension function?)
Please report at bugzilla.freedesktop.org
Mesa 7.0.1 implementation error: User called no-op dispatch function (an unsupported extension function?)
Please report at bugzilla.freedesktop.org
Mesa 7.0.1 implementation error: User called no-op dispatch function (an unsupported extension function?)
Please report at bugzilla.freedesktop.org
Mesa 7.0.1 implementation error: User called no-op dispatch function (an unsupported extension function?)
Please report at bugzilla.freedesktop.org
Mesa 7.0.1 implementation error: User called no-op dispatch function (an unsupported extension function?)
Please report at bugzilla.freedesktop.org
Mesa 7.0.1 implementation error: User called no-op dispatch function (an unsupported extension function?)
Please report at bugzilla.freedesktop.org
Mesa 7.0.1 implementation error: User called no-op dispatch function (an unsupported extension function?)
Please report at bugzilla.freedesktop.org
Mesa 7.0.1 implementation error: User called no-op dispatch function (an unsupported extension function?)
Please report at bugzilla.freedesktop.org
Mesa 7.0.1 implementation error: User called no-op dispatch function (an unsupported extension function?)
Please report at bugzilla.freedesktop.org
Mesa 7.0.1 implementation error: User called no-op dispatch function (an unsupported extension function?)
Please report at bugzilla.freedesktop.org
Mesa 7.0.1 implementation error: User called no-op dispatch function (an unsupported extension function?)
Please report at bugzilla.freedesktop.org
Mesa 7.0.1 implementation error: User called no-op dispatch function (an unsupported extension function?)
Please report at bugzilla.freedesktop.org
Mesa 7.0.1 implementation error: User called no-op dispatch function (an unsupported extension function?)
Please report at bugzilla.freedesktop.org
Mesa 7.0.1 implementation error: User called no-op dispatch function (an unsupported extension function?)
Please report at bugzilla.freedesktop.org
Mesa 7.0.1 implementation error: User called no-op dispatch function (an unsupported extension function?)
Please report at bugzilla.freedesktop.org
Mesa 7.0.1 implementation error: User called no-op dispatch function (an unsupported extension function?)
Please report at bugzilla.freedesktop.org
Mesa 7.0.1 implementation error: User called no-op dispatch function (an unsupported extension function?)
Please report at bugzilla.freedesktop.org
Mesa 7.0.1 implementation error: User called no-op dispatch function (an unsupported extension function?)
Please report at bugzilla.freedesktop.org
Mesa 7.0.1 implementation error: User called no-op dispatch function (an unsupported extension function?)
Please report at bugzilla.freedesktop.org
Mesa 7.0.1 implementation error: User called no-op dispatch function (an unsupported extension function?)
Please report at bugzilla.freedesktop.org
Mesa 7.0.1 implementation error: User called no-op dispatch function (an unsupported extension function?)
Please report at bugzilla.freedesktop.org
Mesa 7.0.1 implementation error: User called no-op dispatch function (an unsupported extension function?)
Please report at bugzilla.freedesktop.org

Can not change gamedir while client is connected or server is running!
Mesa 7.0.1 implementation error: User called no-op dispatch function (an unsupported extension function?)
Please report at bugzilla.freedesktop.org
Mesa 7.0.1 implementation error: User called no-op dispatch function (an unsupported extension function?)
Please report at bugzilla.freedesktop.org
Mesa 7.0.1 implementation error: User called no-op dispatch function (an unsupported extension function?)
Please report at bugzilla.freedesktop.org
Mesa 7.0.1 implementation error: User called no-op dispatch function (an unsupported extension function?)
Please report at bugzilla.freedesktop.org
Mesa 7.0.1 implementation error: User called no-op dispatch function (an unsupported extension function?)
Please report at bugzilla.freedesktop.org
]disconnect
Client "player" dropped
]

Added packfile id1/pak0.pak (339 files)
Added packfile id1/pak1.pak (85 files)
Added packfile id1/pak2.pak (818 files)
Added packfile hipnotic/pak0.pak (140 files)
Playing registered version.
restarting renderer
OpenGL Backend shutting down
OpenGL Backend starting...
glDrawRangeElements detected (max vertices 3000, max indices 3000)
multitexture detected: texture units = 8
OpenGL backend started.
Trying to load library... "libjpeg.so.62" - loaded.
JPEG support enabled
Mod_LoadModel: progs/beam.mdl not found
Unknown command "gamma"
couldn't exec autoexec.cfg
4 demo(s) in loop

OpenGL Backend shutting down
[email protected]:~/Desktop/darkplaces-quake$

Does that mean anything?

[Canadian*Sniper]

are the pak files in your rogue and hipnotic folders in all caps? is so make them lower case. Folder names should be in loser case as well.

[Tom]

They all are.

Is there any alternatives to darkplaces and can be installed in linux?

[Canadian*Sniper]

Tyr-Quake is reliable.
http://disenchant.net/engine.html

edit:

What build of darkplaces are you using anyways?

[Tom]

DarkPlaces engine Windows/Linux OpenGL build 20071120

I've got the mission packs working now

I will look at the other engine.

But darkplaces is weird. Every 20mins of playing quake my pc crashes :\
Every time. Its annoying. How can I stop this?

Also.. When I put in r_novis 1 in my config file and save it... when I open darkplaces and play quake.. the water is not transparent (its set to .4) If I type in r_novis 1 when pressed ~ it works then. When I look at my config file after playing quake. My r_novis 1 has gone. I've doubled checked to see if it has saved, and it has. So why is it getting wiped every time I play quake?