ams999

Maybe ED is just going with the flow... :music_whistling::megalol: https://neutralfooting.wordpress.com/2017/09/19/the-unated-nations/

Yes please! But then not with that weird synthetic voice in the video - either that it sounds better or with beeps...

Hi, I noticed the following when using SRS (1.4.8.0) with the Gazelle: on default, the radio is on TRAP 138A. When I want to switch to UHF TRA 6031 and press the button on the middle console (press to select UHF, turn to change volume) I see the button pressed but SRS stays on 138A. I can change to 6031 (or any radio) by using the SRS radio overlay. However, turning the button on the middle console does change the volume (as seen on the overlay), so it's not totally without function in SRS, I just can't change between radios. How do I change radios in SRS using the Gazelle's clickable cockpit and not the overlay? I did a search but didn't find an answer. What am I missing? Thanks!

I have the same effect, also since 2.5 came out and still after the latest update.

1. do you get the 'copy' from the ground crew and then no re-arm or are you being ignored completely? 2. Only on that server or on others, too? Both re-arm an engine failures? 3. Were you on interphone or something else?

found it, nvm

Is it the viewporthandling.lua in \DCS World\Scripts\Aircrafts\_Common\Cockpit? How do I have to edit the viewporthandling.lua to switch of the MFDs in cockpit? Thanks!

Fixed for me now via latest update, thank you ED!

Latest update fixed most of my issues, thank you very much ED! The only thing still happening was the key request for the F-15C module at program start - I have now actively disabled the F-15C in my module manager which has also fixed that - I can still use the F-15C in game as it is FC3

Numbers are gone for me, too, except the negatives starting from -10

And I just noticed that in the other missions where the engine is running (dogfight, free flight) the engine immediately dies. Hope ED can fix this soon...

Problem with the Fw190: Since the update to 2.5.0.15085 the gear switch of the Fw190 is at the 'ein' position, so as soon as electricity is switched on, the gear retracts on the ground. Easy enough when doing the cold start (just press 'aus' first) but the instant action take-off mission is unplayable this way. From cold start, I can't start the engine anymore; doing the same procedure as before the update, the engine splutters but doesn't run - has the startup procedure been changed? Thanks!

Since the update to 2.5.0.15085 the gear switch of the Fw190 is at the 'ein' position, so as soon as electricity is switched on, the gear retracts on the ground. Easy enough when doing the cold start (just press 'aus' first) but the instant action take-off mission is unplayable this way. From cold start, I can't start the engine anymore; doing the same procedure as before the update, the engine splutters but doesn't run - has the startup procedure been changed? Thanks!

I have problems with FC3 after the update: 1. on every startup, I get asked for a key for the F-15C module, when I ignore it says F-15C will be deactivated but I then can still enter the F-15C in-game 2. but the F-15 and Su-33 are unusable, F-15 goes to 86% throttle and stays there, can't steer, snapviews aren't like before, stick is fully deflected right and stays there, brakes axes don't work. When I check in 'adjust controls' all switches and axes (stick, throttle, brakes) work as intended. 3. Su-27 may be working better but crashes after a few seconds. Su-33 and 27 are now askew on the ground or the carrier, turned between 30-90° to the left 4. Other modules (A-10, Ka-50, Huey) work normally for me 5. mods or no mods, repair, clean, no difference

Interesting, I see the same thing in the Ka-50 (on the left window frame), in white with cockpit illumination, in purple with the NVG-lighting switched on

I don't have VR but also still experience FPS loss when using MSAA 2x, and still the same amount (without 50-60, with around 30 FPS, so effectively halved) :(

I tried it and found no difference, unfortunately, I still have the same loss of FPS

It looks the same for me, also two monitors. Any solution yet?