they can't be walked on, only downside. 

thank you. 

I would be interested in the source for Nehahra - if you can let me know when you are uploading it, I will watch out. 

http://www.quaketastic.com/upload/files/single_player/mods/NehQCsrc.zip

Glad that my obsessive packrat tendencies came in handy. 

Didn't know it had been released. 

It's pascal, I remember the dev tool stuff.

Can it be c+p'd into regular Qc? Not enough of a coder to know. 

And it says:

More than a year after the release of Nehahra, I am releasing the "QuakeC" source code to Nehahra. I have placed QuakeC in quotes because it is not what you would call true QuakeC, but a Pascal-Hybrid. The compiler/decompiler was created by Armin Rigo, a set of utilities called ACCQC.

I have included in this archive REACC.EXE, which will compile a progs.dat from the .QC files. The error messages are in French. Sorry. :)

So yeah. Good luck with that, guys. Pretty sure this came from planetquake.com/nehahra at some point in the distant past. 

Hello all,

I've been itching to create a map using the darkplaces engine, and since gtkradiant 1.5 has this option available 'out of the box' I went ahead and used this instead of Worldcraft 3.3.

I can compile a map and run it no problem, but here is my dilemma:

Not all of the textures load into gtkradiant. I've downloaded and installed the
rygel-dp-texturepack-high.pk3 and it is installed to:

C:\Program Files\Quake\Id1

The textures show up fine in darkplaces and in dpmod but only a certain few are showing up
in gtkradiant, and it is only like 5 or so that show up.

Can someone please provide me with specific directions on how to get all the textures to
load or show up in gtkradiant 1.5?

If I have to, I would be willing to use an older version of gtkradiant as long as I had
specific directions on how to set up darkplaces in it.

Thanking you in advance,

Protocol01 

Doesnt Radiant require a .WAD file in order to view the textures? Rygels pack would be irrelevant especially in the instance of any editor because the textures which are "replaced" and "upgraded" by that pack all come from the originals which came from the WAD format used to create Quake.

The bottom line is that if you dont have the Quake wad file loaded into your editor then you wont be able to compile maps with all of the textures available from Quake.

The wads are somewhere within:
http://www.quaddicted.com/wads/

probably quake.wad or quake1.wad

The ting is there are loads of wads there for the Quake engine, and may have not been "re-made" by someone and have no hi-rez replacement. But that shouldnt meen you shouldnt use them because you can achieve many different themes with these wads and you dont have to worry that they wont load up in the end user's engine of choice. If you wanna use mega-hi-rez textures then use Source or Cryengine or Unreal Engine 3 or IdTech4 or something.......

[rant]
Merry Christmas BTW ;) 

i think its http://www.quaddicted.com/wads/id.wad that you need to load into your Radiant editor to work

bare in mind I have never used that editor, I always used Worldcraft, but I would have thought that this form of texture handling would be fundamental 

Personally I find GTKRadiant 1.5 to be stupid and terrible, whereas version 1.4 is excellent. As you have discovered, Protocol01, 1.5 has a real problem loading external texture sets. I don't know why. If you had Quake 1 .wads, then they should in fact load from the id1 directory.

Version 1.4 cannot natively load .wads but it has no problem with TGA's and JPG's. Seriously, try exactly what you were doing except using 1.4 and you'll probably have no problem.

Have a look at this guide for a reference on setting up Radiant for Q1:
http://industri.sourceforge.net/howto.php

Hmm, Ricky is probably right though, that you need to texture your map with the original quake101.wad. Then if there are TGA textures in the appropriate game directory with the same name as ones in the map's BSP, they will be replaced at runtime. The BSP needs those texture names and coordinates so it knows what to replace, and the ones from rygel's pack are far too big to fit into the bsp anyway.

Unless... what exactly do you mean by "mapping for darkplaces?" This has always kinda confused me. Which features and game are you trying to use? Cuz if you were trying to use Q3 or HL bsp support, then a lot of what I just said would be irrelevant. 

Thank you RickyT23 and thank you Grahf both for helping me. I guess I just assumed that radiant would have been able to read directly from the pk3 file, I didn't know I was going to have to have the .wad file. I see now that mapping for Quake 1 is VERY different than mapping for quake 3 arena. >.<

As for darkplaces, I mean that I was trying to make a Quake 1 map that could be used with the darkplaces engine.

I will try what you all suggested and go from there, thanks again and Merry Christmas all! 

GTKRadiant 1.4 has a variety of game packs for Q3-engined games, but none for Q1. In the guide I linked to in my previous post, what you are basically doing is building a Q1 game pack from scratch and script files to trick the editor. The single most important change is in the .game file, "default_scale=1" instead of .5 as is used in Q3. You still don't get .wad loading, so you export that to jpg/tga and load those instead. Then after making a map, you run the .map through a map converter to get it into Q1 .map format so that your compile tools can read it. It's all kind of a hack, and adds several extra steps to the mapping process, but it does work.

Radiant absolutely can read and load .pk3's from the base game directory, assuming the directory structure is laid out like Q3's. This is how Radiant loads external textures and models, after all.

GTKRadiant 1.5 changed all this by using a totally different (xml-based) file format for the scripts, game packs, map format, etc. There is a Quake 1 game pack, which allows for .wad loading, but I think how it works is that if you are in this mode, it will not load jpg/tga textures. Also, GTKRadiant 1.5 is just a crappier editor generally, that messed up the clipping modes, vertex editing, and brush manipulation compared to the glorious perfection of version 1.4. Gee, I'm not biased at all, am I.

If all this sounds horribly roundabout and complicated (and it kinda is), there is a simpler way. A Q1-specific version of Radiant, developed by Sikkpin, that is based on the original opensourced QE4 editor that id used to make Quake 2. So basically you get all the goodness of oldschool Radiant style, with native Q1 .wad loading support and none of the added cruft like curve patches that is useless for Q1 editing.

Link should be somewhere in this thread:
http://www.celephais.net/board/view_thread.php?id=60225

Something else you might look into is guides on Nexuiz mapping, which uses the Darkplaces engine. Nexuiz mappers use a fork of Radiant called "NetRadiant," and I don't really know how it's different because I've never used it. However I do know Nezuiz maps usually have externally loaded jpg/tga textures, so you could probably find some info in that community on how to make sure they show up in a map, which directory to put them in, etc. 

Gee, I'm not biased at all, am I.
you may be biased, but you aren't alone.

the 1.5 interface is overall slower and clunkier requiring more keypresses to achieve the same goal as in 1.4.

i believe the intent behind the 1.5 changes was to make it more like a professional 3d package. ironically, i felt the changes moved it farther away (i use 3ds max). 

Grahf,

Thank you for the link and information. It was very insightful. I hope to get radiant setup soon.


Radiant 1.5 really sucks in my opinion, they keep messing up all of the features and usefulness, now it is more complicated to get things done, and I'm going to uninstall it and just use an older version.

Thanks guys. 

Any idea what magic do I have to do to get UnrealED (for UT3) to properly take advantage of 4 cores on my new i5 750 rig? For some reason, it only ever seems to use just 1 (even when doing a level build) and I am absolutely sure I read that UnrealED does scale well with multiple cores. 

It scales to multiple cores during lighting rebuilds via Lightmass but UT3 doesn't support that. UDK would though... 

Have an ATI Radeon HD 2400 Series. So have the no select in 3D window bug with Hammer 3.4.
Just gave the new ATI driver a try. ATI Catalyst 9.12 Driver XP x64. Seems to be working. 

Wow, I never thought the quake mapping community was still kicking. I've decided to finish my old quake1 DM level which has been sitting on my HD since early 2003. It's a great and pleasant surprise to see there are still enthusiasts to share mapping experiance with :D

Anyway, as I'm trying to relearn everything I've stumbled across an issue. I cannot get the teleporter to work. Everything seems to be correct but I get this error message when loading the level.

Object error in info_teleport_destination:
No targetname

In the map file I have:

Target_teleporter
Target tele1

and

Info_teleport_destination
Targetname tele1

I use GTK radiant 1.2.x something and Sleepwalkers mapconv tool.

Any ideas?

And a happy new year to all of you :D 

"classname" "trigger_teleport"
"target" "XXXXX" 

Make sure it's all lowercase 

Human error this time :P
Thanks for the replys.

And while I'm at it I might just throw you another question :) I want to make a lift that travels up only when a button is pressed. I get everything to work, but the lift starts behaving differently when connecting the func_button to the func_plat obj. Without the button connected the lift starts in "down" mode and raises when a player walks over it. However, when the button is connected the lift starts in the "up" mode. Then goes down when I trigger the button. AND after that it starts behaving as if it wasnt connected to the button. wtf?!

Any help here would be appreciated. I know it's possible to do this :) For example it works in the "Pinion1" map.

Thanks again guys. 

you have to use func_door instead, not a func_plat 

You have to have a door which travels "up", cant remember the exact map file key/value of the top of my head.

You can have it travel a negatve or positive value "up" to 256 or 512 units. And theres a spawnflag for "toggle" (1 press, door opens, another press it will close). An you can link as many buttons or triggers to it as you like :D 

its either 256 or 512 - thats what I meant