stgatilov

According to the log, you should have proper 2.05 version. I could suspect that probably you run 64-bit version, forgetting that 2.05 did not have one. But your log suggests that you did a clean download, so you should not even have the 64-bit executable. I tried to update from same address starting with 2.07 installation. I see version 2.05 both in menu and game console after update. Maybe you should disable you antivirus and run the updater again with same settings.

Yes, it is most likely 2.06. Do you have a tdm_update.log? Where exactly do you see 2.06? Could you attach condump? Could you post tdm_mirrors.txt?

Oh, please, don't be so strict! Any bug report or feedback is welcome! I only wanted to spread the word about that wiki article: posting the link in appropriate conditions is the only way to make it known over time. In fact, the article was not even present at the time this bug was initially reported

The problem was finally diagnosed by developer only because one of the victims posted config file I believe a lot of problems would be diagnosed faster if reporters attached all the typically needed information. 4797 already done: the bright future will start somewhere at 2.08-to-2.09 update

If you mean fresh TDM 2.05 install, then tdmsync prototype is probably the easiest way. Copy your current TDM installation (no matter which version), then downgrade it to 2.05 with tdmsync updater.

I think we can leave the cvar as it is now. I'm afraid with the current pace of changes config reset is necessary after every TDM update to avoid issues. It is not clear if tdm_update should remove it automatically, because it may contain something player wants to save. One example is custom key bindings, although in the current SVN they are stored in a separate file (meaning that starting from 2.08, config reset will not destroy key bindings). One possible approach is to rename darkmod.cfg into darkmod_old1.cfg, darkmod_old1.cfg into darkmod_old2.cfg, etc every time tdm_update is run. This way player will not loose information completely, but is forced to config reset by default.

A minor note: TDM 2.07 hotfix has been finally released. The old ("original") 2.07 version is no longer available (except by tdmsync prototype). To everyone having TDM 2.07: Please run tdm_update to make sure you have the latest version. Note that savegames from any kind of TDM 2.07 will load properly in the latest/hotfixed version. P.S. And please execute r_useFBO 1 in game console and make sure this cvar stays enabled.

A brief update on issues: White compass: please set r_useFBO 1 (either in game console or in darkmod.cfg) and make sure it stays so (comment). If it does not help, please report to the bugtracker issue. Loading crashes: there is a way to bump maximum number of events to fix it (link), but I'm afraid it will only be released with 2.08. For now, deleting the whole FM directory and downloading it again (to ensure you have latest version 1.21) is the better workaround.

Please open game console and execute: r_useFBO 1 Alternatively, perform config reset (i.e. delete darkmod.cfg and start TDM). It should fix the problem.

0) Ctrl+Alt+Tilde should open game console. I cannot reproduce anything like this on my GPUs. 1) Could you attach console dump? I see you have a video recorded. 2) Is it possible to download it? P.S. It's better to put darkmod.cfg contents inside

Try to change this line of darkmod.cfg: seta r_multiSamples "16"To: seta r_multiSamples "1"Then try again to see if it helps. Also you might want to change: seta r_useFBO "0"To: seta r_useFBO "1". Or if you don't want to go through all this trial-and-error, then reset your darkmod.cfg: 1) Copy this file to safe place 2) Delete this file 3) Try to start TDM again If only this part helps, then you may want to move all the "bind" lines from your old config to the new one to save key bindings, then just forget the old config.

Could you attach your darkmod.cfg ? I'll try to reproduce it on my AMD card. Also, did you update to 2.07-hotfix? P.S. I think I have heard this complaint for many times lately.

Ignore the error. As long as TDM starts without nasty message boxes, you are OK. UPDATE: And if TDM does not start, then is not related to vcredist. Report when and how exactly it fails. Provide condump and darkmod.cfg for a check.

The text you see IS the file you want to download. So you can either right-click the link and choose "Save Link As" and save it near tdm_update.exe, or left-click the link and then do "File"->"Save" (Ctrl + S) to save this text into a file named tdm_mirrors.txt near the tdm_update.exe. You may try to execute r_useSoftParticles 0 in game console and see if it helps. This article explains how to open game console. P.S. You should probably attach darkmod.cfg and condump. Just in case there is anything suspicious there.

Reported this as issue 5030. Nbohr1more, please copy your findings about reproducibility to there.

I'm afraid that's on coding department. Also, I think it is not mission-specific, just a nasty bug of 2.07. Just created an issue: 5030

This means that the crash is happening inside your video driver (Intel Graphics, I suppose). It may be due to issues with your driver, or due to TDM doing something incorrectly. Updating graphics driver is definitely a good idea. We have a bug-reporting wiki article. Please provide darkmod.cfg, condump. If you can record and share crashdump, it would help a lot.

Could someone please write down what the issues turned out to be? Was it only the default sound (s_playDefaultFile) which was loud and annoying? Or there are some sounds which are too loud? If there are, which are they?

I have reported issue 5028 about crash during game load. On my side the crash is so reliable and unavoidable, that it makes the mission unplayable.

That's strange. I tried it on StLucia map (new game) on 2.07 hotfix, and I saw compass both while scrolling through inventory and by clicking V. As far as I remember, you cannot actually "do" anything with it: you just select it in the lower-right corner, and it shows you where is north relative to your current position. Also tried on various builds of SVN, compass works fine. Is the problem perfectly reproducible?

I think virtualbox is overkill. Better wait for someone who already has the setup for proper testing.

Ignore that. The build being tested does not need redistributable, so I will remove this part from tdm_update. The main thing is that the updater started, downloaded a bit of files, and finished properly (aside from this warning). Right? I think we can stop here. I wish to hear some more feedback from testers with Linux. In the meantime, if someone takes time to briefly test this on Windows 7 --- that would be helpful (just to be sure).

Please download new version, and overwrite all the stuff with its contents. Then try again. Yes, please. This will be a good test case.

This is in no way 2.08 beta. I simply build some TDM binaries and kindly ask players to test them. This thread will go down by itself after a week or so, I guess.

Due to technical issues, I had to rebuild TDM and create another beta package. Unless something wrong happens, it will become the new 2.07. Please update as described in the first post, and check that 1) it still works, and 2) old savegames are loaded without warnings.