stgatilov

Could you please add a line seta logFile "2" to the end of Darkmod.cfg file and then try to reproduce the crash again? It you succeed, immediately save the contents of qconsole.log located either at fms\ac1 or fms\arena (depending on which FM was installed when the crash happened), You can either attach it renamed to .txt file or post its contents surrounded by spoiler tags in square brackets. I would be happy to hear any more details about how and when it happens. The current details look weird (64-bit-specific 2.07 crash... hmm) I started these two missions recently and did not see any crash. Where is your TDM installation located? Can you e.g. create a txt file there without UAC/admin dialogs, or delete some pk4?... Which OS you use?

I need help from someone else with this one. I can confirm that the problem does not happen with Maps shadows, and that it does not depend on softness. Moreover, it does not depend interaction shader, so this is issue is purely about stencil shadows themselves. It is worth noting that the quads which are blacked out are not aligned with mesh triangles. In fact, they are usually located around some mesh vertex and affect only parts of surrounding triangles. Changing r_fboDepthBits did not help (maybe it does not work?). Setting r_shadowPolygonFactor 1 slightly reduced the size of quads, but clearly an unrealistically huge offset is needed to remove them. So it does not even look like a depth precision problem. I have a feeling that it is related to computation of shadow volume geometry. I wonder what has changed between 2.06 and 2.07 in this regard?... About previous versions of TDM. The issue also happens in both 2.05 and 2.06 x64 (they behave seemingly equal in reproducing the issue). To see the problem on the beds, take a candle in that room, get close to some bed, crouch, and move candle around. With some positions of the candle, you see the same artefacts. However, TDM 2.07 seems more prone to this issue, and you can see it bold even without moving/toggling anything. Also it is interesting to know the history of the bed and the toilet meshes. If they are core and exist for a long time, then the issue should have been noticed already. If they are custom and mission-specific, maybe changing mesh serve as a workaround if we fail to find better solution.

If I understand correctly, this code says the opposite: // translucent automatically implies noshadows if ( coverage == MC_TRANSLUCENT ) { SetMaterialFlag( MF_NOSHADOWS ); } else { // mark the contents as opaque contentFlags |= CONTENTS_OPAQUE; } Aside from that, translucent shadows do not fill depth buffer and are rendered at different --- all of that is probably not important...

I'll check the GLSL shader against ARB-converted one. Probably some saturation dropped again.

I suggest filing a feature request. If you add links, it would be great.

Like a year ago: in theory, it is compatible. People play TDM regularly. Plus there are beta testing phases (one of them is going right now) with emphasis on testing all maps. However, I suspect that FM coverage is not very high during beta-tests. There is no strict plan like "we have to test every FM when releasing new version" (like it was long time ago).

No, this is not that problem. It's not just AI alerts messed up. The whole statistics is completely blank, even gameplay time and number of saves. I have also seen it, but don't remember how I got it (maybe I did tdm_finish_mission).

Did you really calculate this size according to instructions? It should be about 30 MB, I think.

Yes, you are absolutely right, it is an entirely different problem then. Maybe try different versions of shadows implementation (Maps/Stencil, Soft/Hard). Can it be a problem with model normals (although I cannot imagine how bad vertex normal could affect single quad) ?

Please report which exact version of TDM you used a) when dmapping your map, and b ) when running it. Report it both 1) for the state in the past where you got no problem, and 2) for the newer state where you get missing geometry. Please reopen 4877. Explain where to get the exact .map file with the problem (I guess it is beta-tested map), and report coordinates of the places where geometry is missing (the more = the better). The coordinates can be obtained by writing getviewpos command in game console.

The new version beta207-04 is up on the URL: http://tdmcdn.azureedge.net/beta207-04

New version (codenamed beta207-04) is ready for update. The changelog is here, as usual. Please pay attention to any AIs which you are already dead / knocked out by the time you discover them (there should not be any with the new version). Also check out how AIs sit/lie on various chairs and beds. Another domain which needs extensive testing now is mantling, which has been changed a lot. Check out mantling as is, and combined with crouching/jumping. Check it near ceilings and in places where there is not much space. Check it in water, on starts and ropes, etc.

That's exactly where I got the idea from. rsync needs special server, but there is zsync which downloads over HTTP. It looked too Linux-specific, so I rolled my own equivalent. Anyway, the current plan is to switch to a different synchronization algorithm which is tightly integrated with zip file format.

Savegames are usable. We can do a bit of time-travelling if it is absolutely necessary. Also, developer can take source code of that version directly. Just note which version you were using (either SVN revision from game console or codename). But the most convenient information on a stable map is: 1) Which mission it is, and 2) Your exact location (execute getviewpos in console to get it).

I think the current SIMD memory copy is weird. Using MMX for copying memory is stupid this day, and in 64-bit mode it is excluded anyway (no MMX). Someone should replace the MMX version with the SSE one. To be honest, I think custom memcpy should accept a flag which tells if the copy should be cached or not (or implement two versions). SSE has ordinary writes and "streaming" writes, and which is faster depends on circumstances (and the first one is faster in most cases).

As a matter of fact, now the updater works with the official TDM beta-testing location. See updated point (2a) of the original post. Note: remove the tdmupdate_tdmsync.exe that you have already downloaded and download the updated version. Otherwise, updates from TDM beta-testing location won't work.

Created 4940. Caught into this myself by noticing that most of women are off before I even find them in Crucible Omens. For instance, here is Lazarova, which was "drunk as dead" when I found her:

My personal "thank you" for this map! While it is not a "mission" at all, it is fun to play with! I did not even imagine we already have so many AIs Moreover, it will serve as a great test map for TDM team P.S. noticed a problem with bumpmap on the walls of the arena:

Lowering "Render Scale" slider in the upcoming TDM 2.07 is a good way to decrease GPU load. while sacrificing image quality. But if you are limited by CPU, then it won't help (just as downscaling images won't, I think).

I think there are tons of weird behavior with dead bodies and such. I often see knocked out women remaining on their feet in ragdoll state (while chest going horizontal). I noticed that if you take a rat corpse in the goal location of Rat's Triumphant and move it into wall/floor, than it starts crazingly fast rotations. Please post which mission it is and which exact location (getviewpos) it is. The behavior can depend a lot on coordinates. A config file may also be worthy.

Happy New Year! Interesting to see that I'm not the first one to meet New Year here (with my GMT+7)

GUI nicety is definitely missing. The prototype was created by applying minimal changes possible to make the update work. Of course, no GUI was added: only the existing one remained.

Yes, I saw this. Doesn't matter right now. FM files rarely change. I wonder what those 116 MB megabytes are. I'm afraid my mirror is working weird sometimes... Do not remove keep-mirrors! You did a very ordinary update to 2.06 release: all pk4 files which were different were downloaded from scratch. The codename of TDM 2.06 is release206, that should be put instead of e.g. beta207-01 in tdm_mirrors.txt. Check out the original post, codenames release206 and release205 are available in addition to beta packages. If you have not noticed that, 2.07 installation is about 340 MB larger than 2.06 release (starting from the very first beta). So this is quite expected download size. That's normal. You can probably try to set OpenAL settings in another place?... Or remove the need for alsoft.ini with integrating HRTF on/off switch into TDM That's expected. When a release package is created (whether it is beta or final release), a differential update from the previous release is created. When beta207-03 was generated, differential update from release206 to beta207-03 was created. You can use it only if you have exactly the "from" version, and it carries you exactly to the "to" version. When you updated from TDM 2.06, stock updater applied the differential package. When you updated from previous beta, it simply downloaded complete pk4 files which were changed.

I tried to run updater from TDM 2.06 on my beta installation (not exactly the same environment, should not differ). The self-update worked properly. I guess a log file is needed from our side (the one saved just before you click "Restart" for the first time).

The problem with testing package is resolved. Well, it turned out that there was no problem at all You can now freely use tdm_update to get new beta package. In fact, it is advised to run tdm_update now just to be safe. The new beta release beta207-03 is available. The summary of changes is available here. After update, please make sure that cvars are: r_useFBO 1 and r_fboSharedDepth 0 The problem with heatHaze materials and depth-reading material stages is resolved. Adding maskDepth keyword to such materials is no longer necessary (is it was in 2.05). The keyword has been removed from all corresponding stock shaders. Please test various heatHaze/translucent/postprocessing materials with the new beta, with antialiasing off (and also test a bit with AA on). Another thing which needs serious testing is the Linux build. Whoever runs native Linux build, please check how Alt+tabbing works in various modes (Windowed/Fullscreen). One known issue is that some Linuxes has "Alt" as a hotkey, which somewhat messes with Alt-tabbing. P.S. And if you are feeling lucky, you can try to get beta207-03 via tdmupdate_tdmsync prototype. It greatly reduces download size for beta207-02 to beta207-03 update. Just make sure to configure tdm_mirrors.txt properly and enable two checkboxes if you do so.