Ramikad

You can actually fly an X-Wing using a console command in Jedi Outcast. I think that was fly_xwing, or something similar. Though I never managed to get that thing to work properly, also because of the maps not large enough for starfighters.

What have I unleashed with a single, swift comment...

Do you happen to have any other mods installed? If another mod changes something about the weapons it might conflict with the infinite ammo mod.

Personally, if I may suggest a spherical refraction effect, I'd love it if it could be like the (removed) Hopwire grenade from Half-Life 2: Episode 1: Perhaps not as powerful - it's a Force Push after all, not a microscopical singularity

As far as character in-game screenshots go, you may want to play around with the various cg_thirdperson console commands (to open the console, press Shift + Tilde, the key generally on the left of the 1 key), which allow you to set the distance of the camera from the player (cg_thirdpersonRange <number>), rotate the view angle (cg_thirdpersonAngle <number>), and alter its height (cg_thirdpersonVertOffset <number>). You may also want to disable the HUD, which you can do with the command cg_draw2D 0. When you're satisfied with the camera angles, you can then take a screenshot using the command bind <key> screenshot, and pressing that key.

Yep. At least for the second option you can target the buttons to a target_counter, which in turn will activate the door once the count is reached. Not sure how to go about the first one, though.

Feel free to send them over. I'll take a look, though I can't promise anything.

You can try to use the Decimate modifier. It will reduce the overall vertex count of the mesh, but results can be unsatisfactory.

Tim claims he made that skin, in the credits. Judging from the quality it's hard to tell, and a quick search on JK3Files returns no such skin.

That error means that the UVMap of that specific mesh of the model is composed by one or more "islands", the seams being the contours of those islands. It occurs because the exporter needs the meshes to be split where those seams are. Now, with another model I'd tell you to select that mesh, enter Edit Mode, then switch to the UV/Image Editor, press on the "Keep UV and edit mode mesh selection in sync" button, select all of the seams which contour the islands, switch to 3D View, press Ctrl + E, and then D, which would split the edges as required to export correctly... but in this case I'm not positive that it will export correctly anyway. Not only does the mesh split procedure increase the vertex count a lot, but that model already has 34544 vertexes, which means that it probably won't export. And even if it did export correctly, .glm (and maybe .md3) models in Jedi Academy only work with a limit of 1000 vertexes per mesh, for a total of 32 meshes, so it would crash the game. And if you actually managed to get that working, you'd probably have to say goodbye to a smooth framerate. So if you really want that model in the game you'll have to consider cutting down the vertex count a lot, either manually or with the Decimate modifier. Be mindful however, because the Decimate modifier doesn't destroy the UVMap anymore, but it will change it, so don't split edges before decimating.

There was a young Boba in the Kamino demo of KOTF. Other than that I don't know.

Nope. It would simply take ovah.

I just move them from GameData/Base to Jedi Knight Galaxies/Base whenever needed. Aside from that, I can tell that system is working fine for me.

Found it here. Love those screenshots...

I've experimented a bit with scaling ships down a lot and fly them in gigantic maps. We're still far away from X-Wing Alliance and Rogue Squadron: in SP (without coding) the ships must mantain a very high speed compared to their size to not fall down, not to mention the culling problems that cause them to disappear when too close, no matter the size. At least their weapons fire OK in OpenJK, but the accuracy doesn't seem really good. On the other hand they fit very well for the dreaded tunnel-flights in Rebel Assault II, it's amazing to fly through like that, always checking the ship's health! Haven't really checked how things do in MP, but as far as I remember you can't just scale the vehicle down from the .npc / .veh files, and that would involve modeling to change the scale. All of this completely leaving aside the fact that you can't directly script vehicles and NPCs so that they fly like fighters - or fight like cruisers. Aside from all this, there was some coder who achieved a proper X-Wing / TIE Fighter like gameplay for Jedi Outcast. There should be a thread somewhere here.

For what it's worth I've never had any single "no assets detected" (or any other) error just after I made a brand new folder elsewhere like this: - Jedi Knight Galaxies - base - assets0-3.pk3 - jkgalaxies - exe + dlls - JKG - assets + dlls - glua - server

This one should do. //(BHVD) set ( /*@SET_TYPES*/ "SET_NO_ACROBATICS", "TRUE" ); Quoting from BehavED, "Jedi won't jump, roll or cartwheel"

Apparently that's from the 1997 Canadian movie Cube!

Money and other toydarian tricks. Mostly more money. Check out the Wiki for more details.

I got Alderaan. Here's the levelshot: And here's an in-game screenshot: That's Evil Genius level, I was actually amused

Given that the shield is also fully weighted (1.000) to the skeleton_root of the Assassin Droid I think that's not the problem. The hierarchy isn't a problem either. I guess that only really changes the way it's dismembered, but I'm not sure. Does the unweighted vertex error refer to the spherical mesh of force_shield_off_0? In that case, I can only suggest you to put aside vertex painting, which I think might miss some vertexes, and instead select the shield, enter Edit Mode, select all the vertexes (A key), then, under Object Data, Assign all the selected vertexes of the mesh to the Vertex Group Skeleton_Root, with a Weight value of 1.000. More or less the same applies in case the error refers to a different mesh than the shield. The other model_root empty entities are used for LOD (level of detail) support. You'll notice model_root_0, which is the main model, model_root_1, which is the first LOD, up to model_root_3, each tied to a decreased quality version of the model, which is loaded in-game when far away or when forced. They certainly are useful, but not essential to the game.

... let's not take too much creative freedom now, shall we?

You'll need a proper shader to get the mirrors working. I'm not sure if base JA has it, but this is what the shader looks like from a map I can't remember right now: textures/camera/camera { qer_editorimage textures/camera/camera surfaceparm playerclip portal q3map_nolightmap { map textures/camera/camera blendFunc GL_ONE GL_ONE_MINUS_SRC_ALPHA depthWrite alphaGen portal 2048 } } Once you have that, create the mirror in Radiant, then create one misc_portal_surface sticking to the mirror's surface, and linked to a misc_portal_camera in the same place.