discwalker

And with overcast blue fog came back.

Fog in my latest test only starting with the morning, NVIDIA GTX 1070

At least since two updates, sun position matter

When you look around with mouse (clickable cockpit off state, cursor off) or numeric keypad direction keys.

What are you doing? Could you provide track file? I have 4 DCS installations, so I can test. Have you ever tried to reset Su-33 input settings? Tried to spawn with keyboard only (disconnected HOTAS)? If you rolling with main wheels to the middle of the holdbacks then raise hold backs, gear collapse; a damage that not repairable since many years. No not only you using Su-33, I used as 2.5.6 stable without problems.

pid.dll is part of the core os, see the details tab in the left click menu; or you can not found if you save the dxdiag to a text file

We ask back the ordinary good old HUDs for FC3 modules HUD only view was dim in 2.5.5 too 2.5.5 max comparison to 2.5.6.50979 max in same gamma:

Nowadays Win key + L lock the screen during DCS gameplay. Maybe wort to ask ed for authorize Win key + R (Run) combination during DCS gameplay, that could be helpful for troubleshooting, like "pskill dcs" command to run (In LOMAC times that was very helpful. That worked in blind mode, blind typing.)

Maybe you should write to Microsoft to ask to fix ALT+TAB function with a not responding fullscreen application. Are you complaining with you can press CTRL+ALT+DELETE? With that you can do what is doable in Windows. ALT+TAB is always a solution for me in Win8.1, I use DCS in full screen but full screen is not checked in options! I always run at least 1 app beside DCS. And I use Classic Shell for the familiar start menu. Working for years. I've seen many hangs, crashes and hardware failures too, but ALT+TAB worked.

ALT+TAB switch is not disabled, so you can perform core PC functions and troubleshooting

Please don't complicate things for FC3 planes, thanks! Or when easy comms on for example on the Hornet. Backslash menu could be handy when you look for nearby freqs when easy comms off mode for example on the Hornet. (Tomcat is overpowered in own menu for nearby freqs.)

-1 Clients not always takeoff at once and discuss about codes, but can work in the same area; bad luck with using the same code and can not alter, only when return to the airfield Time shifting to change bombs code is allowed to a game.

Please give some love to FC3 planes, latest fix not restored the full max HUD intensity for them.

Only If I change bindings in multiplayer and before press OK server disconnects me. Crash zip could help diagnose. on saved games/dcs/logs folder EDIT: my case is fixed by ED

Your score in the logbook only increasing when you fly the mission with the same country as your pilot in logbook. Then you will get medals too. Defected design IMO.

This is a feature, we desperately need as many as possible modifier keys.

"NO bug"??? If SCUD hits friendly site rather than the target seems like a bug for me. If cannot shoot to the target should not shoot at all.

download te actual for actual OB https://forums.eagle.ru/showthread.php?t=257887 (https://github.com/mrSkortch/DCS-ME_coalition-modification / clone or download / download zip) updated for 2.5.6.50793 https://forums.eagle.ru/showpost.php?p=4380515&postcount=36 next time use correctly cleanup and repair

I propose a multiplayer mass test with the attached mission That particular mission caused me high rate of trigger colorblind errors, even I tested only with one client on my own norender server. (mission editing started with 2.5.6, so fresh) Krymsk is Red Anapa is Blue both bases has continous trigger for enemy appearance, which is impossible when no planes take off, or f10 optional menupoint not called a red vehicle for Anapa temporarily And the impossible is possible with this ancient bug: v1FalseBlueInKrymskZoneMessages-2ndConnect.trk https://cdn.discordapp.com/attachments/543358251694292992/721170551254810644/v1FalseBlueInKrymskZoneMessages-2ndConnect.trk v1KrymskDisaster-3rdConnect.trk https://cdn.discordapp.com/attachments/543358251694292992/721170559379177564/v1KrymskDisaster-3rdConnect.trk v1KrymskDisaster2longTryDeadEnd-4thConnect.trk https://cdn.discordapp.com/attachments/543358251694292992/721170558368219146/v1KrymskDisaster2longTryDeadEnd-4thConnect.trk v1falseTriggerKrymskShort-6thConnect.trk https://cdn.discordapp.com/attachments/543358251694292992/721170555922808962/v1falseTriggerKrymskShort-6thConnect.trk v1Secondrun_BLUEa10a-Anapa-2ndConn.trk https://cdn.discordapp.com/attachments/543358251694292992/721170560113049620/v1Secondrun_BLUEa10a-Anapa-2ndConn.trk With slightly modified mission: v2_redInAnapa-blueF15C_3rdspawn_4thConnect.trk https://cdn.discordapp.com/attachments/543358251694292992/721170561673330708/v2_redInAnapa-blueF15C_3rdspawn_4thConnect.trk TwoTriggeredBasesForEnemy.miz

Su-33 test track: 2_5_6_50793_framesInstruments_distorting_sea_at_low_and_med_water.trk https://cdn.discordapp.com/attachments/543358251694292992/721081436249260092/2_5_6_50793_framesInstruments_distorting_sea_at_low_and_med_water.trk Scope: possible for all flyables where to look: unmodifieds: a little disturbing on the groove/straight in approach

In previous (non 2.5.6.50321) builds max HUD intensity was stronger. Now HUD only view is unusable: so dim. (Both Su-33 and Su-27) Gamma setting 2.2

Yes, time has come to remove those green dots. Since on flankers when F-15C got this, but from F-15C immediately removed. The 3 green dots:

Video with current OpenBeta 2.5.6.50321

the point is yours both 2.5.6 stable and current openbeta cannot handle a "ONCE" type trigger with event "ON MISSION START". but old 2.5.5 stable can handle, but only for flag set not for message to all in this mission: mStart_trig_test_onMissionStartEvent.miz