TOViper

AFAIK it only locks on to units (either dead or alive), but not to terrain features. Are you using TV button for locking?

Can you provide a video or a track file of your mission? I used the official training mission "Air-to-ground: RB75 Air-to-ground Missile", and it worked perfectly. Maybe you can share your mission from the mission editor in order to have a detailed look...

119 works like a charm, thank you very much Bailey!

Hi! Is there a way to trigger the STD flag in the altimeter which came with the big update? I want to use the trigger condition X: COCKPIT ARGUMENT IN RANGE. For me it seems the device FLIGHTDATAUNIT (25) has become some more params, but I don't know how to find out which one is for the pull-out of the altimeter rotary knob. Using DCS-BIOS and the command "return list_cockpit_params()" doesn't give any parameter showing a change when I pull the knob out or push it it. The input file keyboard.lua shows "down = 3711, value_down = 1.0, cockpit_device_id = devices.FLIGHTDATAUNIT " Checking the files clickabledata.lua and many other files in the scripts folder of the module gave me no hints. Help please!

Nice idea! Always wondered why this didn't become standard. Are you going to add this to the official wishlist?

Hello schurem & welcome to the Viggen world! I also highly recommend using the RC2 manual that comes with the module. It is a very good manual IMHO. Personally, I like it VERY much! I think there is no way around reading it in total when you really want to dig into this wonderful beast to get out as much as possible. Happy landings! TOViper Edit: I forgot one thing to say... when the manual states that 3° nose up would be a good take-off trim ... use 5° nose up and everything is fine!

Hello! I use DCS BIOS, and I have one question: It delivers the following output: "BASE_SENSOR_VERTICAL_ACCEL:1.671939\" How can I use this in triggers, e.g. by checking if g-forces have been too high?

Hello! I am just playing around with the Viggens accelerometer. I am using the trigger condition "PLAYER'S UNIT ARGUMENT I RANGE. Argument: 136 Min: -0.3 Max: -0.05 I just want to sense negative g's ... thats all. Why does this not work, und much more important: How can I get this work?

OB 2.7.10.19473, SP from mission editor The ground collision warning is not triggered when using the radar in mode A1 and the radar altimeter set to off and master mode NAV active. According to RC2 it should work; the manual for this situation says: "Ground collision warning is received when the radar is used (mode A1 or A2) when the calculated altitude and descent rate is such that the aircraft will impact the ground within 7 seconds. If the radar altimeter is available, the warning is always based on the radar altitude. This warning is blocked during aiming against ground targets, as well as when the landing gear is extended and the ground calibrated altitude is less than 50 metres." AJS-37_Viggen_Ground_Collision_Warning_via_Radar_not_working.trk

OB 2.7.10.19473, SP from mission editor As written above, these failures do not work properly, the flaps continue to operate normally; see track. Edit: The other two flap failures "Canard flap surface left/right" seem to work fine. AJS-37_Viggen_Flaps_Servos_Failure_not_Working.trk

Hello! Was the Bränsleregl switch set to MAN intentionally for spawning (no matter if cold or hot)? I remember this switch usually to be found at setting AUT...

Replay: Video: Edit: It seems the TRIGGER UNSAFE is causing this problem.

OB 2.7.10.19402 SP, mission editor Using two consecutive M-points (target points) when overflying the first M-point causes the second M-point to have same coordinates as first M-point. In this example, I overfly M1 by attacking a fuel tank on top of the mountain (not replayed correctly on my machine, it was offset), and then M2 has the same coordinates as M1, despite they were differently before taking off. When overflying, M1 should switch to M2 (not B3), because I am not in NAV mode (not in ANF where automatic switching would be inhibited). If you are not able to replay the TRK, just load the MIZ and fly along the waypoints. AJS-37_Viggen_M-points_mixup.trk AJS-37_Training_Nevada_Rb75+AKAN.miz

For me personally your version is more clearly

Thanks Grimes! Since I wasn't able to get this out of it, this information could be added to the official DCS User Manual: Weapon Free: AI will engage any enemy group it detects. Target prioritization is based based on the threat of the target. Open Fire, Weapons Free (Priority Designated): AI will engage any enemy group it detects, but will prioritize targets specified in the groups tasking. Open Fire (Only Designated): AI will engage only targets specified in its taskings. Return Fire: AI will only engage threats that shoot first. Weapons Hold: AI will hold fire under all circumstances.

OB 2.7.10.19402 SP, in mission editor F-4 aircraft with TASK "CAP" Advanced Waypoint Action "CAP" removed from waypoint "0" Start Enroute Task -> Search Then Engage In Zone, with radius 5000m at waypoint "1" F-4 is constantly ignoring this setting and engages targets outside this radius. It happens when the Advanced Waypoint Action "ROE" was set to WEAPONS FREE or PRIORITY DESIGNATED. It workes with ROE setting "ONLY DESIGNATED" or ROE not set at all at waypoint "0". SEARCH_THEN_ENGAGE_IN_ZONE_fails.miz

Grimes, for which unit types did you get it work? Currently, the F-4 doesn't respect the action with a radius of 60000m, because once the unit is set to general task "CAP", it starts engaging everything within 400 miles. Edit: the problem here was that the aircraft was set to ROE = Weapons Free

Have you performed consecutive roll maneuvers before landing? This would also induce the tilt ... I think this was introduced a (felt) year ago ...

Ok, sounds good, happy it works now!

Hey Flappie! Thanks for the hints! I'll give it one more try, I think I mixed up two bases for any reason (maybe I just was too upset caused by the IMHO bad mission design) *LOL* Are the other missions as bad as well or will it get better?

I recently started to fly mission 1 of this campaign, and after several tries it is still not possible to complete it. Can someone please elaborate what exactly has to be done in this mission and where and how? Also, an audiofile indicates to fly 075 and then turn left at the outpost? What outpost? If the next one is meant, heading 113 would be right, not left. Radio is also not working, not even one farp is answering my calls on the respective frequency. Next, how should I land at Balaani farp? There is no helipad there, and the terrain is everything else from flat and the troops are not visible due to trees all around. For what is Leningori needed? Do I have to land there or not?

It uses the RWR to receive radar signals from other radars, yes. The pod himself then analyzes the received signals, and jams them using his own antennas. It is also able to do triangulation to determine the position of an emitter.

Hello Hawkmoon! Yes, you can put the knob "U22 mode selector" to position A and the knob "U22 bandwith selection" to F. With that setting, which is a "preheat" mode, the jammer does nothing except warming up. If you then need recording during flight, simply put the knob from F to any of G, H, J or K. Then it should record silently. After recording you can put it back to F.

Oh, because I have different settings, depending on aircraft (module). Depending on the throttle configuration (I use Warthog), I had to create different profiles, since the PTT config is not the same for all aircraft I fly. I found one common setting for usage in F-16, F-18, AJS, and some other aircraft I usually fly. This profile I use most. I have another 3 different profiles for the F-14, depending on the slot (front with Jester, front with real RIO, rear with ICEMAN or real PILOT). The F-5 always required a different setting for me. The UH-1 needs another setting. In terms of switching profiles, VIACOM worked really fine so far, and I was happy that this function was offered. But as written above, nowadays this doesn't seem to work anymore due to something I cannot figure out I will try to make the common profile work with the F-5 and the UH-1 as well maybe someday, but currently I would prefer to have the software work correctly before I put hours into re-configuration of something that worked pretty fine. Are you still approaching this issue somehow, or do you think the software works correctly? Depending on your answer, I will just wait, or re-configure the one or other part ... waiting is no problem, but re-configuration makes me not too happy. ;)

If I may add: .... or gunpods + Rb-75s