RAZBAM_ELMO

As determined by SME, sound is correct. Labelling AS INTENEDED and moving to resolved.

Perhaps, but unfortunately we don't really support exporting displays, most is all designed to work around a single screen or a pair of VR goggles.

Thanks for the effort you put in, I was having trouble with the forums but it has been reported.

For future reference, you should use supporting material from the same aircraft model, in this case an AV8B NA and not a GR.7, however the symbology should be identical but will be subject the cross-referencing the manual as well as conferring with the SME

Ok so from what I've been able to gather from the team and ED, the sidearm runs the same behaviour and logic in DCS as every other Anti Radiation missile does. So its behaviour and performance is based on that which ED has dictated. Now in conjunction with that, that behaviour and logic is tied into the coding which can limit what we are able to represent via displays on the HUD. The team has tried solutions to work around this but it seems until the logic is fixed, we are only able to work with what is available. However we do have our eyes on this and should anything change in the future that allows us to rectify these then we will do so. As for the symbology i will have that reported and see if it can be changed.

Confirmed to be incorrect behaviour for this type of scenario, conferred and confirmed with the SME.

I'm not sure If im understanding this one right, can you help me to understand what you mean? Perhaps we can schedule a time in discord to go over it?

set as a separate bug report. I was in single player last night trying it all out and it was working fine for me.

Right so the dude flying this thing daily and who flew it in combat checks everything out and says yeah that good and correct, leave it as is to be accurate is wrong........LIKE I SAID we are leaving as is to simulate the restrictions one would be under if they flew the actual jet and the limits imposed on them by the USMC.

So from the SME "The crew doesn’t physically set the pod, I do." and regarding the ability to set the ripple mode from the team "That is selected on the ME before the mission start, so it is analogous to ground crew physically setting the pod." Also some context of how its done in real life from the SME "In order to ripple fire pods two things must be true. The pod must be physically set to ripple on the back of the pod. You need to enter the right stores code on the stores page, I don’t think you guys simulate this, which is fine, it’s superfluous if you ask Me. The jet only knows the pod is set to ripple because of the stores code you enter. With a ripple pod stores code entered, quantity and multiple works like this: Quantity is the number of pods that will ripple fire their rockets Multiple is how many will fire simultaneously With 4 pods loaded you can enter up to Q4M4 Which I don’t think is actually authorized. There are limitations to how many you can fire at once, 2 at a time is normal for ripple fire If they have 4 pods set to ripple and enters quantity 2, two pods should fire, With Q2M1, two pods will fire sequentially, 1 then the other So with this behaviour, it is as intended in order to simulate restrictions on the amount of rockets fired in a ripple salvo. Moving to resolved under AS INTENDED

@exhausted still waiting on that .log file bud.

I'm gonna stop there and remove some comments cause this is getting way off topic and the real issue is becoming buried. If you want to open a discussion then you're free to do so in the main razbam or harrier section. Sorry about this guys.

But again, I'd suggest waiting till the next update lol.

Well the TPOD receives information from the way point if its been entered correctly and is designated but can be made more accurate with the laser. Not to mention you can employ alot more accurately and in the dark. Sent from my SM-N960F using Tapatalk

Right. I never closed this because there was some confusion in the way this was described. So as per the book on how designation should work, the behavior is correct. I've tried to get your bug to occur but I can't. Ill have to get some testers to give it a whirl but I'm hesitant to make more TPOD or DMT reports as there are some SIGNIFICANT changes coming down the road. And while your "preference" may be to use the DMT, the SOP is to primarily use the TPOD. It and the DMT are equally accurate but the TPOD is more accurate when you combine it with the laser ranging portion. I will leave this unmarked for now but might get just pushed off as old behavior after the new update but we shall see. You will all be pleasantly surprised. Sent from my SM-N960F using Tapatalk

Not to my knowledge. I dont think its a bug, might be how its set up. If you go to the discord can you send me a PM and we can sit down while you stream your view? I was playing this morning on a MP server and had no brake issues Sent from my SM-N960F using Tapatalk

*sigh* they need to be careful for what they wish for lol

What I have been told is it is as intended. I nor are any of the testers experiencing the issues described under normal operating procedure. The issue is stemming from people using the DMT and the TPOD at the same time...which confusing alot of us. So I'm trying to get to the bottom of Why people are doing this and then providing guidance on how to avoid it. When the SME was asked about this behaviour he said that sometimes new guys in the fleet would use both and the DMT would revert as an NA system prior to the TPOD. After just moving to the TPOD and IGNORING the DMT completely this no longer occurred. I would suggest waiting until the next update because after that ABSOLUTELY NONE is going to want to use the DMT ever again. Thats fine to be disappointed, I get that not everyone will be pleased with choices made. From what I've gathered over the past few weeks I seem to be getting a good rapport with everyone from ED to the regular user. If you have concerns or want to talk in detail more the I urge you to reach out to me personally and set up a meeting in DISCORD so we can talk and I can possibly explain questions you may have. Im not here to do the biddings of my over masters, im here to engage with you guys and convey feelings, wishes and desires to the dev team in a constructive manner.

I think you both may be correct on different points, I'll report it and let the SME take a gander.

Thanks for the input Fred. Heli, despite the INS update logic can you confirm or not that you had =15Nm of drift on the ins system here? Just want to check all the bases first is all.

Noted, perfect report as usual Heli.

Now im not sure how I pronounce your name in English nor do I have the ability to spell it so for now I will use Rob (it looks similar but i do apologize if i offend you in any way), but were you not the same gentleman saying that you flew Mirages or have experience in them? I'm just trying to get a grasp of the field of expertise surrounding this place.

so now its not a bug with the mirage, the range works its just the buttons in the pit do not perform their funtion?

Right but I want to here Recluse's answer. Sent from my SM-N960F using Tapatalk

Ok, I understand. Question. What purpose is it that you require the use of both the TPOD and the DMT simultaneously. Sent from my SM-N960F using Tapatalk