Flappie

Fixed with today's update.

Thanks for your thorough testing! Devs recently explained to me why, on some maps, Petrovich is unable to detect any target, although they are standing in plain sight (especially over Syria and Cold Ware Germany). The cause is the same: the more terrain objects stand in front of Petrovich, the more trouble he will have finding valid targets. The detection system needs to be optimized. I'll add your findings to the internal report.

I've just asked Deka to take a look (the 071 is part of the China Assets pack).

The template issue is fixed internally. The fix will be part of the next update.

Issue reproduced and reported. Thanks for the heads up. By the way, I also tested REFDFOR: they are both named "1" instead of their full numbers.

Hi @hotstick. Sorry about the delay in my answer. I tried your script but I'm getting an error. So I tried to have it display a message ingame instead, but it did not work either (I'm not a script guy). function LuaExportStart() local OwnAirframe = LoGetSelfData() local Module = OwnAirframe.Name trigger.action.outText( 'Module name: ' .._Module,40) end function LuaExportOnHumanStart() local OwnAirframe = LoGetSelfData() local Module = OwnAirframe.Name trigger.action.outText( 'Module name: ' .._Module,40) end

Hi @Migow. Sorry about the delay, I kinda took a vacation from DCS bug reporting. I can't tell you if it's like this in the real thing, but it's like this in the Mi-8 module as well: the R-863 can always be heard, while you can only monitor the R-828 radio when you switch to it.

I've just bumped the internal report.

Thanks for your feedback.

@buceador Can you please confirm the issue was fixed?

No idea. We'll see once it's done.

I've just tried it in fake VR (I don't have a VR gear) and it looks normal to me. Was it fixed with June 3rd update, or is it just a matter of not using fake VR to reproduce the issue?

No problem: I've just been able to reproduce the bug in a SP mission. Issue reported. Nice investigation, I'll add your findings to the report.

Hmm, there is no truck in the track.

There's a recent internal request for a completely cloud-free preset, yes.

I tried your track and it worked just fine: the HQ-7 missile is fired, I am then switched to the MiG-29 cockpit, then back in the HQ-7 and there are 3 missiles left. Are you able to reproduce the issue if you replay this track?

Hey fellow Viggen pilots! I've been busy recording, listening to, then drawing sound codes that come from our beloved RWR in order to display them on a "map" the size of a kneeboard page. If you find any error, please send me a private message or ping me here. I'm aware a lot of equipment are not listed yet. I might start a second page someday. If you want to help me with that, go ahead! https://www.digitalcombatsimulator.com/en/files/3345141/ HOW TO READ THIS PAGE: Radar emissions are sorted by length, from shortest to longest. Each tone is represented by a colour. Scan tones are displayed in the top half of the page. Lock and Track tones are displayed in the bottom half. HOW TO IDENTIFY A RADAR EMISSION: Start by measuring the entire loop duration, which includes the silent part. If the loop duration is less than 5 seconds, look at the first "Scan" chart. If the loop is longer, look at the second "Scan" chart. Now, try to identify the sequence you're hearing, according to the estimated loop duration, the number of tones and their height. If there is no silent part, look at the "Lock" and "Track" charts and try to recognize the frequency you're hearing in order to determine what is interested in you... ... but you'd better close that kneeboard and use your afterburner third stage to get away from here already!!! EXAMPLES: If you're hearing "doo-DEE-doo-DEE ---------------------------------------" and the whole loop lasts about 2 seconds, it's an F-16 pilot scanning the area. If you're hearing "doo----------------------DEE----------------------" and the whole loop lasts 5 seconds, your are being scanned by a MiG-29 or a Su-27 variant. If the tone you're hearing is a continuous and very high-pitch "DEEEEEEEEEEEEEEEEEE", you're being tracked by a SA-3 or ZSU-23-4 unit.

@SimMotionTuning I've just bumped the report.

Sorry to revive this thread 9 years later... I've read that LegoHeli stopped making/fixing his liveries. I'm preparing a mission with some fake Draken. I badly need this livery, but it has several issues. Can someone please fix it? Nevermind: I've just found the fix @LegoHeli made in 2017 for many of his past M-2000C liveries: https://www.digitalcombatsimulator.com/en/files/2557363/ Many thanks to him.

Feel free to open a fresh report here: https://forum.dcs.world/forum/317-chinese-asset-pack/

@Schlomo1933 Hey, I don't see anything bad in your logs. One thing though: I see you have the K profile enforced in DCS. If you've been using what was advertised by a user a few days ago, try to use default DCS NVIDIA profile instead.

I've added this precious information to the internal report (CVN-73 unaffected).

You're welcome.

@Northstar98 @Red_Camarada This should now be fixed.

Hi @Pizzicato, this should now be fixed.