Search the Community

As soon as I started, I was hooked. Intro, our thief's reactions (can never have enough of those), cutscenes (YES!), dialogue with NPC's... It was great. And the further I went, the more it opened up. Overhearing conversations, a freaking tape recorder?! I found a very sus table in the pantry, and thought that maybe I need to light the candle, which did nothing. But you gotta admit, that looked like a puzzle of sorts. Turns out I was overthinking it... I too completely missed the hidden "chest" with the second book, only after coming here did I went back and found it. , but it's sad that Mage's readable turned out to be only partially true. =D Thank you for your work and release!

I think it's a good idea if done that way - a new light asset that mappers can use. Seems to lend itself especially well to streetlamps. Could be fun to use. I might try to make one using stims, just for schitzengiggles.

Welcome to the forums Ansome! And congrats on making it to beta phase!

That's why last night I went with the idea of making new lamps with this mechanic: They should have transparent clear glass casing and show the light bulb inside, making it obvious they're different and can be shot. Something like this should make them easy to distinguish: Indeed I run into the painting problem myself: I always check every painting to see if it highlights and can be looted. Then again it's the same with doors in some FM's, which don't use a special door handle to make it clear that's a decorative door and not one you can go through.

Hey there, question - Is there a way to temporarily hide the "diamonds" in the rendered view without hiding the light effect? (for screenshot purposes) - pic attached. - DeeP

We didn't make the holidays (such a busy time of year) so here's a New Year's gift, an unusual little mission. Window of Opportunity Recover an item for a regretful trader out in a wilderness setting, and discover more! Available within the in-game mission downloader or: Download: http://www.thedarkmo...ndetails/?id=79 Alternative: https://drive.google...WTMzQXZtMVFBSG8 Some unorthodox gameplay on regular/ghost difficulties. (Arachnophobes might prefer short mode...) Please expect to need your lantern in regular and ghost modes! Short ("easy") mode is a smaller map, so if you are looking for areas others reference below, or 100% of the loot, you'll need to play on another mode. I wanted to create my first mission before I became influenced by too many others' ideas, and limited myself to what has been done before. As such, this mission is not set in a city/town, and has some features that are likely to be provocative. There's a section some really like, which others don't, either way I kept it short to not last too long. That being said, I hope you do find it fun! :-) Special thanks to those who provided valuable testing and feedback: Goldwell, Kyyrma, plotzzz, 161803398874989, PPoe & Bikerdude (who also contributed a sound). (Please remember spoiler tags to not expose things meant to be discovered by playing.) Like so: [spoiler]secrets[/spoiler] If you are having trouble finding the main objective, here's what to pay attention to in the mission for hints: There is a spot it's possible to get stuck on the ground in the corner by the cliff/rockfall where there's a rope laying on the ground, please take care if you poke around there!

It's okay! I'm down with any option hence why I asked. But I agree: Most players would likely not approve of such a change being done retroactively and affecting all old FM's, so it would likely be best as a derivative entity for mappers to use in the future based on new or existing lamps that can provide one. In any case it would likely require engine changes, not something you can currently do with a script: Lights already use their own hardcoded script classname which can't be overridden. Even if it weren't for that I don't think there's a way to intercept broadhead arrow collisions and check what kind of surface they hit, even with the Stim / Response system. There should probably be two new spawnargs: A breakable boolean enabling the feature on an entity, and a skin_broken to specify the skin used when a light was smashed.

This kind of mechanic would break a ton of existing FMs. Some (I dare say even most) mappers often choose electric lamps so that they can't be extinguished or turned off, forcing the player to time their movements through the light. There are of course switchable electric lights, but that is up to the author on how they want to implement those. It would definitely be fun to see an FM implement this Splinter Cell-style mechanic, where the mapper has designed their map to function in such a way, but to add this as a core feature would break the gameplay of countless maps

Sounds like a good idea to me. I'm all for breaking glass, also windows (the "penalty" is that it should be very loud to A.I. So, a thing you surely will only do very rarely.). I think this will take a lot of consideration on the mapper side, though. Amount of arrows in the starting gear and in the mission itself, consideration where to put destructable lamps, and where to avoid them. Not to mention that I don't know how much effort has to be put in the technical side (making the lamp destructable and killing the light it sheds). Thinking about it, I think it kinda defeats the "stealth" element, doesn't it? Why would you make loads of noise and possible alert half the A.I. in a mission, for pretty little benefit? A thief surely will do everything to avoid that kind of noise and attention.

I think there is no problem with noshadows parallel lights: they are well-defined in the current engine. It can be used as local light to brighten the window, as @HMart does. I hope there is no reason to have shadows in this case? The parallel and parallelSky are almost the same thing, except that parallelSky traces light beams from areas containing portalsky world surfaces, while parallel traces light beams from the area where light origin is located, which is never what you need for a global parallel light (like moonlight). There are many missions where this issue is hacked around, and all of them result in issues like double lighting if door is open, or lack of lighting in some outdoors areas. And there is no way to fix the engine to make these missions work properly --- the maps themselves are wrong. If you want to do a global parallel light, the parallelSky is surely what you want to have, and parallel is most likely not. But note that to make parallelSky work you also need to follow some rules. The issue with local parallel light is that objects outside light volume can cast shadow over objects inside light volume. This is pretty weird by itself: you move object closer to light volume, and at some point its shadow instantly turns on. The engine determines whether object intersects light volume approximately (using bounding boxes and such stuff), so whether you get shadow from an object close to light volume or not is implementation-defined. Today you have no shadow and it looks nice, tomorrow culling is changed and the scene gets unexpected shadow. So the bottom line is: Global parallel lights should use parallelSky and follow some rules. Local parallel lights should be noshadows. All the rest is not well-defined: you'll avoid a lot of trouble by avoiding it altogether.

I'm seeing the weirdest thing on my map, not public yet but I have the case for testing: Not only does the light leak, and it does so even as I've textured the walls with shadowcaulk... a light actually leaks only while the door is closed, once I open it the undesired light goes away. It's the glow on the left side of the door and little triangle it casts on the floor in front of it. I think it might be the light at the right shining through though, not sure if it's the light in the newly opened room. The interesting thing is opening the door makes it go away, also using shadowcaulk over mere caulk doesn't seem to matter which is quite odd.

Though this is related to PBR as a component in getting it done right (like reflection probes) I thought it's an improvement of its own that's worth discussing. I don't know if this is implemented or estimated in some form, but working with light entities in my own FM's I haven't seen any spawnargs for it so I presume it's not. At the moment lights in TDM act as zero-scale points, light sources have no actual radius. I know what you might be thinking: Of course lights have a radius, it's the box that decides how far a light shines and what it affects! What I'm referring to is not the range but the emission radius, representing the scale of the bulb itself: Think of it as a minimum radius... at the moment lights only have a maximum radius, the minimum is currently a point. In modern engines this affects both specularity and shadow softness as well as how the light is distributed. Like most engines we shouldn't need anything more than a float describing the size of the bulb, a simple sphere ought to be enough... given we already work with radius boxes, we could instead use a separate box which would give us better control with unevenly shaped bulbs. Every default light entity should of course be updated to use this: Torches / candles would set it to the average size of their flame particles, gas / electric lamps should have it represent the scale of the light bulb or the lamp head. If done right this can greatly improve our graphics and add more realism, but as with most things it's not going to be that simple. Also this would create changes to the lightgem in all FM's but very minuscule ones that shouldn't even be detectable. There's 3 different components I presume we have to tackle independently. Soft shadows: Shadowmap softness is probably the easiest, just add the average bulb radius to their value. Specularity: At the moment all lights seem to produce specular orbs of the same fuzziness on shiny surfaces. What we probably want is for lights that keep their min radius 0 to produce a fully sharp orb or dot, softness is added to each light's ball based on this radius. Light projection: The biggest aspect is changing how light is distributed, the projection texture / falloff material would emanate very differently. Everything inside the bulb would shine at the intensity of the center pixel and should start fading from the min radius toward the max, the projection texture would get slightly inflated like a balloon. The best solution (which also accounts for blur) seems like a 2D shader that copies the light texture onto itself at slightly different offsets to make it fuzzy: There's already a blur filter that does just that when you're underwater for example, we could to get away with doing the same thing to light textures using the min radius as the offset parameter. As lights typically don't change scale, this should be possible to do only once at map start rather than every frame including for moving lights like torches, this way we should have no performance loss.

Beta 11 Fix finished-on state auto-update was unreliable Slighty improve scanner title/author detect Tags are now named some whatever regular-version-looking thing to force GitHub to put the newest at the top

This case in Poets and Peasants is something new: In this case we have on same line: light brush wall fully closed room closed door with visportal in a brush wall player Since only backfaces cast shadows, only the door and the first brush wall can cast shadows. The brush wall does not cast shadows because the entirety of its area is unreachable by light. So the door should. It turns out that all doors that are connected to visportal should automatically get this "forceShadowBehindOpaque" flag. When the door is closed, it closes the visportal and thus becomes part of the wall, just like a brush would be in its place.

DarkRadiant does not care about engines at all, it only cares about file formats. Whether you can use DR with your Godot-based game will therefore depend on whether your game's assets are arranged in the same way as TDM. More specifically: Your game will need to read map data from the Doom 3 .map format. If it does not, there will be no way to save your map from DarkRadiant in a form that your game can access. Export to OBJ is available but if all you want to do is produce OBJ models then DarkRadiant isn't the right tool for the job (you should use a proper 3D modelling app like Blender/Max/Maya/LightWave etc). Your game assets will need a tree of .def files defining important entities to be placed in your map, including certain "fixed" entity types which are used directly by DarkRadiant itself. There will need to be a light entity defining light volumes, a func_static entity defining a static model, an info_player_start entity to define the starting position, a speaker entity to define sound sources, and probably several others. If these entity types are not defined, then built-in features like "Create light" and "Place player start here" will not work correctly. Your game will need a tree of .mtr files defining material shaders, referring to image paths which will be resolved to either uncompressed .tga files in a textures/ hierarchy, or compressed DDS files in a dds/ hierarchy. If these material shaders are not defined, no materials will appear in DarkRadiant. DR does not make any attempt to load "raw" image file hierarchies which are not referred to by material shaders. Your game will need to define a hierarchy of 3D models in ASE or LWO format. No other formats will show up in the model selector. These models can be stored directly on disk (there is no "model shader" tree required like with materials).

Since I'm bored and haven't posted in a while and yet still finished Thief 4 a few times, I feel compelled to post. In response to a number of observations @Rio_Walker made: Seeing your hands and all the animations newGarrett would do was fun... at first. But given all the looting and environmental interactions the game has it really did slow things down a lot, especially when the game would occasionally realign the player just perfectly before playing an animation to open a drawer. If they had an option to disable these animations or speed them up significantly I'd have been happy. I've played using the Custom difficulty with the option to disable focus and the experience is kinda mixed. While it does make things a bit more traditional without the superpower ability to find loot more easily, it does seem like the game is designed very much for focus and disabling it can hide things you never even knew were present. If it weren't for the focus for example, I would never have noticed the "special" candles hidden around the city that talk when you light them. This game reminds me of a movie that has been reshot several times with footage from separate reshoots blended together with bad editing. It's painfully clear the story has been chopped and changed over the many years of its development and there's assets in the game that clearly had greater importance in a previous iteration but for which their plot points were cut. The most obvious example is the automatons. There's a dude who provides missions on obtaining pieces for one he's building, but apart from that there's also signs in other areas they had more importance (e.g. you see rooms full of them when going up an elevator, the Baron has disassembled ones on tables in his cutscene, etc.) Some plot elements just feel not fleshed out because they had to cobble together something to create this Frankenstein's monster of a game from so many elements. The ending sucks and is incredibly abrupt. Do we even know what the deal is with that half-built ship? Probably another abandoned plot point. With all of its problems, I still kinda like it in so far as its general gameplay. But it doesn't have the longevity of something like TDM or the classic Thief games especially with all the user missions available for them. Oh well, maybe I'm just pining for what it could have been in the hands of a better developer.

In my mission, there is a script that is supposed to display a message if a player is damaged by an explosion. It didn't work because health stays at 100 even when the light gem shows damage was taken. at the start of script I did this; PlayerHealth = $player1.getHealth(); sys.print("Start health = " + PlayerHealth + "\n"); and it reports 100 (or less if player is damaged already) after the explosion (more) damage is taken per light gem, but this; PlayerHealth = $player1.getHealth(); sys.print("health now = " + PlayerHealth + "\n"); Still shows the value recorded before damage was taken. So how do I test for actual health?

Been looking forward to this for ages but am very disappointed with the start. Dying Light 1 had/has the best climbing in any game I've ever played. BUT the start of Dying Light 2 is a scene where you have to climb up to a ledge. Two sessions and 90 minutes later and much frustration, I've still not succeeded. Endless failure is NOT the way to start a game! What am I missing? Move and jump. Fail. Move and jump. Fail. Move and Jump. Hey, I'm up a step! Move and jump. Fail. Move and jump. Fail. Move and jump. Hey I'm up another step! Move and jump. Fall. To my death. Start again. Repeat 50 times. In different places. I got within 8 metres of the guy above but still couldn't reach him. By contrast, the parkour training in DL1 was much more fair.

Normally the aiSee property is set on the light entity, and in this case the property has been set on the light's material. The property sets whether the light makes things more visible to AIs, so its not meaningful to set this property on model materials. If you want to stop AIs from reacting to an object you need to disable its visual stim, and if you want AIs to be able to see through it you need to give it a material that doesn't contain visual clip. Id say we can be grateful someone had the foresight to implement this as a material keyword, too, in cases like this one where you probably can't set spawnargs.

Regarding worldspawn "forceAllShadowsBehindOpaque" set to "1", it doesn't seem to get restored on game load. To reproduce (works with any fixed mission using "forceAllShadowsBehindOpaque"): Add "forceAllShadowsBehindOpaque" "1" to the worldspawn in the map file. From main menu, "Start this Mission" or "Restart Mission". setviewpos Notice that the light leak is fixed (not present). Save game. Load game. Notice that the light leak is present (not fixed). Example 1. From main menu, "Start this Mission" or "Restart Mission". 2. Run setviewpos. 3. Save game. 4. Load game.

Thief's Den 3: Heart of Lone Salvation 1736.48 3691.68 -137.75 -5.4 101.1 0.0 Light leak: No light leak:

You cheeky nandos. XD Have you not considered using the screen? She walks behind it, there is a shadow of her lifting her arms, the light flickers - POOF - model swap, she steps out clothed. Although, there had to be something preventing the player from walking behind the screen. I liked how you handled her undressing to begin with. What startled me earlier tho, along with creepy music while the Builder's priest sings in the background, is the dress mannequin... with human hands.

I've idly wondered if you could have a monster that reverses the light gem. That is, it can see you in darkness better than in the light.

Oh yes: I have both sight and hearing set to Forgiving. I didn't think that would be related: IIRC it only affects the multiplier for how much being seen in light or heard while making noise increases the alert level per event. I should test on a higher alert level too just in case: I tend to be sloppy and impatient thus I used that for years so I wouldn't get caught all the time on more difficult FM's (lots of guards in tight areas with lights you can't turn off). I have noticed an aspect that does work well: If you're making noise by running even in darkness, alert AI will head toward your direction while searching, they won't go around randomly but actually care where the impulse came from. The problem is that this doesn't seem to scale over larger distances: If they briefly see you in broad light at a distance enough to draw weapons, AI won't head toward your general direction but begin searching their own vicinity... and at least on Forgiving the same happens if you shoot a broadhead arrow at a guard's helmet: I still think the guard should actively run toward your location instead, not exactly where you are but they should go to that road or barge into the same building.