discwalker

The above track still replayable (2.5.4.29167) to the first forced repair, which is started because the lost canopy and repaired the 3 blown tyres but not visually.

very short track Still autostart fail in cold after successful right engine start, with message right engine rpm failure. 2,5,4,29167_Fa18C_too_COLD_to_autostart.trk

COPY the cockpit mod to "C:\Users\???\Saved Games\DCS.openbeta\Liveries\Cockpit_Su-27"\ in a new folder, like "English Blue" list of mine: C:\Users\pitwalker\Saved Games\DCS.openbeta\Liveries\Cockpit_Su-27\English Blue\description.lua C:\Users\pitwalker\Saved Games\DCS.openbeta\Liveries\Cockpit_Su-27\English Blue\su27_cpt_devices01.dds C:\Users\pitwalker\Saved Games\DCS.openbeta\Liveries\Cockpit_Su-27\English Blue\su27_cpt_devices01_spec.dds C:\Users\pitwalker\Saved Games\DCS.openbeta\Liveries\Cockpit_Su-27\English Blue\su27_cpt_devices02.dds C:\Users\pitwalker\Saved Games\DCS.openbeta\Liveries\Cockpit_Su-27\English Blue\su27_cpt_devices02_spec.dds C:\Users\pitwalker\Saved Games\DCS.openbeta\Liveries\Cockpit_Su-27\English Blue\su27_cpt_inter.dds C:\Users\pitwalker\Saved Games\DCS.openbeta\Liveries\Cockpit_Su-27\English Blue\su27_cpt_inter_spec.dds C:\Users\pitwalker\Saved Games\DCS.openbeta\Liveries\Cockpit_Su-27\English Blue\su27_cpt_interior03.dds C:\Users\pitwalker\Saved Games\DCS.openbeta\Liveries\Cockpit_Su-27\English Blue\su27_cpt_interior03_spec.dds C:\Users\pitwalker\Saved Games\DCS.openbeta\Liveries\Cockpit_Su-27\English Blue\su27_cpt_k36.dds C:\Users\pitwalker\Saved Games\DCS.openbeta\Liveries\Cockpit_Su-27\English Blue\su27_cpt_k36_spec.dds C:\Users\pitwalker\Saved Games\DCS.openbeta\Liveries\Cockpit_Su-27\English Blue\su27_cpt_lamps.dds C:\Users\pitwalker\Saved Games\DCS.openbeta\Liveries\Cockpit_Su-27\English Blue\su27_cpt_panel01.dds C:\Users\pitwalker\Saved Games\DCS.openbeta\Liveries\Cockpit_Su-27\English Blue\su27_cpt_panel01_spec.dds C:\Users\pitwalker\Saved Games\DCS.openbeta\Liveries\Cockpit_Su-27\English Blue\su27_cpt_panel02.dds C:\Users\pitwalker\Saved Games\DCS.openbeta\Liveries\Cockpit_Su-27\English Blue\su27_cpt_panel02_spec.dds C:\Users\pitwalker\Saved Games\DCS.openbeta\Liveries\Cockpit_Su-27\English Blue\su27_cpt_panel03.dds C:\Users\pitwalker\Saved Games\DCS.openbeta\Liveries\Cockpit_Su-27\English Blue\su27_cpt_panel03_spec.dds C:\Users\pitwalker\Saved Games\DCS.openbeta\Liveries\Cockpit_Su-27\English Blue\su27_cpt_panel04.dds C:\Users\pitwalker\Saved Games\DCS.openbeta\Liveries\Cockpit_Su-27\English Blue\su27_cpt_panel04_spec.dds C:\Users\pitwalker\Saved Games\DCS.openbeta\Liveries\Cockpit_Su-27\English Blue\su27_cpt_panel05.dds C:\Users\pitwalker\Saved Games\DCS.openbeta\Liveries\Cockpit_Su-27\English Blue\su27_cpt_panel05_spec.dds C:\Users\pitwalker\Saved Games\DCS.openbeta\Liveries\Cockpit_Su-27\English Blue\su33_cpt_rsbn.dds C:\Users\pitwalker\Saved Games\DCS.openbeta\Liveries\Cockpit_Su-27\English Blue\su33_cpt_rsbn_NRM.dds C:\Users\pitwalker\Saved Games\DCS.openbeta\Liveries\Cockpit_Su-27\English Blue\su33_cpt_rsbn_SPEC.dds

Spawn on ground for all aircraft would be good without a mod. And please extend ground services to all regions of Krasnodar-Pashovsky.

Somewhat unrealistic, but I want to hear Jester's priceless comments in outside view.

Need support I run out of options, please support us ED! -I eliminated one active network device, now only use the ISPs (UPC-Hungary) cable modem and router in one device -I turned off antivirus -I turned off windows firewall -I turned off router firewalls (IPv4nat, ipv6nat...) At any settings I see only 36% of the servers. Every refresh an other 36 percent. And now stable and openbeta is the same! I tired of the connect by IP feature, but love it. Usually I see 1 or none of the 5 24/7 Hungarian servers (search for "HUNAF") which is running in 2 physical hosts.

The list by distance is a big blockage if you fly past a carrier battle group or a multitude of farps. Su-27 is nothing to do with cruisers.

Epilepsy warning! "play" with F-5E-3 in low water settings, result: extreme flickerings with GTX 960 4GB EDIT: lightly modified Caucasus takeoff instant action mission EDIT2: if I take control and switch off the mirrors at flickering state the flickering stops 2,5,4,29167_F5E-BATUMI_BLACK_FLICKERS2.trk

Original ingame footages of attached tracks: Tracks replayed best at high graphics preset or in my settings. EDIT: Water settings is NOT IMPORTANT, for me in low setting flickreings came. ED is unable to provide frickerless rendering for Tomcat, flying the Tomcat and other planes is not fun anymore, because all of the 2.5.4 series has flickerings. If Heatblur cannot provide the Tomcat for the 2.5.3 flickerless series, please drive ED to a complete solution to flickerings. The most reliable solution: go back to the 2.5.3 graphics engine. the unsuccessful litany: Video Corruption and Related Card Issues » [REPORTED] Screen flickering since 2.5.4 https://forums.eagle.ru/showthread.php?t=227646 2,5,4,29167_F14B-BATUMI-BLACK_FLICKERS.trk 2,5,4,29167_F14B-BATUMI-BLACK_FLICKERS2.trk 2,5,4,29167_F14B-BATUMI-BLACK_FLICKERS3.trk

Kuznetsov spawn logic is weak now. The screenshot case: no other Su-33 in the server free Kuznetsov start positions 3 different slot choosed and no one can spawn! EDIT: Go to spectator then back is our workaround long ago. Figured out after a long time. Please not scare newbies! When the scene is empty let us to spawn please! EDIT: real world MP track 3x unsuccesful spawn: https://drive.google.com/open?id=1GHSyICi8GT5jaynLNExISPBrPguta8tc ( BATTLEFIELD-20190710-181516-yfidtspWaitx3slotKuznetsov.trk)

Your problem is similar to this? Restart mission without rendering https://forums.eagle.ru/showthread.php?t=221674

in DCS ver. 2.5.4.29167 (in the stable, this in ME and ingame and was reported by auto report sender, before this pushed to stable) steps to reproduce: - load game with Perisan map MP os SP - switch to F10 map view - play with the zoom full zoom out icon scrollwheel to fully zoom in OR plus icon usage to zoom in as quick as possible to an airfield dcs.log-20190403-154415ingameMP_F10plusIconKhasab.zip https://drive.google.com/open?id=1ZkIZMCevV4a8hxuXn3jKYtRHkO9_ZIju

In the mission editor the fastly used scrollwheel can cause game crash in the freshly loaded Persian map, mainly fully zoom in (3m scale) and fully zoom out (100km scale) state. In "ALT" and "SAT" view. There is no waiting to load samples from SSD. There is no edit box in crash submission. Reported now with 2.5.4.29167, but the previus open beta has this bug. Waiting for a hotfix. Editing in persian is impossible for me. Thanks. dcs.log-20190401-165942_3mZoom_nomods.zip

yes Too much lamps on the right side of rwy 19 in 2.5.4.29079

Confirm. The appearing mouse cursor is annoying.

C-17 AI able to not loose flaps when lose wing.

Currently you must set INS knob to NAV manually after auto start INS alignment: https://forums.eagle.ru/showthread.php?t=237364

I ask for support, ED. No improvement in 2.5.4.29079 2018 february date marking an old issue: https://forums.eagle.ru/showthread.php?t=201656

adjust controls/throttle quiadrant/cycle afterburner detent on-off and there is a default behaviour in options/special options

"Down Lock Override Button" as is F/A-18C for easy testing the incredible Tomcat stand up from belly capability without making a belly landing.

tracklist The black flickerings remained for me with the latest NVIDIA driver. If ED accept i can provide private additional testing. tested tracks, valid with 2.5.4.29004: 2,5,4,26825_free-YAKtakeoffReplaced-BlackFlickeringUnc.trk https://forums.eagle.ru/showpost.php?p=3785773&postcount=244 2,5,4,27430_flankerMirrosOnOffFlickering.trk https://forums.eagle.ru/showpost.php?p=3804981&postcount=278 2,5,4,27430_HornetBeslanApproachFlicker.trk https://forums.eagle.ru/showpost.php?p=3807656&postcount=287 2,5,4,27430_FrogfootTSukhumiApproachFlicker.trk https://forums.eagle.ru/showpost.php?p=3815083&postcount=300 2,5,4,28461_f14b_flickers.trk https://forums.eagle.ru/showpost.php?p=3838608&postcount=316 + NOW with video 2,5,4,29167_F5E-BATUMI_BLACK_FLICKERS2.trk https://forums.eagle.ru/showpost.php?p=3873606&postcount=351 + 2.5.4.30386 MP track with video BLUE_vs_RED-20190519-205207_flicker_Su25tapproachSochi_11h10m_3,5km_288m.trk https://forums.eagle.ru/showpost.php?p=3916661&postcount=367

I read the brave statement: "it's fixed", but the joy was short. I tested 4 tracks attached by myself to this thread and flickers is the same. I now update the GTX drivers. fxo and metashaders2 was dumped.

Maybe you encountered coalition accounting mess bug: https://forums.eagle.ru/showthread.php?t=215146&highlight=unable+place+chinese+assets

You sounds like trapping anywhere on the world doesn't exists: DCS: F/A-18C Hornet » Wish List » Field Carrier Landing Practice https://forums.eagle.ru/showthread.php?t=197436&highlight=fclp https://forums.eagle.ru/showpost.php?p=3535954&postcount=54 If arrestor grear will be a placeable object we can place it anywhere. Our right.

I'm not against it if is only an OPTION, for basket also.