bertOC

When doing multicrew, on almost every sortie the RWR audio will become desynced, leaving the front seat with a constant RWR beeping if a few radars paint you.

So when taking some screenshots of an Mi-24 formation flight with a buddy of mine, i noticed the elevators on his Mi-24 moving as he was changing cyclic pitch. I pointed this out to him, but he could not see those elevators or rear stabilizers moving. On my own helicopter i too cannot see them moving. Are they even supposed to be moving in flight?

Gotta love the frequency of additions and fixes, keep up the good work Right now with SAR missions i'm experiencing weird stuff, i'm landing near units, a single unit gets loaded into my helo, but the other units don't get in and aren't rescuable by slingload either. This is with Mi24 on Syria, havent tested other helos.

Another Mi-24 request, how about removing the IR suppressors for looks? I think it looks much better without them and theyre not needed for civ ops

Ohh what a bliss finding the Syria server finally having Mi24 slots, thanks a lot! I just found it's missing from Rayak and Beirut spawns, so adding a couple Mi24s there would be very nice, especially because of that sweet helipad on the roof in Beirut!

Ok, just did some testing and i think this describes the issue quite well. https://imgur.com/a/GdnVWpW Pay attention to the controls indicator for the cyclic and autopilot channels, aswell as the picture's descriptions. In a nutshell: Releasing the trim button will have the autopilot pitch and roll channels snap back to their original center, rather then accepting the new trimmed position of the cyclic as its center.

Experiencing this aswell, before and after 2.7.4 patch. It feels like the trim system doesn't realign on the current attitude after releasing the trim button. Can't really describe the behaviour but it's definitely weird, very wonky and unstable compared to the Mi-8.

I love the server but also the Hind, when will there be Mi24 slots on Syria?

Can confirm, even tho the heading is set to magnetic in the NS430's settings page, it's showing true heading in the default nav page. Changing the setting to true heading will change the heading shown to true heading + magnetic deviation, so a complete nonsense number. A fix would be much appreciated...

It's definitely some sort of bug, as others stated bombs only work if they are pre-loaded on the helicopter via mission editor. Spawning empty and rearming via ground crew only lets you drop bombs with the emergency jettison switches. Funny enough, a helo that for example spawned with FAB-500s can drop them, come back, rearm and also drop the same bomb type again without breaking the system.

For a long time now slingloads have been basically weightless, leading to weird swinging behavior and other problems. Is there a big underlying problem that needs months to fix? It's causing problems for lots of campaigns and hasn't really been adressed anywhere. You can easily test it, it's bugged in SP and MP. Hook up to a cargo, stabilize hover and tighten the line by climbing at about 0.3 to 0.5 m/s, (300-500fpm) so pretty slow. Once the line is tight you'd expect the cargo to anchor you to the ground until you apply enough power to lift it, always worked that way. Now all cargos are lifted effortlessly, weighing close to nothing as it seems.

I can't be the only one really missing trim tabs on this otherwise awesome plane, cruising around for a longer period of time can really be annoying because of it's nose heavy flight characteristics. So i had a look at the axis config and did a little testing. By enabling the manual curve control for pitch and roll and offsetting it along the Y-axis, my controls indicator diamond looks like this: With my stick centered, it commands a pitch up and slight right aileron, making the plane fly straight and level. My curves: This workaround makes the cruising part way more comfortable until Ivan finally gets around to weld a simple trim tab to the elevator and aileron.

This is not a bug but a feature. You are not supposed to run the viggen's engine in full idle, instead the first click marks the ground idle positing with the engine sitting at 10% like you described. Syncing your hotas will just move the throttle when you enter the cockpit. This is how it should be done and why the mission starts with the throttle in the correct position. However this is a pain in the ass and I ignore the rule all the time, the ground crew guy responsible for your brakes will thank you. Never had bad repercussions from going full idle for extended amounts of time.

I've done it and can continuously hit Tblisi Airbase, i haven't tried another place yet, just kinda tested it at Tblisi. It's not too accurate and relies highly on your altitude in relation to BX6, also the place you wanna hit can't be too close to sea level i think. My BX6 was about 3-4KM short of Tblisi in line with the BX7 & 8 placed about 10km behind my intended target. Its just trial and error i found, but the higher you release the higher the distance between BX6 and the impact point will be. When I tried it initially there was a mission on 104th with like 40 guys continuously launching out of Tblisi, but by the time I figured out how to send RB15s their way the mission changed. It definitely is possible, but not really practical.

I know for a fact that this is true for the RB15s, yesterday though i got a liiiiittle desoriented getting out of an SA15s engagement zone and steered my Viggen into the ground. The two BK90s i launched at it continued to guide and employ properly though, killing the SA15. If you tested it with ejecting, maybe there is a difference?

I've also been noticing this, and helping myself by ofsetting my target waypoint into the wind. Also, i think to implement such a function to the BK90 automatically shouldn't be too hard, correct me if i'm wrong. My idea is as follows: Take a readout of the wind as calculated by the CK37 when the trigger is pulled, and offset the BK90s target position by a set distance into the wind. I've done this mostly on Kirks Hangar with a 5m/s wind on the deck. 150m of offset seems to be working quite good for this. That offset happening automatically would be super sweet!

Damn your graphics, the patch is there and its working glorious. You didn't check the fixed wind correction for example, right?

Check your bindings and have a look at the procedure again i'd say, Rb75 has always worked perfect for me as of yesterday.

Brilliant, thanks a lot!

If you think about the real thing, a pilot would never subject himself to those Gs voluntarily, aswell as the airframe. I bet a 5G evasive turn is already stressing enough, so 7g pullup shouldt be normal procedure anywhere. Good its all working as intended on that part, happy illuminating :)

The manual page for the Lysbomb states to perform the pop-up at 4G, while in your video you pulled 7G initially and 6G constantly until release. Could this be what is making your bombs fall short? I remember it working fairly accurate the last time i used it. I am doing everything exactly as you do except pulling 4G constantly. Maybe test again with this method? I'm away from my hardware right now otherwise i'd test myself.

Hope the issue is fixed in the near future then, thanks for the clarification! :thumbup:

I tried my best at visualizing it here. Wind setup at the deck is 12m/s with a wind direction of 270°, so its blowing east to west. Loadout is 16x HD bomb, plane set to standard interval, master mode NAV and weapons selector on BOMB PLAN. The symbology is cueing me to offset my plane with the wind as opposed to offsetting myself into the wind. I hope i cleared it up a bit more. EDIT: QFE is set wrong intentionally to get the symbology visible, i am away from my flightsim hardware right now, so i chose to configure the system rather than fly any longer with arrow keys...

push... this is a really annoying issue

I just played around with the high drag bombs in a pretty windy scenario today for the first time, and tried to bomb a convoy of vehicles lined up in a way giving me a substantial crosswind for the approach. The wind ingame was blowing towards the west, coming direcly from 090, the readout on the viggen's wind function in the CK37 was showing 090221(?) not sure about the last two digits. That indicates wind 22km/h coming from 090 right? When i approached and switched trigger unsafe, i noticed the aiming symbology offset into the wind, as opposed to be offset with the wind. To picture this a bit clearer, the convoy was lined up on 325, which was my heading aswell. With the wind coming from the east, the computer should tell me to fly offset to the right in this scenario, so the wind blows the bombs onto target. Instead it showed the complete opposite, telling me to offset myself into the wind to the west, which made me drop the bombs off target and the wind carrying them a bit further away even, as opposed to the wind carrying the bombs right onto the targets. Am i missing something here? It seems to me like a value needs to be flipped around somewhere in the code. Should the Viggen's wind readout in the CK37 display where the wind is coming from, (090 in my example there) like it does in DCS right now, or does it maybe need to display the direction the wind is blowing towards, like the A10C does?