discwalker

In an Su-27 or Su-33 formation if we all use smoke, the last turned on smoke color forced to all generators: Client: 2.5.6.43872 EDIT: visible same way to both members

Spectate from Su-33 on deck of Kuznetsov water_flicker_2-5-6_su25t_until_1500kg_v2seaLevel.trk: https://cdn.discordapp.com/attachments/600718659031400487/679812233810804810/water_flicker_2-5-6_su25t_until_1500kg_v2seaLevel.trk (options.lua is the same; first 2.5.6 OB;single player) EDIT: TEXTURES-sea-bug-2020.trk - terrific experience on replay - confirmed

(I hoped too test as a .zip extension file, archive testing bring success, it should on .miz files.)

You attached a file filled with zeroes So your filesystem is corrupted. Maybe a faulty SSD. Sorry. Not the unicode filename the problem. EDIT: There is an advantage of using hexadecimal views.

its a piece of cake the reproduction - Get any flickering mission with dynamic weather - open in ME - ad a name and save weather and time - create new mission - load saved weather and time - add a plane - play, and fly at least 5 minutes over sea After you see the flickerings in my track near Batumi in su25t cockpit "take control" and "select slot" Su-27 at Sukhumi and do experiment in that region https://cdn.discordapp.com/attachments/599576363837423619/679415118341341215/water_flicker_2-5-6_su25t_until_1500kg.trk with the first 2.5.6 OB version options.lua

bug reproduction client tracks for 2.5.6 bug_redpartzone_bluetrigger.miz bug_redpartzone_bluetrigger-20200217-203419_connect2_su25t.trk bug_redpartzone_bluetrigger-20200217-204036_connect3_j11a.trk connect2_20thSPAWN.jpg connect3_20thSPAWN.jpg dcs.log.server.txt debrief.log.server.txt https://cdn.discordapp.com/attachments/543358251694292992/679055932944285736/blue_as_red_2-5-6.zip

Hot started on airfield. Land on Stennis. Try various catapults, all hooked, but none will launch.

Thanks Thanks ED for fixed in 2.5.6.43453. So nice the addition of colored circles to each country name in the selection drop down list, this way we can easily edit foreign missions.

At least 21500m is service ceiling. source: COMBAT APPROVED S1 • E19 "MiG-31: The Near-Space Plane. Russia’s super-fast interceptor"

Requested in 2018: https://forums.eagle.ru/showthread.php?t=204801 "Debriefing/Attrition: truncated digits" (modern test case files here: https://forums.eagle.ru/showpost.php?p=4204283&postcount=11)

Test cases for everybody Play this track after fresh DCS start and wait for menu after debriefing, my tip you would use task manager to kill DCS process: https://cdn.discordapp.com/attachments/543358251694292992/674341587873955841/2-5-5-41962_debriefing_attrition_truncated_23slash12.trk (2-5-5-41962_debriefing_attrition_truncated_23slash12.trk) Play this mission after fresh DCS start in main menu/mission and wait for menu after debriefing, my tip you would use task manager to kill DCS process: wait for all helos to fall to the sea (autorotate) https://cdn.discordapp.com/attachments/543358251694292992/674341590428286990/2-5-5-41962_debriefing_attrition_truncated_23slash12.miz (2-5-5-41962_debriefing_attrition_truncated_23slash12.miz) The latest lines in my side on logs from these: 2020-02-04 19:31:06.657 INFO VISUALIZER: StopSimulation 2020-02-04 19:31:06.658 INFO VISUALIZER: Stopped collection of statistic. 2020-02-04 19:31:06.704 INFO EDCORE: (dDispatcher)enterToState_:3

Yes, TRIM Reset for all planes (Su-25T too). I'm not a polip, I only have two hands. In full fidelity planes without head tracking is very unlikely I'm able to adjust the trim after the last Mk-84 drop as needed before I crash. DCS adjust controls section can be task oriented for full fidelity planes too, nut just the bare minimum to force MORE WORKLOAD to us: NOT simpit users. Who have simpit not forced to use the simplicity.

So Grimes wanted to say, run a clean up of foreign files? (or just clean "C:\Users\username\Saved Games\DCS\Liveries")

Question on thread title Is the crash reporter working in the same "ineffective" way as in 2019? Because 4 of 5 times the OS (Win 8.1) intercepted the crash reporter with system32/WerFault.exe modal window, it renders unusable for crash .zip creation and/or automatic upload with a comment. Impossible to answer the dxdiag creation question under a modal window. :( Do I still needed to run a modified (system32/WerFault.exe renamed) Win 8.1 to able to catch possible crashes? Is this the case for only Win 8.1? Is storage read error still displayed as IN_PAGE_ERROR in crash?

Thankfully the old log was preserved It was a terrible ear experience. It happen to me at first time in Multiplayer: 2020-02-03 18:41:23.793 ERROR SOUND: render time = 0.091959s exceeded allowed slice of 0.042667s 2020-02-03 18:41:23.900 ERROR SOUND: render time = 0.061213s exceeded allowed slice of 0.042667s 2020-02-03 18:41:25.894 ERROR SOUND: render time = 0.245209s exceeded allowed slice of 0.042667s 2020-02-03 18:41:27.071 ERROR SOUND: render time = 0.192426s exceeded allowed slice of 0.042667s 2020-02-03 18:41:27.319 ERROR SOUND: render time = 0.247744s exceeded allowed slice of 0.042667s 2020-02-03 18:41:27.509 ERROR SOUND: render time = 0.189667s exceeded allowed slice of 0.042667s ... My F2 view was on a buddy Su-33 shutting down engines on the deck of the Kuznetsov. (EDIT: I just spawned a Su-33 on Senaki-Kolkhi, and changed view. After a while (approx. 1 minutes) sounds became to normal.) dcs.log.sound.render.time.exceeded.txt.zip

If I were you, I would delete/move the DCS_open_beta\CoreMods\aircraft\M-2000C\ folder and then run a repair. Repair don't read back file contents. Are your drives S.M.A.R.T. attributes good? (especially Reallocation events raw data)

I tought it was fixed, my bad: unbind again BUG: tape player CTD during multiplayer or singleplayer with switch side keyboard shortcut (rightctrl+M) Player completely stopped playing functionality before crash, In multiplayer, was hotStart too. Reproducible 100% Easier reproduction: - start DCS - load instant action F14 Takeoff (Caucasus) - use tape switch side keyboard shortcut (EDIT:if i set only to joystick button that is equivalent) - CTD LOG: logs attached. Ver: openbeta 2.5.5.41962 mods: almost vanilla! (only skins in user folder (no Tomcat outer or inner skins) + scripts/MissionScripting.lua from slmod) Specs: above minimum req., 16GB DDR3, GTX 1070 8GB dcs.log.walkman.switchside.txt.zip dcs.log.walkman.shortest.instaTakeoff.txt.zip

If you want quick help use the official ED Discord help room: on https://discord.gg/ZpCfd4 I tried to answer your issue on your second thread. NVIDIA Ingame overlay (or AMD equivalent) video recording with mouse cursor can help us to diagnose what you've done wrong, because on our end this function is working with all modules.

Possibly you terribly do the wrong things Here is how it works, adding joy axis to F-16 thrust, previously empty: (Track recording is useless in this GUI case, video recording shows what you've done with mouse recoring. Or maybe your mouse button is died.)

Please calm down Jester on the friendly Kuznetsovs deck. F-14B landing is an every day practice on our server:

4th join, and blue F-15C act as red: https://cdn.discordapp.com/attachments/543358251694292992/672851731528286218/bug_redpartzone_bluetrigger-20200131-180934_f15c_onlyblues_client_4thjoin.trk

@BigMongostyler, it is not fixed. After 3 connections to my norender server and 15 minutes of continous spawning a Blue Su-25T trigger what should not. client side track: https://cdn.discordapp.com/attachments/543358251694292992/672848238604189715/bug_redpartzone_bluetrigger-20200131-175050-su25tBlueTriggerWhatShouldNot-clientside.trk EDIT: Tested with latest openbeta: 2.5.5.41962

In a newer thread this reached reported status Now moved to general questions: https://forums.eagle.ru/showthread.php?t=232968 Dynamic weather causing the flickers in cockpit. ED maybe consider to mark a year to fix it.

Too often and long ago happen in DCS: MP become SinglePlayer! You understand our love-hate relationship with DCS? (My plane is the starting F-14B) Log: https://cdn.discordapp.com/attachments/606862310853574667/672509062126239744/dcs.log.stopsync-Aerobaticserver.txt At the end the last connections can done nothing on server. mission: https://cdn.discordapp.com/attachments/606862310853574667/672511669099823193/AEROBATICS-20200129-204359.miz On our Aerobatic dedicated server A/C position sync frozen with 22 players. Only the own plane is moving, everyone else in the air is levitating with zero speed. After disconnect reconnect was unsuccessful to members, until server is not listed anymore. (died without a crash) Player list frozen too in MP session, show the disconnected members. The chat events (landing/takeoff/crash) updated a long time after A/C position sync lost. This bring back memories from dedicated server multiplayer mass test data collection. After sync loss go to spectator or change slot is impossible. Only disconnect worked. The voice chat was off, no SLMOD, no MIST. The max client ping was 128 ms. No hardware issue, sure, another two instances run fine on the same physical machine, one with multiple players after the Aerobatic instance become inoperative. (another instances: https://cdn.discordapp.com/attachments/606862310853574667/672511044094263306/Screen_200129_235455anotherinstancesLongAfterAeroDied.jpg) ("ERROR Lua::Config: Call error debriefing.addEvent" happenig on our server quiet often too)

"INFO DCS: Command line: "E:\Eagle Dynamics\DCS World OpenBeta\bin\DCS.exe" --server --norender --webgui -w HUNAF_aerobatics INFO DCS: DCS/2.5.5.41962 (x86_64; Windows NT 10.0.17763)" wRadio.dll is the Voice Chat server? We turned that off now and this kind of problem is gone. When will voice_chat.log be timestamped and attached to auto generated crash report file? When will old voice_chat.log be renamed to voice_chat.log.old? See the two auto generated zips in the Logs01_27.rar: https://drive.google.com/file/d/1GDK_TNgh-sTG5ZyuBlP03sDul50tYFUw/view?usp=sharing