Search the Community

In this video I let you see the differences between static and none reflection. if there is a reflection then there is in both a reflection and it is in front right of the canopy. And it is in an triangular form!! Canopy & MFD Reflections static and none are the same!

Pilots heads Position mismatching between internal and external views. in single player only for pilot and in multiplayer for copilot and crew chief.

When loading multiplayer replays game crashes or drops to to desktop. Tried 2 servers, clean install, file integrity checks nothing helps and the problem is reproducible. Attaching replays and a crash log. Cold-War-Syria-v182_DME1-20231228-015508.trk dcs.log-20231228-072742.zip

Hello, We noticed an issue with GBU-16 in loft bombing on the F-18: the unguided ballistics is so long (2000') that the bomb never acquires the laser spot if we try to guide it. Therefore the bomb is always long and unguided. By comparison, an unguided GBU-12 in loft bombing is approximately 700' long, and can easily be lased to its target. Self-lasing loft bombing with GBU-12 is indeed quite effective. The attached tacview track will illustrate this issue: first pass is guided GBU-12 (direct hit), second pass is unguided GBU-12 (700' long), third and fourth passes are unguided GBU-10 (2000' long, laser ont target, climb 25° and 40°), last pass is guided GBU-12 (direct hit). Tests with GBU-10 are pending. Did anyone notice this issue already? Did anyone managed to do loft bombing with GBU-16? Thanks! Test GBU-12 and GBU-16.zip.acmi

Map in the hornet on syria not set up for use out to 40nm scale like every other map in the game (barring Marianas, also having this bug). Simply displays a black screen underlay until scale is 10nm or lower - it should work to at least 40nm as other maps do.

Hey you guys at ED have been doing some really good work with the new maps and improving performance, but the issue with the A-10 pitching up needs to be addressed once and for all. I was coming in to land and as I come off the overhead break and drop my landing gear the jets starts pitching down then I add a ton of trim to keep the nose up and once I get about to the overrun bam all that trim, I put in catches up and the jet starts pitches up almost stalling. I'm close to 1,000 hours in the A-10 at this point so I've seen the issue more times than I'd like... I would have sent a track but the file was too big besides there have been a number of reports on this.

Any chance of having the PDL lights get reworked for night time? Or a radio option to bump up the brightness, these are LEDs after all. Left side (forward and aft)is fine. But the right side (elevation) is really really tricky to see at night. Or even have the aircraft turn the white lights on pointing to the middle of the aircraft. I know there is a mod, but I don't think everyone in my community wants to download a mod for a night time flight. The real deal.

My brother (@Brother_Leb) and I repeatedly fly a very lite mission on a self-hosted server with no mods and only 2 jets and like 5 static objects. Recently we both are receiving the following error when trying to load Replays of our flights: Here is the Track file: server-20250520-204029.trk Here is the crash log: dcs.log Here is the miz file: Paphos_Airshow_FILMING_v5.miz Here is a related issue, but I believe they may be different: https://forum.dcs.world/topic/343255-dcs-crash-when-loading-replays/#comment-5380922 Does anyone know why this could be happening? I flew a solo flight (on a multiplayer server I hosted with the same details as the logged flight) the other day, and I can replay that flight just fine. Its only when my brother flies with me that the issue occurs.

It only seems to happen if the track is longer than a few minutes

I notice that disperse under fire isn't working for AI for some reason, this is a command I use often but now it isn't working; basically I have ground units I want to stay in a particular position but once they are fired on now they are moving around heck even my ground crew that I have at the airfield changes position once the firing starts although they are nowhere near any combat action very strange behavior. this is happening on the Afghanistan map I'm not sure if its happening on any other maps. I tried to upload the track file but even after letting the mission run for less than two minutes it says it's too big to upload.

the title tells all

In capturing events on a dedicated MP server, I've found that there are several world.event events that either don't get triggered, or only get triggered occasionally. These same events are triggered very reliably in single player. Specifically (but not limited to): S_EVENT_REFUELING - NEVER triggers S_EVENT_REFUELING_STOP - unreliable - triggers less than 50% of the time S_EVENT_PLAYER_ENTER_UNIT - unreliable S_EVENT_PLAYER_LEAVE_UNIT - unreliable

I have seen on the Apache, the Gazelle and the Mi-24, the windscreen wipers actually wipe off the rain. And it looks cool and it's very immersive. Unfortunately, the Mi-8 and the Huey don't have that at the moment. The wipers work, but the rain stays on the windscreen. Will this be available for the Mi-8 and Huey soon? Could you please forward this as a question to the team? That would be very kind.

for about 1.5 years, in an update of the Huey, the fuel consumption was changed and also the flight pattern was touched. The helicopter is now too reactive, even when fully loaded (armament and fuel) the aircraft takes off and flies too fast. Also in the hover, it requires too much left pedal. Reading online, watching various UH-1H videos on youtube and also talking to real pilots, all confirmed that the current flight model of the huey is wrong. It requires too much left pedal and is too powerful currently. In the various virtual groups, we all edit the .lua file named FM, setting from “TRUE” to “FALSE” in order to return to the old flight model which was much better. Please check and have the flight model analyzed by some real Huey helicopter pilot (so he can confirm the figure), also check the manuals where the flight data and performance are present. This is a bug. I hope it will be reported and corrected or at least restored to the old flight model.

They sont work at all. Tested before September 30th Patch and after. Raindrops don't appear to even blow away from the movement of the aircrafts anymore either. Just makes it harder to fly in the rain, especially the Paradise Lost campaign. Thats all. I can provide a video if needed. Thanks in advance.

I only play in vr.. and at times .. not all the time, the nights are EXTREMELY dark to the point where the game is unplayable. There is no rhyme or reason as to when this happens.. it can be fine in one mission, but impact another, even on mp servers. When it's happening it looks like the lighting bloom level inside the cockpit is set to burn your eyes out mode.. I can see the displays and everything inside the cockpit, but the reflections from the glass inside the cockpit are horrible and it's pitch black outside.. no lights can be seen from city lights or stars.. even the moon is gone. If taking off from a fully lit carrier tou can only see it's lights if you are very close to it.. otherwise you can't see ANYTHING. Switching to f2 external view it looks similar.. no stars, no city lights etc.. like there's a pitch black cloud obscuring the view. this hasn't happened often.. but when it dies it's extremely frustrating.. especially after I purchased the fear the bones campaign and can't get past the first mission due to this. I tried starting the mission without vr and noticed that everything was very dark as well. Turning up the gamma from 2.2 to max just washes everything out, turning the pitch black background..with invisible stars and city lights grey instead. Heres what it looks like in 2d.. external views.. in vr its even worse.. as everything outside the cockpit is just pure black.

Hi, both Su-25T and Su-25 shaking on the ground during taxi. Is it going to be fixed in future? This is old issue.

As title - ACM appears to be functioning all the time, regardless of the ACM switch position. Track - hot start aircraft, ACM switch in OFF (default position). ACM applied to FLIR video. Apache FLIR ACM.trk

Hello folks! After yesterday's update that I installed on our server, I can no longer start the server. This message appears when I try to start it. What could be the reason? And how can I solve the problem? null

hi, got dcs.log error and warning logs. right ears might find this useful. ERROR Scripting (Main): No preset named 'MDRN_B_A_PGM_HTP' in table 'UNKNOWN'; called from: './CoreMods/tech/HeavyMetalCore/Database/Aircraft/B_1B.lua:159' WARNING EDCORE (Main): Source coremods/tech/southatlanticassets/textures/vehicles is already mounted to the same mount /textures/. WARNING EDCORE (Main): Source coremods/aircraft/av8bna/shapes is already mounted to the same mount /models/. WARNING EDCORE (Main): Source coremods/aircraft/chinaassetpack/textures/vehicles/hq7 is already mounted to the same mount /textures/. ERROR EDCORE (Main): Drivers errors while mounting coremods/aircraft/f-15e/liveries/f-15ese/usaf 17th ws af90 low vis clean.zip: ERROR EDCORE (Main): ZipDriver: Failed to open zip archive coremods/aircraft/f-15e/liveries/f-15ese/usaf 17th ws af90 low vis clean.zip. ERROR Scripting (Main): declare loadout fail, duplicate not allowed: "{SPRD}" from "./CoreMods/aircraft/MiG-21BIS/Entry/Aw", original located here "./CoreMods/aircraft/AircraftWeaponPack/JATOConts.lua" WARNING EDCORE (Main): Source mods/tech/wwii units/textures/ju-88 is already mounted to the same mount /textures/. 2025-02-02 19:34:57.874 ERROR EDOBJECTS (Main): Destruction shape not found URAL-APA_P1 2025-02-02 19:34:57.874 ERROR EDOBJECTS (Main): Destruction shape not found URAL_ATMZ-5_P_1 2025-02-02 19:34:57.888 ERROR EDOBJECTS (Main): Object HB_F4E_GBU15V1 with id=42 already declared in table BombTable 2025-02-02 19:34:57.888 ERROR EDOBJECTS (Main): Object OH58D_FIM_92 with id=93 already declared in table MissileTable 2025-02-02 19:34:57.888 ERROR EDOBJECTS (Main): Object X_25MP with id=47 already declared in table MissileTable 2025-02-02 19:35:00.407 ERROR WORLDGENERAL (Main): Error: Unit [F-4E-45MC]: Effect presets records are defined but empty. 2025-02-02 19:35:00.410 ERROR WORLDGENERAL (Main): Error: Unit [OH58D]: Asymmetrical wing configuration found. 2025-02-02 19:35:00.410 WARNING LOG (6112): 2 duplicate message(s) skipped. 2025-02-02 19:35:00.410 ERROR WORLDGENERAL (Main): AJS37 AI by Heatblur Simulations: Unexpected fires_pos index 12 2025-02-02 19:35:00.413 ERROR WORLDGENERAL (Main): Error: Unit [Hawk]: Cell "COCKPIT" is linked to self. 2025-02-02 19:35:00.413 ERROR WORLDGENERAL (Main): Error: Unit [Hawk]: Cell "CABIN_BOTTOM" link to cell "COCKPIT" produces a link loop. 2025-02-02 19:35:00.413 ERROR WORLDGENERAL (Main): Error: Unit [Hawk]: Cell "CABIN_BOTTOM" is linked to self. 2025-02-02 19:35:00.413 ERROR WORLDGENERAL (Main): Error: Unit [Hawk]: Cell "CABIN_LEFT_SIDE" is linked to self. 2025-02-02 19:35:00.413 ERROR WORLDGENERAL (Main): Error: Unit [Hawk]: Cell "CABIN_RIGHT_SIDE" link to cell "CABIN_LEFT_SIDE" produces a link loop. 2025-02-02 19:35:00.413 ERROR WORLDGENERAL (Main): Error: Unit [Hawk]: Cell "CABIN_RIGHT_SIDE" is linked to self. 2025-02-02 19:35:00.432 ERROR WORLDGENERAL (Main): Error: Unit [CH-47Fbl1]: Effect presets records are defined but empty. 2025-02-02 19:35:00.448 ERROR wInfo (Main): negative drag of payload "MK_82*28" 2025-02-02 19:35:00.448 ERROR wInfo (Main): negative drag of payload "{F4-2-AIM9P5}" 2025-02-02 19:35:00.448 ERROR wInfo (Main): negative drag of payload "{MAK79_MK20 1R}" 2025-02-02 19:35:00.448 ERROR wInfo (Main): negative drag of payload "GBU-31*8" 2025-02-02 19:35:00.448 ERROR wInfo (Main): negative drag of payload "{D8F2C90B-887B-4B9E-9FE2-996BC9E9AF03}" 2025-02-02 19:35:00.448 ERROR wInfo (Main): negative drag of payload "{BRU-70A_2*GBU-54_SIDE_RIGHT}" 2025-02-02 19:35:00.448 ERROR wInfo (Main): negative drag of payload "OH58D_Violet_Smoke_Grenade" 2025-02-02 19:35:00.448 ERROR wInfo (Main): negative drag of payload "{FE382A68-8620-4AC0-BDF5-709BFE3977D7}" 2025-02-02 19:35:00.448 ERROR wInfo (Main): negative drag of payload "{A6FD14D3-6D30-4C85-88A7-8D17BEE120E2}" 2025-02-02 19:35:00.448 ERROR wInfo (Main): negative drag of payload "{FAB_500_DUAL_R}" 2025-02-02 19:35:00.448 ERROR wInfo (Main): negative drag of payload "{F4-2-AIM9B}" 2025-02-02 19:35:00.448 ERROR wInfo (Main): negative drag of payload "{FAB_250_DUAL_R}" 2025-02-02 19:35:00.448 ERROR wInfo (Main): negative drag of payload "{BRU41_6X_MK-82}" 2025-02-02 19:35:00.448 ERROR wInfo (Main): negative drag of payload "GBU-31V3B*8" 2025-02-02 19:35:00.448 ERROR wInfo (Main): negative drag of payload "{BRU-70A_2*GBU-38_SIDE_RIGHT}" 2025-02-02 19:35:00.448 ERROR wInfo (Main): negative drag of payload "{5F1C54C0-0ABD-4868-A883-B52FF9FCB422}" 2025-02-02 19:35:00.448 ERROR wInfo (Main): negative drag of payload "{HSAB-6xAGM-84}" 2025-02-02 19:35:00.448 ERROR wInfo (Main): negative drag of payload "{773675AB-7C29-422f-AFD8-32844A7B7F17}" 2025-02-02 19:35:00.448 ERROR wInfo (Main): negative drag of payload "{HOT3_L2_M}" 2025-02-02 19:35:00.448 ERROR wInfo (Main): negative drag of payload "{BRU-42_2*GBU-38_RIGHT}" 2025-02-02 19:35:00.448 ERROR wInfo (Main): negative drag of payload "{BRU-70A_3*GBU-38}" 2025-02-02 19:35:00.448 ERROR wInfo (Main): negative drag of payload "{2234F529-1D57-4496-8BB0-0150F9BDBBD3}" 2025-02-02 19:35:00.448 ERROR wInfo (Main): negative drag of payload "{BRU-42_2*GBU-38_LEFT}" 2025-02-02 19:35:00.448 ERROR wInfo (Main): negative drag of payload "{29A828E2-C6BB-11d8-9897-000476191836}" 2025-02-02 19:35:00.448 ERROR wInfo (Main): negative drag of payload "{BRU-32 BDU-45}" 2025-02-02 19:35:00.448 ERROR wInfo (Main): negative drag of payload "{MAK79_BDU45B 3R}" 2025-02-02 19:35:00.449 ERROR wInfo (Main): negative drag of payload "{45447F82-01B5-4029-A572-9AAD28AF0275}" 2025-02-02 19:35:00.449 ERROR wInfo (Main): negative drag of payload "{FAB-500-TA}" 2025-02-02 19:35:00.449 ERROR wInfo (Main): negative drag of payload "{CLB4_BR250}" 2025-02-02 19:35:00.449 ERROR wInfo (Main): negative drag of payload "{96A7F676-F956-404A-AD04-F33FB2C74881}" 2025-02-02 19:35:00.449 ERROR wInfo (Main): negative drag of payload "{HOT3_R2}" 2025-02-02 19:35:00.449 ERROR wInfo (Main): negative drag of payload "{BRU-32 CBU-99}" 2025-02-02 19:35:00.449 ERROR wInfo (Main): negative drag of payload "OH58D_Red_Smoke_Grenade" 2025-02-02 19:35:00.449 ERROR wInfo (Main): negative drag of payload "OH58D_White_Smoke_Grenade" 2025-02-02 19:35:00.449 ERROR wInfo (Main): negative drag of payload "CBU87*10" 2025-02-02 19:35:00.449 ERROR wInfo (Main): negative drag of payload "OH58D_Green_Smoke_Grenade" 2025-02-02 19:35:00.449 ERROR wInfo (Main): negative drag of payload "OH58D_Blue_Smoke_Grenade" 2025-02-02 19:35:00.449 ERROR wInfo (Main): negative drag of payload "{F789E86A-EE2E-4E6B-B81E-D5E5F903B6ED}" 2025-02-02 19:35:00.449 ERROR wInfo (Main): negative drag of payload "{BETAB-500S}" 2025-02-02 19:35:00.449 ERROR wInfo (Main): negative drag of payload "{BRU-32 MK-82}" 2025-02-02 19:35:00.449 ERROR wInfo (Main): negative drag of payload "{RN-24}" 2025-02-02 19:35:00.449 ERROR wInfo (Main): negative drag of payload "{RN-28}" 2025-02-02 19:35:00.449 ERROR wInfo (Main): negative drag of payload "{IAB-500}" 2025-02-02 19:35:00.449 ERROR wInfo (Main): negative drag of payload "{FAB-500-M54-TU}" 2025-02-02 19:35:00.449 ERROR wInfo (Main): negative drag of payload "{FAB-250-M54}" 2025-02-02 19:35:00.449 ERROR wInfo (Main): negative drag of payload "{BKF_PTAB2_5KO}" 2025-02-02 19:35:00.449 ERROR wInfo (Main): negative drag of payload "{MAK79_MK20 1L}" 2025-02-02 19:35:00.449 ERROR wInfo (Main): negative drag of payload "{MAK79_MK20 2R}" 2025-02-02 19:35:00.449 ERROR wInfo (Main): negative drag of payload "{B5CA9846-776E-4230-B4FD-8BCC9BFB1676}" 2025-02-02 19:35:00.449 ERROR wInfo (Main): negative drag of payload "{FAB-250-M54-TU}" 2025-02-02 19:35:00.449 ERROR wInfo (Main): negative drag of payload "{MAK79_BDU45B 3L}" 2025-02-02 19:35:00.449 ERROR wInfo (Main): negative drag of payload "{MAK79_BDU45B 4}" 2025-02-02 19:35:00.449 ERROR wInfo (Main): negative drag of payload "{4D459A95-59C0-462F-8A57-34E80697F38B}" 2025-02-02 19:35:00.450 ERROR wInfo (Main): negative drag of payload "{9DDF5297-94B9-42FC-A45E-6E316121CD85}" 2025-02-02 19:35:00.450 ERROR wInfo (Main): negative drag of payload "{8_x_AGM_86C}" 2025-02-02 19:35:00.450 ERROR wInfo (Main): negative drag of payload "{RBK_500_PTAB105_DUAL_R}" 2025-02-02 19:35:00.450 ERROR wInfo (Main): negative weight of payload "{LAU-7_AIM-9L_Left}" 2025-02-02 19:35:00.450 ERROR wInfo (Main): negative drag of payload "{BRU-70A_2*GBU-54_SIDE_LEFT}" 2025-02-02 19:35:00.450 ERROR wInfo (Main): negative drag of payload "{BRU-70A_2*GBU-54_RIGHT}" 2025-02-02 19:35:00.450 ERROR wInfo (Main): negative drag of payload "{ODAB-500PM}" 2025-02-02 19:35:00.450 ERROR wInfo (Main): negative drag of payload "{BRU-32 GBU-24}" 2025-02-02 19:35:00.450 ERROR wInfo (Main): negative drag of payload "{BRU-32 GBU-16}" 2025-02-02 19:35:00.450 ERROR wInfo (Main): negative drag of payload "{BRU-32 GBU-10}" 2025-02-02 19:35:00.450 ERROR wInfo (Main): negative drag of payload "{BRU-32 BDU-45B}" 2025-02-02 19:35:00.450 ERROR wInfo (Main): negative drag of payload "{BRU-32 MK-83}" 2025-02-02 19:35:00.450 ERROR wInfo (Main): negative drag of payload "{BRU-32 MK-84}" 2025-02-02 19:35:00.450 ERROR wInfo (Main): negative drag of payload "{3EA17AB0-A805-4D9E-8732-4CE00CB00F17}" 2025-02-02 19:35:00.450 ERROR wInfo (Main): negative drag of payload "{07BE2D19-0E48-4B0B-91DA-5F6C8F9E3C75}" 2025-02-02 19:35:00.450 ERROR wInfo (Main): negative drag of payload "{CLB4_BLU107}" 2025-02-02 19:35:00.450 ERROR wInfo (Main): negative drag of payload "{FAB_500_DUAL_L}" 2025-02-02 19:35:00.450 ERROR wInfo (Main): negative drag of payload "{40AB87E8-BEFB-4D85-90D9-B2753ACF9514}" 2025-02-02 19:35:00.450 ERROR wInfo (Main): negative drag of payload "{5A1AC2B4-CA4B-4D09-A1AF-AC52FBC4B60B}" 2025-02-02 19:35:00.450 ERROR wInfo (Main): negative drag of payload "CBU97*10" 2025-02-02 19:35:00.450 ERROR wInfo (Main): negative weight of payload "{LAU-7_AIM-9L_Right}" 2025-02-02 19:35:00.450 ERROR wInfo (Main): negative weight of payload "{LAU-7_AIM-9M_Right}" 2025-02-02 19:35:00.450 ERROR wInfo (Main): negative weight of payload "{LAU-7_AIM-9M_Left}" 2025-02-02 19:35:00.450 ERROR wInfo (Main): negative drag of payload "{BF83E8FD-E7A2-40D2-9608-42E13AFE2193}" 2025-02-02 19:35:00.450 ERROR wInfo (Main): negative drag of payload "{BRU-32 MK-82AIR}" 2025-02-02 19:35:00.451 ERROR wInfo (Main): negative drag of payload "{RBK_500_PTAB105_DUAL_L}" 2025-02-02 19:35:00.451 ERROR wInfo (Main): negative drag of payload "B-1B_Mk-84*8" 2025-02-02 19:35:00.451 ERROR wInfo (Main): negative drag of payload "{C535596E-F7D2-4301-8BB4-B1658BB87ED7}" 2025-02-02 19:35:00.451 ERROR wInfo (Main): negative drag of payload "{BRU-70A_3*GBU-54}" 2025-02-02 19:35:00.451 ERROR wInfo (Main): negative drag of payload "OH58D_Yellow_Smoke_Grenade" 2025-02-02 19:35:00.451 ERROR wInfo (Main): negative drag of payload "{BRU-32 MK-20}" 2025-02-02 19:35:00.451 ERROR wInfo (Main): negative drag of payload "DIS_LS_6_250_DUAL_R" 2025-02-02 19:35:00.451 ERROR wInfo (Main): negative drag of payload "DIS_LS_6_250_DUAL_L" 2025-02-02 19:35:00.451 ERROR wInfo (Main): negative drag of payload "{FAB-500-M54}" 2025-02-02 19:35:00.451 ERROR wInfo (Main): negative drag of payload "{RBK_250_PTAB25M_DUAL_L}" 2025-02-02 19:35:00.451 ERROR wInfo (Main): negative drag of payload "{RBK_250_PTAB25M_DUAL_R}" 2025-02-02 19:35:00.451 ERROR wInfo (Main): negative drag of payload "GBU-38*16" 2025-02-02 19:35:00.451 ERROR wInfo (Main): negative drag of payload "{FAB_250_DUAL_L}" 2025-02-02 19:35:00.451 ERROR wInfo (Main): negative drag of payload "{MAK79_MK20 2L}" 2025-02-02 19:35:00.451 ERROR wInfo (Main): negative drag of payload "{D8F2C90B-887B-4B9E-9FE2-996BC9E9AF0A}" 2025-02-02 19:35:00.451 ERROR wInfo (Main): negative drag of payload "{FAB-500-SL}" 2025-02-02 19:35:00.451 ERROR wInfo (Main): negative drag of payload "{X-31P}" 2025-02-02 19:35:00.451 ERROR wInfo (Main): negative drag of payload "{HOT3_L2}" 2025-02-02 19:35:00.451 ERROR wInfo (Main): negative drag of payload "{96A7F676-F956-404A-AD04-F33FB2C74884}" 2025-02-02 19:35:00.451 ERROR wInfo (Main): negative drag of payload "{F503C276-FE15-4C54-B310-17B50B735A84}" 2025-02-02 19:35:00.451 ERROR wInfo (Main): negative drag of payload "{AABA1A14-78A1-4E85-94DD-463CF75BD9E4}" 2025-02-02 19:35:00.451 ERROR wInfo (Main): negative drag of payload "{4D13E282-DF46-4B23-864A-A9423DFDE50A}" 2025-02-02 19:35:00.451 ERROR wInfo (Main): negative drag of payload "{8DCAF3A3-7FCF-41B8-BB88-58DEDA878EDE}" 2025-02-02 19:35:00.451 ERROR wInfo (Main): negative drag of payload "{BRU-70A_2*GBU-54_LEFT}" 2025-02-02 19:35:00.451 ERROR wInfo (Main): negative drag of payload "{BRU-32 GBU-12}" 2025-02-02 19:35:00.451 ERROR wInfo (Main): negative drag of payload "{BETAB-500M}" 2025-02-02 19:35:00.451 ERROR wInfo (Main): negative drag of payload "{X-31A}" 2025-02-02 19:35:00.452 ERROR wInfo (Main): negative drag of payload "{HOT3_R2_M}" 2025-02-02 19:35:00.452 ERROR wInfo (Main): negative drag of payload "{BRU-42_3*GBU-38}" 2025-02-02 19:35:00.452 ERROR wInfo (Main): negative drag of payload "{0180F983-C14A-11d8-9897-000476191836}" 2025-02-02 19:35:00.452 ERROR wInfo (Main): negative drag of payload "{BKF_AO2_5RT}" 2025-02-02 19:35:00.452 ERROR wInfo (Main): negative drag of payload "{4D13E282-DF46-4B23-864A-A9423DFDE504}" 2025-02-02 19:35:00.452 ERROR wInfo (Main): negative drag of payload "{BRU-70A_2*GBU-38_SIDE_LEFT}" 2025-02-02 19:35:00.452 ERROR wInfo (Main): negative weight of payload "DIS_GDJ_YJ83K" 2025-02-02 19:35:00.452 ERROR wInfo (Main): negative drag of payload "{F4-2-AIM9L}" 2025-02-02 19:35:00.452 ERROR wInfo (Main): negative drag of payload "{7C5F0F5F-0A0B-46E8-937C-8922303E39A8}" 2025-02-02 19:35:00.452 ERROR wInfo (Main): negative drag of payload "{E1AAE713-5FC3-4CAA-9FF5-3FDCFB899E33}" 2025-02-02 19:35:00.452 ERROR wInfo (Main): negative drag of payload "{BRU-32 MK-82SE}" 2025-02-02 19:35:10.967 ERROR EDCORE (Main): Can't open file './CoreMods/aircraft/AV8BNA/UnitPayloads/358th FS Davis Monthan AFB, Arizona (DM)' from real path fs. 2025-02-02 19:35:11.020 ERROR EDCORE (Main): Can't open file './CoreMods/aircraft/AV8BNA/UnitPayloads/25th FS Osan AB, Korea (OS)' from real path fs. 2025-02-02 19:35:11.159 ERROR EDCORE (Main): Can't open file './CoreMods/aircraft/AV8BNA/UnitPayloads/74th FS Moody AFB, Georgia (FT)' from real path fs. 2025-02-02 19:35:11.175 ERROR EDCORE (Main): Can't open file './CoreMods/aircraft/AV8BNA/UnitPayloads/81st FS Spangdahlem AB, Germany (SP) 1' from real path fs. 2025-02-02 19:35:11.307 ERROR EDCORE (Main): Can't open file './CoreMods/aircraft/AV8BNA/UnitPayloads/81st FS Spangdahlem AB, Germany (SP) 2' from real path fs. 2025-02-02 19:35:11.433 ERROR EDCORE (Main): Can't open file './CoreMods/aircraft/AV8BNA/UnitPayloads/354th FS Davis Monthan AFB, Arizona (DM)' from real path fs. 2025-02-02 19:35:11.574 ERROR EDCORE (Main): Can't open file './CoreMods/aircraft/AV8BNA/UnitPayloads/357th FS Davis Monthan AFB, Arizona (DM)' from real path fs. 2025-02-02 19:35:16.148 ERROR EDCORE (Main): Can't open file './CoreMods/aircraft/AV8BNA/UnitPayloads/358th FS Davis Monthan AFB, Arizona (DM)' from real path fs. 2025-02-02 19:35:16.153 ERROR EDCORE (Main): Can't open file './CoreMods/aircraft/AV8BNA/UnitPayloads/25th FS Osan AB, Korea (OS)' from real path fs. 2025-02-02 19:35:16.163 ERROR EDCORE (Main): Can't open file './CoreMods/aircraft/AV8BNA/UnitPayloads/74th FS Moody AFB, Georgia (FT)' from real path fs. 2025-02-02 19:35:16.164 ERROR EDCORE (Main): Can't open file './CoreMods/aircraft/AV8BNA/UnitPayloads/81st FS Spangdahlem AB, Germany (SP) 1' from real path fs. 2025-02-02 19:35:16.171 ERROR EDCORE (Main): Can't open file './CoreMods/aircraft/AV8BNA/UnitPayloads/81st FS Spangdahlem AB, Germany (SP) 2' from real path fs. 2025-02-02 19:35:16.177 ERROR EDCORE (Main): Can't open file './CoreMods/aircraft/AV8BNA/UnitPayloads/354th FS Davis Monthan AFB, Arizona (DM)' from real path fs. 2025-02-02 19:35:16.187 ERROR EDCORE (Main): Can't open file './CoreMods/aircraft/AV8BNA/UnitPayloads/357th FS Davis Monthan AFB, Arizona (DM)' from real path fs. 2025-02-02 19:35:18.591 WARNING ASYNCNET (Main): Ignoring duplicate request to imageIRAQ_terrain while one is already in flight. 2025-02-02 19:35:18.594 WARNING ASYNCNET (Main): Ignoring duplicate request to imageAFGHANISTAN_terrain while one is already in flight. Im not sure is it just my system or wider thing? tnx.

I am trying to host my own server, and am getting this as a warning in my logs. However, it's the last line in the log before the DCS Server just crashes out completely. I'm not 100% sure this is the problem, but the DCS Server just dies. This is the last few lines from my log, before it dies: If anyone can assist me with this issue. Maybe the path is too long? Path to my installation; "Z:\Program Files\Eagle Dynamics\DCS World OpenBeta Server\bin" Nothing special there. No mods. I have a mission file loaded which I created. Pretty basic, I think. Latest version. 2.8.1.34667 I restart the server and look at the logs in the WebUI. They're only for the current session but I do see this: There's a few errors there. Not sure what they mean or if that's the problem.

I have been having difficulty with getting the data link to work, so I generated a number of simple test missions and tracks which would take some of my questionable start-up behaviours out of the loop: 1) -1 and -2 members of the same flight, both hot start on the ground with an AWACS on the data net, -2 does not populate on the HSD from the DL, but the AWACS does 2) same as above but the -1 -2 are airborne, both -2 and AWACS populate from the DL 3) -1 and -2 are members of different flights -2 starts airborne , AWACS and -2 both populate the HSD from the DL 4) as above but -2 starts on the ground, AWACS populates the HSD from the DL straight away, -2 only populates the HSD from the DL after wheels up. My conclusion is that I should not expect DL to populate on the ground, but only in the air? Is this behaviour correct? DL Test 01.trk DL Test 02.trk DL Test 03.trk DL Test 04.trk Data Link Test 01.miz Data Link Test 02.miz Data Link Test 03.miz Data Link Test 04.miz

If you have the pilots body being visible and turn your head in the cockpit view, the camera moves outside the head and forward looking backwards and you can see your own head, in this view it would be better if the head of the model of the pilot was made invisible. Noticing this in the F/A-18, but likely effects other modules aswell. This obviously isn't an issue if you turn off the in cockpit body.

Tonight i have flown F4, F14B and FA18C in Sinia, Caucassus and Syria and have noticed a sighnificant drop in perfornance with approx 40% FPS drop since 24 Dec update.

Theory: in RUK, the HARM should have a search radius of 20nm around the selected steerpoint (according to the linked video below). this should ensure the HARM does not target something further out etc. according to the early access manual (page 397), EOM should require much more precise target location information than RUK (or PB) Now in my test, i placed 2 steerpoints. one on which i fire the HARM and the second one where the location of an actual SA-15 is.The goal here is, that the HARM will only attack a SA15 emitter around a specific steerpoint, not any other SA15 outside its 20nm search radius. Test: In this example I fire at a target steerpoint (kutaisi) with an SA-15 along my ingress axis, however outside of the 20nm search radius. expected result: HARM flies to Kutaisi, impacting on the steerpoint as it cant find any emitter there. observed result:HARM_RUK.trk HARM attacks SA-15 even though it is outside of the 20nm search radius around Kutaisi. this does not reflect what wags talks about here (first 2min): Test 2: after seeing that i was curious if the HARM in EOM does the same, even though the search radius around the selected steerpoint for the HARM should be even smaller than in RUK: expected result: HARM impacts steerpoint at Kutaisi observed result:HARM_EOM.trk HARM kills SA-15, 25nm short of intended steerpoint Test 3: Same setup this time using PB mode expected result: HARM impacts steerpoint at Kutaisi observed result: HARM_PB.trk Harm kills SA-15, 25nm short of intended steerpoint. Conclusion: in all of the POS modes, the HARM seems to target the first possible emitter of the selected emitter it can find, goes active too early and attacks "wrong" targets.