RagnarDa

Using the F10 Map to Place Waypoints It’s just B1...B9 M1...M9 BX1...Bx9 S1...S9 R1...R9 MR1...MR9 (recon target) With mach B6 M0.8 With time on target M6 15:10:22 Edit: Recon target = MR

M4 13:02:56 -> two minutes and fifty six seconds past one in the afternoon.

Meanwhile end-users can actually fix this themselves but it will probably break integrity check. In DCS World/CoreMods/Aircraft/AJS37/Entry/Weapons.lua got to line 2492 and change this: attribute = {wsType_Weapon,wsType_Missile,wsType_Container,wsType_ARAK70HEPOD}, into this: attribute = {wsType_Weapon,wsType_NURS,wsType_Container,wsType_ARAK70HEPOD},

I’m happy to tell that ED helped us find where we made a boo-boo and I’m making a build right now that fixes this issue.

Issue fixed and will likely be in next update

We believe this is a issue introduced in the core game and has been reported to ED.

Katj check that you don’t have easy flight model on.

And for the self-destructing one I don't have a clue right now. Thanks for posting replays btw, very simple to have a look at such short and to the point recordings.

Same with the second one here

Just checked this and the launch-inhibition comes on because the distance between Bx8 and Bx9 needs to be at least 8670m and it's 6645m in the track.

It has had FFB support since before it was released. Or am I missing something?

Is it possible you could record a track? Seems like it would be noticeable on a very short track

Making a radar fix on an empty Bx-point is not described in the documentation, so we added the feature of moving it in front of the aircraft. I don't believe it works like that in the real plane.

How to reset Bx points for RB15F? They are reprogrammable but you’ll have to input coordinates unless the target is near. The Bx-waypoints wheren’t originally used as targeting waypoints, the Rb15s as well as the Bk90s wherent part of the original design of the Viggen.

Hi! I’ve noticed this issue and tracked down the problem: to make track replays reproducible I created my own random number generator by adding a bunch of variables together. Turns out that because of this: https://en.m.wikipedia.org/wiki/Central_limit_theorem the approach wasn’t truly random and evident here when the Rb15s are supposed to select targets at random but are more likely to select the same target. I changed it a bit so the Rb15s are less likely to engage the same ship (from like 90% chance to 10% chance).

But the Bx8 is at the last target no? The functionality of setting the Bx8 in front of the aircraft when it hasn’t previously been set is not in the real aircraft, it’s something we added in DCS. You can’t reset the waypoint either.

It’s bx8 that you put over the target. The rest (bx6, 7 and 9) will be moved too automatically.

And thanks ED that was kind enough to release a hotfix.

Sorry guys I messed up. Uploaded a fix to ED.

Thanks for the reports! I am really really sorry I haven’t responded to Leviathans excellent report. I tried the things he mentioned a while back and couldn’t replicate the issues reported and somehow forgot to write back it seems. Will have to recheck based on these new reports.

Ok [emoji106]

Where did you read the term “sight mode selector”?

I guess it means the J/A selector?

This is fixed in our internal build and will be available in the next open beta.

I’ve spent this week looking into this and made some changes. The mode is still a fair bit confusing and as said the documentation is very vague but I will try to explain the difference between my interpretation and yours. In the other thread you assume that the safety height will be achieved in “phase 1” over the selected waypoint (ie B1). I don’t think this is correct, the wording in the documentation is very different to the “NAV-fällning” where the waypoint position is used as a target. In “phase 1” the documentation only mentions the sight is set “as a function of safety height and the airplanes altitude”. It doesn’t unfortunately mention what the third variable would be in that function but until now I just assumed it would be a fixed distance (4km) and a arbitrary angle (3,8deg) taken from elsewhere in the documentation. When originally creating this mode I tried out a bunch of different interpretations of the wording and arrived at the “current” solution as the one that made most sense. In the internal build are now a bunch of changes to the sight that includes adding the climb angle into the mix so that the plane more easily will reach correct height. Still unsure this is correct according to the docs but it works well. Also corrected the radar measurement so now it’s a lot more accurate and QFE don’t matter as much. Found a bug too that would make the bombs miss. Hope you like it!