discwalker

dxdiag for nothing track recorded with old driver video recorded with up to date driver: flickerings are the same jump to 2:40 to fickerings edit: if you want to replicate please use the HIGH graphics preset (or get my settings from the end of the video, in paused state) edit: and don't touch your mouse during replay, started with pause button on keyboard for sure not modify view DxDiag20190616_gtx1070_430.86drv.txt.zip 2,5,5,32299_blackFlickersLeftLookingAfterForcedLanding.trk

Black flickers are continous since first 2.5.4 for me never gone in any build since. Recorded at first play with GTX 1070 The client side track was the worst, with most frequent flickering in the starting phase. The 3 tracks are from the same mission. ED, plesae strive harder, this bug is the most annoying!!! Good enough to fix it to yesterday. Until 2.5.3 everything goes fine! Su-33 - Caucasus - Carrier LandingInad-20190616-113040_blackflickers.trk 2,5,5,32299_blackFlickersPlaceOnSea.trk 2,5,5,32299_blackFlickersPlaceOnSea2CanopyOpenSideLookingFlicker.trk

Not a good point to release a new game with black flickering bug. The most annoying for me since ED history. ED coders unable to hunt down this bug since last december.

Proof to trap both carriers at once for Singleplayer and multiplayer across two Kuznetsov or across 1:Kuznetsov and 2:Stennis or 1:Stennis,2:Kuznetsov, (and maybe across 2 Stennis) MP track, on the second landing: AEROBATICS_AIR_RACE-20190615-194715-KuzCableToStennis.trk https://drive.google.com/open?id=1veNeemZpwVHQIXVz9VDxgAez149pY7VE Until reconnect to server the streched carrier is unusable, in SP you guess it. SP track attached, on the third landing: 2,5,5,32299_trapBothKuznetsovSameTimeSP.trk

mission this mission run significantly different in offline mode, Su-27 is invulnerable (not true to canopy) Shilkas ang Gepards are disabled for run, because that units fire in dedicated server Small ground battle is simulated, dissimilar, because only the red units fire (USAF Aggressors), that is limited not to crash DCS in single player after simulation exit. (Because of the possible many fire events.) I tried a workaround by overfly force AI PUSH tasks, but ineffective! (last test: 2.5.5.32299) AI_not_fire_in_MP_test-20190614-182141-clientOnDED.trk

checked and still broken in dedicated server, will prepare a track

thanks seems to fixed in 2.5.5.32299

in 2.5.5.31917 the FC3 planes lack of default shortcuts for Next waypoint, engines start, engines stop. All working with joystick keys, but not on the default keyboard shortcuts. The defaults are assignable manually in adjust controls.

Same problem without VR. Font Scale:1

@Shadow.D. This is a similar but different bug. Not occuring in single player only in multiplayer when the carrier making a turn.

Yes the same happening on the deck of the CVN-74 during turn in MP

ED not yet reproduced, but you not the only one user has the error: https://forums.eagle.ru/showthread.php?t=242503

I asked for improvement, not the downgrade in 2.5.5.31917. Lost canopy is not enough damage to a repair in Hornet and all the tested FC3 planes. After a forced repair, the new canopy not closeable all the tested FC3 planes. The least thing in FC3 planes the missing canopy blew sound. 2,5,5,31917_hornet_canopy_and_repair!.trk 2,5,5,31917_FC3_canopy_and_repair!.trk

Multiplayer game on NTTR with hornet is broken. You can start without weapons, then rearm hot.

And in autostart INS to NAV should happen ***before*** Parking Brake release.

in 2.5.5.31917

manual rearm case: freeze+minidump and workaround freezeNTTR-hornet_with_loadout.zip https://drive.google.com/open?id=1L82nQUwpkfmp0_0wSxKX1amQrBqbHIAd -Start DCS -LOAD "nttr-hornet_client_cold_empty.miz" mission in ME, or with mainmenu mission -FLY -Immediately after spawn rearm with a AA weapon a fuel tank and full gun (1:sidewinder M, 5:fuel, default gun) or for me any weapon loadout with guns -wait to "rearming complete" message -Autostart -freeze without you see anything in AMPCD, 24% left engine RPM (AMPCD turn on exactly after 24% left engine RPM IN AUTOSTART.) If you startup the plane empty MANUALLY and shut down auto, then rearm, then autostart, plane startup normally. ->2,5,4,30386_NEVADA_HORNET_workaround.trk /bad version in filename, should 2.5.5.31917/ (Autostart after spawn (in empty) is successful in the mission.)

I must join the freeze club. Reproduction was easy with the track in the opening post. (Airstart client on NTTR; i saved the loadout before fly.)

yes picking up what not should in 2.5.5.31917, breaking the multiplayer experience

I wrote about the steps needed to reproduce the fail in two versions.

Please fix it! 11+hour runtime multiplayer mission client side track NEW_AEROBATICS_AIR_RACE-20190603-213404_11h27min_runtime-su33senaki-2,5,4,30386.trk

The netcode is not enough first party? Or Su-33? Or Kuznetsov?

All FC3 planes able to refuel hot, but no hot rearm.

This affecting F-5 also.

In all of the examples the carrier sailing with 20 km/h. Unwanted "reverse gear" in a 22MB, long, 2 planes track: The MP tracks recorded as client on a localhost dedicated server. The attached mission is not dangerous in single player. (DCS 2.5.4.30386) deck_sliding_in_turn-20190601-195717.trk deck_sliding_in_turn-20190601-200301.trk