MoonDog

Rendering "light" in Radiant is no simple thing. Quite the opposite. In the scheme of things, it loses it's importance anyway. Eventually you become good enough to predict how the falloff of each light entity will look, same thing for surface lighting. Even with light preview, one wouldn't suddenly become a light artist. I'd much rather GTKRadiant adopt things for CODRadiant besides the light preview, such as the camera movement system for the 3d view. It's very much more efficient. There are other features such as Z-Axis cubic clipping, hide unselected without requiring invert selections( Or, Regions. *Shudder* ), measuring tape line, model viewer, better texture window, better entity control and linking, more keyboard shortcuts for more functions (Rotate X, Y, Z, Lock X, Y , Z, etc... ) that I'd rather have. Because currently, using GTKRadiant is NOT a pleasure. Using CODRadiant is, because it feels more accessible and more fluid.

I usually just place team based spawns only; in order to handle both situations. It's not a HUGE deal in JKA, but it's still a wise practice to carefully consider the amount of space and the layout of your level when placing your spawns. A common mistake for a community made competitive map is misunderstanding the importance of spawn placement. As for the limit of spawns, I'm not sure. I know the entity limit is 1023( +1 Required Worldspawn ).

A decompile isn't necessary, unless you need it for education purposes or to more easily get origins. With the state of this community, anyone using a decompile for benign purposes would be shocking. You can open the .bsp with notepad, search for "worldspawn", and find the entity list that way. Everything from the opening bracket of the world spawn entry { "classname" "worldspawn" } to the closing bracket of the last entity example: { "classname" "your_mom" } needs to be copied out into a new txt file. Simple save that file as the_maps_name.ent. Modify the existing entities or add new ones, keeping to the proper syntax. You can then recompile the .ent file back into the BSP with an onlyents compile on Q3map2. There are a bunch of tutorials out there on how to do this. I like to use Boba Fett's little entity re-wrapper. Just need to setup your paths, and have the .ent file and the .bsp in the same folder as q3map2. Drag and drop the .ent file onto this .bat @echo off cls title Entity Recompiler - Wrapper made by BobaFett echo q3map2 entity recompile wrapper echo by BobaFett echo. m: cd C:\Program Files\GtkRadiant-1.4 q3map2.exe -v -game ja -onlyents %1 echo. echo Compiling finished, press any key to close this window pause>nul

You bet your ass poison is doable. Loop //Generated by BehavEd flush ( ); rem ( "This script is ran when the player spawns every time" ); loop ( -1.000 ) { rem ( "This loop sets their parm15 to timer2 and begins the poison loop" ); wait ( 1000.000 ); set ( /*@SET_TYPES*/ "SET_PARM15", $get( FLOAT, "timer2")$ ); if ( $get( FLOAT, "SET_PARM3")$, $=$, $1$ ) { rem ( "If the player triggered poisonactive, count down their HP" ); if ( $get( FLOAT, "SET_HEALTH")$, $!$, $100$ ) { if ( $get( FLOAT, "SET_HEALTH")$, $!$, $0$ ) { if ( $get( FLOAT, "SET_HEALTH")$, $<$, $0$ ) { set ( /*@SET_TYPES*/ "SET_HEALTH", "0" ); } else ( ) { if ( $get( FLOAT, "SET_HEALTH")$, $>$, $90$ ) { set ( /*@SET_TYPES*/ "SET_COUNT", $get( STRING, "SET_HEALTH")$ ); set ( $get( FLOAT, "SET_COUNT")$, "-1" ); set ( /*@SET_TYPES*/ "SET_HEALTH", $get( FLOAT, "SET_COUNT")$ ); } else ( ) { if ( $get( FLOAT, "SET_HEALTH")$, $>$, $80$ ) { set ( /*@SET_TYPES*/ "SET_COUNT", $get( STRING, "SET_HEALTH")$ ); set ( $get( FLOAT, "SET_COUNT")$, "-2" ); set ( /*@SET_TYPES*/ "SET_HEALTH", $get( FLOAT, "SET_COUNT")$ ); } else ( ) { if ( $get( FLOAT, "SET_HEALTH")$, $>$, $70$ ) { set ( /*@SET_TYPES*/ "SET_COUNT", $get( STRING, "SET_HEALTH")$ ); set ( $get( FLOAT, "SET_COUNT")$, "-3" ); set ( /*@SET_TYPES*/ "SET_HEALTH", $get( FLOAT, "SET_COUNT")$ ); } else ( ) { if ( $get( FLOAT, "SET_HEALTH")$, $>$, $60$ ) { set ( /*@SET_TYPES*/ "SET_COUNT", $get( STRING, "SET_HEALTH")$ ); set ( $get( FLOAT, "SET_COUNT")$, "-4" ); set ( /*@SET_TYPES*/ "SET_HEALTH", $get( FLOAT, "SET_COUNT")$ ); } else ( ) { if ( $get( FLOAT, "SET_HEALTH")$, $>$, $50$ ) { set ( /*@SET_TYPES*/ "SET_COUNT", $get( STRING, "SET_HEALTH")$ ); set ( $get( FLOAT, "SET_COUNT")$, "-5" ); set ( /*@SET_TYPES*/ "SET_HEALTH", $get( FLOAT, "SET_COUNT")$ ); else ( ) { if ( $get( FLOAT, "SET_HEALTH")$, $>$, $40$ ) { set ( /*@SET_TYPES*/ "SET_COUNT", $get( STRING, "SET_HEALTH")$ ); set ( $get( FLOAT, "SET_COUNT")$, "-6" ); set ( /*@SET_TYPES*/ "SET_HEALTH", $get( FLOAT, "SET_COUNT")$ ); else ( ) { if ( $get( FLOAT, "SET_HEALTH")$, $>$, $30$ ) { set ( /*@SET_TYPES*/ "SET_COUNT", $get( STRING, "SET_HEALTH")$ ); set ( $get( FLOAT, "SET_COUNT")$, "-7" ); set ( /*@SET_TYPES*/ "SET_HEALTH", $get( FLOAT, "SET_COUNT")$ ); else ( ) { if ( $get( FLOAT, "SET_HEALTH")$, $>$, $20$ ) { set ( /*@SET_TYPES*/ "SET_COUNT", $get( STRING, "SET_HEALTH")$ ); set ( $get( FLOAT, "SET_COUNT")$, "-7" ); set ( /*@SET_TYPES*/ "SET_HEALTH", $get( FLOAT, "SET_COUNT")$ ); else ( ) { if ( $get( FLOAT, "SET_HEALTH")$, $>$, $10$ ) { set ( /*@SET_TYPES*/ "SET_COUNT", $get( STRING, "SET_HEALTH")$ ); set ( $get( FLOAT, "SET_COUNT")$, "-8" ); set ( /*@SET_TYPES*/ "SET_HEALTH", $get( FLOAT, "SET_COUNT")$ ); else ( ) { if ( $get( FLOAT, "SET_HEALTH")$, $>$, $1$ ) { set ( /*@SET_TYPES*/ "SET_COUNT", $get( STRING, "SET_HEALTH")$ ); set ( $get( FLOAT, "SET_COUNT")$, "-10" ); set ( /*@SET_TYPES*/ "SET_HEALTH", $get( FLOAT, "SET_COUNT")$ ); } } } } } } } } } } } } } } } } } } } } Deathscript //Generated by BehavEd rem ( "When the player dies this script runs on them" ); set ( /*@SET_TYPES*/ "SET_PARM3", "0" ); rem ( "Clears their parm3 so when they respawn they arent poisoned again" ); set ( /*@SET_TYPES*/ "SET_DEATHSCRIPT", "NULL" ); rem ( "Clears their deathscript so no script is ran when they die unless they are poisoned" );Poisoner //Generated by BehavEd rem ( "This script poisons the player and should be in a target_scriptrunner" ); rem ( "make sure the scriptrunner is count -1 and spawnflags 1" ); rem ( "Make sure whatever you want as the delivery system targets the scriptrunner" ); if ( $get( FLOAT, "SET_PARM3")$, $!$, $1$ ) { rem ( "parm3 is the poison parameter on all players DONT TRY TO USE IT FOR SOMETHING ELSE" ); set ( /*@SET_TYPES*/ "SET_PARM3", "1" ); rem ( "Sets the deathscript on the player so they are cleared of poison when they respawn" ); set ( /*@SET_TYPES*/ "SET_DEATHSCRIPT", "nopoison" ); }

I got enough plant the bomb/Defend against bomb plant in Counter-Strike. Doesn't interest me in JKA.

A lot *could* be done with advanced entity modding on existing SP levels. I think this would be a major waste of time anyway though. You can put a hat on a pig, but it is still a pig. Icarus is much too weak to script anything approaching good combat. Also, the waypoint/combat point system and AI is atrocious. Pretty much, SP is a wash in terms of revamping the shipped levels. Especially since the source map files are not/will not be in circulation. When I played JKA, I loved alternate game modes like Siege and CTF. I was never "pro" at either, but I still had the most fun there. I would definitely play again if I saw CTF expanded on and popularized. Fresh levels would be good too. Only if they are very well designed ASYMMETRICAL CTF levels. Many of the custom levels that claim to support CTF are very very very very shitty CTF maps. You can't just slap a couple of fucking flags in a level.

@@eezstreet. I'm certain you know how vain it is to help someone perpetually plagued by user error, stubborn stupidity, and downright unwillingness to read. Nod, smile, move on.

This thread can teach you a great deal. http://www.quake3world.com/forum/viewtopic.php?t=3620

You'll need to script it. http://jkhub.org/tutorials/article/148-icarus-scripting/page-3

That is an inefficient way to do visability for a level. It will end up being an FPS and entity nightmare later. Before you worry about anything else, take a few steps back and replan your use of structural vs detail brushes. This thread contains a lot of information about visibility. http://www.quake3world.com/forum/viewtopic.php?t=3620 Your playable space is split into leaf nodes by the compiler. A leaf node is defined by the plane of a structural brush. A recursive operation in the BSP phase continues to split volumes into nodes until it has used all the planes of structural brushes in the volumes. The Leaf Nodes in the void are carved away because they are non entity containing hulls. Where leaf nodes join, portals are created in a .prt file for when visibility is calculated. Where one leaf node sees into another leaf node, all geometry and entities are drawn. Because everything your map is detail, you basically have giant leaf nodes (A lot of them the 512 x 512 default blocksize) that see into each other. Meaning, no matter where you are all the complex tris, expensive entities and so forth are being rendered. This will cause you a lot of issues with performance. You will also start running into problems with entities being truncated because you are drawing too many at once.

Use the skip shader, not hint. Hint is for creating manual splits.

Sounds precisely like the problems of a decompiled map.

lol.... Know how I know you still hadn't read the manual?

Did you read the documentation that came with wonko's tools?

http://jkhub.org/files/file/1413-blender-264-jedi-academy-plugin-suite/

It's actually pretty easy to use patch meshes in radiant. Show me a pic of this pillar, and I'll mesh your pillar.

What are the funniest //comment lines?

No, you need to have COD4 installed. It worked on Vista fine for me. You need Quake4 for the built in mod tools. You can't take a map from GTKRadiant and make it work in CODRadiant, or vice versa. The .map files differ slightly in ways they format the syntax for entities, brushes, and curves.

Thats an extra step. It also tends to chug machines when you have a large amount of objects in a map. In CodRadiant you just hit alt + H and see results immediately.

Oh, in that case. Yes. I use the COD4 mod tools, Hammer Editor and in house development tools at work. I've got the UDK for Unreal Engine 3 that I mess with from time to time, but that is a much more artist friendly set of tools than anything else. Plus, it takes me a long time to get a complex mesh setup with pretty UV's. Most of my time is spent getting rid of bad stretching. GTKRadiant is something I go back to from time to time at home, but its hard to enjoy because it just isn't as well setup as Hammer or the COD tools when it comes to working fast and efficiently. It needs quite a few things to get to that point. None of those being a light preview. I don't even care about that anymore. Alt drag from CoDRadiantA keyboard shortcut for rotate on axis. Plus the keyboard shortcuts for locking on X, Y, and Z respectively. It takes a bit of extra time to go up to a toolbar to click these thingsRotation and translation Gizmos in all new versions, not just 1.5.0Hide unselected, instead of trying to work in RegionsZ axis cubic clipMeasuring tape clip line. (Place points similar to the clipping tool. Except it draws a line and tells you that distance in radiant units.)Some sort of support for model preview in the file dialogue. (CoD tools does this with a special folder that contains jpegs by the same name as the models. If the support for that feature were there, than the modders themselves could do the rest.)More convenient control and drive scheme for the 3D window, not requiring you to move your left hand from that side of the keyboard.

The shader keyword you are looking for is deformVertexes http://q3map2.robotrenegade.com/docs/shader_manual/general-directives.html#deformVertexes Good work on your level. However, from a complete environment standpoint it looks like a good blockout rather than something complete. The texture usage is very samey throughout the shots. You need to spend more time in other game levels looking at the floors, ceilings and walls asking why and how they look good. Use a lot of industrial reference too. Start getting elements in there to break up that monotony.

When I did JKA stuff I used 1.6, 1.5 and blender. 1.6 for most of my building. 1.5 for model placement, making complicated meshes, trisouping and patch texturing. Misleading topic title btw. These are all different version of the same editor. The best answer though is that GTKRadiant blows.

I'd get fired.

Is there a statistic for heavy handed moderating? Or lack of moderating in situations that warrant it? That would be a fun statistic.