norman99

I too would like to know what “Fixed many small and large issues” means. Has the display export rendering problems been fixed?

A LOT of DCS comms are incorrectly given in ° true, instead of ° magnetic. ATC bearings, AWACS bullseye & BRAA calls, as well as Carrier comms. Unfortunately it’s probably a bigger issue than it initially appears, and hence more time consuming to fix.

It’s just a control input, I see no reason why it shouldn’t work. Saying that, I wouldn’t expect the AP button lights, AP mode selector dial or caution light panel to work the way they do in civil FS games, as those use sim specific honeycomb drivers to enable these functions.

It appears very much like you have some inherent instability in your system. Many users use the MIP trouble free, so, without try to sound dismissive, I’d take a good hard look at everything in you system. Make sure you have enough power to drive everything, try running in 2D instead of VR, remove unrelated peripherals & close background software, etc etc. Anything you can to narrow down the problem.

I wonder if the recent news of a full F-15C in development for the “other sim” will make ED change their minds?

Yes. SimAppPro needs to be running for the UFC displays to work correctly.

Not really a big problem when 99% of the time there's no weather at all.

100% this. Can you imagine the uproar if there was just silence until the 1st.

I'm so glad we're getting the old/red UFC. It's unique, and what I picture when I think F15E cockpit. The LCD/green UFC is too generic, and just make it look like a SuperHornet (sort of...) I just hope WinWing like it as much as I do.

Hi, The forum activity feed is not updating for me. When I enable all posts, read & unread, the newest listing shown is now 22 hours old. Occurs both on an Android browser and iOS safari. When browsing through individual subforums, new post and replies are present and viewable as per normal. Cheers. P.S. On a PC, a still get all other notifications, but the newest post reply is now a day old.

Aircraft radios are usually “channelised” for the mission/theatre/location. As an example, here is the recommend channels for ops out of Nellis & the NTTR, from the real world 57th Air Wing’s In-Flight-Guide. As you can see, it is very easy to fill up 20 channels. The lower table contains additional frequencies that may or may not be needed, depending on the exact sortie to be flown. Instead of overwriting one of the stored frequencies, (which are usually the most commonly used) any “one off” frequency used can simply be dialled in using manual mode, leaving the channel frequencies the same every time.

Haha, you got me there.

Hmmmm, your definition of a sure thing is definitely different to mine. Seems a very standard DCS style, non-comital answer to me.

Just to clarify for anyone else, the initial "intent to refuel" call just starts the AAR process, it does not yet assign baskets to aircraft. Aircraft can call "intent to refuel" in any order. Assigning a basket happens with calling "ready pre contact" AND when in the correct position. The first aircraft to call "ready pre contact" and be in position,(not receiving the "return pre contact call"), will get the left basket, the next aircraft the right. Note that if the first aircraft hears "refueling complete" before the second aircraft successfully calls "ready pre contact" on the right basket, they'll have to change back to the left, as it's now deemed empty and has priority again.

I'm hoping to see lots of improvements on the item's they've continuously stated "currently in development" for the last few years. So that means new ATC, data cartridges, dynamic campaign, etc, etc. If all we get is hints at new modules, personally I'll be quite disappointed.

I have a feeling the GBU-24 is not completely modeled yet. Or maybe more specifically, the release cues are not accurate for the bombs flight profile. My experience is with the Hornet and at low level, but similar to yours, in that the release cues aren't to be trusted.

Still only managing a 70-80nm range against a large, non manoeuvring target at 25K. Can anyone from ED confirm this is the desired implementation. If not, can we expect either: a) changes to the current SA-5 equipment (P19/Square Pair) to enable the correct range, or b) the addition of real life equipment, such as the P35/P14, therefore enabling the correct range?

Honestly, I've never found a flight simulator that truly recreates the feel of "atmospherics", as you call it, completely realistically. Whether it's P3D, MSFS, XP, DCS or even a $20M Level-D full motion sim (and I've spent more than enough time in these), they all have their deficiencies. In this regard, DCS is no better, and also no worse, than anything else currently on offer. Commercial FFS systems have an advantage, as the motion goes along way to tricking the mind and therefore increasing the perceived realism.

I think the huge problem with enabling more mission planning options, especially flightplan/waypoint changes, is that the underlying DCS mission concept is entirely reliant on scripted actions/triggers that are themselves heavily reliant on aircraft waypoints. Allowing users to freely modify flight-plans, such as moving or adding waypoints, changing times, speeds of altitudes, etc, will very quickly and easily break missions.

Interestingly, when you export MFS to external screens, they be come substantially more readable. No more constant fiddling with brightness/contrast/auto or manual gain etc. It just works perfectly 95% of the time. Because of this, I’ve come to the conclusion that the raw MFD/FLIR displays are actually recreated rather realistically, but once they are placed into the 3D environment, and all the environmental lighting effects/shaders are applied on top of the raw MFD/FLIR image, readability drops considerably. I don’t have my export displays currently available to provide an example, but I’m sure someone else could create an example.

Disregard, I’ve found an explanation. It was due a texture mod applied to the carrier.

Well spotted. Change your ATT switch (second row below the UFC) from STBY to AUTO. That should fix it for you.

Thanks Minsky, I appreciate the explanation, I had a feeing this was going to be the answer. Unfortunately, a selectable livery means these textures won't be available on multiplayer servers. As I'm happy with the look of them during the day, I guess I'll just have to enable/disable the textures based on my planned recovery time each mission.

I did a clean & repair of my DCS installation, and it fixed the problem. I guess somewhere along the line, some of the data in the .lua files that control MFD/HUD rendering had been changed.

Introduced in May, but basically broken on arrival. (Obviously no more than 5 min of testing was completed before release.) 7 months later, not even a mention of a fix in the works. And the community managers wonder why, occasionally, customers appear to loose patience with ED....