Bagpipe

Changed nothing and it fixed itself. Weird. Maybe a restart or something i dunno. Anyway, we are now rockin and rollin with the correct version again so all is well at last Thanks for your help

Yes only default defender and no other av software. Yes restarted several times trying to get it to work. Exclusion is set correctly but somehow it keeps blocking this file from installing and i need to do the whole process again each time i try. (i.e. downloading, unpacking etc.)

Hi, I have already tried all of the slow repair and rebooting and what not several times. The update goes fine until this file attempts to install and then, somehow, defender flags it even though the DCS folder is clearly excluded. Should I try excluding the dcs updater utility folder too? It doesn't make sense to me to have to but at this point I am trying anything

null

Please can someone take a look at the attached log and advise. I have the entire DCS install directory (E:/DCS World OpenBeta) set as an excluded folder with windows defender and I also excluded the DCS saved games folder for good measure. I ran a slow repair and it updated...something...but then the next update (because I am way behind in updates) is throwing up the same issue and defender still flags this "wacatac" file as a severe threat though when I allow it, the installation still fails. It is very frustrating and my head hurts pity me autoupdate_log.txt

you will be hearing from my legal team XD

I just did the above while climbing 10 degrees at 300 kts. Stuck it on 090, engaged AP and flicked HDG mode FWD. Held it fine, booted the burner on and it fought the asymmetry and held 090. Then back down to idle and then cut the right engine and put the left into burn and it continued at as close to 090 as it could manage.

Had a quick search for any similar posts but could not find any. I noticed while doing the Syria Dances with wolves Instant action that when/if the tomcat takes damage there is a bug, at least a visual bug, where the wings flicker between swept and extended very fast. It's hard to say what effect it has as the pilot tends to blackout shortly afterward. Is anybody else experiencing this? In this case I only tested the A-model and the damage was from guns only, not sure if relevant. Can try and get a track if required but should be fairly simple to reproduce.

Well looks like every Tom rick and harry continuing to badger them got the job done folks. Thanks for chiming in

.

Thanks for the update, I just reinstalled the Yak the other day so will check it out!

Oh drat, that is a long time to forget about posting something eh! lol I have gave up the VR for now tbh, too much strain on the neck for an aging potato like me. Time flies!

Standby instruments probably

If I were you I would email ED support directly and ask the question. It will be up to them to improve the TDK after all. If you create a support ticket it needs to be looked at and answered in some form.

try a different AV program if all else fails

have you tried just simply running a repair using the updater to see if it makes a difference?

Think I better knock, knock, knock on wood

yeah i have not tried hot start, all have been cold start and allowing the oil to heat to 40+ prior to runup tests. I guess for now i just avoid the runup tests and see how it copes without. I feel like the tests overheat the oil and once it is past a point there is no saving it

Out of interest, have you attempted to do the run up test at all? I cannot get half way through it without sending the oil temp off the gauge.

The issue now is that you still cannot make it through the run up test checklist provided without exceeding the suggested parameters/temperatures. Which indicates something is still not being simulated adequately. Would the prop wash provide some air flow through the oil cooler when opened during a run up test? There has to be some reason that you can do it fine in the real Yak but not quite in the DCS Yak. I wonder if the weather settings, wind etc, would have an impact. Will have to play around in the editor to test that I guess. Will watch your track this evening

Hi, I'm a different guy, totally not the same guy as posted above ... My Yak happens to be starting fine , however, I am finding that the oil temps continue to max out regardless of flap settings etc and that I do not have to prime at all in order to get a perfect start. I take it there is still work ongoing on the systems? yaktest.trk

I ran a quick repair. Will run the slow repair (groans) and check keybinds and see if it helps. If not I will post a track, cheers EDIT: omg it was the air cock. *insert expletives ad nauseum*. Clearly the one time i got it running i remembered to open the valve Please delete post to save my precious ego

IGNORE THIS PART NOTHING TO SEE HERE MOVE ALONG Since the recent update I have excitedly reinstalled the module to try out the temp simulation from cold start but now I have managed to get it to start once and then it cut out and won't start again even if I reload the miz, load a new miz or really do anything at all. First couple of attempts did nothing when the starter button was pressed. Third or Fourth attempt worked, got it running, warmed up, started testing then took the throttle too far back and choked it out. It has not restarted in any mission since. I am painstakingly following the extremely simple start-up checklist to the letter each time and the prop just will not crank when the starter button is pressed. I am clicking to open the starter button cover (no keybind). Possibly worth noting as I saw there was an issue with the keybind function reported recently. The front and back seat's magneto switches are not sync'd by default. Could this be an issue? Is there some kind of a persistence system being worked into the module that is preventing it from working after a mission restart? I am not running any mods at all so it's not that either. @Flappieare there known issues that the devs are aware of and if so could you let me know? EDIT: tested the flap cover keybind too and it is still broken. I can open it using the "toggle" bind but it won't close using either "toggle" or "CLOSE" binds nor will "OPEN" open it etc. I am just wondering if the flap cover logic is preventing the starter button from being "pressed"? IGNORE THIS PART NOTHING TO SEE HERE MOVE ALONG

THE YAK GOT AN UPDATE!!!??!?!???! Waited so long for this and I completely missed it in the patch notes Off to test it out, Happy Christmas to all and to all a Good Night!