JanTelefon

I would also very much like to see this. As is, the transition between gear down and gear up (and vice versa) is very unsmooth.

It is supposed to calculate the speed from the waypoint you specify to the next target waypoint, or if there is none the landing waypoint. I haven't been able to make it do so properly though. It only seems to calculate the speed between the last waypoint before the target and the target properly. I have tried following the procedure in the real manual for the Viggen, but it doesn't work as expected.

Alright. Noted and confirmed. Thanks.

I will be testing the BK-90 in MP later. I did however just test the LOLA-input in nevada, and sadly the waypoint ended up quite a bit to the east of where it was supposed to be. I didn't measure exactly, but it was something like 30-50 km I believe. I'll provide an update with more testing.

Thanks for the info Cobra! Now we know. :thumbup:

There's a lack of information in the changelog, and I'm really curious as to whether any changes for the Viggen made it into the build released today. I really hope so.

I have actually yet to try the illumination bombs in the Viggen. I simply haven't gotten around to it. I have been unable to discern any way of reading the proper pull up distance from the hud. I simply read the range from the range needle in the cockpit. It might not be the right way, but it's been working pretty well so far. :) If you do discover an indication of the proper pull up range, please tell me. :)

I have the same results. Releasing outside of the envelope has the weapon gliding over the target area with no effect. If you look at page 340 in the manual you can see that the maximum range seems to be something like 7km at M0.9. I guess 10 km is a bit optimistic, but it's a nice and round number to use when "selling" the weapon. It is still quite an awesome weapon though that can be used over hills etc. :)

What range you get really depends on speed, but 4.5km is a good rule of thumb. M0.8 = 4.4km, M0.85 = 4.6km, M0.9 = 4.8km. It's on page 311 in the manual. You will have to estimate pull up distance based on these numbers, but if you're fast enough 4.5 usually does the trick. What I do is keep it in NAV mode. Fly straight towards the target. Unsafe at about 5km. Pull up with 4G at about 4.5km and keep the trigger held when the climb has been established (very soon after the pull up). If done correctly the bombs should come off when the time is right and land in a line through the target. I'ts not strictly by the procedure in the manual, but it works pretty well. The hard part isn't hitting the target in the vertical "lengt wise" plane, but rather in the horizontal plane. Not many bombs will fall on the waypoint, but the center of the ripple should be somewhat close. As for the symbology, I too get the range markers straight away, but they move laterally when you pull Gs so that might give you a feel for the range etc. I hope this helps. Ask again if anything seems unclear. Happy bombing! It takes quite a bit of practice. :)

Is this in live, open beta or open alpha or all of them perhaps. I have had this issue in 2.0, but have yet to try it the caucasus.

I think what you are after is a toggle function that switches between the two states with a momentary press (like that of a button or a keyboard key), this mod however does mainly deal with toggle switches, which have two states they stay in ON-OFF (or PRESS and RELEASE if that's clearer). I'm sure Franky could add the toggle function, since he's awesome, but I don't think that was his original intention.

Has worked well for me so far.

Check! Thanks for your responses. :pilotfly:

Now that the Viggen has been released for 2.0 we can start showing Vegas what Sweden was really about during the cold war. I do remember reading about a solution for punching in coordinates in the CK-37 when in Nevada, but I can't find it searching the forums. Could someone please point me towards, or tell me how, the principle of punching in custom waypoints into the CK-37 in Nevada works? Thanks!

I can't say enough good things about this mod. It does make the trigger work properly and so much more. https://forums.eagle.ru/showthread.php?t=181720

The drop altitude can be set (in the ME somewhere) to low, medium and high (200, 400 and 600 meters I think). I remember reading something on the forums that the default setting is medium (400 meters). For the drop procedure you should go into ANF and when you are diving by more than 5 (or is it 3?) degrees the radar ranging tick should appear on the top. When pointing the pipper at the target you then unsafe weapons to tell the computer your designated target. If you then fly level at about 400 meters the pipper should stay roughly on target and enable a quite precise "CCRP" release with the standard symbology. Putting the HUD glass in low level mode helps quite a bit. I hope that makes things clearer. If not, shout and I'll try to explain again. :)

I have also experienced odd performance when reloading the low drag bombs. I just noticed they looked like they were still hanging under the wings, but I never really looked if they fell anywhere that wasn't the intended target. Can't say if they fell straight down or not.

Here's a link to a mod made by franky. It enables the functionality of the two stage trigger to work properly, along with a bunch of different key binds to work with proper toggle switches (like the ones on the warthog throttle base). I'm so happy this mod was made. https://forums.eagle.ru/showthread.php?t=181720

The B-scope will provide a somewhat zoomed in image around your current navpoint (circle on the radar). The circle will have to be close to your radar centerline however. The zoomed in image can be used for making out troop formations for instance. A ship column might show up as a blob, but when you zoom in you might be able to make out individual ships.

I recall seing black streaks on the radar with it in passive mode. These streaks would come roughly from a known ship location of a ship. I don't know for sure if it's from a search radar or a jammer.

As far as I know the passive mode will return any radar echo it encounters. I think that means both jamming signals and signals such as search radars. I'm almost certain, but it would be good to have it confirmed by someone else. I suppose it's easy enough to test. Set up a mission with a bunch of different radars at different locations and point the passive scanning nose at them. :)

I just remembered something. Make sure you don't launch the BK90 before the time line has reached the launch zone markers. I f you do, the BK90 might reach the target but will only fly over without deploying the submunitions.

I might be launching early/late with the ARAK. I will have to review my launch parameters. So as for level bombing with slick bombs, is the same thing true there? I was under the impression I could press and hold the trigger as a kind of CCRP when the target has been designated with the safety latch. I was also under the impression that the flashing time line indicated a two second window during which the firing solution is valid. I seem to be mistaken. Thanks for your response by the way.

This needs more testing, but I'd like to air my thoughts on it. Currently I have a tendency to land my weapons long of my intended target. It seems to be mostly ARAK and slick bombs. In both level drop and dive mode my bomb salvo usually lands long. In the tutorial the ARAK usually land long as well. High drag bombs in CCIP mode seems to work well. I try my best to set the QFE properly and unsafe only when I have the pipper on the target and the radar ranging fin showing. Could the QFE settings be bugged? I'd like to know if anyone else has experienced this, or if it's simply me and my procedure that is wrong. Thanks in advance.

The BK90 works well over hilly terrain. You may want to increase the cruise altitude of the BK90 to 150 meters if there are sharp climbs.