corvinus

This seems like to way to go for me. Thanks.

It is not clear to me if you are in ground or air mode. Weapon selector should be in ATTACK not in AKAN JAKT. What mode were you in?

I already had the task set to "Runway Attack". To be sure I also checked CAS and Ground Attack, but to no avail. Any more ideas?

TaskBombingRunway I'm trying to get AI planes to bomb a runway using MOOSE. However the plane does not seem to accept the task (shows "Nothing" under task in the F10 map) and just lands at the nearest airbase (which is, ironically, usually the airbase I tasked it to bomb :huh:). This is the code I'm using: local airGroup = GROUP:FindByName("Airplane") ab = AIRBASE:FindByName("Gudauta") -- This works: -- task = airGroup:TaskAttackMapObject(ab:GetZone():GetVec2()) -- But this doesn't: task = airGroup:TaskBombingRunway(ab) airGroup:PushTask(task, 1) What am I doing wrong?

Yeah, the original code works in that case. I am happy with my workaround for now, but it is good to have a backup solution.

My two cents ... The Viggen has a ground mapping radar, two types of anti-shipping missiles (RB04 and RB15), a remote controlled missile (RB05) and a stand-off cluster munition bomb (BK90). It all makes the Viggen a very unique and fun plane.

Really? In that case I will check them out again, thanks for pointing out!

These are my first steps with MOOSE and Lua too. I'm going in head first! :pilotfly:

See also this post (about wind correction and the BK90): https://forums.eagle.ru/showpost.php?p=3742595&postcount=7 Apparently the wind direction is 180o off for the BK90, is that also the case for the SB71 bombs?

Ok, I figured out how to do it. The PLAYER_ENTER_UNIT event is fired before the scripting is started. However use can use the initializer script option of the mission editor. This comes in two flavors: file or code. Specifying a file does exactly nothing. However the code input box does work. If you paste the following code into the box: clientDCSUnit=nil; handler = {}; handler.init = function(self) world.addEventHandler(self); end; handler.onEvent = function(self, event) if event.id == world.event.S_EVENT_PLAYER_ENTER_UNIT then env.info("INIT SCRIPT: player entered unit"); clientDCSUnit=event.initiator; world.removeEventHandler(self); end; return true; end; handler:init(); Then you will have the clientDCSUnit available in the rest of your scripting.

I guess you are right about this. Concerning their Viggens videos, they were kind of hilarious and certainly entertaining. But ... it was called a tutorial, so I was watching it hoping to learn something, only to find out they were strafing ground targets with the gun in air to air mode ... So, yeah, that was kind of a downer. Anyway, you are right, it is none of our business (not that that will stop us from having lengthy discussions :smilewink:).

Yep, when you are out of bombs, just touch and go to destroy the bridge! :D

I was not aware of any personal problems of the GrimReapers. I wish him well.

How is the quality? I own an X52 pro, which has loads of functionality, but it is very poor quality. The precision (:megalol:) slider is so jittery I have turned it into a three position switch. In fact almost all axes are jittery. Logitech sent me a replacement, but that was just as bad. If the X56 is better I would seriously consider it.

The recent Viggen videos they did were full of incorrect statements, so I would understand if the Grimreapers are not on the shortlist. I have learned a lot from their videos in the past though, so I hope they make a comeback.

I'm building a mission that has multiple client slots. The idea is to use the mission as a single player, but giving the player a wide variety of starting positions at various airfields. For scripting I rely heavily on MOOSE, which is working great so far. But there is one problem I cannot seem to solve. After the player chooses a slot, I want to be notified. I've tried using events, but the PLAYER_ENTERED_UNIT event is only sent after changing a slot, not after the first slot is selected. So I thought I would use the database, but there do not seem to be any player or clients. The following code: sched = SCHEDULER:New(nil, function() env.info("Scheduler callback") env.info("num players = " .. #(_DATABASE.PLAYERS)) env.info("num players joined = " .. #(_DATABASE.PLAYERSJOINED)) env.info("num clients = " .. #(_DATABASE.CLIENTS)) end, {}, 0, 5)yields 2019-01-01 14:38:26.340 INFO SCRIPTING: Scheduler call back 2019-01-01 14:38:26.340 INFO SCRIPTING: num players = 0 2019-01-01 14:38:26.340 INFO SCRIPTING: num players joined = 0 2019-01-01 14:38:26.340 INFO SCRIPTING: num clients = 0 This is after I have selected a slot ... Any help would be appreciated!

Do not forget about the rudder pedals! The TM Warthog stick does not have a twist axis that can be used as a rudder. Pedals or not that expensive, but it has to match your setup (for example a desk chair with rollers/wheels is not a good combination).

One line of lua and such a big difference! This opens a lot of new possibilities for mission building! Starting from a road works without sideeffects. Starting from a bridge (near Sochi there a few large bridges that are wide and straight) gives a very interesting side-effects: If you start building up speed the bridge catches fire and is finally destroyed. It makes for a very dramatic take-off, but a bit too dramatic don't you think? The same happens when landing on the bridge. I guess DCS views a high speed Viggen as a projectile? Best wishes to everybody!

Thanks for the pointer! I was under the impression that the wind parameters would already be stored in the CK37 or that the Doppler unit would take care of it. Apparently the automatically determined wind speed/direction does not match the actual parameters?

I've created a track file showing how to make a target fix (SPA/MAL) and target track (SPA/SKU). The fixes are made using the radar, this makes it easier to see when I press T1 and TV. In order to make the track I wait at least three minutes between the first and second fix on the target. You can see that the track heading and speed match the actual heading and speed quite well (considering how inaccurate the radar fix is). Note that I do press T0-T1-T0 sometimes to restore the radar screen image. That seems a bit strange to me. Hope this helps. spa test.trk

Did you check the bx7 and bx9 waypoints? They are not always ok, especially if you change the bx8 after an automatically generated bx8. The red light indicates that either bx9 is too close to bx8 or the placement of bx7 is such that the missile heading change is too large.

Hmm, you are probably right. The manual says "Missile will determine a group of ships that are within 3 km of each other. From this group, a target is selected at random." It does not speak of the ships being three deep as with the rb04. For quick mode it indeed locks on to the first target it finds, at least according to the manual. So I guess the rb15f is not working properly atm?

Thanks for the heads up. Looking forward to the final push!

What is the final attack heading of the missile? For grupp mode to work there have to be three ships in depth. From the figure it looks like the missile might not see three ships in depth.

Actually I tried today and it was working. You have to select the target waypoint by press "1" on the data selector numeric keypad (for selecting the first target). It doesn't automatically select the target waypoint. I can post a track file tomorrow. But if you have a track file ready, that would work too I guess. P.S.: The ruta point are indeed displayed as M1, ..., M9 now, weird ...