Search the Community

https://wiki.thedarkmod.com/index.php?title=Collision_Models https://wiki.thedarkmod.com/index.php?title=Clipmodel and what is an example of a TDM CM? That is what DMAP produces. It is a map-wide representation of collision. It is not a "model". ( hence all the brush references in the text ) Look again: barrel01_cm.lwo is a typical collision model in TDM. It is a Lightwave object. ( LWO ). If you know of a single editor program that manipulates Doom 3 DMAP collision products ( cm files ) I would be happy to hear of it.

There is no such model format as "CM". A CM is either an OBJ, ASE, or LWO with a collision texture. The cm data in the map compile cannot be natively manipulated, it is the result of a dmap operation.

Well, I am not sure where you get your information from, but I couldn't export selected ASE mesh in the map as CM model. It's either a bug in DR or the limitation is that only brushes can be exported as CM (which is in fact how dmap generate .cm files - only from brushes)

There is no need to "export" a model as a "model". You can export a model as a different model format if desired but there is no logic to it. The model is already in optimized form and ready to be re-textured with collision textures.

Is it possible to export ASE mesh as CM collision model (and then somehow view it to visually confirm if it's good or not) ? If I select my model and then go to File > Export Selected as Collision Model, I get model selection dialog window popping up and when I select model there and hit Ok, nothing happens (window closes and I am back in the Editor). No .cm file gets saved.

While browsing for 3d objects I saw these 3d Frieze models and was thinking they could be of use for someone making TDM resources. In some scenarios the 3d shapes themselve may be good, or it may be better to use them to generate the various texture required for materials: https://creazilla.com/nodes/63996-frieze-set-3d-model Note that they are in the native format for Blender, and there are other models on that site that may also be suitable.

@Dragofer had good luck with the DDS exporter in GIMP. It allowed him to export at BC5 \ ATI2 \ 3Dc:

Looking at the source code and the core pk4 asset files, I don't see any changes that would make a difference. Does this happen with a single FM? Does the FM pk4 file include an "autoexec.cfg" file? From the source code, here's the load order of config files. exec default.cfg exec Darkmod.cfg exec DarkmodKeyboard.cfg exec DarkmodPadbinds.cfg ==> exec autoexec.cfg <load language> <exec command-line arguments> <init input> <init sound> <init OpenGL> <init ui> <load DLL> <init session> ==> exec autocommands.cfg Details about the addition of "autocommands.cfg" are at https://bugs.thedarkmod.com/view.php?id=3199 I thought "autocommands.cfg" was the right way to do it, because that is what I've read on the forums. It seems that "autocommands.cfg" was originally designed for one use case: running "dmap". However, maybe over time "autocommands.cfg" became the de facto config file for user commands and "autoexec.cfg" became the config file for FM authors to use. I don't know. Does anyone know for a fact whether or not this is the case?

Sounds very interesting! Let us know how it goes. Something I was thinking about: It would be fun to see how TDM maps would look with raytracing... granted our engine will surely never have such a thing unless a complete technological miracle happened, importing it to Blender and rendering in Cycles could give us an interesting view As for such scripts I write them when needed which isn't all that often. Without Google (or DuckDuckGo in my case) I wouldn't be able to do it in Bash's case, both as it's more complex and I use it more rarely compared to JavaScript.

Hey wow, this is so gnarly! I spent the last little chunk of my life learning a bunch of commandline stuff like awk, sed, grep and a lot of versions and other utilities, things like ImageMagick. I thought I was the only one actually taking that seriously for making utilities like this. The last year of my life has involved obsessively hoarding and learning all the CLI stuff I can find, to automate as much as possible, combined with a little Python for Blender and MAXscript for 3DS. I'm currently working on something that will convert lights in MAP files to DAE Collada files, for import into Blender and 3DSMAX. After that, a solution to read from MTRs and setup basic (or potentially not so basic) materials to automatically take care of monkeywork between Radiant and that software, by using MaterialIDs coordinating with headers and propagating its only little contextual base of assets for itself. It's convoluted, but should get the job done. It wouldn't be so far off what you've done here. but I hope to expand it along the way and make it easy for people to finally render their maps in Eevee, etc. and beyond.

So I think we can count 12 or 14 missions depending on our opinion of La Banque Bienveillante and Sneak and Destroy. If these two reissues are counted as new missions (as JarlFrank did here: https://www.ttlg.com/forums/showthread.php?t=152035), then we have 14 missions. If not, then 12. Personally, I don't consider them new missions, so 12 in my opinion. Have no problem with other opinion. In any case, last year was productive!

I should also mention that I do love that old demo, not trying to knock it. But its pretty tough to make animated grass conform to the terrain like that without using a 3D tool like blender, max, maya, ect. Im also curious if these will work with our SEED system? SEED might only work with static meshes

My dream is for forums.thedarkmod.com to link to thedarkmod.com

Purah also worked on Dishonored: https://www.ttlg.com/forums/showthread.php?t=136214 One of my neurons knew it started with a 'P'

The main problem with LWO is that engine always "fixes" them, which often breaks them And engine cannot be changed due to backwards compatibility. On the other hand, now we have OBJ support, which does not mess with geometry. I already suggested to provide a way to load single group/object from OBJ by its name, by writing model name like "mymodelfile.obj$group=lod0". This way we can store all LODs in one OBJ file. Maybe we can extend this group selection to other formats, although that would be harder. Speaking of default distance. The formula should be something like distance ~= A * sqrt(TriangleCount) with some constant A. I suppose constant A can be deduced by setting approximate average size of a triangle on screen with some default resolution (e.g. FullHD).

OBJ does not have anything like LOD info in the format. It only allows aplitting geometry into groups/objects of different names. Putting all the LOD settings into OBJ is barely possible. Maybe it is possible to use defaults in such case, but wouldn't it be better to implement some Blender export or DarkRadiant import for such case (i.e. that would create entityDef automatically) ?

I've recently searched the internet with the aim of finding importers and exporters for all model formats used by TDM, both for older and newer versions of Blender and any other common modelling apps. Here's the result: As a precaution I've made a backup of these importers and exporters on TDM's FTP server in case these links go dead. I won't provide download links to them here so we don't compete with the authors' links, but if at some point in the future someone isn't able to model something for TDM because the right import/export scripts don't exist anymore they can contact a team member. If the original authors want their work removed from this backup they can post here, send a PM to a team member or write an email to the address found at the bottom of this page: https://www.thedarkmod.com/team/ ASE Blender 2.80+: Orbweaver and chedap's importers and exporters for ASE & LWO, should be regularly updated (ASE importer only imports geometry, no materials or UVs) Link Blender 2.79b: Orbweaver and chedap's exporters for ASE & LWO Link Blender 2.79b: JediAcademy importers and exporters for ASE & MD3: Link Blender 2.76b: JediAcademy importers and exporters for ASE & MD3: unknown Blender 2.76b: Motorsep's updated importer for ASE (download link access has been restricted): Link LWO Blender 2.80+: Orbweaver's importers and exporters for ASE & LWO, should be regularly updated (2.79b scripts no longer available): Link Blender 2.80+: douglaskastle's importer for LWO: Link Blender 2.79b: ken9's importer for LWO: can't find the link anymore, used to be on Blenderartists.org MD5 Maya: idTech and greebo importers for MD5: Link 3DSMax: Berserker importer and exporter for MD5: Link Blender 2.80: KozGit importers and exporters for MD5: Link Blender 2.79b: Nemyax importers and exporters for MD5, made for 2.66 and still works for 2.79b: Link Blender 2.72: RPGista's guide for MD5: Link Blender 2.66: Sotha's guide for MD5 (access to the link for Arcturus' rig has been restricted): Link MD3 Blender 2.79b: JediAcademy importers and exporters for ASE & MD3: Link

We got TDM VR, for a start. https://forums.thedarkmod.com/index.php?/topic/20468-the-dark-mod-vr-210-alpha-is-now-available/

Yes, it does. Which makes it interesting that you yourself explicitly said that it's interesting nobody had complained here on the official forums: I did, which is why it stood out to me so much that even though you yourself had personally been involved you would reply claiming nobody had complained here on the official forums. I'm not colorblind at all. Does that make people pointing out that almost no modern games have proper colorblindness support hyperbole? Just because it doesn't affect you, or you choose not to pay attention to the discussion of something, doesn't make it hyperbole. Pick pretty much any modern FPS and you will find plenty of discussion about the near universal disregard for FOV and camera movement as accessibility issues. Denigrating those as hyperbole because you personally don't feel the affects is as bad of a look as demeaning people who bring up the importance of valid allergen warnings like gluten or colorblindness and deafness support.

I literally registered just to point out that people HAVE been raising this as a serious accessibility issue since as far back as 2008. It's been repeatedly brought up over and over and over again. And that is just here on the official forums. If you really mean what you've said I think you should find it genuinely concerning that one of the single most widely discussed accessibility issues in gaming has been repeatedly brought up for over a decade with your game and apparently this is the first you've heard of it... even though it's even been subject to multiple issues in your issue tracking system according to these threads and other google results.

here use this link and never miss again its my startpage https://forums.thedarkmod.com/index.php?/discover

There is a small and simple feature I thought to suggest: In the Entity menu (n key by default), would it make sense to have a button to export the selected entity to a custom def? This would make it easier to create a common customized ent on your map, without needing to manually do so in a text editor. Practical example: You want to have a custom city watch used multiple times. First you add an atdm:ai_citywatch to the map. Then set your custom stuff like skin, def_head, def_vocal_set. There would be a button labeled Export or similar, which when clicked prompts you for a file name and custom entity name. This will create or override the entity atdm:my_citywatch in file def/my_file.def which starts with "inherit atdm:ai_citywatch" followed by your custom spawnargs.

You can find a test map here. Note that I remember not being too happy with it. https://forums.thedarkmod.com/index.php?/topic/19825-negative-spectrum/&do=findComment&comment=432949

There was a thought still stuck in my mind that I wanted to put up. I noticed DOF as a post-processing feature isn't desired and probably won't happen, I'll likely attempt it as a new fog light shader at some point. But an interesting concept popped to mind which I felt would be interesting at least for the sake of discussion. People complain of how expensive anti-aliasing is, something I can fully confirm as even 2x or 4x reduce more than 10 / 30 FPS at best. I suggested implementing shader based AA like FXAA for this very reason but that's another story. As its name suggests, MSAA uses multiple samples so each pixel is rendered several times with different interpretations. I believe MSAA is a fixed OpenGL feature in the graphics driver and likely can't be modified directly. My thought was: If we're trying to get rid of sharp edges and may use multiple samples to do so, a custom AntiAliasing system could do it using positional / angular variation per sample. Think of it as physically based sampling, which as a consequence can also be used to achieve a DOF like effect by naturally emulating the f-stops of a real camera. This was inspired by how the Eevee rendering engine in Blender seems to function: You give it a fixed number of samples. Each sample is used to randomize various things in the frame, including pixel directions to emulate DOF. Even the soft shadow samples are controlled by it... this might be an interesting way to get soft shadowing, which could be achieved by having each sample interpret the light source as being at a slightly different position. Unfortunately this would likely be slower than MSAA: It requires rendering the camera multiple times per frame from a slightly different position / rotation to mix up the average result... this must be excruciatingly slow, even at a low value like 4 samples which wouldn't be enough for good looking results. As such it's likely an experiment that won't be considered worth attempting; I'm mainly curious at a concept level how such a thing could work and look like... the technique must have been done before in realtime engines, there's likely even a term for it though I couldn't find it.