Silver_

I have excluded the two MFDs in the script, so many buttons should not appear, right?

In the virtual game controller appear more buttons than my hotas stick has, is this normal?

Checking the output log of the target when I load a script I have seen that there are several entries that are not found, but the only thing I have is the warthog stick, I have nothing else. Could this be my problem? Running script: C:\Users\Silver\AppData\Roaming\Thrustmaster\TARGET\Scripts\DCS_Warhog.tmc *** Allocated ProcInstances found from the previous run: use FreeProcInstance() *** Mapped plugin module "C:\Program Files (x86)\Thrustmaster\TARGET\Plugins\sys.dll" Compile Succeeded. Physical USB HID devices managed by script! Currently plugged USB HID devices[3]: 1: "Joystick - HOTAS Warthog" - "USB\VID_044F&PID_0402&REV_0100" 2: "F16 MFD 2" - "USB\VID_044F&PID_B352&REV_0100" 3: "F16 MFD 1" - "USB\VID_044F&PID_B351&REV_0100" USB HID device "Joystick - HOTAS Warthog"(USB\VID_044F&PID_0402\8&2EFE0359&0&5) selected USB HID device with hardware id "VID_044F&PID_0412" cannot be found USB HID device with hardware id "VID_044F&PID_0413" cannot be found USB HID device with hardware id "VID_044F&PID_040E" cannot be found USB HID device with hardware id "VID_044F&PID_040F" cannot be found USB HID device with hardware id "VID_044F&PID_0416" cannot be found USB HID device with hardware id "VID_044F&PID_0417" cannot be found Virtual HID devices managed by script! Connecting virtual joystick...Done Device name set to Thrustmaster Combined Connecting virtual keyboard...Done Connecting virtual mouse (absolute axes)...Done main returned 0 Script stopped!

I hope DCS takes note of this and doesn't ask for more evidence.

I like your way, it's better, but try PRESETs. You're going to get a surprise. I add the track I made to demonstrate the illogicality. Let's see if I can convince DCS. Thank you so much @Moonshine DemoWithPresets.trk PD; Without presets goes like a champ, with it NO.

My evidence is that of working with electronic radio equipment all my life and that does not follow any logic.

What I want to tell you is that in UFC mode (C&I switch) you use one radio and in Backup mode you use another (emergency radio, normally the one preselected with the switches on the left panel). When you change to UFC, the UFC presintonized configuration of tuning/channel must remain in the radio and when you change to Backup, the radio presintonized (in lateral panel) configuration tunning/channel must remain in backup, I think it is simple to understand. This does not happen in your current software.

Situation: When I change the C&I selector to backup to communicate (transmit) through the guard channel previously selected on the switch indicated with the red arrow, the DED, as normal, shows me the guard frequency (previously I had a preset set in for example, channel 8). When I go back to normal mode (C&I to UFC) the preset I had disappears and instead of showing me channel 8, the DED continues to show me the guard frequency. I understand that this should not be like this. Please correct it. Thank you.

"Pathetic" no, I would never say that. Tell that to those who speak in those terms, but it borders on the absurd, yes.

You need to create a file called settings.cfg, it is a bit handmade but it is not complicated, you can guide yourself here to configure what you want on your gogles.

That "nearly" sounded very bad but I thank the ED team for being on it and not falling on deaf ears.

I'm trying to find a solution both at the hardware and software level but I can't find it. I have changed from USB 2.0 to 3.0, I have updated the firmware to the latest version (12), I have connected the Stick to a USB hub and I still get absolutely nothing. Sometimes I have had the feeling that the TARGET application, when I load a script in my startup, blocks my controller. The symptoms presented are that of a dead stick, the USB controller is detected by Windows but neither the axis nor the buttons respond, they are frozen. I take out and insert the USB and it comes to life again. I have read a lot of posts with similar things but none of them clarify a valid method for this problem. I have also heard of static problems, I am electronic and I could solve it somehow but I don't think this is my problem. Does anyone have any effective solution for this? (downgrade firmware, need electronic mod, software problem) I'm tired of taking the USB in and out so much, I hope someone can enlighten me with something good. Thanks for reading me. Note: I have Win11 64 bit (could this be the problem )

Friend @BIGNEWY, you are right in stating that community testing is very useful, hence the Beta version, to improve a product, but also keep in mind that a product that does not even provide the minimum quality for testing will never be tested by this just as your efforts and dedication deserve, especially having competing software like SRS that does not present problems. Let it be known that I prefer a thousand times more the immersion and realism that Voice Chat provides (noises, signal fading, etc.) but unfortunately I have fought a lot in my flight group to have it tested and people are already tired of so many problems of connection and disconnection, hearing and not hearing and many others that I currently do not remember. Please try to make an effort and focus a little more on the real problems and not on the minutiae as the community does for you. Thanks you.

I totally agree it is wonderful but when it works. A few days ago we tested it in my flight group and observed the radio effects, I was impressed. When you get into a valley you see how your partner's signal deteriorates and the noise increases until it cuts. I also observed that when someone was talking to me and a third person was transmitting above, the voice of the person transmitting could be heard, the one who was closest to you) attenuated and over-modulated and those who transmit further away cannot even be heard. I have been a radio amateur for many years and this advance was impressive for me and, by the way, very immersive. It's a shame, as @gallorojo says, that sometimes it works and other times it doesn't, it always gives us problems with more than seven people. Me too, please fix it.

For me, OK.

Where this problem becomes evident is in the Instant Action mission, F16, Caucasus, free flight. When I activate the TGP and fly over the enemy troops it gives me several flashes.

There were 8 of us in my flight group and we opened our ports on the router to try, no luck either. Some saw each other and others didn't, others of us saw everyone. In the end we have opted for SRS. I dont know what is the problem.

In my case with HP Reverb G2 I cannot see anything under the NVG tube, I would like to be able to raise the NVG vision a little but I don't know how. Another problem is that through NVG the noise is very loud and everything is out of focus (I imagine reality will be that harsh).

Yes, here is the answer, although I personally get more performance by raising PD in DCS. But hey, you can try this thing I put here: To do this you will have to edit your QVF config file

On the Hornet the STN numbers are meaningless in fact, as far as I know, only the Viper uses them. In our flight group we add that information to the kneeboard, previously extracted from the editor, but this is only useful for the Viper guys. On the other hand, in the Hornet a very different method is used but for practical purposes it is the same. On the SA screen you have two buttons, at the bottom left, one is MEMBER and the other is DONOR, you have to stand above each plane in the SA and press one of these two buttons depending on whether it is your Member or your Donor (in a dot will appear when assigning them to the donors and a flight letter will appear on the members). In case it is not clear to you, a MEMBER is an aircraft in your flight group and a DONOR is an aircraft in another flight group with which you can/want to share data. In the Viper, at the moment, sharing data is limited to, for example, the video you posted above, although there are more unimplemented functions such as indicating to a member of the flight which plane should attack. On the Viper you indicate that you want to share information with the letter "T" (Transmit). The Hornet video clarifies all this:

In the instant action mission in the F16, free flight, Caucasus theater and coinciding with what the companions point out, that is, with the TGP activated, the white flashing occurs (like a photographic flash). I use MSAA at x2 and nothing else, no SSS and no DLAA. Everything in VR. I have flown several missions at night and during the day and this flicker occurs interchangeably but always in white, I never saw it in black unless my glasses for some reason lost tracking, but that is another topic. I have started to observe it since your last update, I never had this problem.

Another thing that I have noticed and that has nothing to do with the configuration of the graph, it happened to several members of my squad, is that randomly, sometimes, you see a flash in the glasses, as if they were doing a photo and I'm sure it wasn't my wife. This not only happened to me, as I said, and it coincided with the last patch, at first I thought it was the strobe but that was not the case because I turned it off and it continued doing it but very occasionally.

Another thing that I think has not been mentioned, apart from the radar lines, is how bad the TGP camera looks on the F16 when DLAA is applied with or without DLSS, all caused by what has been said here in previous posts. The trace left by the objects blurs everything. With MSAA all this disappears and the movement of objects is smoothed even when flying at low altitude. Of course, the FPS performance is wonderful with DLSS but no more.

I did exactly that and I say the same as @Qcumber, I'm still not sure which one gives better results. Although referring to what he told me in a previous post. I notice that I do slightly better by increasing the pixel density than by keeping it in the unit, especially when I apply DSLL. I have tried several online flights with positive results. Either way we are here to continue testing any good suggestions with QVF and the new anti-aliasing modes.