iChasney

Reporting the same issue with the T45 salute on the Super carrier. hope it's something they can resolve quickly

This Reddit post from Nineline explains all the current issues. Doubtless there will be things that come up in OB that will want to be resolved before Stable.

Have you done a regular update first, to bring down the new updater, manifest and deltas?

I got the same issue but all working fine for me now after I waited a few minutes.

I've resolved my issue, thought I would post what I did here incase anyone is having the same issue. I removed SRS completed, kept my config but then went hunting through all the scripts folders and cleaned everything out from my Save Games\Scripts and SRS stuff in the main DCS\Scripts folder. Performed a full install of 1.6.1 again and this got round the problem I was having with the FC3 radio channels, I guess something didn't update correctly last time I updated SRS. That said it still didn't work, I noticed that the SRS volume was 0% and changing the volume on the MiG-19 Radio panel didn't change it, although it definitely did something as I could hear ATC. So I had a poke about in the SRS lua file (DCS-SimpleRadioStandalone) in both the SRS folder and the one in my Save games, it looks like one is a copy of the other. I found a line that looked like it was taking the volume to use in SRS from the volume knob position. So I commented out line 1357: _data.radios[2].volume = SR.getRadioVolume(0, 329,{0.0,1.0},false) and replaced it with: _data.radios[2].volume = 1.0 This forced it to go to 100% and all was well from there, happy MiG-19 flying with my friends. I hope that helps I'm sure the issue will get sorted in the future but this workaround at least gets you flying and talking.

I'm having a very weird issue. It's like SRS doesn't properly detect the MiG-19. My buddy who hosts the server and SRS doesn't seem to have the issue but when I jump into the MiG-19 I get a default FC3 3 radios setup, locked to 124.800, 251.000 and 30.000, see the screen grab. I have no problem with any other module. It doesn't seem to be map specific. I've tried reinstalling SRS and re-configuring from scratch, also removing and reinstalling the MiG-19 module and finally running a repair on DCS itself. I use Voice Attack and have reinstalled that too but the issue still occurs even when VA is not running. Has anyone experienced this before? With the MiG-19 or any other module? Any advice would be greatly appreciated as I'm left scratching my head on this one. Thanks Charlie https://www.dropbox.com/s/zh2z77sx88k0uft/Screen_190815_195518.png?dl=0

I realise this is an old thread but I only started aerial refuelling lately, I tried it first with the Tomcat, which I was able to do reasonably well after a bit of practise but the Mirage was something altogether more difficult. I find the Mirage (when compared to the F14) overly pitch and roll sensitive and with a less sensitive throttle. After a couple of hours practise and some tweaked settings I was able to refuel it ok. I thought I would share my setting and experience. This is what worked for me. I'm doing this in VR on Oculus Rift. On my mission, I used a KC-135 MPRS set to fly at 15,000ft and 270 Knots out over the sea on the Caucasus map. For some unknown reason the tanker decided to fly at 217 Knots. Your tanker speed may be different to mine, so you'll have to convert the speeds I mention here. As I approach the tanker I set the G limit switch to prevent extreme flight modes, and extend the slats, this dulls the performance and help stabilise things. I practised using x3 empty fuel tanks and x2 Magics. Trim the aircraft spot on before you start and get the throttle set so that it will gently accelerate by 1 knot every few seconds. I found the throttle was too insensitive, you'd end up giving it a shove to get the aircraft moving and then almost immediately dialling back the power or it would start overspeeding. I approached the tanker slowly at about 220knots, keeping the horizontal top of my HUD lined up with the centre cross section of the basket (like the HUD top was chopping the basket in two) and trimming the speed with a dab of air brake I keep my eye on the MPRS fuel pod and try to line it up with the centre of my HUD but fractionally to the right. As I start to get close I dab the air brake to keep the speed at 218 or 219. Don't look at the basket and don't make any sudden pitch or roll movements, above all don't try and chase the basket. If you miss, just engage the brake and drop back slightly. Connect at 218 knots and immediately let the aircraft run on slightly, so there is slack in the line. From here on it keep watching the speed. If it picked up to 219 or 220 I'd dab the brake and if it got to 216 I'd release it and maybe punt the throttle slightly. After connecting I found it helpful to fix my eyes on the MPRS pod and move the aircraft so it lines up with a fixed point on the HUD, like the compass bearing or something, this would mean raising up slightly behind the tanker but I found it help keep the wandering oscillations to a minimum. I found it helpful to add some curve into the axis tune in DCS, attached below are screen grabs of what worked for me. Above all smoothness pays dividends. When I started the pilot induced oscillations kept making me think there was something wrong with the tanker or me. It does get smoother, just keep at it. https://www.dropbox.com/s/g51cz3xs4tk44em/IMG_6803.HEIC?dl=0 https://www.dropbox.com/s/w13worbnhz6jdbk/IMG_6804.HEIC?dl=0 https://www.dropbox.com/s/3k51kcsko4806ft/IMG_6805.HEIC?dl=0