HMart

Orbweaver said all what I thought, I also hardly always follow programing "rules", mostly because "basic naming conventions in programming" change with times and as the languages evolve and change. So imo no one should get to much hung up on those, specially when some rules aren't even evidence based but some famous coder thought it made the code "cleaner" and people just followed. For example Hungarian notation, so many coders use it but to me it can crash and burn. I played around with Penumbra HPL engine for a time and it is riddled with such notation and not once, I felt it helped me understand better the code, for the contrary.

Why? Can you explain? Personally I see nothing wrong with that, looking at that function is obvious that they made it to not return anything, it just writes a float value to a file, and in C any function that doesn't return anything returns void. And those inner write functions may have error handling of some kind, so no need to return a bool for success or failure by the main function. The only potencial problem I see with it is they pass the file handle by pointer and there's no guard there for a eventual null pointer being passed to the function and it will crash if that happens but the fact this worked for years tells me they made sure that never happens.

Doing that without permission from the author/s is frowned upon, saying this because if I'm remembering correctly, caused some stir in this community in the past, including a ban. And telling the truth, if I was a mission maker (that I'm not), I personally wouldn't want anyone to mess with my mission without my permission.

Ak ok my bad, I didn't read all the discussion so I missed that.

It is possible to override "core" files in TDM, without messing with the original files, from the beginning. This is a feature of the Doom 3 engine and obviously transitioned into TDM. In Doom 3 and TDM, you just make a copy of a def, mtr or any other file inside your mod or mission folder, respect the same virtual file path from the originals and the modified files will take precedence over the files inside the .pk4's. This could be used by mission makers to for example override the "noshadows" from some alpha materials, for example to permit trees, grass, banners, etc, in their mission to cast shadow maps, something the core materials can't do because they are limited by the need to support the old stencil shadows. But a brave mission maker, could recommend players to only use shadow maps on their mission and say, if a player wants stencil shadows they will have to accept that trees will cast ugly shadows. (I'm sure there's ways to automatically disable shadows for trees and such, when a user sets stencil shadows on, but it may take a bit of scripting madness...)

Indeed sad times.

I agree with @OrbWeaver, IMO DR is not the right tool to make models for Godot or any other engine using triangle mesh's only, if anyone wants a simple and relatively easy 3D tool (but still very powerful in the right hands) to make models, I personally recommend Wings3D instead, is free as Blender, way less complex (no animation/bones support) and it supports obj, collada, and other formats.

This is what I personally know about it: No diffuse means "skip the diffuse path code for this light" essentially means don't add/mix this light color/texture color info unto the surface, only use it as a simple b&w light. No specular is essentially the same but for specular textures, it skips the specular component/code/calculation and makes the light less heavy by removing the specular effect. About performance impact, for today GPU's, I don't think is as important as it was in 2004, but still, I'm sure it does have a small impact on performance, for the better of course, specially if done for many lights, but will also make them way more unrealistic. Btw lights with both no diffuse and nospecular, were used for the "projected shadows" or lights used to project fake "shadows" unto surfaces, this was used in Doom 3 to simulate basic, shadow mapping, for rotating fans and grid materials that use alpha textures, all because stencil shadows ignore those. Now that TDM has real shadow mapping, IMO such lights are less necessary and I wouldn't recommend their use for such effect. Thou lights with no specular and no normal mapping, are still useful for some effects, like simulating casting colored light from painted glass, like something bellow, and they are faster then normal lights:

Is all a matter of opinion and tastes but to me, Risen 1 was awesome, with its indie Gothic feel, I'm even replaying it today. Risen 2 was cool for many hours I most say but I reached a point, got bored and never finished it. Risen 3 somehow I never played more than 10 minutes of it, it just didn't get me.

What do you mean? If you are talking of the second par of brackets then in my experience, materials are done like this. [material name] { [global material options] { //material stage 1 or draw call 1 [local stage1 options] } { //material stage 2 or draw call 2 [local stage2 options] } ... } So those brackets are used to define individual material stages or "layers".

Oh that makes sense! I didn't thought of that, it was just that "ai_see" keyword throwed me off, because to me implied more "object is or not visible to AI", so I wondered why not put that in the object .def file or mark it in the editor with a spawnarg? But, yes now I see why, you may want to mark some individual surfaces as see through for AI, but still imo the keyword could be made more descriptive, for a material, like "aiSeeThrough" for example.

Glad it worked it means that is a global material token, btw those 2nd brackets are called "stages" and a single material can have more than one stage (draw call). But I still don't get the reason why an AI vision feature, is handle at the material level?! Normally you mark a entire entity/model invisible to the AI, not just a single surface on a model.

Not a TDM developer so perhaps that is how it works but why would such a thing as "ai_see 0" be a surface/material token?! That to me sounds more like something that should be on the light entity definition the .def file not the .mtr file, but I don't really know. Also if it is a real material token, try putting it at material global section, where the description is, outside the second pair of brackets.

Why? What did I miss? And personally I don't have the asset pack and if I add I would do what you demand. Just curious why you decided to do this.

Yes a gui editor would be cool but IMO is very easy to just have the game running the gui in real time, edit the code, press a key bound to reloadGuis and see the gui update ingame, in almost real time, that is the main reason idSoftware never did a gui editor. And the one the Quake 4 dev's (Raven software) made is unfinished (the above may explain why...), very bare bones and I don't recommend using it, specially in TDM.

My implementation is just a simple gui script cmd, is very naive and just follows the same system of other existing gui script cmds, made by idSoftware. I have zero idea if is synchronous or asynchronous that is beyond my expertise, nor if it is the same as done in Quake 4. Plus like I said above I do remember experiencing some small problems with it, when trying to use it to call more complex namedEvent's, that may be connected to the "synchronous or asynchronous" stuff.

There's ages that a wrote scripting for TDM or idTech4 in general but I think something like this should work. float objstate = $player1.getObjectiveState(objNum); if(objstate == OBJ_INVALID) { sys.print("warning invalid Objective found!"); } else if( objstate == OBJ_INCOMPLETE ){ sys.print("Objective is not complete. Please find all the apples."); } else if(objstate == OBJ_COMPLETE ){ sys.print("Objective is complete. Congrates you have all the apples!"); } else if(objstate == OBJ_FAILED ) { sys.print("Objective failed. The time to get all the apples as passed!"); } edit: modified the script code to be more correct according too @Dragofer suggestions bellow.

I updated for the new build and saw overly bright plates in "The House of deLisle" mission.

More or less, it doesn't save any real brush data in it, it is more like a "tag", is a peace of memory where info that should represent the entire "world" is defined and handled and brush data is "tagged" has THE worldspawn. Again is where all map data that should effect the entire map is handled, it is where the map script is run/called and other global stuff.

Afaik worldspawn is also a entity ( at lest in c++ it is a instance of idEntity), the only diference is that is a entity that represents all brush data.

Nice knowing you are looking at this. Btw when I made my own version of "namedEvent" gui cmd, I just copied the convention of other gui cmds like the "localSound" cmd, what I found is that it made the usage of simple nameEvents in GUI's very fast, with no need to mess with c++ and compile the engine. I think exactly the same reason quake 4 developers said they implemented it, thou like you said we don't know how they made their version. Perhaps is why I had some issues with my implementation when trying to call more complex onNamedEvents, so is something that needs to be well tested. Simple example of usage (the following code is untested and should be looked as "pseudo" code) windowDef Desktop { rect 0,0,640,480 backcolor 0,0,0,1 menugui 1 float "text_state" 0 onInit { // just in case ... if("Desktop::text_state" != 0) { set "Desktop::text_state" "0"; } } //*************** Events ************************* onNamedEvent ClearText { set "Text::text" ""; set "Desktop::text_state" "0"; } onNamedEvent SetText { set "Text::text" "Hello world"; set "Desktop::text_state" "1"; } //************************************************ windowDef Text { rect 240,41,165,110 visible 1 forecolor 1,1,1,1 text "" textscale 0.5 font "fonts/micro" textalign 1 } windowDef back_btn { rect (320-55),(240-35),50,30 visible 1 text "Click Me" textalign 1 textscale 0.3 font "fonts/an" onActionRelease { if("Desktop::text_state" == 1){ namedEvent "ClearText"; } else { namedEvent "SetText"; } } } }

yes but this requires that you make a copy of the original .def file where the text entity is defined, that I personally don't know where in TDM (in Doom 3 is in misc.def) and make a def folder for your own mission where you put the .def file copy (your copy will override the original def file, when your mission is played). see the new "text" default var entityDef text { "editor_color" "1 1 0" "editor_mins" "-4 -4 -4" "editor_maxs" "4 4 4" "editor_showangle" "1" "editor_rotatable" "1" "editor_usage" "Used to display debug text in a level" "editor_var text" "text to print" "editor_bool force" "if set to 1 prints always otherwise only in developer mode" "editor_bool playerOriented" "if set to 1 text always faces the player" "editor_var scale" "text scale" "scale" "0.25" "text" "default text shown for all text entites" "spawnclass" "idTextEntity" }

Sikkmod has some cool shaders indeed but wasn't the old ARB2 render totally removed in TDM and now only uses the modern GLSL one? At lest that is what I seem to have read some time ago. So if the ARB2 render was removed, sikkmod shaders will not work in modern TDM as is they would need to be converted to GLSL, don't know how hard that is.

This is why AAA developers have specialized lighting artists in house, is very important for the mood of a scene indeed.

Unfortunately many things in this engine are best done on the editor and then called through script, not created directly through script, one of them afaik is triggers. You normally create a trigger by creating a square brush on the editor manually, and give it the trigger_hurt material, so the size and shape comes from that brush, it also creates the physics (a clip model) automatically, then just need to use the script function, entity ent = sys.FindEntity("entity_name"); To get it and use it in the script to do whatever you want. Creating a clip model from script, is probably possible, thou I never did it, so I don't know how... thou I do know how to do it through c++. But I don't think there's any equivalent script functions exposed to the script system, if I'm mistaken please anyone correct me. Perhaps something to recommend in the TDM roadmap?