Ramikad

It needs a shader with cull twosided or cull disable, like this:
models/players/<model name>/<cape texture> {     cull    twosided     {         map models/players/<model name>/<cape texture>         rgbGen lightingDiffuse     } }  

1. I'm not sure what you mean by 3D sounds. Could you elaborate? As far as I know sounds in general are pretty limited in Jedi Outcast and Jedi Academy, as they have to be mono .wav files. Sounds in general are placed around the map with target_speaker entities.
2. There are two ways, a simple func_glass, or a func_breakable brushes with the thin and no_explosion option checked (spawnflags 264) and material 1 (glass). Not sure if there are any advantages in doing the latter, but it's there.
3. The water texture needs a shader to be recognized by the game as water. You'll have to create a new shader, like this one:
textures/common/water_1 {     qer_editorimage    textures/common/water_1     surfaceparm    nomarks     surfaceparm    nonsolid     surfaceparm    nonopaque     surfaceparm    water     surfaceparm    trans     q3map_material    Water     q3map_onlyvertexlighting     deformvertexes    wave    100 sin 1 2 2 0.6     {         map $lightmap         blendFunc GL_DST_COLOR GL_ZERO     }     {         map textures/common/water_1         blendFunc GL_DST_COLOR GL_ZERO         tcMod turb 0.01 0.03 5 0.1         tcMod stretch noise 1 0.01 1 1     }     {         map textures/common/water_1         blendFunc GL_ONE GL_ONE         tcMod turb 0.02 -0.06 0 0.1         tcMod stretch noise 4 1 0 0.01     }     {         map textures/common/stars         blendFunc GL_ONE GL_ONE         rgbGen wave sin 0 1 10 0.5     } } Modify it as you see fit (this is just an example of water shader taken directly from shaders/common.shader), then save it as a <shadername>.txt file, rename the extension from .txt to .shader and put it inside your shaders folder. The last step: open up the shaderlist.txt (also found in the shaders folder) and add <shadername>.shader at the end of the list. This last step is necessary, otherwise the game might still not recognize your shader and your water might end up being solid.
4. Teleports need to be linked to a target_position, that determines where the player is placed. Simply right click -> target -> target_position where you want the teleport destination to be. After that, first select the teleport trigger, then the target_position, and press Ctrl + K - that will link the two automatically. More technically speaking, what it does is it sets the trigger's target to target_position1 (that's the default targetname it gets if it's not specified when linked).
5. Absolutely! color R G B sets the light color to anything you want. color 255 192 0 gives a nice orangeish light, for example. Admittedly, though, I'm not sure if it uses 0-1 or 0-255, though from what I saw the latter seems to work.
I also advise you to read the tutorials Circa suggested as they cover many mapping topics, including these and more (like skyboxes, sky lights, scripting, and more advanced shader effects).

Make sure that you import the model from a folder with the correct hierarchies (models/players/<model>/model.glm, models/players/humanoid/humanoid.gla). Generally this solves it. Basically, the importer looks for the .gla based on the skeleton reference in the model itself, including the path.

Is that actually the model name? car01.md3_car01_des.md3? You only need to set the "healthy" model in the model field - it will automatically switch to <modelname>_d1.md3 once destroyed.
I see you ticked the use_model option - but that doesn't make the model usable: you'll have to tick the player_use option for that, as well as use_not_break. That will make the model usable, it will prevent the model from being destroyed by using it, and will display <modelname>_u1.md3 when used. It will still display <modelname>_d1.md3 - the damaged model - when destroyed. All these models will be automatically displayed in the right conditions (used and destroyed), you just have to set the proper model name. If that's correct, then there may be something wrong with the model so that it can't be dynamically loaded.

distancecull is the value you want to modify. I'm not sure what's the default value, but if I remember correctly it's measured in game units, so you can set it to whatever is the max distance the player can see.

I think this can explain it, anyway.

Reinstalling the game won't be of any help: this error is due to the naming of a model in a custom map you're trying to load. To fix it, you could contact the author and ask him to fix the name so it works in singleplayer too, or you could open up the .pk3 file which contains the model and delete it (although the model itself will disappear from the map). You could also try using OpenJK, although I don't know if this is fixed. Other than that, I don't know.

MB2 has a commando droid, as well as the knife, you could probably get them from there.

It's technically not easy spawning NPCs through ICARUS - it doesn't have a "spawn" command, but it can be achieved with a trick that involves the command SET_VIDEO_PLAY, which would work like this:
//(BHVD) set ( /*@SET_TYPES*/ "SET_VIDEO_PLAY", "-;cl_noprint 1;helpusobi 1;npc spawn stormtrooper;helpusobi 0;cl_noprint 0" );Although it should technically work, and it opens up a lot of possibilities in-game, it's really a workaround. A much easier and better way to spawn an NPC is to use a NPC_Spawner previously put in the map in GTK Radiant (but I guess entity modding to insert one should work as well): you just need to assign the NPC_Spawner a targetname (for example, stormtrooper1). Then, in ICARUS, you just need this simple command:
//(BHVD) use ( "stormtrooper1" );to use the NPC_Spawner and thus spawn the NPC. The same thing applies if you want to trigger any entity through scripts: you just need to assign that entity a targetname and create the proper script for that.
 
As for moving NPCs, you need to assign the NPC_Spawner a NPC_targetname (I'm not sure, but it should be different from the targetname), which you'll have to use if you want to affect them through scripts:
//(BHVD) affect ( "stormtrooper_1", /*@AFFECT_TYPE*/ FLUSH ) {     set ( /*@SET_TYPES*/ "SET_SABER1", "luke" ); }To move them, you'll need to put a system of waypoints in your map. This tutorial does a good job at explaining how to do this.
 
To move brushes, you need to make them brush-based entities in the first place: func_static, func_door, maybe func_breakable too, but I'm not sure. There's an easy explanation of how things work here.

Yep, I don't think it's even a modifier. Though I think that's only doable in Edit Mode, if I remember correctly. Also, for completeness, the reverse operation can be done just as easily with Alt + J, or alternatively, in Edit Mode, Mesh -> Faces -> Tris to Quads.

Create a script like this with BehavED:
 
 
 
 
In this case, just for a test I set up a wait time of 6 seconds (6000 milliseconds). Compile and put the .IBI in the scripts folder of your mod.
Now in Radiant set up a NPC spawner like this:
 
 
 
 
Set the count of the NPC spawner to whatever number of enemies you want to fight. Create a func_usable and link it (Ctrl + K) to the NPC spawner, so that it's used at least once, otherwise it won't work, since it has a targetname. Using the button will spawn the enemy, and once the enemy is dead another will spawn after the time previously set in the script (in this case, 6 seconds).

It doesn't work because that model doesn't have any specific head, torso and legs .skin files. Try instead playermodel cloud model_default or playermodel cloud model_default model_default model_default.

The error doesn't refer to the fact that there are split meshes at UV seams - it is instead telling you to do that to export the model correctly. Basically run through all the edges of the UV islands in UV/Image Editor of the meshes affected by the problem, making sure to check Keep UV and edit mode mesh selection in sync, then, once the edges are selected, click on Mesh -> Edges -> Edge split. That should do the trick.

You have two options here: if you want to take screenshots in MP you can simply open the console and enter /devmapall <mapname> - you won't be able to play with anyone else than bots, but that way the camera console commands won't be protected anymore. I think you'll have to type the same command in SP to unlock the camera commands, so either devmapall <mapname> (without the "/" key, console commands won't work in SP if preceded by that key unlike MP) or, when already in a map, helpusobi 1. To change player model in SP you'll have to enter the console command playermodel <modelname> <skin> <skin> <skin> (perhaps playermodel <modelname> <skin> would suffice, but I'm not sure), respectively the .skin files for head, torso and legs. For example: playermodel kyle model_default model_default model_default.

Nope. Name it whatever you want, and it should run this code:
@[member='Echo'] OFF "glamerge.exe" "_humanoid.gla" "<new animations>.gla" -o PAUSE EXIT Input a name for the newly created .gla and you're good to go. You can keep merging on that new .gla, and stuff all the animations you want (until you hit a limit, but considering my merges it isn't near).

I'm not aware of any, but the "npc" command can show the NPC score (npc score), bounding boxes (npc showbounds), and to kill them (npc kill <targetname>), and probably a few more that I can't remember right now.

If you want to upload a mod as opposed to creating a topic and post your updates / download links, you can click on Files, then Submit File, and follow the instructions.

Try with SET_SABER1 and SET_SABER1_COLOR1.

If you don't have to make it run from point A to point B, you can use the SET_ORIGIN script command.

It is normal. The vehicle, that you spawn using npc spawn vehicle atst_vehicle, is designed to be used properly in multiplayer games only. This is also true for most, if not all, other walker vehicles you may download. It's also normal that you can't select its weapons: a characteristic of vehicles in singleplayer game is that you can't shoot their weapons if you drive or fly them with your lightsaber or blaster rifle selected. Use the blaster pistol instead, or for what it's worth any weapon other than the two I mentioned.
The trick with the AT-ST is that the vehicle you're driving on Dosuun is a different entity, that you can spawn using the console command spawn misc_atst_drivable (which will not work in multiplayer games). This one will be fully functional, walking and aiming properly with the weapons it's armed with.

It's a shader, not sure exactly, but try with surfaceparm forcefield.

Salvoo has a Shrek model:
 
https://jkhub.org/topic/4632-%C5%9B%C4%83%C4%BCv%C3%B5%C3%B6s-skins-and-kitbashes/

If this tutorial wasn't of help:
https://jkhub.org/tutorials/article/137-fix-hapslashs-anakin-model-no-lightsaber-blade/
 
I'd suggest reimporting the compiled model into Blender and check it out once more. Perhaps something went wrong during the export phase.

Not sure if it's Blender 2.64 specific, but in my experience the vertex count on the right top of the screen shows the total vertexes of all meshes. To see the number of vertexes of a single mesh, I simply select that mesh and enter Edit Mode.

/viewpos returns the player's location and angle.