Cpt.Rookie

I landed and logged off. And as you've damaged me before, you got the kill. Nice flying (:

I guess it is now quite late, so just fyi, I wrote a dumb utility which purpose is exactly to check for any extra files that user might have in DCS installation directory - http://forums.eagle.ru/showpost.php?p=2281569&postcount=112, so full re-install can be avoided. Currently, it contains list from patch before the latest one, but judging by this thread, it really might be useful to rewrite it so it will use list of files that is used by the DCS's repair utility (that is autoupdate.dat, I guess) as it seems that extra files are causing troubles quite often.

For the post-flight analysis, I would definitely recommend TacView utility (http://lomac.strasoftware.com/tacview-en.php). It gives you enormous amount of information to study, especially in cases you're wondering, how the hell did that guy managed to get on my six when I was starting in higher altitude, with bigger speed and behind him. It works just nice on currently most populated server - Dogs of War (http://forums.eagle.ru/showthread.php?t=133245)

Bumping as this is easily reproducible crash bug. Anyone from ED QA to confirm this and log to internal bugbase eventually?

edit: Utility below is obsolete, use the new version from now on - http://forums.eagle.ru/showthread.php?t=137438 I take it now that integrity checks are temporarily disabled, so if you'll be able to connect, we'll know that integrity check is the root cause. However, if you won't be able to connect after they will be enabled again and repair didn't help, then there will be probably some extra files or directories that are failing these checks. As mentioned, repair will not delete them, so user don't have much choices about discovering what is the problem. To help a little with this task, I wrote a dumb python script that will check all the files and directories in DCS installation directory and will compare them with default, clear installation. Options: 1] You know what python script is and you know how to run it - download script - download list - save these two files into same directory (right click and "Save link as...") - run extra_file_checker.py path_to_dcs_installation e.g. extra_file_checker.py C:\dcs - note that if there is a space anywhere in path to your installation, you need to enclose the path in double quotes ("C:\games\dcs world") 2] Py... what? - download zip package - extract it somewhere - start command line - in command line , go to the directory with unpacked zip archive - run extra_file_checker.exe path_to_dcs_installation e.g. extra_file_checker.exe C:\dcs - note that if there is a space anywhere in path to your installation, you need to enclose the path in double quotes ("C:\games\dcs world") Either way, extra files will be printed to the console + to file results.txt (created in the same directory as the script is) Notes: - the list is based on my clean installation. At least clean enough to connect to both DoW servers - you can ignore about three files with name of ...Spain\Troops\10� escuadrilla.png. They will be always printed. - if you have your DCS installed in some really cool directory that contains non-ascii characters, the script will probably not work at all. It is just a dumb one. - if this will really help someone, I might think about rewriting it in a way that it will be using file autoupdate.dat, which seems to contain all the necessary data in neat SQL Lite format. - if there will be some other problems with running my script, feel free to contact me via mail/jabber cpt.rookie [at] gmail [dot] com (I don't want to spam/hijack this thread) - I scanned all the files in zip package via virustotal.com, so I'm quite sure there is no hidden surprise. But of course feel free to re-analyse them.

Unfortunately I really don't remember what exact files did I have to delete; it is possible that integrity check is failing on any extra files in directories that are being checked (not sure about the exact behaviour). The obvious solution of last resort is uninstall and deletion of any files that might have left after uninstallation. With having user's setting backed up (C:\Users\<user_name>\Saved_Games\DCS), it could be relatively painless one. Or, once (if) we'll know what exact directories are checked, delete these exact directories and run the repair (which should re-download them). And one more thing - today, I noticed that DoW servers are no more allowing objects to be exported (allow_object_export in network.cfg), thus you cannot see the other airplanes in TacView log. While I'm aware that having the export turned on could allow people to cheat, I still think that ability to have a flight log with all the data (speed, alt, Gs, ...) recorded is really great feature. Especially if you're flying in formation with someone and at least trying to use some tactic maneuvers. You can of course create these TacView logs later, when replaying the track, but we all know how "reliable" these tracks are.

During yesterday's session on TS (what a bunch of amazing people there!), I learned that there were enabled several integrity checks on both DoW's servers. The effect was almost immediate - I realized that I'm not able to join one of the servers. Disabling all the mods via JSGME and running repair didn't helped me - I was still getting "Connection Interrupted" error message (which is little bit cryptic considering that it actually means that there is either game version mismatch or integrity check failure (but I guess there is nothing you can do about it)). In the end, I used open beta (for which I was dead sure that I wasn't putting any mods whatsoever into it) and compared the whole directory structure between regular DCS installation and open beta one. Doing this, I realized that before start using JSGME I manually installed mod that was putting some extra EDM files to particular directories. After deleting these extra files, I was able to join both of the servers. I'm not sure if there is some more easier way how to check what files are causing integrity check to fail. So to prevent anyone else having similar troubles - I would like to ask whether it will be possible to let us know what particular directories are subjects of integrity checks? And by the way, thank you very much for altering the weather in River Riders mission - it is definitely easier to start the P-51's engine now.

Setup: clean installation no mods Steps to repro: P-51 or TF-51 spawn (or climb) at altitude where 2nd supercharger mode is engaged (e.g. 25 000 ft) RPM to max, throttle to max throttle to min decent to altitude when supercharger mode is changed from high blower mode to low blower mode crash Logs attached. Video - Logs.zip

Definitely something that 1.2.12 brought up. Even when engine is properly warmed up, oil pressure is still too high and it is impossible to keep it in the green area.

There is actually one nice topic for that - http://forums.eagle.ru/showthread.php?t=134084