corvinus

Yes, the manual could be clearer in this respect. Also, you need to keep the dot on the target even after trigger UNSAFE, right? Keeping the dot on the target automatically steer you to the correct height?

As a workaround cant you program the hotas to send ctrl-e when pressing the button?

I just started this campaign (bought it recently), should I also try this replacement? I'm asking because I noticed the flight leads flies very low. Also he does not mention when to steer towards the redfor radars. The mission briefing mentions these radars and that we should try to pin-point them using our U22/A. However during the tour my flight lead never comes back to this.

Yeah, that sig, although being somewhere in the neighbourhood of a little bit funny, is very unprofessional. Not that I'm personnally offended, I'm a coder myself so I can pretend the line does not apply to me. But I would never ever refer to my customers like that.

Thanks for the explanations!

Now I am confused ... Does it work by integrating velocity, heading etc.? Nothing more?

Is it obvious that I want this plane as a module? :D

If you, like me, accidentally switched to NAV, there is a workaround. Do trigger unsafe, master select to DYK and back to PLAN. Now CCIP works again ... Still, it would be really nice if this gets fixed. Typically, I forget all about it, and only find out I forgot when I'm over the target. :cry:

Thanks for the heads up. Looking forward to RC1!

Too bad ... thanks for pointing it out though.

I hear you. Do you know what Object.Category a tree would be? I'm just trying to clear the trees around group spawned within a zone (sometimes I have rocket artillery in the middle of a forest, doesn't stop them from firing, but it looks rather silly and it is hard to spot them).

Just a small addendum: If you want the TIR (target indicator ring) to display correctly, the qfe also has to be correct.

What if you do a hot start? I'm asking, because for me setting the Bx8 still works, also with F10 mark points. However, I always use a hot start.

By default the RB-04E is in GRUPP mode. Your ingress direction is from the NE and then the ships do not have any "depth" only width. In GRUPP mode it then fails to detect a group (you need a depth of three ships within 2.7 km if I recall correctly). Did you use GRUPP or ENKEL mode? In ENKEL your mission works fine for me.

If I do the following with Moose: local zone = ZONE:New("TestZone") env.info("zone data " .. zone:GetName() .. "," .. zone:GetVec2().x .. "," .. zone:GetVec2().y .. "," .. zone:GetRadius()) zone:Scan(Object.Category.SCENERY) for scenType, scenObjects in pairs(zone:GetScannedScenery()) do for k,scenObject in pairs(scenObjects) do env.info("destroying scenery object") scenObject:GetDCSObject():destroy() end end Then the log shows "destroying scenery object" several times, but it is not clear that any objects are actually removed. If I set the zone around a unit, like this: local zone = ZONE_RADIUS:New("temp", unit:GetVec2(), 1000) then nothing is removed (the unit is near some trees and a village) and the text "destroying scenery object" is not called. It is completely unclear to me what GetScannedScenery actually returns.

Anyone knows how to do this with Moose? Is there a handy "ZONE:RemoveScenery" function?

Sorry, I misunderstood. I do not have this mapped, so I do not really know how to help you.

So I wanted using a target waypoint to help me in CCIP release. I set everything up for CCIP release, but when inbound to the target I switch to ANF such that the TIR is displayed over the target area. This helps me in finding the target. I then switch back to NAV, trigger unsafe, line-up, pull trigger ... and ... nothing :cry: If I do not go to ANF everything works fine, so for now I try to remember of not going NAV->ANF->NAV, but it is a bit of a pain (mistakes are easily made!). In the track I switch to ANF, then to NAV and try CCIP bombing. You see the HUD symbology for CCIP, you even see the altitude indication switch to the right in the HUD when pull the trigger. But no bombs release. Then I switch from PLAN to DYK and back to PLAN on the weapon selector switch. The bombs are now released, although I did not pull the trigger ... It smells like an initialization issue to me. The mission uses unlimited ammo. After the bombs are reloaded I refrain from switching to ANF and stay in NAV all the time. Everything works fine as you can see. no ccip release.trk

It is the "Fast countermeasure dispense" command, I have it under the "C" key (I think that is the default, but check anyway).

The radar is used for ground mapping, I dont think radar ranging is active. I mean, in radar ranging the antenna probably has to stop scanning order to achieve a high update rate of measurements.This holds for nav and rr bombing. In any case, a barometric altitude below zero is a good reason for the Viggen to inhibit release. The 3 km cross is displayed on my system. It does not correspond to the manual 100%, but is is there. In A1 mode it looks ok, in A2 mode, well I do not really understand it. The problem I am having with rr bombing is that the bombs are released too late. It is as if the bombs are release at the location of the 3km cross when trigger was pulled. Anyway, did you try setting the qfe?

I've watched your track and I noticed that you did not set the target QFE. The radar altimeter indicated 200 m, but the barometric one indicated something below zero. The red warning light just above and to the left of the CI was on to indicate that something is wrong (often it has to do with your altitude). If you set QFE properly and fly at 200 m above target, then you will find that the bombs drop. I've checked this by taking control of your track.

Not sure if it has been mentioned before, but here is a very interesting read about it: http://www.ausairpower.net/Analysis-ODS-EW.html This is a detailed analysis of the electronic battle in the initial phase of Desert Storm.

:thumbup:

Well, in case you didn't know, Heatblur is busy finishing the Viggen and the Tomcat. So if they find any spare time, they'd probably go for some R&R. ;) Besides that, it's a nice request.

I don't understand why it is politically correct to be wanting a pilot skin in your own skin color or gender for that matter. Just a legitimate request from the OP. Moving on ...