Migow

for me the tpm2 in ryzen processor was stutter culprit i had to desactivate . it triggers periodic stutter

hello when my team start a mission on "dedicated server" without 3d render with 30 player with a mission with high count of asset) the server lag , every player and AI start teleporting stop moving sometime for 1 minute , the weapon are still sync when they shoot,flare are sync(but not the targeting )),only position is out of sync. the game become unplayable. it is not a fps issue,or stutter etc.. on client. the problem happen only under high load in "dedicated server" without 3d render. especially if a lot of unit are moving or shoot if 3d render is activated the problem does not happen with the same player ,same mission. it seems the problem got huge seems last patch 2.9.16.10523MT , the problem exist to a less extent since the "dedicated server" mode exist

@Flappiehello here i describe the bugon mi24 ( but mi-8 is also affected , and to a less extent the ka-50 with intercom only) : radio bug mi24.miz ->if i put radio audio message from ground unit very close i only receive the message on r828 when it is selected on spu-8 ,i if select r863 i no longer receive anything on r828, -> expected behavior whatever i select on spu-8 i receive all radio message on r828.(unless it is a real limitation?) ->for r863 i receive no matter what spu-8 selection as expected.

@Flappiehello , i describe the bug (in sinai ) OPERATION RED DUST FALLv11 testmigow4.mizi put in some s60 aaa unit in a AAA defense area with concrete protection (in red circle) null from any angle the s60 in green area can be seen as expected by petrovitch, but even when i face a s60 in defence area (in red) they become invisible for petrovitch even at high altitude from south or north , on east it work sometime starting at 300 -400 meter at 6km from it but not always and after 20 min of flying it no longer see them but as a cpg i can see them in most case , it could be a sinai map issue and not mi24 i am not sure the expected behavior petro see at least 3 s60 AAA

please ed provide a solution +1

@Flappie on last patch 2.9.12.5336MT : -forest tree LOS -> still buggy (1st example video) the big tree there is another bug with the bush asset : the infantery ai can see each other with " x ray", and shoot! nullnull nullnullnull

thanks for report

the bug is partially fixed on last patch 2.9.10.4160MT : -forest tree LOS -> bug (1st example video) the big tree ----------------------------------------------------------------------------------------------------- -cultivated field tree LOS -> FIXED(2rd example video) the little tree in field

@Flappie the bug has nothing to do with mi24 (whatever you play) , the AI (sam, tank anything)( not petrovitch!) can see and shoot through the tree(XRAY vision!) , all the obstacle i reported , only the building work as intended , this a bug unique to syria: either syria map maker use wrong physic asset or DCS provide buggy physics for syria map , test the mission i provided you will see like the video that IA can see with XRAY and shoot on this map ! the bug is still here for years as of now! this is serious one for NOE flight.

for people interested i modded the NVG so they render at higher position , so it can clear the FOV without nvg to read the instrument

hello this feature can be implemented by modifying the shader file "NVD_common.hlsl" in "DCS World\Bazar\shaders\PostEffects" tested only with 2D screen , tell me if it works for VR (not sure) it will not PASS IC ! version 0.1 (need adjustement for nvg black body (too big i think) add the constant #define NVD_HIGHER_AJUSTEMENT -0.4 //0.4 good then replace : float2 calcMaskCoord(float2 projPos) { return float2((projPos.x - gNVDpos.x) * gNVDaspect, projPos.y - gNVDpos.y ) * MASK_SIZE; } by: float2 calcMaskCoord(float2 projPos) { return float2((projPos.x - gNVDpos.x) * gNVDaspect, projPos.y - gNVDpos.y + NVD_HIGHER_AJUSTEMENT ) * MASK_SIZE; }

Please ED fix this bug +1

@Recoil16 @Flappie @MAESTR0 the bug is still there since the last update , this is serious bug please i need a feedback for this issue

+1 Please ED we need those feature , thank you !

Please ED we need the bug to be fixed thank you

Please ED we need Unit.setLife(Class Self, number ) function , the trigger exist(unit ai set life) already(the function exist for the trigger) , it can be implemented , it would help a lot for mission editing/ability to simulate fragment explosion with script in a better way , ability to set mobility kill etc... it would make the game better

Please ED we need this function asap please if it does exist with a trigger then it could be implemented easy way!

i hope they fix it , thanks for report

updated with videos of LOS bug , i will add more

in sinai or caucasus it does'nt see this is very different , it is specific to this map

hello the map(syria ) has serious issue with line of sight for AI unlike other map BUG : the AI can see and shoot through all the tree in syria map only! it prevents correct NOE fly for HLO (unrealistic) test sa8 roland syria LOS.miz test LOS syria striker forest tree.miz test LOS syria striker field cultivated tree.miz test caucasus LOS lav25 sa8 forest tree.miz -> it is not an AI bug there is no issue on other map only on this map - flat (building)LOS(line of sight ) -> ok -forest tree LOS -> bug an apc lav25 attacking my helicopter with forest tree it should not see me: -cultivated field tree LOS -> bug a apc lav25 attacking my helicopter with cultivated field tree it should not see me now sa8 osa ( basic radar simulation should not see throught tree(map issue) (to see clearly the pov of sa8 without smoke): comparison with caucasus there is no issue

+1

hello ED team i would like to know the map parameter for UTM projection lon0 central meridian of the projection (degrees) is 147°(correct me ) i think but i need the correct "a (equatorial radius)" and either "f (flattening of ellipsoid ) "or "b " . also"k0( central scale factor) "( i guess 0.9996) thanks by advance my regards

hi , i found a good Fix for the periscope issue , problem solved find the file in {DCS World directory }\Mods\aircraft\Mi-24P\Cockpit\Scripts\9K113_CAM\9K113_CAM_init.lua then at line 18 swap local x,y,w,h,GUI_scale = get_UIMainView() by local x,y,w,h,GUI_scale = 0,0,3840,2160,2--get_UIMainView() resolution is 3840 / 2160 scale 2 for me , set your parameter it will work!(remember it is x,y,w,h,GUI_scale) (dont forget to put comment with get_UIMainView() -- or get rid of it whole file corrected. dofile(LockOn_Options.common_script_path.."devices_defs.lua") dofile(LockOn_Options.common_script_path.."ViewportHandling.lua") local use_helmet = false use_helmet = LockOn_Options.screen.oculus_rift purposes = {render_purpose.AUXILLARY_SIGHT_SCREENSPACE} if use_helmet then indicator_type = indicator_types.COLLIMATOR purposes = {render_purpose.AUXILLARY_SIGHT} else indicator_type = indicator_types.COMMON purposes = {render_purpose.AUXILLARY_SIGHT_SCREENSPACE} local x,y,w,h,GUI_scale = 0,0,3840,2160,2--get_UIMainView() dedicated_viewport = {x,y,w,h} dedicated_viewport_arcade = dedicated_viewport end page_subsets = {LockOn_Options.script_path.."9K113_CAM\\9K113_CAM_base_page.lua"} ---------------------- pages = {{1}} init_pageID = 1 the issue come from get_UIMainView() it report incorrect parameter!

thanks for your investigation :thumbup: ok , first i 'm not native english , so it likely hard for people to understand what i'm trying to explain ,the way etc...^^ 330 km/h IAS in forward flight with 0 m/s VVI at 50m msl ,in your example you are diving a little at 4m/s not the same thing i said 330 km/h to show you that the animation is sync with flight model , there is no bug in animation ( at least in forward flight) the subject is mostly about rotor clearance , check the rotor clearance it must match the data "Your still talking about this clearance of blades at speed, most of what you are taking about is theoretical" not correct the data come from real flight test in all kind of maneuver even forward flight please check the rotor clearance in your video ,fly at same parameter than kamov data full forward flight 0m/s VVI the thread is about that ; if possible slow down the video look at rotor at 47° 107° like in document 90% time in your video must look at rotor clearance 47° 107° you talk about flight enveloppe , i talk about rotor clearance , we dont talk about the same problem :) i'l make video about that like you say it is very unlikely that flight model will change . still people and ED need to see that something is wrong with rotor clearance, and by the way flight model likely the deviation is about rotor Dissymmetry of lift