Vakarian

VOX works with the VoIP (when VoIP works). Just yesterday I was flying with human CPG and as I was teaching we were on Discord. We both had to flick the intercom to PTT to stop hearing each other two times

I have right now tried mic test in the audio window, no crash. I've also tried testing the sound filters in the radios (this caused crash for me in the initial 2.9 release), no crash there. So far, so good

Are you now intentionally being thick? If the changelog says the manual is updated, yet the manual contains old date, isn't is valid to be concerned about it?

Well, the idea is not to use modifiers...

Comm menu is for use on the ground. User radio PTT keybind to talk through the radio and then you'll get a response

Do you see the irony in your statement? VR users are vocal minority. Multiplayer PvPers are also vocal minority. For the people playing on monitors, on higher resolutions (yes, it's 2023 and people use something else than 1080p monitors these days) it was impossible to see something 2-3 miles away unless you actually knew where stuff was so you could focus there. Now, is the current system perfect, no, it's not. Is it better than it was previously? Depends who you ask. In VR, mostly people say no (don't have VR anymore so can't personally test and say my opinion). However in 2D I'd say hell yes. I can actually fly visual circuit without having to guess where people are or use zoom for basically 2-3 nmi bubble.

Force trim is not only used to keep the cyclic where you left it, but it is used to recenter the SAS authority sleeve. Just look on the forums for this, it's been repeated for 1681681816 times and reiterated about the same amount by the SMEs. Even if you have springless controller, you should still use force trim release

Ah, thanks @Ramsay for correction. That would make sense to me as I was wondering why is "northing" off by ~3km which could be RWY length, but "easting" only few hundred meters... Something was odd to me there, but I didn't realize I switched northing and easting.

Yeah, the issue is shown on the screenshots, but not that easily spotted Look at the MGRS grids, the northing is off by 3km if I read it correctly

Videos have hard time portraying the actual benefits of the FFB base because it's in the feel, rather than motion. Hope I don't get banned for this, but the difference is similar to watching "certain videos" and then doing it live. It's not really comparable. Is it worth the money and wait, I'd say 110% yes. The amount of on-the-fly customization is immense and with the additional TelemFFB you can get even more haptic feedback than is coded in the modules themselves. Yes, mimicking the F-16 type of controls (pressure sensing) is very hard/nigh impossible due to physics, but everything else is right there, few mouse clicks away. Join the discord, you'll see that there's 230+ happy users and base your judgement on that.

Yeah, that's what caught me up too. From what I've read on TURN protocol, that's what is supposed to help with the NAT issues and "automagically" make networking work. Why it worked after this port forwarding, I have no clue. If you get any feedback on this from the devs, it would be nice to know.

Now I kinda feel like an idiot, but also feel like this could be highlighted in the voice chat guide or at least in FAQ as I haven't seen it there. We got the VoiceChat working after I stumbled on the thread here by accident: In there I saw that VoiceChat needs 10309 port and as soon as we got that port open, VoiceChat started to work without any issues. No need to disable SRS (as is logical).

Oh yeah, that's the first thing we checked. Volume was 50% on my end at the start, later it was 100% and we ensure it was 100% on all clients. Didn't help. Will try later today again with more of us and we'll try disabling SRS too to see if it helps.

Yesterday we have tried VoiceChat in our group. On a first attempt we used it via dedicated server. There we couldn't see each other in any of the rooms. When in cockpit, we could see the radios light up when people were trying to talk, but no voice made it over except those transmission end sounds. Next, we tried via in-game hosting. There we could see each other in the rooms, but either talking there or in cockpit no voice made it through. We could see the radios change indication colors when people are speaking, but zero voice. For our setups we have tried: TURN servers on/off, ensured VoiceChat is enabled in the server/host and all the clients, ensured audio devices are selected instead of using "default". Is there anything else that's missing that could help in troubleshooting? I've even tried port forwarding the default TURN protocol port, but by the looks of it that shouldn't be necessary as TURN is supposed to help with the NAT issues.

Yes, this would be very nice QoL feature

Thanks a lot for putting me up on a right path. For some reason, the tesselation was already set to x16 (current max is x64). However, because of that I now set the option to "Use application settings" and the problem is gone. Would have never thought about that.

Huh, I'll give this a try. I usually stay away from messing with those options, but shouldn't be any harm in setting Tesselation. Will report with the results

Adding screenshots as eye-catchers

IIRC ever since MT update, I've been experiencing broken up smoke trails / contrails. After my SQN mates told me that it works fine at their end on MT version, I've decided to completely reinstall DCS to remove all possible mod interference. After reinstall, I'm still seeing these broken up smoke trails. Am I missing something? I've tried searching the forums for this issue, found nothing so I'm not completely sure what to do next. smokeBrokenUp.trk smokeBrokenUpMissiles.trk dcs.log

Might it be worth to take another look at the RCS values? When looking at it from pure layman perspective, it is impossible that a smaller object will have smaller RCS than an object that's larger version of it. In this case, GBU-38 will be intercepted (Mk-82 bomb body), but GBU-12 will not (same body, but with guiding fins equals to more things "sticking out of it" and increasing the RCS), let alone Mk-83 and Mk-84 class bombs and its derivatives. I am only speculating, but with the size and shape of CBU-103/105 canisters, they should be roughly in the same category as Mk-83s

@BIGNEWY Can you merge this one too? It does looke like it's related to this issue

Is it like this?

Yes, this is exactly what we've been experiencing? Do you maybe have a track of this mission?

Hmm, could be that it happens when I get TADS feed on my MFD. A point to test out, hopefully I manage to get it captured in a track

Last two nights, we had training and an mission flying in our group. What I noticed is all of us in Apaches are getting weird white flashes every now and then, looks like only at night. Both training and mission had a transition afternoon -> dusk -> night and the flashes started to happen after dusk. I was trying to reproduce it by just sitting in an Apache at the airfield (for about an hour) and hoping the flashing will start, but nothing... Maybe this will give few pointers? I mean, we were a 3-ship, one was fully crewed, other two were pilot only and all four humans saw the white flashes. I will try to run few more tests tomorrow, but I don't know what could be the common thing to try to trigger it. One guy flies in VR, other three were in pancake mode, all different resolutions and settings, so pinpointing will be difficult