SomaZ

Yea, I used this addon: https://github.com/c-d-a/io_export_qmap I used blender to blockout everything. Later, once I've added all the models, I build collision brushes for the models in Radiant though. Building brushes in blender is a huge pain tbh. Wouldn't recommend it. Extruded terrain is something different, I would never do this in radiant agian but always with the addon I linked.

Yea, I will release some of the sources when I had some time to tidy them up. One essential part for rend2 is just modern asset creation. I can't really teach that. Though there are lots of resources online for it. I planned on doing some tutorials on some things like: "How to properly bake normal maps for rend2","How and where do I place cubemaps and what do they actually do?" or "What are deluxemaps and why should I bother?" All the blender lighting/mapping stuff I'm still figuring out myself tbh. Theres some kind of workflow, but I think I could potentially streamline this much more, make it less error prone etc. Main problem about that is that I really dont have much time right now and it will just get less end of october. Trying to teach as much as possible to others and helping where I can.

So, I started baking the remaining textures for the vanilla mp/duel1 map. Once I've finished the remaining ones, I'll update the download.

So this is intended to be some "behind-the-scenes" and/or feedback thread for the released Bespin Duel Reborn mod, which you can grab here: The idea behind this mod is simple: I need something to show the modern rend2 features. Duel1 is quite small, so lets just remake this. Easy Like so often in life, things aren't as easy as they seem at first glance. I imported the original duel1 map into blender and realised that this will take quite some time to actually remake the complete map. This is like redoing 40 materials and rend2 requires Albedo/BaseColor textures, normal maps, roughness maps, metalness maps, ambient occulsion maps and in some cases hight maps. Uff. Since most of the walls are based on the same materials, I created one material from scratch. This material I repurposed as a master material in substance designer. All other wall materials are based on this master material. Here are some images when I was testing the first iterations of the textures in-game After finishing all the materials I wanted to replace completely, I started modeling all the missing parts of the map. After that I started building the new map. After I added all the materials and models to the map, I started working on the lighting in blender. The first iteration of a lighted map looked like this I worked on a proper sky for a night time version of the map, but was never really satisfied, so I started working on a day time version instead Last few edits for the materials and some adjustments to the lighting If you are interested in more details of some of the workflows or if you want to know more about a specific model or material, feel free to ask.

In your latest example the line must be surfOn "torso_galaktorso_off torso_collar_off torso_galakface_off torso_eyes_mouth_off torso_galakhead_off" Single arguments dont need quotation marks, multiple arguments must use them like above demonstrated. But this still won't work in JA because you need to use the .skin file instead. Or maybe both is required?

Aren't we completely on the wrong track here? The mod is used in JA not in JO right? If I understand it correctly, JA uses the .skin file for visability and not the npc file?

Have you tried this? surfOn "torso_eyes_mouth_off torso_galakhead_off" surfOff "helmet torso_galakface_off"

Looking very good so far! Be warned that jedi academy lighting can actually just darken your diffuse images though. Just because it is often just mutliplied and lightmaps and diffuse images are in 8bit (per channel) color depth. If you are interested I could show you how to use a blender addon that I've written to properly bake lighting with blender. I could also offer help if you are interested in providing rend2 support with your maps. Blender addon in action: Old version of rend2 in action:

I just released the first verison of rend2 in a very long time. I've been busy with fixing and reworking alot of things. The weather system is fully functional now as also alot of other things. You can grab the latest release here: https://github.com/SomaZ/OpenJK/releases Changelog: - MSAA antialisaing cvar changed to r_ext_multisample which is the same as in the vanilla openjk renderer - Added external hdr lightmap support - Added autoload of images with following suffix "_specGloss", "_rmo" and "_orm" - Realtime sun shadows won't flicker anymore when the player is moving around - Some fixes regarding the HDR rendering pipeline (means rendering in hdr colors, but there's no HDR display support (and never will because OpenGL)) - Thanks to @Almightygirfor contributing a velvet shader (you can use it per shader stage, just add a 'cloth' to it (same as with glow or detail)) and fixes regarding pbr shading - Added a shader stage keyword to "pull out" parallax mapped surfaces ('parallaxBias [0.0 ... 1.0]', you can easily test this with r_forceParallaxBias [0.0 ... 1.0]) - Added mikkTSpace for normal mapping (means baking normal maps in blender or substance will result in the same shading in rend2 now) - Fixed rendering cloud layers - Fixed wrong camera exposure on maps with sky portals - Fixed alot of problems regarding fog - Added flare rendering back - Added most features back to surface sprites (only thing missing afaik is wind handling, swaying is implemented though) - Speed up rendering dynamic lights with parallax occusion mapped surfaces by alot - Added distortion rendering back (invicibility sphere, push/pull sphere) - Added glass shattering back - Added ghoul2 sabermarks back - Added r_showTris 1 back - Fixed a crash regarding md3 model caching - Lots of other small things I think that's all for now. Some WIP pictures of my bespin duel remake with hdr lightmaps

That is not a thing. Q3map2 assignes lightstyles to surfaces, not entities. The entities are just linked by target and targetName keys in the triggers and target entities. So, as long as theres the keys intact, this shouldn't be a problem at all. Sounds more like q3map2 just clears the lightstyles on the corresponding surfaces. @KyleFanwould you mind sending me your patched bsp file in a dm? This would make the debugging process much easier.

Might be a compiler bug or something like that. I'm not entirely sure how triggering lightstlyes works, but it looks like its using the actual light entities. Those are usually removed on compile in newer versions of q3map2. I guess, you did an ents only compile to add your "level change" entity. You might want to try doing this again, but add a "_keeplights" "1" to your worldspawn before. Else, we could try adding the entity via my blender addon to the bsp and see if the problem still exists.

This is a short tutorial on how to import/export md3 models with the (currently) latest version of Blender which is 3.3.1. Installation of the addon: First of all you need to install the "Import id Tech 3 BSP" addon. You can download the lastest release here: https://github.com/SomaZ/Blender_BSP_Importer/releases If you want to utilize the addon to its full potential you need to extract the "models", "shaders", "textures" and "maps" folders from the games pk3 files into one seperate folder. If you only want to use the addon for exporting your models, you won't need to do that. In either case its needed to set the base path of your game install in the addons preferences. If you unpacked the folders I mentioned before, make sure the addon points to the folder where your files were extracted to. So, open Blender, go to 'Edit -> Preferences -> Add-ons' Click the 'Install...' button on the top right and navigate to the zip you downloaded, then click 'Install Add-on' Tick the checkbox next to 'Import-Export: Import id Tech 3 BSP' to enable the addon Open the addons properties with the arrowhead next to the checkbox and set your games basepath This is the default setting when installing the addon. Make sure the basepath is correct for your install. Importing MD3 files: Once you installed the addon, importing md3 files is as easy as opening the import dialog via the import menu entry and selecting a md3 file. If you want to skip importing md3 tags, you can untick the "Import Tags" checkbox on the right side of the import window. On default, the addon will merge all objects in a md3 file into one blender object. You can change that behaviour when you change the preset to "Objects". The addon will look for valid shaders and textures for the imported md3. The addon will also add some control elements to the UI under the Q3 Shaders tab on the right side of the viewport to manipulate the lighting preview. If you want to use the model in a rendering, you can just select your models and hit the "Reload Cycles Shaders" button to get a shader without fixed lighting values. Exporting MD3 files: Just open the export dialog via the menu. You can choose to only export the selected blender objects, or all meshes in the scene. The local space coordinates will export all models as if they are moved to the origin. Setting the start and end frame to different frames will result in exported vertex animations. The surfaces option will change the way the addon will export the model. If you choose the "From Materials" setting, the addon will create obejcts based on the used materials. You can use this with multimaterial blender objects like shown above. If you choose to export "From objects" you need to make sure your blender objects only have a single material. The addon won't split your model automatically then. Material names are based on the blender material name. The custom property which was used in older blender addons is not supported anymore and is completely ignored. Let me know if I forgot to explain something.

I just uploaded a working version of the addon for Blender 3.3. This is a patched up version which still doesnt have pk3 support. https://github.com/SomaZ/Blender_BSP_Importer/releases/tag/v0.9.633 @Tchefuncte Bonaparte If you are used to the old md3 exporter, you can name the materials directly. The md3shader custom property is not used in this addon. You also dont need to split the model anymore, the exporter will take care of it. Triangulation is also taken care of by the exporter. Install guide is found here (but use the version I linked above): https://trello.com/c/aMEbgAXC You all can now also use this tutorial instead