methosXX

Trying to reproduce the freezes I noticed that I had SweetFX/ReShade running. Since deactivating that I haven't encountered another freeze.

I was finally able to do some flying (KA-50 in multiplayer) and encountered another freeze after ~20 minutes. Before the freeze I could observe my fps drop from ~50 to 6 within 1-2 seconds, then the game stopped responding (waited 1-2 min before closing). Attaching my dcs.log, there was no crash dump. dcs.log.txt

Within 30 minutes of testing 1.5.2 I have encountered multiple freezes where my game stops responding (15+ sec before I kill it). My method of initial performance testing is usually to join a multiplayer server (e.g. aerobatics server) and start watching other players in f2 while moving the camera and looking for fps drops. Since 1.5.2 I have noticed a correlation between network lag and fps. If the player I'm watching starts lagging/warping, my fps drop and in extreme cases (3 instances in 30 min) my game freezes. I have yet to do some flying in the current version. Maybe someone can post their findings of freezes and whether they occur in single player as well. Sidenote: On my System (i7 3770k, gtx 680, 16GB, ssd) I have encountered almost no crashes since the initial 1.5 release (no dx11 backend crash) except for crashes I believe are related to memory leaks (after 2+ hours of flying/hosting coop server). Edit: Attached my logs folder for DCS openbeta. Unfortunately there are no crash dumps for freezes, but maybe the logs shed some light. Logs.zip

Awesome, thank you!

Hey guys, I'm having trouble with the mist flag functions. Since I'm completely new to mist it could be an error on my side ... anyways, here's what I see. I was trying to use the functions mist.flagFunc.units_in_moving_zones and mist.flagFunc.units_LOS and when using the function as follows, everything is fine. mist.flagFunc.units_in_moving_zones{ units = {'[red]'}, zone_units = {'hmv1', 'hmv2'}, flag = 1, radius = 1200, zone_type = 'sphere', } However, if I try to use UnitNameTables for zone_units as in, mist.flagFunc.units_in_moving_zones{ units = {'[red]'}, zone_units = {'[blue]'}, flag = 1, radius = 1200, zone_type = 'sphere', } the flag will never activate. The problem with mist.flagFunc.units_LOS is similar to this but for both sets (unitset1 and unitset2). "Custom" sets of units work, but UnitNameTables (e.g. '[red]' and '[blue]') do not. Could be an underlying issue or just me.:) PS: If anyone would like to do a quick check, here's the mission I used for testing. (mist_test.miz) edit: Observed in DCS 1.5 hotfix 2 with mist 4.0.55.

That! +1

I'd like to register as lonewolf for round 3. Callsign: methosXX Aircraft: A-10C, Ka-50, Su-27 RED pls!

First and foremost I want to thank you guys for hosting and organizing such a great multiplayer event. I've been flying DCS on and off for the last 3 years and this was arguably the most fun I've had in DCS multiplayer so far! As I've been fighting for REDFOR (without registration, will definitely register for next round :thumbup:) I would like to vote for =238.lbae=Gruja since he's done a hell of a job coordinating the players. Cheers!