Arbil

I'm speculating but I think one of the ways they have alleviated this issue for the super carrier is by disabling the ship reacting to the movement of the water. The carrier is solid in the water like an island, with no deck pitching. I hope I am wrong on this and if I am not wrong I hope that it gets fixed very soon.

I have a 3900x, 2080, and 64gb mem. Even with wake turbulence off when the bombers drop their ordinance on mission 3 it absolutely tanks my machine. Then, when we merge with the German fighters during egress and everyone starts shooting, I get another hit not quite as severe as the first one but still pretty bad. I will try with the lesser units option and see how it behaves. Seems to me it's when DCS starts calculating all the bombs falling/guns shooting it's not properly optimized to handle all that ordinance at once.

Awesome, thank you for the reply. What is happening with the radio thing is: 1: I switch the radio to channel A so I can give orders to my wing. i.e. have them switch formation or have them attack targets when we engage. 2: As soon as I select the final menu option, like "finger four" or "engage bandits", the radio automatically goes to channel C and I get no response from my wingmen and they don't follow the order. Again, thanks very much for your reply and all your work.

In mission 4 Yellow flight members 2 and 4 seem to be parked in the same parking spot. So they never start up or take off and I never have the full flight to trigger the start of the mission. I checked in the mission editor and it looks fine there, they are in separate parking spots. But when the mission starts yellow 2 and 4 seem bugged out. Please help. Also, in mission 3 when switching the radio to channel A and trying to give my flight orders it automatically switches back to channel C and nothing works/no one responds. I was still able to complete this mission though. Thank you for any suggestions/help. I already tried uninstalling and reinstalling the campaign. Also, I do not have easy comms enabled. I also tried going into the mission editor, making a new mission, and putting a 4 wing flight in the same parking spots as in mission 4 of the campaign. The bug did not replicate this way. There was a plane parked in spot 7 whereas in the campaign mission they are both in spot 5.

I think I replicated(x2) what you are talking about by using the mouse wheel to click/hold and drag the bearing/distance line. After I did that I could only select units I had placed on the map already. I can't select any of the menu items on the left or upper part of the screen. Mousing over them does not highlight them like it does when it's working properly. Have to quit the game from task manager.

I tried deleting the imagesShop folder and it had no reproduceable results. The only thing I was able to repro 100 percent of the time was this: Launching the game from a shortcut pinned to the start menu failed to launch\hung 95% of the time. Launching the game from a new shortcut created from the run.exe in the main install folder and placed on the desktop successfully launched every time. Pin that newly created shortcut to the start menu and it goes back to hanging and not launching.

I'm getting a consistent crash on the 4th mission, fairly sure it's the 4th. After you destroy the 3 bunkers and the friendly AI is going to move forward and they tell you to help where you can. I get a crash every time when, I'm assuming, they start moving\pathing.

This is exactly my issue as well. Here is my thread that a mod can either merge or close if they'd like to. https://forums.eagle.ru/showthread.php?t=265913 After trying secretcode's idea and running the game from the run.exe in the main install folder instead of the pin'd shortcut in my start menu, I just got the game to launch 3 times in a row, yay. :) Here's what I noticed: When launching the game from the .exe in the main install folder the small windowed splash screen pops up, the resolution looks normal, then the screen flickers and the small windowed splash screen goes to an incorrect resolution(looks warped\stretched) and then the full screen splash screen comes up and the game loads correctly. When launching the game from my old shortcut pin'd to the start menu the stretching\warping of the small windowed Eagle Dynamics splash screen did not happen. Also, I tried deleting my old shortcut\pin from the start menu and then pinning the run.exe back to the start menu anew and the game failed to launch. I also created a shortcut from the run.exe and placed it on the desktop, not pinned in the start menu, and the game launches normally from there. It seems like the issue comes from trying to launch the game from a shortcut pinned to the start menu. Let me know if you need anymore help.

I deleted the folder and then it launched, this was also the first time I had tried to launch the game since yesterday(if that matters. It seems to me like it will always launch the first time after sitting for a while, IDK). Exited the game and tried launching again, it hung this time. Killed the process and the deleted the imagesShop folder again and tried launching and it hung, did not launch even though the ImagesShop folder was deleted. I notice that in the task manager, after the sign-in\authentication happens, the DCS process goes not responding for a bit while the new little windowed Eagle Dynamics splash screen is up. Not sure if this is normal or not. Then it starts responding again(according to task manager) and the full screen splash screen comes up, then the menu music kicks in but the splash screen just hangs.

On the 2.5.6 patch my game hangs at the black DCS full screen splash screen with the menu music playing in the background. I uninstalled SRS and Tacview then ran the cleanup and repair but no joy. Restarted the PC. Game is still hanging on launch. Please help. Standalone, not Steam. Logs.zip

Issue still persists after letting the game create a new saved games folder and re-logging in. I'm beginning to think my issue isn't related to the mods or saved games folder. IDK

Not using Viacom or voiceattack. When I say this is a brand new PC build and srs is the only mod ever installed on this machine I mean that literally. I rolled back but I'll update again when I get home and try renaming the saved games folder and report back.

Here are my logs. Hopefully it helps. Logs.zip

The only mod I had installed was srs. This is a new PC I just built recently. Srs is the only mod that has ever been installed on this machine. Last night I tried uninstalling srs, then doing a clean and repair per the instructions in bignewy's sig. The game still hangs 90 percent of the time on launch. Hangs on the black dcs splash screen but I can hear the menu music. At work now but I'll get my logs posted when I get home this afternoon.

What's the best way to go about adding my logs to this thread here? Putting them in a ZIP in my google drive and creating a shareable link? I can hardly get the game to launch for me at all.

I have no mods but SRS installed. Can confirm game just hangs while trying to launch when SRS is running beforehand. Shutdown SRS and the game boots up fine.

This would be great and very much appreciated.

This doesn't make any sense to me. We're talking about position lights, which unless I'm totally out in left field, are supposed to make your aircraft visible to other pilots/jets and controllers, and you're telling me that you can't tell if these lights are on unless you're close enough to see them reflect off an external surface?

The right and left upper wing glove lights, and really the wingtip lights too when the wings are fully extended, are clearly visible when sitting in the front seat of the cockpit. Now, I suppose the argument can be made that during the day they could be too dim to see from the cockpit no matter what(which I don't believe) but at night you should definitely be able to look over your right or left shoulder and check the status of the upper wing glove lights. As of now, there is absolutely no change in the lights when turning them on and off and viewing from the cockpit, has nothing to do with dimness. Also, the wingtip and wing glove lights should be operating dynamically depending on the wing sweep angle. Also, what exactly constitutes the approach lights? Because the approach lights should be operating independently of the master lights switch on the throttle.

I brought this up when she first came out but haven't seen anything about it since. I should be able to turn my head in the cockpit and see if my exterior lights are on or not and not have to go to the exterior view to confirm this. I know it's minor but this would be a huge qol and immersion boon for me. Please at least let me know if this is on the radar to getting worked on at some point. Also, does the main lights switch on the throttle have an audio cue? Doesn't seem so to me.

Mine defaulted to 305.000 when turning it on.

As I understand it I believe that when entering ILS data once you hit enter inputting a correct ILS frequency the DED should auto-step down to the ILS course field, shouldn't have to dobber down to it.

Since I started this thread I wanted to update and like others have said, I'm 99% sure my problem here was related to the left wheel brake acting funny/not working, which Nineline has said they have reproduced and it's a known issue now.

If I'm going off exactly what your title says, "Autopilot Pitch Attitude Hold switch engages Roll Attitude Hold", then that is how it should work. There is no off position for the Roll autopilot, it's either in steerpoint, heading select, or attitude hold. The autopilot on/off switch is the pitch hold, either Altitude or Attitude. Turning the autopilot on is always going to engage one form of roll autopilot no matter what. The only one working right now is the basic attitude hold, the middle position on the roll switch. I haven't had any problems with it working correctly so far. Now if the aircraft is out of trim it can feel like the roll attitude isn't really working but that is how its supposed to work. None of the autopilot modes engage if pitch/roll exceeds/is exceeding 60 degrees, but the switches stay in their on position making it seem like maybe they should have engaged ... perhaps you are seeing this sometimes?

A quick Google search should net you an actual f16c\d manual that answers all these questions in depth. One thing I gleaned from it that isn't right in our simulation is that in autopilot modes the stick trim should not be functional.