Tailhook

While everyone here I am sure appreciates the work already dedicated to a third-party communication system like SRS, from a product standpoint, it is in the best interest of ED to also produce their own system of realistic radio transmission. Digital Combat Simulator, AKA The Battle Simulator is also a platform used by the US military. If ED integrates their own radio communication system it will more accessibly open militaries to using DCS for coordinated training scenario's via local multiplayer.

https://forums.eagle.ru/showthread.php?t=211195 This one too.

No, but actions speak louder than words. You experienced the competition and chose to switch sides. Doing so contradicts your claim the F-15C (with only 120B) is still superior in this scenario.:doh:

Is that why you switched to Blue (Iran) after Red got smacked the official round?:music_whistling: Your stats per the gadget: (F-15C PvP kills October 19-22) 2 MiG-29A 4 Su-27 4 M2000C 1 F-5E 1 AJS37 8 Su-25T 3 Mi-8MT 1 MiG-21Bis The round IS the test. And it lasted 3 days. 2 actually, but we can say 3. Strengths and weaknesses? Blue is the strength and Red is the weakness. The proof is in the available modules and weapons. True to a margin if we're referring to numbers. Blue currently has 300+ registered while Red has 500+. During the start of the official round, Red had roughly 100 more registered players than Blue by the end of all 3 days. Each team is limited to number of consistently active players, their ownership of not only Persian Gulf but also the aircraft modules themselves and their efficiency in those aircraft. Aircraft and helicopters alike.

Of course, when you have nothing to internally look at, you are going to reference "the ball" in this situation. ;) Unfortunately however, the Hornet's current damage model programming is so weak right now that it's impossible to recover a damaged aircraft when you lose electrical. Every single, and I mean every single sortie, I've lost electrical, both engines automatically shut off after 10 seconds forcing me to eject. Yes, the vector placement will never be exactly the same depending on conditions, but the movement of position is minimal. I've grown accustom to knowing what I should be seeing depending on wind and carrier speed. I just prefer to "ballpark" it by flying the vector anyways. I've ignored the "by the book" way for over a decade and instead do what works well for myself. ¯\_(ツ)_/¯

I'd like to see you switch to our side and fight 1v2 with 120B's against coordinated opponents with ET's and ER's. 1v2'ing over equal terrain isn't hard, actually trying to kill them both before they kill me with their faster and longer range missiles IS. ;) Statistically on paper, as I put it above, 1v2+'ing with possible 8 120B's on F-15C vs possible 14 R27ER/ET's on two Su-33's is a clear disadvantage, regardless of the AMRAAM fire and forget. The 120B is only effective less than 8 nm with kill range of about 4 nm. The only way to win in such engagement is to gain some type of advantage like being sneaky, having more altitude, or catch the opponent off-guard by joining in on an engagement with another friendly. Other than that, when fighting against someone head-on that knows what they are doing, the situation is tricky. During the official round Blue had most of the virtual squadrons participating as CAP while others were taking objectives. Red (USA/UAE) was having a hard time holding back the enemy CAP just off the coast of Dubai for a quite a while. Most of Red CAP was 70% Hornets 30% Eagles which resulted in a number of friendly fires. During the second day, Blue managed to take Khasab and proceeded to attack and capture the whole South-eastern side which ended up pinching Red badly. Third day, most of Red gave up cause it was already game over with carrier dead and 85% of map was Blue.

I almost never reference "the ball", even in VR. The only time I do, during daylight, is peripherally for a split second to verify my altitude on glide slope. Other than that I'm watching my velocity vector and speed the whole time. https://clips.twitch.tv/ClumsyLuckyRedpandaBibleThump

I don't want to be that one that complains about imbalance, but wow. After some testing and researching, I simply don't know why Red (USA/UAE) isn't allowed the 120C but Blue (Iran) gets their whole A2A and SEAD/Ship arsenal. Below is tested in current OB 2.5.3.23225, F-15C and MiG-29S/M2000C flying around 7000 feet and 550 knots with radar lock on each other: (Note: 2000 knots equals to 0.639 MILES per second.) 120B - Rocket lasts 8 seconds. Hits 1600-1800 knots at 8 seconds. 120C - Rocket lasts 8 seconds. Hits 2000 knots at 7.5 seconds and sustains for 0.5. R27ER - Rocket lasts 10 seconds. Hits 2000 knots at 3 seconds and sustains 2000 knots during remaining burn. R27ET - Rocket lasts 10 seconds. Hits 1900 knots at 3 seconds then slows to 1700 knots during remaining burn. R77 - Rocket lasts 6 seconds. Hits 1900 knots at 6 seconds. Super 530D - Rocket lasts 10 seconds. Hits 1700 knots at 10 seconds. Why is Su-25T allowed Kh-58U and Viggen allowed RB-15? Nothing A-10C has can compare and neither F/A-18C or AV-8B has HARM/Harpoon yet...:music_whistling: No wonder Red got absolutely smacked the official round. Trying to head-on BVR fight 1 F-15 vs 2 Su-27/33's (or J-11's)(non-suck pilots) is impossible. If we don't TWS spamraam every 3-5 miles starting at 18 miles, we're dead before we make it to 120B's effective kill range of 3-6 miles, depending on each other's engagement tactics. If we aren't given 120C's to counter the ER or if the ER isn't removed from Blue, I think I'm done on Blue Flag for a while. Getting tired of being outnumbered as CAP (F-15) and outgunned because of it. Hornet's are useless CAP right now and everyone seems to prefer it over the Eagle. If the ER gets banned then the M2000 could stay on Blue, but maybe in order to fix the Blue to Red ratio of players, it should be moved to Red. Also, I think helo's shouldn't be able to carry both a repair crate AND troops at once. P.S.- My stats aren't registering on the gadget website; only sorties, landings, and deaths are being recorded.

Been wanting to start a thread on this for a while now. Thanks for doing so. Ever since we got the first aircraft with an actual radio, a built-in radio system should have been started. We are long past due now. Would be no issue if it runs on a parallel server (different port) similar to Falcon BMS.

No. We already have wing flex and it was done just right. Any more wing flex arguments and you'll see every Hornet over multiplayer with continuous flappy wings.

So I took an IR up the butt and resulted in complete loss off electrical and power. Most of the enemy airfield was cleared so I glided back to dead-stick land it with hopes of being able to wait for my team to capture it and repair. I managed to belly land and waited for the capture (15 minutes). Repair started and the moment it dropped my jet to the ground I exploded. I assume this might be an issue with every aircraft (or maybe just non-FC3) but I haven't experimented. It would be nice if the repair would auto extend the gear during repairs so this type of thing won't be a problem again. https://clips.twitch.tv/BloodyFamousMomItsBoshyTime P.S.- I've also noticed EVERY single time the electrical gets shot out, the engines cut off after 10 seconds too. Is that realistic with the Hornet? Cause I'd like to still be able to RTB without any electrical like I frequently can do with the Eagle.

This. I'm undecided on how to feel about the decision to put the Hornet (in it's current state) in such a hostile environment. It's not ready. Without IFF it can barely handle one bandit at a time because you spend more time verifying contacts than actually focusing on your situational awareness. I heard a number of friendly fires and "raygun"'s and the arguments over SRS weren't pretty. Also, the reason why Red had so many registered numbers (and yet got SMACKED) was because every casual decided to join the server just because it was on top of the list and Red had the only American aircraft. They just hopped in, died, and left. And don't forget most importantly, most of them weren't on comms. Blue however, had the most number of virtual squadrons participating and forward observers. I feel if you consider the variety of aircraft and module ownership, Red was outnumbered 3 to 1. I think I got engaged by more Mirage 2000's than MiG's and Flankers. Therefore I think to help balance this fight, either add France to Red and remove it from Blue, or have M2000 on both sides. The A-10A should also be available.

Figured I'll share my 48 hours of trail and error. Enjoy! :) I'll maybe add more when the Tomcat is released. For now the projected image is fps is 7, but Rift fps is normal... sceneVR (Hornet Dusk Deck Level).lua sceneVR (Hornet Dusk Paddles).lua sceneVR (Hornet Dusk Vultures Row).lua

So your choice is to harass them until they tell you something you don't want to hear? It will be released when it is ready.

That PBR texturing though! So pretty. :pilotfly:

Subtle and PBR rich.

Is there any benefit to installing the Su-33 module (or any FC3 aircraft) on top of FC3? Wondering cause myself, and probably everyone else, got the notification to install it.

Also wipe the _downloads folder contents too.

They're not supposed to work in VR. If you want to change the default viewpoint switch to 2D, save new location by the key command or edit the plane views LUA (look for CockpitLocalPoint), then switch back to VR.

Nice. Will try this out. I haven't gotten around to setting up my own kneeboard yet but will cross-reference this when I do. :)

I voted for HARM as ultimate request but I know it will require a lot more work. My order of preference for updates, based on want vs need with consideration for multiplayer and joint tasking effectiveness 1-10 with 1 being most needed 1- Data Link (MIDS / Link-16 / IFF) 2- ATFLIR Targeting Pod 3- Guided Bombs 4- Air to Surface Radar 5- HARM 6- A/A Radar TWS/RAID/AZ EL/LTWS 7- Harpoon 8- Joint Helmet Mounted Cuing System (JHMCS) 9- Automatic Carrier Landing System (ACLS) 10- SLAM / SLAM-ER

Clearly snapped by force or didn't set them up correctly. Between us using them for months now with no issues and the thrashing use of them by big and small people at Oshkosh with no issues, there's no way that part snapped without sheer weight on the pedal.

Please remove the 'lock' between the VR/mouse cursor and the headset when 'Use Mouse" is enabled. When enabled, the blue VR cursor SHOULD NOT move around with headset movement. Currently, we have to look straight at the button or switch and keep our head stationary while moving the mouse to click, or else the headset will drag the mouse away from the button/switch. Having to fight between the two different cursors with this override lock in VR is frustrating, especially during a battle. Edit: To make it more simple... Let us choose between Headset Cursor or Mouse Cursor. Choosing one disables the other.

If Alt-Tab doesn't work, just use Windows key, then click on the taskbar to click out of DCS. Control-Alt-Delete and then Task Manager also works. In Windows 10 there is a very small vertical bar on the bottom right in the task bar with no icon to the right of the clock time and system notifications icon, click that little bar and it will switch to desktop view.

After spending some time in VR on multiplayer servers that run custom scripts (mission intel) that require key functions, I found it annoying to keep raising my headset just to input keys. I think a virtual keyboard you can toggle on and off in both 2D and VR would be helpful and efficient. I used the Windows virtual keyboard as an example.