al531246

I'm not sure about this anymore. Look at these images I've been analyzing, you can clearly see this 'block' at the top of the lollipop every time it's a friendly emitter. Original image with the lollipop highlighted; You can see the 'block' at the top of the 18 RWR symbol, I think we can safely assume this is an F/A-18 and as such would be considered friendly. And again you can see the same thing in this image for what is almost certainly an E-2 Hawkeye; There's definitely some sort of IFF at play here. The documentation for the ALR-67(V)2 states the following; This confirms the system is able to differentiate between friendly and non-friendly emitters, most likely through pre-programming the threat library before mission start. I'll continue to search for more images and video with these friendly RWR symbols in.

I'm having the same issue here on Persian Gulf. I've added the code to the autoexec.cfg to get the extended logs. The issue seems to be here, these are the only errors in the entire log; 2018-09-01 16:40:50.361 WARNING ANIMATOR: Asimp: 3.3 2018-09-01 16:40:50.369 ERROR EDCORE: Can't mount bazar/effects/particlesystem2/overwingvapor/. Drivers errors: 2018-09-01 16:40:50.369 ERROR EDCORE: FSDriver: there is no directory bazar/effects/particlesystem2/overwingvapor/ 2018-09-01 16:40:50.369 ERROR EDCORE: ZipDriver: Can't open zip archive bazar/effects/particlesystem2/overwingvapor/.zip. 2018-09-01 16:40:51.122 INFO SOUND: XAudio2: channel layout: Headphones/Stereo 2018-09-01 16:40:51.124 INFO SOUND: Using SSE FTZ/DAZ mode. 2018-09-01 16:40:51.131 INFO DCS: gDescription: "NVIDIA GeForce GTX 970" gVendorId: 4318 gDeviceId: 5058 gMemory: 4043 MB 2018-09-01 16:40:51.144 ERROR EDOBJECTS: Destruction shape not found AVIASHTAB_CRASH 2018-09-01 16:40:51.350 ERROR EDCORE: Cant open file: /models/bk_90.edm.json. 2018-09-01 16:40:51.389 ERROR EDCORE: Cant open file: /models/rbk_250_ptab_25m_tail.edm.json. 2018-09-01 16:40:51.453 ERROR EDCORE: Cant open file: /models/rbk_500_255_ptab_10_5_tail.edm.json. 2018-09-01 16:40:51.476 ERROR EDCORE: Cant open file: /models/rbk_250_tail.edm.json. 2018-09-01 16:40:51.980 INFO EDCORE: (dDispatcher)enterToState_:1 I've ran a cleanup & repair and all the rest of it. Still no luck. DxDiag.txt dcslog.zip

I do sort of understand the frustration in reading the manual, it gives me a bit of a headache but the problem isn't the font. I think it's the traced outline of a Viggen that lies underneath the text on every page. You've essentially got lines running all about and through the text. That's where the issue lies. It needs to be a plain white background, that would be much more pleasurable on the eyes. Other than that the manual is gold. It's spot on.

Yeah, that makes sense.

After many hours of research I think I've worked out the HUD RWR system for the AV-8B. To begin with I can say RAZBAM's simulation is 95% correct. There are 5 key points I will note below, if anyone has contesting evidence please let me know. 1) The HUD RWR cannot be turned off, see the RWR rotary on the right hand side of this image. With the rotary off the ECM page will not function. 2) HUD RWR is limited to 6 threats at once I cannot find any documentation, imagery or video showing more than 6 threats on the HUD at any one time. All documentation shows a maximum of 6. Also EWM (Electronic Warfare Menu) page which works very similarly to HUD threat display only displays 6 threats. (see page 23-48 in the NATOPS) 3) The three HUD RWR symbols are as follows; Non-lethal Lethal Critical 4) Unknown and friendly emitters always appear as Non-lethal threats. I think this is achieved by the RWR analyzing the emissions for IFF codes before going onto the HUD? 5) I think non-lethal threats only appear for 5 seconds on the HUD after detection. I'm not certain about this though.

I'm convinced there is a button that enables / disables HUD RWR but I cannot find it. I've got a lot of AV-8B documentation but so far as I've read none of them mention an option to toggle it.

RAZBAM, the RWR threat ring labeling and position is incorrect. You have 3 bands; Nonlethal Band - search radars and other radars not capable of launching missiles Lethal Band - radars within active tracking range, not necessarily locked onto you though Critical Band - radar is within engagement range, can also be here if the radar has launched on you From inside to outside it should run; Critical, Lethal, Nonlethal. As for HUD RWR I'm not sure exactly how the stem's should appear. I have a couple videos but I don't know if they're nonlethal, lethal or critical threats. https://i.imgur.com/BlHRjvF.mp4 https://i.imgur.com/yJ2DRUz.mp4

Brilliant!

Seems that way. It's the same the weapon placement issue on pylons (mk.82's and stuff clipping through the pylon). It's a one line fix in the AV-8B.lua, takes 1 minute to fix. The Harrier has been abandoned.

What are you on about?! Nice derailment, now go away.

3 questions; 1) are you referring to the 'bomb impact circle' appearing on the HUD during the run in? 2) Were you using retarded bombs? 3) Are you on stable or OpenBeta branch? If the answer to all of them was yes I've had the same issue but the problem was me! I didn't quite realize how low you really need to be for it to appear. If I'm talking about something completely different then my apologies in advance!

GBU-38's (JDAM's) usually do miss by a couple of feet. There are aiming for a grid square, not a target vehicle or whatever. They're only as accurate as the grid is. GBU-12's (Paveway's) on the other hand should always hit bar there being any serious wind. For a GBU-12 it's simply release then lase. That's all there is to it. The best advice I can give you is to read the manual.

One with front row parking?!

Dude, it's quite obvious you're out of your depth here. There exists a multitude of documents, videos, images and books all confirming what we believe to be true, that the simulation within DCS is incorrect. A few were posted in this thread but removed under rule 1.16. You haven't cited a single source for your hypothesis and you will struggle to ever find one.

Found some evidence to back up your claim in A1-F18AC-NFM-000 from September 2008. Rule%201.16 Rule%201.16

As much as it pains oneself to label the module as dead or forgotten about I do fear it is quickly becoming the case. Update after update I see semi-functional additions being made and less than a handful, if any, bugs being quashed. Some of which have existed since release and shouldn't take anywhere near this time to fix. Take the RWR sounds for instance. I find it most odd that after almost a year RAZBAM is yet to fix this essential feature that comes without issue to every other module. But amateur DCS players managed to work it out amongst themselves. This is to say the very least, shameful. Another example could be the placement of the dumb bombs and rocket pods, they clip through the pylon. See this image for reference. This can be fixed in less than 5 minutes by editing the AV8BNA.lua located in CoreMods\aircraft\AV8BNA and going to line 426 and beyond. Why am I able to figure this out and fix it but a professional development team cannot? Yet another example would be the bombing interval programming. Since release this has been non-functional. Again I don't understand how such an essential and basic feature like this can be shelved in place of features like the VREST page. I do question who is making these decisions?! Early access is not an argument for these failings. 2 of the issues I've listed have been diagnosed and fixed by the players themselves. I could list these until the sun goes down and comes back up again. I don't want this to be seen as a crushing morale blow to RAZBAM. You've got an excellent module on your hands but you must remember to walk before you can run. Implementation of new features should not be a priority over fixing basic issues. My $0.02 on the matter.

Can confirm, one is witnessing similar issues on my end.

Can you cite a source or some proof for this claim?

Sure about that? https://forums.eagle.ru/showthread.php?t=201489

11/10, best bug report ever made.

Your video shows a bug in of itself. The launch tone is not meant to be that strange sound. What you're hearing there is the sound file replaying itself hundreds of times a second. It's supposed to be one solid sound. This is the case for the new guy tone, lock tone and launch tone. This has been an issue on the Mirage too since it first released. So as it stands both the M-2000C and AV-8B have broken RWR's. I suspect it'll be another 10 years before it's fixed at this rate.

In this video you can clearly see search mode activated and the SA-2 has launched on the aircraft.

It's broken, very broken. Both CCIP and CCRP functionality are broken.

Has it? Standing in your garden exposes you to more radiation than a DU round!

The tone you're hearing is the release tone. It can be activated by the pilot in the stores page. The chevrons can be set to a custom depression by the pilot. For takeoff they are set to 14° high.