Saber2243

If you want to add your track files or anything here

Bug submit form, Multicrew Radio Menu Does Not Work: Bug: When flying multicrew, trying to use the radio menu does not work, Tankers, AWACS, and the supercarrier will not respond to radio calls Can I reproduce it 100%: Yes If not 100%, how often out of 10: How to reproduce/ description: Step 1: F-14B cold/hot/air start Step 2: Tune Radio to intended frequency Step 3: use radio menu binds to contact AI aircraft (tanker was our usual test subject) Result: No response from AI Neither Pilot nor RIO can contact once the RIO slots in, even if the RIO slots out and is replaced by jester, the AI will continue to not respond to radio calls. DCS Version: 2.8.0.32066 Open Beta System Specs: Varied-able to reproduce across multiple people Peripherals: Varied-able to reproduce across multiple people Headtracker: Varied Mission File: Attached Log: N/A Track: Attached, Video/ Screenshots: Mods: This track file was generated after disabling mods, I am currently running a repair, if a new track is needed post repair, let me know and I will provide --- testing29OCT22.miz server-20221029-154047.trk

The issue appears to occur if a pilot and RIO slot and load into a jet (lets call it Jet A), and then unslot and slot into a new jet (Jet B), then another crew slots into Jet A. Sometimes all four members of the crews end up in the same jet, with various parties having control of various components, and stuff generally just breaking. Here is a track file from both sides after we managed to reproduce the issue, it occurs about 45 minutes into the track, just after the Jet B does an aileron roll for the second time, (after the touch and goes are complete) Jet B RIO trackfile https://drive.google.com/file/d/1QSL5ryVTx1l_gRY1I5iGAHoOUTyAA4o9/view?usp=sharing Jet B Pilot Trackfile https://drive.google.com/file/d/1R5hk5EVi4BvcI6_JOEaRp-oTpZgrPbmE/view?usp=sharing Jet A RIO Track file (trackfile is completely destroyed) https://drive.google.com/file/d/1JvicxWDxNlI4NoLocLD2uCdxVhU76-AV/view?usp=sharing We did this mission with no mods in order to ensure a clean track for you Mission file attached CASEIII_training_CA_04_29_2021.miz

Thank you, @IronMikeI am available for any questions, we will try to get you as many track files as we can, this only started with the most recent patch, there was a line about the netcode being changed.

--- Bug: When playing multiplayer, RIOs may sometimes be accessing the same cockpit, changing a switch in one jet results in the other jet having the same inputs, the end result is the controls get swapped back and forth as both RIOs try to make changes Can I reproduce it 100%: No If not 100%, how often out of 10: 5/10 How to reproduce/ description: Multiplayer Mission on dedicated server (have not tried on self host) Load into at least 2 jets (this has occurred on a server with about 8-9 jets fairly consistently today) The most obvious sign the bug is occurring is when the sounds stutters as if its switching back and forth between 2 jets. DCS Version: OpenBeta 2.7.0.5118 System Specs: CPU Intel Core i7-9700K GPU NVIDIA GeForce RTX 2080 8GB RAM 32GB RAM SSD EINTEL SSDPEKNW10T8 OS: Win10 Peripherals: Joystick: Thrustmaster T1800M Throttle: Thrustmaster T1800M throttle Pedals: Thrustmaster FCS pedals Others: Clickedyclick MFDs and Squeektech Radio Panel(*) Headtracker: Opentrack Mission File: See attachment Log: please attach if you have. Track: no promises it works, but thats what I have, issues are more or less constant through the flight, I (Stick is fliyng and I, (TiFuS) am RIO) seem to be linked with Zerk (pilot) and Bulpup (RIO), but I am not sure. Drive link for trackfile: https://drive.google.com/file/d/1A-J1nnvwFxD-mx7zlYeiDHDhB_JPR0qT/view?usp=sharing Mods: a whole bunch, but none that should affect the tomcat, none of them were used for this mission fighter_sweep_04_22_2021_v0.1.miz

I know that one of the big appeals of static units is that they have less impact on performance compared to other units, would this affect that?

So you agree though that the MH works as expected

PD and P STT against a MIG-29A, I am using the MH not the M, the M shouldn't be lofting at all

I am moving into shaky territory here but I have made general observations: 6.5 seems to be fairly safe from an INS perspective, 8Gs tends to drift the INS by a noticeable amount but it remains functional, 10Gs routinely either drifts the INS a ton or breaks it entirely The rate of onset of Gs makes a difference, sudden hard pulls are much more damaging to the INS than gradual G onset

I am very sure, the Aim-7M issue with jammers non-widthstanding, the Aim-54 now properly goes active on lost tracks, it goes active immediately and properly after a pulse-stt launch, and the aim-7mh lofts correctly for long shots and doesn't loft for short range shots

Unless you are flying 3hour+ flights consistently or pulling over 6.5Gs, the drift shouldn't be large enough to be noticable most of the time. In your average 2 hour flight, you might get a drift of .1 minute lat and long. It's only when you pull lots of Gs you drift the INS significantly. EDIT: also the TA AN fix takes about 30s if you have connection to a TACAN station, so hop in the backseat and do it really quick if it's an issue in single player.

I just want to say thank you so much for fixing the AIM-54 and AIM-7 guidence, it is soooo nice to have missiles that function as expected. There are still some random desync issues, and the AI still go defensive for TWS launches, but the missiles do what they are supposed to and it makes a world of difference

I mean it clearly doesn't operate the same way as a traditionally steered radar, because it can engage 4 targets simultaneously with its ostensibly semi-active missiles, which is not something a conventional radar can do. It is not a stretch that RWRs would react differently to this type of STT

This is true of most conventional radars, but nobody really knows how the PESA and AESA radars handle this, and the currently accepted rumor is that they don't have to add in an additional signal and therefor do not provide any kind of launch warning for the RWR

You can, the procedure is the same as on the ground 1. select the waypoint on the CAP panel 2. punch in lat-long as you would for ground alignment or any waypoint things to make sure of: you put the lat long in the correct format degrees, minutes, decimal minute you have the right N/S E/W set when entering the waypoint your INS is aligned correctly and has not drifted The waypoint is in the TID field of view