Search the Community

Awesome! Post is up! https://forums.thedarkmod.com/index.php?/topic/22200-beta-testing-the-house-of-delisle/#comment-487365 Thanks!

Hi guys, through the "cheats" topic I got the idea, that it would be quite useful, if there were tags for missions (the post was about removing the killing restriction in some missions to suit the prefered play style). I don't know how easy or difficult this is, but with them, it would be quite convenient to pick missions with playstyles, environment, etc one does want to use. This could also be expanded to other mission properties. I remember a discussion about climbable drains, handles on doors, that cannot be picked and other things the map author chooses for himself. That way these things would be clearer and as I said before, it is easier to choose missions with playstyles that suit oneself. What do think?

Hi, I'm Biel Bestué, and I've been trying to contact Lloyd for his liquid physics code. there is another lad that goes by the name of Motorsep (he is the mastermind behind Steel Storm a GPL game made with a Quake1 engine port), he also has tried to contact Lloyd for this code. We intend to release the liquid code as GPL, but since we weren't unable to contact him, we've though of contact you guys, is the liquid physics code GPL in your amazing mod/game? and would you see any trouble from me extracting that part of the code from yours and release it as GPL? all credit given of course! my take on mods, is that I like to create GPL code infrastructure so other people can use it, as a way to give the oportunity for the people to test, play, and change innovations in the idtech4 / BFG engine, as well as grow from it. and liquid physics seems to be another chance to release one of such things.

id Studio did a poor job in defining its categorization of variable nomenclature, so in subsequent documentation and discussions there are divergent views (or just slop). In my series, I had to choose something, and went with what I thought would be clearest for the GUI programmer: Properties, which are either Registers (like true variables) Non-registers (like tags) User Variables (also true variables) I see that your view is more along these lines (which perhaps reflects C++ internals?): Flags (like my non-registers) Properties, which are either Built-in (like my registers) Custom (like user Variables) Also, elsewhere, you refer to "registers" as temporaries. I am willing to consider that there could be temporary registers during expression evaluation, but by my interpretation those would be in addition to named property registers. I'm not sure where to go next with this particular aspect, but at least can state it.

To clarify, you can sell code under a GPL license, but the license requires you to release all of the sourcecode in a form people can compile it, and it retains the license. So practically you can't stop people from just taking the sourcecode, possibly changing some things, compiling it, and independently releasing it for free. Also, outlets like Steam really don't like GPL licensed code because it puts them at risk. And they already mentioned that all of the game assets are strictly non-commercial. So idTech4 derived things aren't the best platform for a commercial game. That's separate from what our team thinks. I don't think you'll get much objection from us for trying. The whole point of GPL is to give people the most freedom to do what they want with the code under it without past devs standing in their way. Even that said, it probably wouldn't go over well if you just blatantly copied massive chunks of the game straight. One guy that had been on the team was doing something like that for a commercial project and got some pushback and grumbles. But that would have been different if he had been an outsider doing a completely different project with a very different look and feel and they just needed the base to build from. That would be more respected. But, again, that's aside from the issues above.

The *DOOM3* shaders are ARB2 ('cause of old GeForce support) carmack plan + arb2 - OpenGL / OpenGL: Advanced Coding - Khronos Forums

Doom 3's fog design is pretty strange. It re-uses the light architecture to define the volume but it treats the player as the "light_center". The projection image is then projected outward from the player's eyes. From that description ( via the GPL source ), one would expect the "lightFalloffImage" would have an effect on the outward density from the player? From old doom3world.org discussions I recall that it was claimed that the falloff image instead defines the vertical density of the fog in relation to the real light_center. Thus, one could potentially make the transitions smoother by making sure the falloff image was darker near the boundary areas via estimating the radius distance to the real light_center. Not very practical. Looking over the code, I do not even see where lightFalloffImage is handled by fog. It seems to only get the projection image and "fog enter image" that is auto-generated in image programs so I think lightFalloffImage is ignored by fog? https://github.com/TTimo/doom3.gpl/blob/aaa855815ab484d5bd095f347163194ac569abcc/neo/renderer/draw_common.cpp RB_FogPass // find the current color and density of the fog lightShader = backEnd.vLight->lightShader; regs = backEnd.vLight->shaderRegisters; // assume fog shaders have only a single stage stage = lightShader->GetStage(0); ( nbohr1more: doesn't the lightFalloffImage count as a stage? if so, what happens to materials which include it? ) // texture 0 is the falloff image GL_SelectTexture( 0 ); globalImages->fogImage->Bind(); ( nbohr1more: why are they calling a projection image a falloff image ? ) // texture 1 is the entering plane fade correction GL_SelectTexture( 1 ); globalImages->fogEnterImage->Bind(); ( nbohr1more: this image is auto generated, is it somehow altered by lightFalloffImage ? Not that I can tell ) qglDisableClientState( GL_TEXTURE_COORD_ARRAY ); qglEnable( GL_TEXTURE_GEN_S ); qglEnable( GL_TEXTURE_GEN_T ); // T will get a texgen for the fade plane, which is always the "top" plane on unrotated lights ( nbohr1more: this seems to track with the Doom3world description of "vertical density" but is it really controllable ? ) fogPlanes[2][0] = 0.001f * backEnd.vLight->fogPlane[0]; fogPlanes[2][1] = 0.001f * backEnd.vLight->fogPlane[1]; fogPlanes[2][2] = 0.001f * backEnd.vLight->fogPlane[2]; fogPlanes[2][3] = 0.001f * backEnd.vLight->fogPlane[3]; // S is based on the view origin float s = backEnd.viewDef->renderView.vieworg * fogPlanes[2].Normal() + fogPlanes[2][3]; fogPlanes[3][0] = 0; fogPlanes[3][1] = 0; fogPlanes[3][2] = 0; fogPlanes[3][3] = FOG_ENTER + s; qglTexCoord2f( FOG_ENTER + s, FOG_ENTER );

Thanks, I can also recommend gog galaxy. The idea of the custom tags is really nice, I'll have to try this out too!

Keep in mind also that mission size, and complexity have increased dramatically since the beginning. For a lot of veteran mappers, it can take over a year to get a map made and released. The last dozen missions have for the most part been pretty massive, with new textures, sounds, scripts, models etc. We seem to be long past the point of people loading up the tools, and banging out a mission in a few weeks that's very barebones. We still do see some of those, but I noticed in the beta mapper forums and on Discord, that mappers seem to make these maps, but don't release them, and instead use the knowledge gained to make something even better. Could just be bias on my part scrolling through the forums and discord server though.

YOU TAFFERS! Happy new year! Deadeye is a small/tiny assassination mission recommended for TDM newcomers and veterans alike. Briefing: Download link: https://drive.google.com/file/d/1JWslTAC3Ai9kkl1VCvJb14ZlVxWMmkUj/view?usp=sharing Enjoy! EDIT: I promised to someone to write something about the design of the map. This is in spoiler tags below. Possibly useful to new mappers or players interested in developer commentary.

Seems to confirm: https://bugs.thedarkmod.com/view.php?id=5718 does it happen in the latest dev build: https://forums.thedarkmod.com/index.php?/topic/20824-public-access-to-development-versions/

https://github.com/HansKristian-Work/vkd3d-proton/tags <- directx 12 wrapper for dxvk https://github.com/doitsujin/dxvk/tags <- directx to vulkan wrappers D3D 9 to 11 eg. dxvk if you want to try it with horizon zero dawn you need to copy out dxcompiler.dll from Tools\ShaderCompiler\PC\1.0.2595\x64 and bink2w64.dll from Tools\bin and place them next to HorizonZeroDawn.exe. then copy over dxgi.dll from dxvk and d3d12.dll from vkd3d and place them next to it to. now fire up the game and let the shaders recompile -> profit.

TTLG? That's Through the Looking Glass Forums. A looking glass fan community. Has been around for a long, long time. https://www.ttlg.com/forums/

I think the reason the dev forums exist is to provide a place where the implementation of features can be discussed without getting mixed up with other debates when someone believes what the devs are doing is wrong. We often post public discussion threads for features with subjective elements like the frob outline, because community feedback is very important. But there will always be vocal defenders with strong views for or against certain features, or how exactly it should be implemented in their opinion. At some point a decision has to be made and be carried through, which is what the dev forums are for. Almost all of the threads are very technical, basically explaining and discussing recent or potential code changes with other devs. Its hard to say. Its a hobby the devs do in their spare time, so people come and go when they're in the mood and when they have the time. The team page is mostly accurate except for some relatively newer additions like myself.

I just read@motorsep Discovered that you are able to create a brush, then select it and right click "create light". Now you have a light that ha the radius of the former brush. Just read it on discord and thought it may be of use for some people in the forums here too.