Jalava

Profile changing works again with alpha 2 About A-10C II throttles, it looks like they have to be cycled once to idle regardless of PULSE time. I believe it is a Cold Start bug on A-10C II and will report that to ED after I confirm the process to repeat EDIT: Looks like if throttles are in cutoff position, you cannot use keyboard commands either

Profile changing doesn't seem to work, when I push S3+LOSB1 TEMPO, it will enter the profile selection mode and I can select profile but pressing S2 to select profile just says profile is selected but doesn't exit the profile selection mode anymore

Ah, that was a embarrasing misread. Another thing, on A-10C-II the engine startup seems to have some issues and it seems to need slightly longer keypress for throttle to move from cutoff to idle. So I need multiple attempts with throttles to get it to actually move them to idle.

On 2.501, at least on A-10C profile, S3+CMS in any direction just sends BTN30 + BTN15/16/17/18 and forward instead of SnapView selection for some reason? I usually don't use snapviews at all but now that I notices there were fixes I decided to try and realized they don't work.

SU-27 does have backwards installed R-77 variant but that is just about only rearwards firing missile system. These days you already have off-boresight missiles and getting into situation where you are surprised by fighter on your six should never happen on the battlefield, hence most of the time rear firing A2A missile would be useless, especially sidewinder as you would be dodging something more medium range way before you have time to fire a short range missile.

Also LMAV view in DDI looks funky and I find it very hard to get a lock on a moving target if target has been moving for a while. It does seem to track the seeker but can't get positive lock from lasing unless designated initial target point is near moving target.

There is something with moving targets now too. It looks like MAV is tracking last designated TGT point and does no longer update it's tracking from PTRK on TPOD. This means that if target has moved sufficiently, it cannot find the laser spot as it is looking into wrong direction. And because you can't re-designate target spot without coming out of PTRK (In PTRK, TGT is still last spot designated as target) it's quite difficult to get a permanent lock on sideways moving targets. That or I'm now doing something wrong which used to work before last patch.

I just slew the maverick directly by undesignating target after mav is slewed roughly to right area. At some point it will acquire IR lock. Not going into PTRK in pod and just following enemy manually and redesignating target also works. Both are a bit of pain though if using stock Warthog HOTAS slew stick

Bumping to confirm this rendering issues still exists in DCS 2.5.6.55363 Open Beta Adding a screenshot illustrating difference in brightness between exported and non-exported gauge (it should not render right ddi in almost yellow when in night mode) and what is being rendered on exported screen.

Would it be possible to get possibility to swap MFD mappings between MFDs? For example, I have 4 MFDs with MFDs 2 and 3 with a screen mounted behind them, so my MFDs are physically arranged from left to right as 1,3,2 and 4. In F-18C I have AMPCD and Right DDI exported behind MFD3 and MFD2 for pretty good match to actual cockpit, but for A-10C I use them as Left and Right MFCD. However A-10C MFD buttons are still mapped to MFCD1 on the left side of the screen. Optimally I'd like to have possibility to have option to map any MFD CTS functions to any MFD and then any MFD physical buttons to any MFD. For example A-10C I would have: - MFD1: CTS Left MFD buttons - MFD2: Left MFD A-10C buttons - MFD3: Right MFD A-10C Buttons - MFD4: CTS Right MFD Buttons This would allow me to still use the printed hint inserts on my MFD1 and 4 but press OSB based on what is shown on my screen without remapping MFD numbers in MFD drivers every time I swap between planes.

Btw, S-3 is flying 280 GS not 280 IAS as advertised on contact. 250 IAS is bit tricky speed to refuel at and I'm not sure if this is a common speed for refueling hornets.

I haven't been able to confirm if this happens with other module MFDs, but I have confirmed it doesn't happen with A-10C, so at least it is not a generic DCS World Multimonitor issue. Someone with F16 could probably try to confirm this as it is from same generation of modules and could have similar MFD rendering code used. EDIT: Went and bought F-16C just to test this bug out, doesn't happen with F-16C either, Left and Right MFDs are same brightness regardless of if their displays are exported to second monitor or not. So it is a F/A-18C specific issue it seems

It's something I actually have forgotten there as I was trying to figure out one scaling issue with UI when I had my second screen under the main screen. Looking at ViewportHandling.lua#set_full_viewport_coverage function, it will ignore the setting anyway. My idea was to set aspect ratios for exports just in case it respects those when pixel aspect ratio differs between screens, but using width/height can be used to stretch the textures right anyway.

Ah, this must be a scripted feature in Raven One campaign and they add some lights in there to make refueling possible during night, made a quick mission myself and just could not get any illumination from probe.

Do you have navigation and formation lights turned up and light switch in forward position?

Related issue: https://forums.eagle.ru/showthread.php?t=284573 the bloom is rendered again in cockpit, not onto exported display.

Ah, so it clearly is. It was Texaco in mission so my brain thought it was KC for some reason.

Running latest DCS openbeta 2.5.6.54046 I was doing night tanking of KC-135 MPRS and noticed that the tiny light in the probe will light up the whole plane brighter than sun ever will, not just the drogue. This also happens when AI does tanking. Gamma 1.8

Running latest DCS openbeta 2.5.6.54046 I was trying to figure out why my DDIs were different color at night and AMPCD was wayy too bright. Then I realized, I had only Right ddi and AMPCD exported. Then I figured I'd just export LEFT_MFCD instead and now difference in brightness swapped over. I also tried to remove AMPCD export. Here are three screenshots (cropped to show just the relevant parts, otherwise screenshots are exactly the same, including exports on the right side of screenshot): First my initial setup RIGHT_MFCD and CENTER_MFCD exported to another monitor on right side. Second RIGHT_MFCD is replaced with LEFT_MFCD Third with just RIGHT_MFCD (AMPCD not exported). So it looks like bloom is rendered twice on exported MFDs but in the cockpit and not on the exported textures? Also including my monitor setup for reference (32:9 Ultra wide monitor with 1920x1080 screen on right side for MFDs). 1Camera_wide_MFCD.lua Edit: Updated to current monitor setup with bug still existing with "aspect" removed from exports.

Todays update seems like it broke the tpod night flir contrast again.. still experimenting

I wonder if you happened to have speed brake open? The Mission 2 AAR tanker track is very stable with no serious wind and I found it very easy to tank from compared to most AAR missions i've flown offline and online. F/A-18C should be able to fly 250 IAS clean with no issues regardless of altitude.

I think it is related to guard because on when you switch AUX to Strike, GRCV cannot be pressed on Comm 2. It can be pressed on PRI but then the COMM 1 will go from AM to FM. If PRI 1 FLIGHT is 300.100 AM and AUX 2 STRIKE is 277.600 AM, there is no way you can monitor Guard on FM. Ah: It seems to be a bug in the UFC, going GRCV on Comm 1 will swap AM to FM and you need to manually swap back as Guard is on AM too.

For me I'm missing most of the voice overs and it seems to go into a bit of a limbo state. I receive following messages: - Prince turns north climbing - Calling for saddled and speed - If we are not at W2 yet, I can call for radios but after this everything goes silent - It gives me a prewarning for turn to W3 if I haven't yet called for radios - After that I can press space for commenting the turn but this doesn't give any audio feedback, only the prompt goes away. - At fight, I'm not getting any voice overs (except once out of 5 tries, then we did call tapes etc, but Prince never disengaged after itself called joker), only once I did 3 hits and then called joker and I managed it to disengage but didn't get any voice until I was already at marshal and only then strike woke up saying Prince is at Waterloo red.

This is good to hear as I was worried during first mission that too many complaints about incorrect formation would fail the mission. Also flying close parade with him, I'm done with that.. Absolutely no calls about intentions and not exactly shallow turns or changes in altitude / speed.

This happens always with ACM using guns, just push radar elevation to one end before going to ACM and you'll notice your VACQ doesn't work because it flips the axis and doesn't reset the radar azimuth. I'm surprised this keeps coming back as Cannot Reproduce on reported bugs