szut

There is a workaround on the Tobii website: start the Tobii Game Hub only once under DCS Main Menu. Disabling the launcher did remove the problem for me.

Hello, Thanks again for the spirit of the campaign - you manage to create a very good atmosphere in the campaign, and at the same time I like the focus on staying alive and navigating. One comment thought, is that I find the mission briefing may lack a little bit of information, particularly mission 7: A) I believe for this mission at least the bomb fusing selected is not provided. B) For mission 7 specifically, I trapped myself into not knowing where the target was - I feel like our good navigator could lead our eyes a bit more onto the target there ! I checked the PDF briefing after the flight and I found it was still a bit unclear where the target really is - I believe only the kneeboard provides some information about the exact target location, 1Nm East of <I don't remember the exact name, it begins with Y>. Perhaps it would help to point in the briefing where the recon photo corresponds to on the main map ? Those are nitpicking thought, after the P47 this campaign and your tutorial videos sold the Mossie for me, and I really enjoy cruising along in this nice twin and learning about oboe !

I had the issue also after trying to fly some Epson mission using the "economy" setting... I probably ended up with too low temperature / too high pressure too. I bought the Big Show campaign yesterday, so I hope the issue will be fixed someday. Thanks for the update and good luck tuning the thermodynamics equations !

Thanks for sharing your findings. I'll try to make the best of it to point my MiG-21 in the right direction.

@Leviathan677: Yes ! I began sims as a child, back in Flanker2 times. So I stick to an old gaming nickname...;)

Hi everyone, Following and inspired by the works of toertchen kid, Apache600,Fisherman82, Chuck's guide and of course Leatherneck, I decided to create my own checklist for the Viggen, by reformating and sometimes merging these works for my purpose. The template is somewhat inspired by the one used by the 476th FG, usually meant to be printed on A5 paper (A4 with 2 pages per sheet). I have not yet included the weapon checklist, so for now it only covers normal operation and CK-37 codes. Feel free to comment / edit / improve / redistribute as needed. Enjoy ! Szut DCS AJS-37 Szut Checklist_20190913.doc DCS AJS-37 Szut Checklist_20190913.pdf

This is totally my opinion too. The Gazelle flight model is probably build using a relatively simple code in which some of the coupling are either non-existant or way too heavily damped. What makes good test pilots different from average pilots is that they have the analysis capabilities and the engineering background to take a step back from what they see in a simulation. Even in the industry, getting constructive feedback from experienced pilots can be useless if steps are not taken to compare and substantiate the raw feelings with hard data. To defend Polychop, though, I do not think there are any relevant sources for the Gazelle flight dynamics.

I unplugged and then plugged again quickly my TFRP, DCS application crashed and produced the following bug report. I do not consider this bug as breaking the game, but still report it for robustness and because I know how it is to be a developer :). Regards, dcs.log-20180711-210327.zip

See attachment, a quick shot of my last flight (I am the MiG-29S above the AI MiG-29S flying without a wing... but with external stores). The AI aircraft had suffered combat damage (there was some smoke coming out of it). The mission was "MiG-29S - Over the Hump - 2.miz".

I would like to be able to see a basic flight log prepared automatically inside the mission editor summarizing the flight plan. Something like this (although the navaids are unnecessary): https://www.ivao.aero/training/documentation/books/PP_navlog.pdf Right now, when flying the MiG-21Bis or the MiG-29, one has to manually use the scale from the mission editor to get those informations (heading / distance to waypoint)... it would be more convenient to be able to copy it from the mission editor interface on a custom paper navigation log.