Stealth_HR

The radio isn't implemented, so A2AR isn't operational yet. As for the TACAN, poke around the channel dial. There are actually two wheels nested in each other and you can easily select a two-digit TACAN code - I tested it yesterday using Kobuleti (67X). The only thing I wasn't able to find is the X/Y selector, but it's in the X position by default and the TACAN needle is correctly tracking the emitter as I circle the airfield.

From what I can tell the ATC in DCS is supposed to give you info in whatever native units your aircraft uses. I don't think imperial units in your settings affect anything except your mission editor and the status bar in F2/F3/F4 views. Also, setting your altimeter to zero on takeoff doesn't help if you've got an air-start or if you're not landing on your initial airport! If you set your altimeter to QFE, you can accurately use your baro-altimeter instead of a radar altimeter (very handy in a Yak-52 which doesn't have one!).

When contacting ATC for takeoff or landing permission, the ATC gives the QFE in inches of mercury, while the Yak-52's altimeter uses millimetres of mercury. The bug is in .\Sounds\Speech\speech.luasince the list aircraftNativeCountry is missing a line: ['Yak-52'] = base.country.id.RUSSIA,The fix can already be applied DIY, I've uploaded it to the files section, but it would be nice to have it officially fixed.

Attaching today's crash log. DCS was updated on Wednesday to the latest OpenBeta version 2.5.1.16543.355, crashing persists. Attaching mission file as well if it helps the debug procedure. Attempted repair in the mean time, autoupdate_log file in attachment. Still running no mods and no reshade. dcs-log-20180429-f5e-crash.zip 2018-04-29 CS Cluster.zip autoupdate_log.txt

Here's hoping someone from Belsimtek can read this and give guidance. I haven't flown the F-5E-3 in a while and decided I wanted to get back into it around the time when the switch to 2.5.0 happened. I've had the issue since the first 2.5.0 open-beta build and it last happened today with the newest build (2.5.0.15365.345). With the first 2.5.0 version, everything worked as long as I was on the ground. From the moment I took off, about 45-60 seconds into the flight DCS as a whole locked up and can only be killed through Task Manager (or Process Explorer, which I use). It used to happen somewhere past the point where I retract the gear and the flaps. Thinking it was a problem with my installation (it was a 1.5.x upgraded and merged to 2.5.0) I reinstalled DCS completely from scratch, but didn't fly the F-5E-3 for a while. Today it happened much later after about fifteen minutes of air-time, after I've done several half-successful bomb passes at parked trucks. I just switched to using guns in M2 mode and made several hits. I'm not sure what my ammo state was and if there was any left. While I was doing a right-hand turn I experienced a game freeze and the only way to exit DCS was, again, to kill the process. I'm copying over the last few minutes of DCS logs if it helps: 2018-04-21 20:42:43.920 INFO Lua: Lua CPU usage: metric: average mission execution: 6.0253 % 2018-04-21 20:47:51.874 INFO TACVIEW.DLL: During the last 600.0s an average of 95 units objects and 0 ballistic objects have been active per frame 2018-04-21 20:47:51.874 INFO TACVIEW.DLL: The average frame rate of 57.6fps would have been 60.9fps if the flight data recorder was disabled 2018-04-21 20:47:51.874 INFO TACVIEW.DLL: DCS World simulation is taking 94.7% of CPU 2018-04-21 20:47:51.874 INFO TACVIEW.DLL: DCS GetWorldObjects is taking 4.3% of CPU 2018-04-21 20:47:51.874 INFO TACVIEW.DLL: Tacview recorder is taking 1.0% of CPU 2018-04-21 20:52:21.119 INFO Lua: Lua CPU usage: metric: average mission execution: 6.2590 % 2018-04-21 20:54:21.701 INFO Lua: Lua CPU usage: metric: average mission execution: 6.2972 % 2018-04-21 20:57:09.780 ERROR EDTERRAINGRAPHICS41: VaryHouse: failed to load fabric "fabric.tif" 2018-04-21 20:57:51.882 WARNING LOG: 4 duplicate message(s) skipped. 2018-04-21 20:57:51.882 INFO TACVIEW.DLL: During the last 600.0s an average of 97 units objects and 0 ballistic objects have been active per frame 2018-04-21 20:57:51.883 INFO TACVIEW.DLL: The average frame rate of 59.6fps would have been 63.2fps if the flight data recorder was disabled 2018-04-21 20:57:51.883 INFO TACVIEW.DLL: DCS World simulation is taking 94.3% of CPU 2018-04-21 20:57:51.883 INFO TACVIEW.DLL: DCS GetWorldObjects is taking 4.6% of CPU 2018-04-21 20:57:51.883 INFO TACVIEW.DLL: Tacview recorder is taking 1.1% of CPU 2018-04-21 20:57:59.937 ERROR VFS: Can't open file //models/tracer_bullet_yellow.edm.json. 2018-04-21 20:58:21.966 ERROR EDTERRAINGRAPHICS41: VaryHouse: failed to load fabric "fabric.tif" The F-5E-3 is stock with no additions (not even liveries). The lockups do not happen in other airplanes. I also created a minidump of the DCS memory, but I would need info on where to upload it as it's a 4.5 GB file. Any help?

I deserve it because I've managed to get a few friends interested in DCS, and one of them doesn't have a HOTAS at all. I've been using a TM HOTAS X for the past year that I've kept well maintained, so I would love to give my friend the X and at the same time upgrade myself to the FCS!

Brixmis, do you want a set of screenshots for the F-5E-3?

Can't wait to see this released. In bocca al lupo!

Dropbox says: Error (429) This account's links are generating too much traffic and have been temporarily disabled! Mod authors, could you please reupload the file to somewhere that's not dropbox, or another dropbox account?

Alright, bit of a delay, but the screenshots are here... definitely a global problem with the MiG-21. Hawk for comparison. http://imgur.com/a/cBUuc

Hi, uboats, checked the mod in 1.5.3.openbeta.steam, works well so far. One question about the rotating models, I noticed some planes are centered well and they spin around their center (like the BAe Hawk) while others are spinning around a point behind their tail so they look zoomed out in order to fit inside the box (like the MiG-21bis). Do you think that is due to the problem with the modelview component?

Yes, I would, for the sole reason that I'd finally be comfortable flying a prop-craft because there'd be no adverse yaw from the two engines.

Here's my pitch in. Nothing fancy, low terrain details, but hell of a time-of-day to fly.

Aaaaaaaand I just saw my score. Needless to say, must git gud. :D

Congratulations to the winners, you earned it! :D Hope to see the calculation worksheet next time, I'd like to analyze my own results.