Yeah, if you're making your own mod then that's a good way to do it - but only if you need the same setting for all your maps!

Another approach is to have a custom QC entity which sends commands to the player's console during the map. This lets you build maps with different settings for the various console commands you have created.

Quoth already has an entity like this:
http://tomeofpreach.wordpress.com/quoth/tutorial/info_command/

It's the moral equivalent of the following QC code:

stuffcmd(player, "r_skyfog 0.3");
 

I only need it for this map because the skybox just looks bad with any amount of fog. I have a custom progs.dat but it's nothing special because I am not a programmer. I consider it completely optional, but I guess I could try a custom QC entity anyway. 

Preach is one of the people that keeps this community going. Without a doubt.

The other is that qc isn't really coding, it's just scripting. Once you open it, look at a few variables and read some of the tutorials on inside3d it's a free bar.

Hm.

I'm a bit drunk.

Doesn't invalidate anything I just said though.

Whatever it was. 

Definitely not invalidated by being drunk. 

 

 

There is a ton of good stuff at Tome of Preach. I now remember going there back in the spring. I switched to a different computer for dev stuff early in the summer and didn't copy my bookmarks from the old Athlon 64 I had been using. I bet I had it bookmarked on that machine though. Excellent site man, thanks :)

I played around with spawning a trigger this morning and had no trouble getting it to work. Much more stuff to read. 

I've got a mesh, that if created causes a hard crash in Fitzquake.

Condebug doesn't give me any readout of the error, nor does developer 1 - it just hangs before crashing to desktop.

Other engines (FTE, Tyrann's) have no problem with the mesh in question.

I can't see anything in the documentation, is there any known issue with this? 

FYI, Fitz crashes if you set a skin on a model that doesn't exist.

I'm generalising gibs and different types thereof. 

ijed: if the skin doesn't exist, or if the model doesn't exist? 

It's a hard crash without an error message, which is what had me scratching my head.

If the model didn't exist it'd give me an error.

It seems the other engines I mentioned default to skin 0 if the qc tries to call a bad skin, same as with a bad frame. 

Interesting, I thought I had set it up to display a blue/black checkerboard texture when the skin is missing. Maybe some other changes have broken that feature. 

I thought it was odd when I figured it out. Ah well nobody's perfect :)

I doubt it matters, but this was with Spike's hack to make it usable with BSP2. 

Remember my cellshading sm134? It uses invalid skin numbers on purpose for the blue/black effect, and there's no crash. So it sounds more like there's another condition at play on ijed's end. 

But like I say, I fixed it by inserting duplicate skins on the mesh. It also only affects this particular mesh as well.

Here it is, if you want to check it out;
https://www.dropbox.com/s/9e5vvwd3vnt8bnh/hunter_gibs.mdl 

It's for Quake 3 but surely there are some experienced Radiant mappers around?

I had a system crash and now I'm kinda worried. In reinstalled and everything works fine. When I open the map in the editor, all textures are nicely aligned (except I'm missing some due to the crash). However, if I compile, regardless of what option I use, I get this:

http://i.imgur.com/2sbGuq4.jpg

Any ideas?

PS: If I build a new map, regardless which textures, the same happens. As if some value is off somewhere that's downsizing them. 

I'm mucking about with weird entity settings as usual. Most of my experiments have found that no matter what classname an entity has, you can give it keys that light.exe recognises and it just works. For some reason, antilights only seem to work on proper light entities, not on these repurposed entities. I'm using benlight for these tests, has anyone ever encountered this and worked around it? Or does another light tool cope any better? 

I'm not quite getting what you are asking. Are you asking if someone has found a way to apply or tie a negative light to an entity as a sphere around the entity? If so I haven't seen it. 

Even the stock Quake3 textures do that? If not, then likely there is a disconnect between the Q1 textures you are seeing in editor and the textures the game is using (maybe there is a pk3 of half-size textures in your Q3 directory stomping correctly scaled textures in a directory you are using for radiant?)

If not, first thing I would look at is if your textures are being scaled down properly. Quake3 generally uses double-sized textures that are scaled down by half in radiant (so, a 256x256 for a 128x128 wall). Select a face in your map and bring up the surface properties, your x and y scale should be "0.5". (in 1.5 at least, there's a setting in 'edit -> preferences -> settings -> brush' that controls this default) I'd then save the .map and then look at it in notepad. You should have brush faces that look something like:

( 0 96 256 ) ( 0 32 256 ) ( -64 96 256 ) egyptsoc_mat/block01a 0 0 0 0.5 0.5 0 0 0

Where the "0.5 0.5" parts of the line are the texture scale. If Radiant showed you something different in editor vs when it saves, then there's a problem that I don't know how to fix :(

I don't believe there are any compiler settings that could be doing this. 

I'm not quite getting what you are asking. Are you asking if someone has found a way to apply or tie a negative light to an entity as a sphere around the entity? If so I haven't seen it.

It's a compiler issue I'm having, and I don't understand the compiler source code all that well. In general, the light.exe tool doesn't care what classname an entity has, it's only looking for the "light" key on that entity. You can give a monster_shambler the key "light" "200", and the compiler will create a light source at that point (obviously it doesn't follow the shambler, it's just static).

The other thing is that antilights - lights with a negative value in the light key which some compilers support. What I've found is that these two things don't mix. If you create two mapobjects with "light" "200" and "light" "-200", what I've found is that the antilight one doesn't have any effect. If you take the entities and just change their class to "light", suddenly the antilight starts working as well.

I think I've spotted a separate issue in what I'm trying to do, so don't worry too much about it, but it's weird all the same... 

AFAIK it was AguirRe who invented antilights, or standardized them at least. Maybe send him a direct email because I don't think he views this board anymore. 

I would guess that when anti-light was added (negative light), that particular code only checks actual Light entities, whereas the original Light code (as you have noticed) just looks at everything.

Personally, I've always considered that to be a bit of a bug. 

Yes, even stock textures do that. Thank you for your suggestion. I checked but Radiant shows the right scales, just like you said. I did some extra checks:

It's not the editor. Regardless which map I make or load, everything works fine.

It's not the game. If I take old compiles or load the original maps. all is displayed normally.

It's not the textures. Even vanilla textures show the same problem.

It has to be a compiler issue. I reinstalled Q3map2 to no avail. 

A google search result that might be fruitful: http://openarena.ws/board/index.php?action=printpage;topic=1820.0 

Hey, I'm using necro's compiling gui and I get this error in the console:
Copying Files... The system cannot find the file specified. Converting map... --------------QBSP-------------- 'C:Program' is not recognized as an internal or external command,operable program or batch file.