andhog

I've just returned to DCS after a long break and stumbled on this issue. It's very inconsistent, sometimes I have it and sometimes I don't (on the same server). Also I've noticed that the bad FPS after F10 map only happens in cockpit (AH-64), if I go to external view (F2) the issue disappear until I return to the cockpit. It usually takes about 3-5 minutes for the FPS to return to normal. Another think I've noticed is that even though it feels like the FPS is single digit it's actually only dipping from 72 to around 60-65. But I guess it can be that it's fluctuating between 0 and 65 too fast for the FPS number to update. I will try the alt-tab fix next time, hopefully it helps but what I would really like is for ED to fix the issue of course.

A mission planner where you could: See weather info (winds, cloud base etc) Create flight plans on a map (waypoints, IPs, offsets etc) Set the payload Configure countermeasures Configure comms Configure data link

Excellent idea that I've been thinking of as well. It's a bit sad that the briefing room is developed only for carrier operations. I would rather see that they split the mission editor into a "scenario editor" and a "mission planner" where the "scenario editor" would be where you set the scene and the "mission planner" would be the tool where pilots plan the mission/missions. The mission editor is currently both and that's perhaps ok when you want to create a single mission and then fly it yourself. However, when we have things like Pretense on MP servers where there are multiple available missions to choose from we really need a way to plan our sorties. Just to have the ability to create flight plans on the F10 map would be a great step.

Same here. When I first launched the game after update I could enable DLSS and SSS, but after restart these options are greyed out and it doesn't matter if I "turn them on" in options.lua No AA enabled.

That sounds awesome! Is there perhaps any chance of a "Declare Hostile" campaign as well?

I have failed this mission twice now for unknown reasons and I am also a bit confused regarding the formation. Yes in the brief it says you're supposed to fly in front of the S-3 but on the kneeboard card it says you should follow it. I'm my two attempts I've been flying to the left and behind it and it doesn't keep the ground speed stated in the mission brief so if I where to fly in front of it and at the briefed GS I would run from it.

Just managed to complete mission 10 after some failed attempts and that was by far the most challenging sortie I've ever made in DCS. The reason for that was about 50% the mission itself and 50% how the mission was created. By that I mean I understand that these kind of missions must be very challenging IRL and I actually liked it, but there where some things I wish the developer had done differently. First, when starting the mission it felt like starting a 100 meter at the Olympics (not that I've done that but anyway) and it took me 3 times to get it right. Configuring those JDAMs and everything else HAS to be done prior to take off because once leaving the catapult all focus will have to be om the flight lead. It would have been nice to have proper time to set things up after "spawning", like with the previous missions where you press spacebar to set things in motion when ready. Then, when I finally managed to get that part right, keeping up with the flight lead was as tricky as it gets. All of a sudden he banks right, then left and light the cans. It's most likely a DCS thing because I've encountered this behavior during the other missions as well, but the fact that this was a night sortie makes it 100 times harder. Perhaps it is what it is, but if there's something you can do to ease those "transitions" it would be nice. ANd finally, during the recovery I didn't get the message to "kiss off" my wingmen until I was about 5nm from mother on final approach. Since this was a CASE III recovery it would have been more natural to let them loose before calling inbound to give them a chance to enter the stack properly.

Just did the CASE III recovery on mission 10 and I got the message about pressing spacebar to kiss off my wingmen about 5nm from touch down. At that point I was pretty concentrated on not crashing so I almost missed it. Feels like it should have been better to "kiss them off" before the inbound call so they could have joined the stack properly.

In this case MOTHER is the same as MARSHAL. As for the recovery procedure and coms I think you are supposed to use regular comms and call "inbound" and "see you at 10" to mother. When you get closer to the carrier you will at some point get a message saying something like "Remember to hit spacebar to kiss off Smoke". So, when you have passed mother at 800ft on the starboard side and are about to break left you hit spacebar.

Just played this mission and I could however proceed with the mission anyway by just pressing spacebar when asked to. This brings me to a somewhat related question. When Knight is on station and calls out various bogeys, aren't they supposed to show up on the SA (datalink)?

I'll join in here hoping that this issue gets prioritized by ED. It's practically impossible to do night (or even dusk) sorties with exported viewports and thus really needs to be fixed. I appreciate it's may be complicated from a developers perspective, but I find it hard to believe it's impossible.

I was just searching for info about this since I have the exact same problem. This is affecting all aircraft for me and makes it almost unplayable when doing night sorties. It seems like the in-game displays and exported viewports are out of sync when it comes to brightness. If I reduce it in the game my exported viewports goes black when the in-game displays reaches an acceptable brightness, making it practically impossible to use separate displays with exported viewports during night sorties. I maxed out the brightness on my touchscreens to match the in-game displays but it hasn't helped.

I hade the exact same issue and was about to write about it, then I noticed that there are separate comms plans for pri and aux with different channels. I suspect you might have done the same thing as me and used the plan for pri when selecting aux channel?

I'm currently about to start my 5th attempt on this mission, in my previous four Prince ended up crashing in the sea! I'm probably doing something wrong but I can't figure out what that might be. Edit: On my 5th attempt he didn't crash but this time I got the same issue as BuLLeT.ZA. Prince remained "hostile" and zig zagged his way towards the next wp. This campaign has been a blast up until now, but this mission is about to ruin the whole experience unfortunately. Edit 2: I don't know about Prince crashing but the other issue seems to have been me not being patient enough, he eventually turned friendly and the mission continued. Very intriguing indeed!

I have a strange issue with my kneeboard. I'm currently playing a campaign where I'm asked to press spacebar from time to time. However, when I do that the kneeboard will switch page and here's the strangest part. It switches page in the direction I last did it manually, that is if I switch to the previous previous page with my mouse, pressing spacebar will switch in that direction and vice versa. I have checked and double checked my key bindings but I haven't mapped spacebar to anything. As a disclaimer I have VoiceAttack and VAICOM PRO with the kneeboard addon but I can't find anything that would indicate that I have the spacebar mapped there either. How on earth do I get rid of this? I usually have the kneeboard up on my second monitor and it's rather annoying to say the least.

I figured it out! I had to toggle listening on in VoiceAttack!

I'm sure this has been covered here several times but I can't find a post explaining how to solve my issue. I can't get training mode to work properly. It did in fact work just fine a while ago but something has happened along the way and now it don't. The steps I follow is: 1. Choose a command phrase 2. Press "Start keyword training mode" 3. Press the microphone button in the windows speech recognition app 4. Say the phrase Now I expect a line in VoiceAttack where it says which command phrase it recognized and the confidence level, but nothing shows up. Could someone please tell me what I've messed up and how to fix it?

Roger that Skickat från min SM-G973F via Tapatalk

I bought the Supercarrier and switched to the latest 2.5.6 OB but I can't find any super carrier module in the module manager nor in the mission editor. What have I missed?

+1 for having optional kneeboard positions. Using two monitors + spacedesk to get a third on my tablet and the kneeboard appears on my tablet with half of it outside the screen!

I'm trying to figure out whether I'm allowed to sell or give my F-14 module to another user since I haven't been using it for quite some time now. I found this on the DCS web page: "If you want to bind a serial number to a different user account as a gift, you have to create a new support ticket the serial number should be new or not activated if it was activated once, you can deactivate the product and only after that create a ticket" Does that mean it's possible?

And just to be clear, this was not intended as any kind of complaint. It's just out of curiosity and I have nothing against having the opportunity to run open beta and test new features.

Roger that! I can certainly see the implications and thank you for clearing those out in a very pedagogical manner!

Yes, I understand that some upgrades depend upon core features, but is that really true for all of them? And that brings me to another question I've been wondering about. How much of each module is really just core features presented in a model specific HMI and what is really module specific? Take the radar as an example, something that works very differently from aircraft to aircraft. In a modular architecture I would have thought that there was an API with certain radar specific parameters and that every module came with their own radar model. As long as they communicate the correct parameters this radar model should be upgradable independently from the core right? It should even be possible to have a radar model that communicates with a newer API than the core as long as there is backwards compatibility (like in protobuf).

I've been searching for this question but haven't found anything. As the title says, why are the model specific upgrades not released independently? I can understand that certain upgrades are dependent on new functionality in the DCS core, but alot of them could certainly be released as stand alone upgrades right? The 2.5.6 open beta contains numerous upgrades to the FA-18 but since the overall performance and stability is pour, especially for online gaming, it seems I'll have to wait quite some time before I can start enjoying them. I have very little knowledge about the architecture of DCS and the modules, but it seems to me like it's a very modular system and that makes me believe that it wouldn't be that hard to upgrade the modules independently from the core?