Search the Community

Hi everyone! Ok, I'm a great fan of Thief series that has been apart for years from the fans community... until now. Days ago I found the DDFix mod, then the HD Mod, and now this! Such a GORGEOUS mod guys, I have seen the demos! I can't wait to play it! Ok, but not that fast. After a hard time with the downloading (I live in the mountains and I connect to internet with a modem service in which I pay for every Mb downloaded), the game won't start. I get first a white screen when loading, and then a big black screen with beautiful and mysterious music (just to grow up my pain ). If I move the mouse cursor, I hear the sounds of the cursor being over the menu elements and I see some grey empty squares, without text. My computer equipement: - Toshiba Satellite (notebook), Intel DualCore T6500 2.10 Ghz processor, 3 Gb RAM - Windows 7 Ultimate 32 bits (Spanish). - External monitor Sony Bravia Smart TV (1920 x 1080 maximum). - Mobile Intel 4 Series Express Graphics GMA 4500MHD (128 Mb dedicated memory video). I have already search for this problem, and the only references to it which I have found involve Linux OS. The description of the bug is exactly the same, but the solutions are not applied to me. The only coincidence that I have noticed is that also involve an Intel Graphic card. I have tried also some editions of the file Darkmod.cfg and to replace the file tdm_base01.pk4 with another one patched for some Intel problem, but withou success. I needyour help guys, I'm about to break in tears. I feel I have all to play this game, but I don't have the knowledge to fix it by myself. Thanks forehand... Elojah.

Hi everyone! Ok, I'm a great fan of Thief series that has been apart for years from the fans community... until now. Days ago I found the DDFix mod, then the HD Mod, and now this! Such a GORGEOUS mod guys, I have seen the demos! I can't wait to play it! Ok, but not that fast. After a hard time with the downloading (I live in the mountains and I connect to internet with a modem service in which I pay for every Mb downloaded), the game won't start. I get first a white screen when loading, and then a big black screen with beautiful and mysterious music (just to grow up my pain :'( ). If I move the mouse cursor, I hear the sounds of the cursor being over the menu elements and I see some grey empty squares, without text. My computer equipement: - Toshiba Satellite (notebook), Intel DualCore T6500 2.10 Ghz processor, 3 Gb RAM - Windows 7 Ultimate 32 bits (Spanish). - External monitor Sony Bravia Smart TV (1920 x 1080 maximum). - Mobile Intel 4 Series Express Graphics GMA 4500MHD (128 Mb dedicated memory video). I have already search for this problem, and the only references to it which I have found involve Linux OS. The description of the bug is exactly the same, but the solutions are not applied to me. The only coincidence that I have noticed is that also involve an Intel Graphic card. I have tried also some editions of the file Darkmod.cfg and to replace the file tdm_base01.pk4 with another one patched for some Intel problem, but withou success. I needyour help guys, I'm about to break in tears. I feel I have all to play this game, but I don't have the knowledge to fix it by myself. Thanks forehand... Elojah.

Not so long ago I found what could make a pretty good profile picture and decided to try it out on these new forums. But I couldn't find a button anywhere that would let me change it. I asked on Discord and it seems Spooks also couldn't find anything anywhere. So I logged into an old alternative account and, lo and behold, that account has a button. This is on the first screen I get when I: 1) click on my account name in the top-right of the browser -> 2) click on 'profile'. Compared to my actual account: Are you also missing this button on your account? It'd be very much appreciated if that functionality could be restored to any of the affected accounts.

Since the Windows 10 upgrade is still freely available, and suspecting it would no longer be after Win7 support ends in January, I decided to bite the bullet and do the nasty. Also, my Win7 was beginning to hiccup. Hahahahahaha. One farking dead-end after another until it finally seems to be stable. Even dealt with the "white screen of death". Unfortunately, I needed to recover my Win7 back to a years-earlier recovery point before installing Win10, which lost me a number of programs which I am now in the process of restoring. Even though I've installed the Visual Studio 2017 redistributable package, I'm getting these errors when starting TDM: missing VCRUNTIME140.dll missing ucrtbase.dll I checked the Windows/System32 folder, and both dlls are present. Any suggestions? Thanks.

Yes, of course I see it. There is another problem, which bugs TDM since 2.06 maybe. When user saves/loads a game, the screen blinks showing some random things. There is also a long-standing issue 4967 on our roadmap about it, although it probably describes some different effects (but for the same reason). I agree that it is sad. While it does not harm anyone and has low priority, it makes the apparent difference between a polished game and WIP build.

When loading any mission, when the loading bar reaches approximately 50%, the screen blacks out for a few frames, then comes back and finishes normally. While this doesn't affect gameplay, it's something that didn't happen in 2.07, and it doesn't look very professional. I assume others are seeing this? Thanks.

4. Switch the 'lightning' light to parallel? Now wait a minute Isn't this an ambient light essentially? I mean, does it need shadows, or direction? If it does need direction, it should be parallel. If it does not need both, it can be ambient. Alternatively, we could use the current world size instead of the hardcoded 999999 One more option, the lightning could be implemented via a screen filter, or something

Sorry for going somewhat off topic but I've seen this problem before in fhdoom and it can be a clue for TDM has well. When using a custom post process glsl shader, a small window at the lower left corner of the main window shows up, the effect works in the small window and the rest of the screen gets like you said. I know almost nothing about shader coding, but it could be connected to the way id tech 4 renders the screen first to 640x480 then converts it to the users screen size after. Here is one of the shaders with problems, for those that want to see it. Btw this code was not written totally by me (just made changes to try blindly convert it to fhdoom), this is a modification of a shader from Total Chaos a free game (gzDoom engine), nice game btw and credit for it should be giving to them. Btw how do you hide text in the forum? (so the reply doesn't get so big) hope this helps. Global.inc #version 330 #extension GL_ARB_shading_language_420pack: enable uniform mat4 rpModelMatrix; uniform mat4 rpViewMatrix; uniform mat4 rpModelViewMatrix; uniform mat4 rpProjectionMatrix; uniform vec4 rpLocalLightOrigin; uniform vec4 rpLocalViewOrigin; uniform vec4 rpLightProjectionS; uniform vec4 rpLightProjectionT; uniform vec4 rpLightProjectionQ; uniform vec4 rpLightFallOff; uniform vec4 rpBumpMatrixS; uniform vec4 rpBumpMatrixT; uniform vec4 rpDiffuseMatrixS; uniform vec4 rpDiffuseMatrixT; uniform vec4 rpSpecularMatrixS; uniform vec4 rpSpecularMatrixT; uniform vec4 rpColorModulate; uniform vec4 rpColorAdd; uniform vec4 rpDiffuseColor; uniform vec4 rpSpecularColor; uniform vec4 shaderParm0; //this shaderParm's seem to be connected to the ARB program.local[0], etc uniform vec4 shaderParm1; uniform vec4 shaderParm2; uniform vec4 shaderParm3; uniform mat4 textureMatrix0; uniform int rpAlphaTestEnabled; uniform float rpAlphaTestThreshold; uniform vec4 rpCurrentRenderSize; uniform vec2 rpClipRange; uniform int rpDepthBlendMode; uniform float rpDepthBlendRange; uniform float rpPomMaxHeight; uniform int rpShading; uniform float rpSpecularExp; uniform int rpShadowMappingMode; uniform mat4 rpSpotlightProjection; uniform mat4 rpPointlightProjection[6]; uniform vec4 rpGlobalLightOrigin; uniform vec4 rpShadowParams; //x=minBias, y=maxbias, z=fuzzyness, w=samples uniform vec4 rpShadowCoords[6]; uniform vec4 rpShadowMapSize[6]; //xy = width/height of far plane, zw = near/far clip distance //TODO(johl): is width/height correctly set for non-parallel lights? uniform float rpCascadeDistances[5]; uniform mat4 rpInverseLightRotation; Vertex shader #include "global.inc" layout(location = 0) in vec3 vertex_position; layout(location = 1) in vec2 vertex_texcoord; out vs_output { vec2 texcoord; } result; void main(void) { gl_Position = rpProjectionMatrix * rpModelViewMatrix * vec4(vertex_position, 1.0); vec4 vertex_texcoord4 = vec4(vertex_texcoord, 1.0, 1.0); result.texcoord.x = dot(rpBumpMatrixS, vertex_texcoord4); result.texcoord.y = dot(rpBumpMatrixT, vertex_texcoord4); } Pixel shader/frag program #include "global.inc" layout(binding = 0) uniform sampler2D currentRender; in vs_output { vec2 texcoord; } vert; out vec4 fragColor; vec2 fixScreenTexCoord(vec2 st) { float x = rpCurrentRenderSize.z / rpCurrentRenderSize.x; float y = rpCurrentRenderSize.w / rpCurrentRenderSize.y; return st * vec2(x, y); } void main() { float samples = shaderParm0.x; float amount = shaderParm0.y; float dist = shaderParm0.z; float threshold = shaderParm0.w; vec2 texSize = textureSize(currentRender, 0); vec2 uv = vert.texcoord; uv *= 1.0 - uv.yx; vec4 src = texture(currentRender, vert.texcoord); vec4 c = vec4(src.rgb, 1.0); vec4 fsrc = texture(currentRender, vert.texcoord); vec4 fc = vec4(src.rgb, 1.0); vec2 tc = vert.texcoord; float size = 0.5; for(int i = 0; i < samples; i ++) { vec2 tc = vert.texcoord; size += dist; tc.x *= 1.0-size; tc.x += size/2; tc.y *= 1.0-size; tc.y += size/2; fsrc = texture(currentRender, tc); fc += vec4(fsrc.rgb, 1.0); } size = 0.35; for(int i = 0; i < samples; i ++) { vec2 tc = vert.texcoord; size += dist; tc.x *= 1.0-size; tc.x += size/2; tc.y *= 1.0-size; tc.y += size/2; fsrc = texture(currentRender, tc); fc += vec4(fsrc.rgb, 1.0); } size = 0.8; for(int i = 0; i < samples; i ++) { vec2 tc = vert.texcoord; size += dist; tc.x *= 1.0-size; tc.x += size/2; tc.y *= 1.0-size; tc.y += size/2; fsrc = texture(currentRender, tc); fc += vec4(fsrc.rgb, 1.0); } size = 1.0; for(int i = 0; i < samples; i ++) { vec2 tc = vert.texcoord; size += dist; tc.x *= 1.0-size; tc.x += size/2; tc.y *= 1.0-size; tc.y += size/2; fsrc = texture(currentRender, tc); fc += vec4(fsrc.rgb, 1.0); } size = 0.98; for(int i = 0; i < samples; i ++) { size += dist*2; vec2 tc = vert.texcoord; tc.x *= size; tc.y *= size; fsrc = texture(currentRender, tc); fc += vec4(fsrc.rgb, 1.0); } fc = fc /(samples*3); fc = fc - threshold; fc = clamp(fc,0.0,1000000.0); fragColor = vec4(c + (fc * vec4(0.8, 0.8, 1.0, 1.0))*amount); }

https://bugs.thedarkmod.com/view.php?id=5068 Sometimes, when going underwater, the shader responsible for blurring the view will shrink the image to roughly 1/4 of the screen (1/2 both horizontally and vertically) and position it in the lower-left corner, while leaving a jumble of textures to display in the background. This only seems to happen on rare occasions; My latest test suggest it occurs if the player has taken any damage and the health bar is showing up on the HUD. I'm running TDM 2.07 x64 on Linux (openSUSE Tumbleweed) with the free video drivers (amdgpu).

I guess that printing to the console and to the top of the screen would be the ideal, as long as there aren't an abundance of missing assets. Otherwise it would need a still obvious, but not as invasive, way to notice the error. Perhaps a frog could croak every time there's some warning, not joking ? That way it would be clear without affecting the game-play. Or just having an easy way to show the console in game...

I can repeat this BUT black is resolved by quick save\load, i.e. it's only black between map start and first load. Also, I can see the quick save/load adds draw calls and tri count. Is this what you see too? If so, it's probably related to BFG-style area\portal culling changes.

This matches what I’ve been seeing. Consecutive game starts w/o rebuilds might blacken the same textures, or the previously black sections might render normally and new sections turn black.

Interestingly, I don't see the problem where Grayman showed it in the training mission. But I see completely unlit pieces of walls behind "Keys and Lockpicks" and "Gamma and Brightness" doors. UPDATE: Doing vid_restart fixes those problematic sections, but breaks different places: they become completely black so that even lantern does not help. This is accompanied with GL_INVALID_OPERATION error spamming in console. I guess vid_restart is broken for a long time already, so no surprise here.

I am seeing the same issue in New Job mission, at the very beginning. Some sections of the floor are totally black, unless I enable a lantern (which lights them). Looks so weird, like if the world is partially disintegrated. Here is the video. Attached config file and console. Darkmod.cfg qconsole.log

I updated SVN to see if I could confirm the problem, but when I try running the game all I see is a black screen. I can hear the music and the sounds of the options, but can't see anything, even when trying to pull down the console.

That's a really poor analogy, since car mirrors are one of the core functionalities of a car. It's more like an FM being shipped with light gem being dark all the time. You seem to be great at dogmatic theories from decades ago, but you're out of touch with modern practice. That's how development works these days, for quite some time now. Project scopes change all the time. Deadlines move, people have to abandon functionalities or settle for less. They leave half-working things in the background, move items to the backlog, so they can work on them when time / client allows. There are select people that prioritize bugfixes, but again, noone in their sane mind would waste time on implementing something that makes non-critical errors critical, just to push people to work harder. And getting back to FMs and more personal projects, the practical side of things is, again, that the map can contain several thousands of entities. Missing even several of them (or missing textures, materials) is a low to medium priority fix. Might be a high priority if it's a plot item, but engine still will render a black box not sure whether it's frobabble. But technically, it still might be possible to finish the mission with a key loot model missing. If a texture or material def is missing, it will just turn black, so again, a high priority, not critical. Nothing worth crashing the game.

Alberto, I think we can introduce a cvar which would control warnings behavior. With possibilities: Print to console and do nothing else (like it does now). Print to console + show a few latest ones on top of the screen even with console closed (this already happens in debug builds, maybe there is even a cvar for it). Print to console + show last few, and produce a beep sound. Raise every warning to error. Errors throw exceptions, efficiently ending the current game session and going to main menu. Given the amount of already released missions, I seriously doubt we would ever have anything except p.1 as default. But we could at least recommend more annoying warning policies to mappers when they are close to finishing their maps.

I'm noting other problems which I'll post issues for once we're up and running again. One of those is related to this one: textures for some non-frobable objects (worldspawn and func_statics) aren't being painted. The same textures will be missing through several dmaps, then suddenly they appear again, and different textures go away. It's as if a) the texture can't be found (though other surfaces with the same texture are fine) or b) the surface is behaving as if no light--not even ambient--is touching it, so it's painted black. In favor of the "texture not being found" thought is that on one load the loading screen was black, as if it couldn't be found. There are no missing texture warnings. Will file an issue with examples when we're back online.

This just started today with my update of SVN to 15737/8388 followed by a rebuild. Some textures (not limited to the door texture shown) are painted black in-game. (Working fine prior to the latest update.) For textures on frobable items, normal highlighting appears when the item is frobbed. For textures on non-frobable items, the texture remains black regardless of distance from the object. Backing away to turn off highlighting paints the texture normally. Anyone else seeing this?

Personally I have a 3D screen and I don't play games that way for the most part, I don't even remember the last time I played a game using the 3D capability of my screen, but for VR I comprehend why people would want it. Btw idtech 3 (quake 3 engine) if i'm not mistaken has stereo capabilities perhaps someone with good knowledge of rendering code could see how it was done back then? Or even see how BFG does it? On my basic comprehension on how this stereo stuff works, it could be made by rendering two views (using two player cameras?!) with a small separation between them, then you just, interleave them for a 3D screen (like mine) or you color one view red and the other cyan for all screens, how that would be done on code is for a rendering programer to think about.

It looks like it's the heat haze, and not smoke particles, that's showing the problem. Okay on 2.07 hotfix. Black on SVN Hardware is NVIDIA GeForce GTX960. CHecking for latest drivers ...

Sorry, I don't know where to look. Here's a screenshot with your .cfg (minus gamma/brightness) Do particles turn black for you? What is your video card? Are you on the latest driver?

Doom 3 \ TDM's affinity for low color saturation aesthetics or even black and white shader filters... Means that red-cyan glasses would probably work better for us than with other games...

Red-cyan mode works on any screen, it's the only mode that does. However it messes up the colors a lot so it's less than ideal. For VR the mode that's needed is side-by-side stereoscopy, one view on each half of the screen. It doesn't even need to be rounded with lens distortion as you see in most cases, though you will need to increase the FOV by roughly 50% since the lenses only see a part of the screen in the middle so it would appear very zoomed in. The HUD also won't be visible since you generally can't see the screen edges, all panels would need to be moved around the crosshair where they're easier to see... here's how I made a VR friendly HUD in Xonotic using the builtin editor:

https://bugs.thedarkmod.com/view.php?id=5055 There seems to be an issue with shadow rendering in the engine: When enabling both Stencil Shadows and Soft Shadows, shadows get incorrectly mapped and are stretched across the screen in front of the camera. I have no issues when using Stencil Shadows without shadow softness, nor when using Map Shadows both with and without soft shadows. I'm running TDM 2.07 x64. My operating system is Linux openSUSE Tumbleweed x64. Kernel 5.2.14. Mesa 19.1.7 (amdgpu module). My video card is an AMD Radeon XFX R9 390. I attached two screenshots from the FM Full Moon Fever: The first shows stencil shadows without softness (normal results) and the second is stencil shadows with softness (corrupt shadows).