Thx1137

I've always wondered if the efficiency cores on the newer chips could be a problem. I'm retired so I no longer bother keep up with the constant changes in software and hardware but clearly they aren't "normal" cores so they should be treated differently. If a game sees 20 cores and 8 of them are efficiency cores then can it utilse each kind of core properly? How much is under dev control and how much, if any, is automatically managed by the chipset? The devil is in the details. I often found that how a low level feature worked in real life was never as simple as some documentation might have us believe. And if we don't know how the system works in a lot of detail it can be damn tough to troubleshoot! Hmm. That's interesting. It might be time to read up

This happened to me if I used my previous DCS MT link from the Windows task bar. I deleted that link and created a new one from the bin-mt folder, that let me choose DLAA again.

I find it a bit hard to understand what you're saying but it sounds like stalling. Maybe you think stalling is based on speed (it isn't) or think any modelled aircraft will somehow prevent stalling for you automatically (they won't)? If you aren't stalling then I think people need to see a video that includes your control inputs.

I'd have thought so but as a guess, they probably put more emphasis on developing the ability to fight using a normally setup aircraft. I wonder if they would have to a new flight model for every possible switch combination. That would be an obscene amount of work.

There is plenty written about pitch already so maybe read those. Yes, it is sensitive in the real jet and can feel weird/oscillate on takeoff if you don't fly it correctly. That said, there will be some *minor* flight model tweaks in the patch so it may change though I think only slightly. The aircraft isn't FBW like the F18 or F16 so yes, trim changes are made after any airspeed change. You fly it like a normal airplane.

1, A poly not seen is probablyusually not drawn so it doesn't necessarily consume frames. 2. Just because you don't want something doesn't mean many others do. It isn't all about you/us. Re #2, I also don't care about opening non-useful panels so I actually agree. But, not everyone is like me and I don't think my taste makes everyone elses less important. 3. If a person making a feature wants to add something because they want to, who are we to tell them not to make what they want. It is *their* product. We just buy into what they create.

Everyone, MFD is on the list of things not yet implemented. See https://www.digitalcombatsimulator.com/en/news/changelog/

Yeah, we want it now! Even if it isn't finished and full of bugs! Then, yuck! it has bugs or it is unfinished! History repeats, a lot.

I don't have many custom keybinds for the F15E but I have trouble with the laser arm side of the WSO panel in that it often doesn't activate on a key press. It can update on one press or rake more than ten presses. All my other aircraft are reliable in that regard. I haven't found a reliable way to cause it to fail yet to log it.

Huh? I and I know of several others start all missions cold and never have an issue talking to ground crew if we turn the switch on.

I found it tough because I'm used to the hornet. But this beast needs to be landed quite differently. Most of the time I have trouble stopping now is because I'm too heavy. Given the standard F15 has a landing distance of 7,500 ft (2,300 m), according to Google, it seems about right. It uses almost 4/5 of the runway at my local international airport going by those numbers.

For mixed/civilian airports then always on is good. I personally don't mind your idea for military too. A couple of other options: 1. If it is possible then you may consider a real life alternative which is to use Pilot Activated Lighting. Typically you would key a comm microphone on a specific frequency and it would turn the lights on for a while. EG: You could toggle the comm radio three times in succession to toggle the lighting. 2. If it is possible, then a shortcut key that turns on/toggles the lighting for the "closest" airfield to the aircraft. 3. Maybe a menu option to turn on/off closest airfield lights. I say "closest" in the last two options because I think having controls for ever airfield might add too much clutter. Dunno.

Heh, I took my own advice and I found I had a key I forgot about that toggles between the map and the pilot view. So that was my issue.

I'd check your F1 Pilot View keybind in the F15 settings to make sure it isn't bound to an "always down" button. That is about the only thing I can think off. I don't think Razbam reply here much but if you go to their discord there is always someone there, after all, that is their support location. Whether they can tell you anything is another question. I expect most of them are seriously busy at the moment.

For comparison. 1 minute 40 second to go from desktop to menu screen for me in MT mode. That includes about 20 second compiling reshade shaders. I have a fast m.2 drive and 12th Gen i7-12700F, 2100 Mhz, 12 Cores with 32mb of fairly slow RAM. Some Sinai based missions were taking a long time to load but I used to have preload radius set to max. At 70,000 it is a fair bit faster. dcs.zip