corvinus

*Ok, I can't quite wrap my head around it, but here are my observations: 1. In the mission the distance between B1 and B2 is just about 10 km, so a pop-up distance of 10 km won't work (you'd have to instantly jump to a different location). But forget this, if you do 349050, it doesn't work either. 2. Well, doesn't work ... What I have seen is that the switching logic seems ok, but the commanded azimuth does,, not bring you to the correct point. So if you input 349050, the azimuth of the target is not 349o if the distance if 5 km. As a result you don't switch to M2 when you would expect it. However if you keep following the commanded azimuth, then you usually do switch to M2. But you're basically circling back to the target location (it's kind of hilarious). 3. For some combinations of pop-up distance and heading I do get good results, but I can't explain why yet. I seems related to the commanded azimuth. When you hit waypoint B1 and the commanded azimuth is way off your current azimuth, then it is impossible to adhere to the commanded azimuth. As a result you end up in the wrong place. Well, that my hypothesis so far. If you use 340050 at B3 in the attached mission, you'll find it is succesful. Also with 270070, but in that case you see the distance indicator hit 7 km, then it decreases, increases and when it hits 7 km again you get the switch (and correct azimuth). It is probably related to a recent fix, see: https://forums.eagle.ru/showthread.php?t=222415 I can confirm chasing the pop-up point ... __________________ M05 - SB71 LD DYK PRECISION.miz

Dumb question, but how can I change the callsign in the ME? Isn't the predefined list fixed?

It seems I can confirm this bug. I personally fly the Viggen in Caucasus only, there I never experienced problems. Would it matter that you are flying in the Nevada map? You could try setting up a similar mission in the Caucasus and see if that works for you. P.S.: Destroyed the TV tower anyway. :D

I'm using Open Beta and are not experiencing problems with pop-up points. Without more context it is hard to say what is causing your problem (you could post a track or mission file).

At the moment it is not possible to turn off ternav, not explicitly using the computer or implicitly by turning off the rhm. Afaik the rhm is the only source that provides height above terrain info. See also https://forums.eagle.ru/showthread.php?t=194809

That sounds about right to me too. In terms of avionics and weapon systems everything is pretty much there. Of course, there are some issues that have to be ironed out. On the other hand, from a user's perspective, one can value a manual, missions and campaign as 25% of the module. ;)

See https://forums.eagle.ru/showthread.php?t=161475

How do you use this feature? That is, what is the proper procedure?

Posting a track file would help in narrowing down the problem.

Thanks, that's great!

And another bug bites the dust! :thumbup:

Shouldn't it be T1 fix? I believe the manual is incorrect in this case.

Thanks for reporting back. Turns out I had IR uncage mapped to LCtrl+LAlt+C, which is apparently also used for "select data cartidge - down". So I had been selecting data cartridges during dogfights all this time :megalol: Anyway, the bug is fixed, all is fine! Thanks devs!

C:\Program Files\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\AJS37\Doc Currently this contains the RC1 version of the manual.

Yeah, medium PRF is more effective against tangential moving targets. For "HOT" targets, with high Doppler, one would choose the high PRF. Interleaved should also work, also initiation takes a bit longer (but it should work).

Can anyone report back if this is currently working? I can't get it to work myself, but it is supposed to be fixed a short time ago.

Detecting a smoke plume is detecting an IR signal, or better a signature (brightness temperature, size, contrast etc.). All bodies emit IR waves, bodies that have a higher temperature than their surroundings can be detected by an IR sensor.

Thanks for the feedback, you bring up a valid point. What I have learned since then is the following. Before the post you referrred to I would fly at what I thought was the safetely altitude (about 200 m). What I should have done is try to keep the reticle on the target after unsafe. The computer will adjust the reticle such that I reach the safety altitude. So this works with the medium safety altitude setting as well as for the low setting. At least, this is how I understand it now. On the other hand, setting it to low is probably easier if you are learning the Viggen, as you are less like to be denied a weapon release due to safety height violations. I'm not sure what to do as I expect the manual to reflect the procedures corresponding to the default settings, which is the medium setting. I'm leaning towards changing the setting to "low", but I'm not entirely sure I do not create collateral damage in doing so. :helpsmilie: Btw, I just checked, but in the mission planner you can change the safety setting. I realize that changing it everytime is a pain, so having a good default is still desired.

In order make landing on a roadbase easier I thought I would add manual reference points, pointing to the roadbase, to the mission. As in the ground crew example mission provided by RagnarDa, I use an initial point for this. Now the weird thing is that, when doing several missions in a row, each with one or more initial points, the list of initial points keeps growing! So suppose you have an initial point in mission 1: 42:15:59 42:39:12, and in mission 2 you have: 43:05:27 40:44:42. Now start DCS and fire up mission 1. In the kneeboard you will see a reference point 9201 with coordinates 42:15:59 42:39:12, all ok! Then you finish this mission and load mission 2, go to the kneeboard and lo and behold. There are now two reference points: 9201: 42:15:59 42:39:12 <= this is the reference point of mission 1 9202: 43:05:27 40:44:42 <= this should have been the only one So the reference point is there, it is not named 9201, but 9202 instead. If you execute more missions, the list keeps growing and growing. Executing mission 2 after a fresh DCS start gives the expected result: 9201: 43:05:27 40:44:42 For mission making it is important that you can predict the ID of the reference point, so you can refer to it in the mission description. It would be great if this can be fixed!

You're welcome!

It's all about the timing ;) However for the highway and road landing missions I disabled civilian traffic in the mission editor. Also I removed any obstacles surrounding the landing strip, so you should be fine!

Sorry, I wasn't explicit about it, but the mission has unlimited ammo. Dropping bombs multiple times wasn't a problem when I tried it. Re-arming could be different, but I did not try it. Btw, there should be a track at: C:\Users\<User Name>\AppData\Local\Temp\DCS\LastMissionTrack.trk Or doesn't that work anymore?

Just want to note here that the system is very precise about the unit names. Initially I named all units in the ground crew group "GroundCrew" (ME automatically renamed the second to GroundCrew #001 etc.). In that case re-fuelling worked for me, but not re-arming. After pulling my hair out for a while, I noticed that the following works: Groupname: Doesn't matter, but I use "GroundCrew Landing Site 1" for example. First unit: HMMVV name: GroundCrew #1 Second unit: Tanker M978 HEMTT, name: Anything but GroundCrew. Third unit: Transport M818, name: Anything but GroundCrew. Once you have the names right, it is working beautifully!

Hmm, did by any chance got a flashing distance line when in NAV? In CCIP release this means a fragmentation zone warning, I don't think it will release in that case. Btw, I just tried both level and CCIP HD bomb releases and they work. So there must be a difference in procedure or mission set-up? You can try the SB71 HD missions from https://forums.eagle.ru/showthread.php?t=222539 which are the mission I used.

Which, in theory, could all be hostile. It would be nice though, it enables you to land any plane on the carrier. :D