Buzzer1977

Starting DCS with SteamVR, the game is unusable, because the Steam library overlays DCS in VR and can't be closed. Restarting DCS fixes the problem until SteamVR is (re-)started again.

F-14 AI flies dangerously low after carrier launch until the entire group is airborne. F-14AB_low_wingman.trk

MiG-21 in a flat spin

VoiceChat in F-15E S4+ kills DCS 2.9.0.47168 MT VR crashes client to desktop ocassionally when entering cockpit in multi player. Happens only occasionally. Not 100% reproducable. Mission attached, AC joined was slot "Colt-1b-1". 2023-10-30 20:30:08.644 INFO ARF (Main): Added NCTR type "F-4E" (1,1,1,45) angle=45.000000 dB=10.000000 2023-10-30 20:30:08.644 INFO ARF (Main): Added NCTR type "Su-33" (1,1,1,4) angle=45.000000 dB=10.000000 2023-10-30 20:30:08.644 ERROR Lua::Config (Main): Lua error can't open 'C:\Users\heiko\Saved Games\DCS\/Config/F-15E/NCTR.lua' in "C:\Users\heiko\Saved Games\DCS\/Config/F-15E/NCTR.lua" 2023-10-30 20:30:08.644 INFO COCKPITBASE (Main): WebRTC VOIP init: registered radio receiver "Base TACAN receiver" with id - 4 2023-10-30 20:30:08.645 INFO EDCORE (Main): try to write dump information 2023-10-30 20:30:08.652 INFO EDCORE (Main): # -------------- 20231030-203008 -------------- 2023-10-30 20:30:08.654 INFO EDCORE (Main): DCS/2.9.0.47168 (x86_64; MT; Windows NT 10.0.22621) 2023-10-30 20:30:08.656 INFO EDCORE (Main): G:\Program Files (x86)\Steam\steamapps\common\DCSWorld\CoreMods\services\VoiceChat\bin\VoiceChat.dll 2023-10-30 20:30:08.657 INFO EDCORE (Main): # C0000005 ACCESS_VIOLATION at 00007ffb2385df9f 00:00000000 2023-10-30 20:30:08.659 INFO EDCORE (Main): SymInit: Symbol-SearchPath: 'G:\Program Files (x86)\Steam\steamapps\common\DCSWorld\bin-mt;', symOptions: 532, UserName: 'heiko' 2023-10-30 20:30:08.661 INFO EDCORE (Main): OS-Version: 10.0.22621 () 0x100-0x1 2023-10-30 20:30:08.663 INFO EDCORE (Main): 0x000000000001df9f (VoiceChat): release + 0x1651F 2023-10-30 20:30:08.665 INFO EDCORE (Main): 0x00000000000161f8 (VoiceChat): release + 0xE778 2023-10-30 20:30:08.666 INFO EDCORE (Main): 0x000000000028a71f (F15E_CPT): cockpit::F15E_RadioSystem::avF15E_ICS::SetCommand + 0xEF 2023-10-30 20:30:08.666 INFO EDCORE (Main): 0x000000000021116f (CockpitBase): cockpit::avDevice::performClickableAction + 0x5F 2023-10-30 20:30:08.666 INFO EDCORE (Main): 0x000000000028a229 (F15E_CPT): cockpit::F15E_RadioSystem::avF15E_ICS::post_initialize + 0x439 2023-10-30 20:30:08.666 INFO EDCORE (Main): 0x0000000000211497 (CockpitBase): cockpit::avDevice::start + 0x37 2023-10-30 20:30:08.666 INFO EDCORE (Main): 0x00000000001d756f (CockpitBase): cockpit::ccCockpitContext::start + 0x5F 2023-10-30 20:30:08.666 INFO EDCORE (Main): 0x00000000003a1a02 (CockpitBase): cockpit::c_draw_debug_cockpit_tripod + 0x5F42 2023-10-30 20:30:08.666 INFO EDCORE (Main): 0x0000000000582cb1 (DCS): SW + 0xC21D1 2023-10-30 20:30:08.666 INFO EDCORE (Main): 0x00000000006f2ab5 (DCS): SW + 0x231FD5 2023-10-30 20:30:08.666 INFO EDCORE (Main): 0x00000000006aebc7 (DCS): SW + 0x1EE0E7 2023-10-30 20:30:08.666 INFO EDCORE (Main): 0x00000000005323ec (DCS): SW + 0x7190C 2023-10-30 20:30:08.667 INFO EDCORE (Main): 0x000000000085b298 (DCS): SW + 0x39A7B8 2023-10-30 20:30:08.667 INFO EDCORE (Main): 0x000000000085c2da (DCS): SW + 0x39B7FA 2023-10-30 20:30:08.667 INFO EDCORE (Main): 0x000000000085b329 (DCS): SW + 0x39A849 2023-10-30 20:30:08.667 INFO EDCORE (Main): 0x00000000008310f5 (DCS): SW + 0x370615 2023-10-30 20:30:08.667 INFO EDCORE (Main): 0x0000000000830c29 (DCS): SW + 0x370149 2023-10-30 20:30:08.667 INFO EDCORE (Main): 0x000000000005629c (WorldGeneral): wControl::Control + 0x5C 2023-10-30 20:30:08.667 INFO EDCORE (Main): 0x0000000000004464 (World): wSimTrace::CommandsTraceDiscreteIsOn + 0x3E4 2023-10-30 20:30:08.667 INFO EDCORE (Main): 0x0000000000004a4d (World): wSimCalendar::DoActionsUntil + 0x21D 2023-10-30 20:30:08.667 INFO EDCORE (Main): 0x00000000008b8199 (DCS): SW + 0x3F76B9 2023-10-30 20:30:08.667 INFO EDCORE (Main): 0x00000000008b7e71 (DCS): SW + 0x3F7391 2023-10-30 20:30:08.667 INFO EDCORE (Main): 0x00000000008da262 (DCS): SW + 0x419782 2023-10-30 20:30:08.668 INFO EDCORE (Main): 0x0000000000897ae4 (DCS): SW + 0x3D7004 2023-10-30 20:30:08.668 INFO EDCORE (Main): 0x0000000000899223 (DCS): SW + 0x3D8743 2023-10-30 20:30:08.668 INFO EDCORE (Main): 0x00000000004a1900 (DCS): (function-name not available) + 0x0 2023-10-30 20:30:08.668 INFO EDCORE (Main): 0x00000000027c4e8f (DCS): AmdPowerXpressRequestHighPerformance + 0x1382E8B 2023-10-30 20:30:08.668 INFO EDCORE (Main): 0x0000000000cd5b6e (DCS): SW + 0x81508E 2023-10-30 20:30:08.668 INFO EDCORE (Main): 0x000000000001257d (KERNEL32): BaseThreadInitThunk + 0x1D 2023-10-30 20:30:09.058 INFO EDCORE (Main): Minidump created. 2023-10-30 20:30:09.058 INFO Lua::Config (Main): stack traceback: 2023-10-30 20:30:09.065 WARNING LOG (18796): 3 duplicate message(s) skipped.dcs.log.old dcs.log-20231030-203008.zip Guam.miz

A Fulda gap map would be cool. From Ramstein/Spangdahlem/Landstuhl/K-town area in the west, to Pilsen in the east. The south of the map should include the area around Schwäbisch Gmünd where the Pershing SRBMs nukes where stationed, maybe down to Ulm/Memmingen area to have a Tornado playground and Kassel to the north where (Western)Germany builds its tanks. But i think with all the forest and gazillion cities and villages it would be a performance killer.

Orrr ... should have known this before i preordered.

Having a Zone with the new linke unit feature kills MIST scripting. My best guess would be that it will cause deep copy to loop, but that's just a plain guess ... DCS DCS 2.9.0.47168 MIST 4.5.118 null dcs.log LinkeZoneBug.miz

Seems fixed with the latest update.

Since 2.9 AV-8B AI units won't take of from ground. AV8B_AI_TakeOffFromGroundBug.trk test.miz

I want to create/activate a static object (comm tower) from a trigger. What is the required trigger action ? The scenario is as follows: If cargo is unloaded in a specific zone, i want to have a COM tower activated (exists only as a static) and play a radio transmission. When i destroy the comms tower, the radio transmission should stop. The later part with the play and stop, depending on UNIT IS ALIVE('comm tower') i've already have realized(RADIO TRANSMISSION / STOP RADIO TRANSMISSION). But i struggle to get the comms tower spawned with a trigger. The condition is already met (CARGO UNHOOKED IN ZONE) but what is the action ? With normal ground units i would mark the tower with late activation and do a GROUP ACTIVATE. with best regards tower buzzer

At least C-130 & C-17 are affected. But not KC-130 thou ...

It would be great if we could transmit voice messages over the radio directly from LUA via text to speech, f.e. via Windows speech synthesizer https://learn.microsoft.com/en-us/uwp/api/windows.media.speechsynthesis?view=winrt-22621, so dynamic radio messages can be generated. Something like the radioTransmission trigger, but with text, voice, language instead of filename. radioTransmission(string filename , vec3 point , enum modulation , boolean loop , number frequency , number power , string name)

Why are there no attributes for boom/drogue on tankers ? For receiver aircraft we have at least ["tankerType"], but recepticle/probe attributes would be nice for receiver aircraft too. This would make scripting much more convenient then maintaining compatibility lists. Something like this: AirTankerType = { DROGUE = "DROGUE", BOOM = "BOOM", BOOM_AND_DROGUE = "BOOM+DROGUE", } function getTankerType( unit ) if unit then local attributes = unit:getAttributes() if attributes and attributes["Tankers"] and attributes["Boom"] and attributes["Drogue"] then return AirTankerType .BOOM_AND_DROGUE end if attributes and attributes["Tankers"] and attributes["Boom"] then return AirTankerType .BOOM end if attributes and attributes["Tankers"] and attributes["Drogue"] then return AirTankerType .DROGUE end -- Not a tanker end return nil end function getRefulingType( unit ) if unit then local attributes = unit:getAttributes() if attributes and attributes ["tankerType"] ==0 then return AirTankerType .BOOM end if attributes and attributes ["tankerType"] ==1 then return AirTankerType .DROGUE end -- Not a tanker end return nil end Something compareable already works fine with aircraft carrier types to decide between CATOBAR/STOBAR/STOLV. function getCarrierType( unit ) if unit then local attributes = unit:getAttributes() if attributes and attributes["AircraftCarrier"] and attributes["Arresting Gear"] and attributes["catapult"] then return CarrierType.CATOBAR end if attributes and attributes["AircraftCarrier"] and attributes["Arresting Gear"] then return CarrierType.STOBAR end if attributes and attributes["AircraftCarrier"] then -- workaround because Type 071 reports back as a AircraftCarrier, but isn't if attributes["typeName"] == "Type_071" then return nil end return CarrierType.STOLV end -- Not a carrier end return nil end

Su-33 can be placed on Type 071 amphibious assault ship. Type 071 identifies as a aircraft carrier, despite only having two helipads. {["massEmpty"]=25000000,["RCS"]=7222.6440429688,["box"]=table: 0000020B07263FC0,["speedMax"]=12.777700424194,["life"]=0,["attributes"]=table: 0000020B07263BB0,["category"]=3,["Kmax"]=0.050000000745058,["_origin"]="China Asset Pack by Deka Ironwork Simulations and Eagle Dynamics",["typeName"]="Type_071",["displayName"]="Type 071 Amphibious Transport Dock"} attr: {["Aircraft Carriers"]=true,["AircraftCarrier With Tramplin"]=true,["AircraftCarrier"]=true,["Ships"]=true,["RADAR_BAND1_FOR_ARM"]=true,["NO_SAM"]=true,["RADAR_BAND2_FOR_ARM"]=true,["DetectionByAWACS"]=true,["Heavy armed ships"]=true,["Straight_in_approach_type"]=true,["Armed Air Defence"]=true,["HelicopterCarrier"]=true,["Armed Ship"]=true,["HeavyArmoredUnits"]=true,["All"]=true,["Naval"]=true,["Armed ships"]=true}

Is there a function to check aircraft type compatibility with a airfield? I'm trying to dynamically generate a mission and therefore need to verify if a aircraft type can start, land, park, rearm and refuel at a given airfield. Is there such a function or how can i implement this (f.e. check runway length, parking type, etc ...) ?

Well, you've could have gotten these results 4 weeks earlier ...

I was shooting 4 of my 6 AMRAAMs, when the circle just disappeared and i couldn't shoot even with a perfect lock. The right DDI showed the 2 remaining AMRAAMs as "STBY". I was also unable to leave the radar screen on the left DDI. Landing turning off/on the radar, the entire airplane, repair & rearm didn't fix the issue. F-15E-AmraamStuckAndRadarBug.trk dcslog.zip

She's even bitchin about low altitude at FL330 ... Track, mission log and video recording with the low altitude warning added. F-15E-LowAltitudeBug.mp4 F-15E-LowAltitudeBug.log F-15E-LowAltitudeBug.trk

I've put a insurgent AA group on top of a building which i destroyed. The AA ground units mostly survived, even with the building beneath collapsed. They should be dead, or at least wounded on top of the rubble. Track, dcs.log, mission debrief, mission file and screenshot added. Sinai-OnBuildingBug.trk dcs.log Sinai-OnBuildingBug.log Sinai-TrainingMods.miz

Huge aircraft don't takeoff from ramp if told so, but respawn in the air and all at the same point, resulting in aircraft being in the same place over the airfield. Track, mission file, mission log, dcs log and screenshot added. dcs.log Sinai-NevatimBug.trk Sinai-NevatimBug.log Sinai-NevatimBug.miz

There's real love to detail at ED.

Liveries for naval units don't match with the mission. The livery set in the mission should be a Iranian vessel like in single player: but in multiplayer the same vessel has the default German livery: Seems to be related to a bug that fixed the same problem for aircraft, but not for other units like ships:

Link/16

I did some testing between WMR/SteamVR, ST/MT, 60/90Hz display setting and several aircraft on a naked map. Best results i've got was when i used multithreading with WMR as runtime and limited the display refresh rate to 60 Hz. The stuttering and switching between CPU bound main thread and CPU bound render thread always happend when i set the G2 to 90 Hz or when i used SteamVR and the AC wasn't a F-16 or F-18. It seems like DCS has some issues in VR when the display frame rate can't be achieved and the render and main thread fight over mutex locks. The stuttering can be seen in the graph below. AC ST 2D MT 2D FPS FPS limit theo. FPS F-16CM 125 138 GPU bound 490 F-15E 110 122 GPU bound 380 F-18C 123 137 GPU bound 470 F-14B 108 121 GPU bound 310 AC ST/VR(WMR) 60Hz MT/VR(WMR) 60Hz ST/VR(SVR) 60Hz MT/VR(SVR) 60Hz FPS FPS limit FPS FPS limit F-16CM 55 60 CPU bound rendering 55 60 CPU bound rendering F-15E 50 60 CPU bound rendering 50 45/60 CPU bound rendering/main thread extremely shaky F-18C 55 60 CPU bound rendering 55 60 CPU bound rendering F-14B 50 60 CPU bound rendering 50 45/60 CPU bound rendering/main thread extremely shaky ST/VR(WMR) 90Hz MT/VR(WMR) 90Hz ST/VR(SVR) 90Hz MT/VR(SVR) 90Hz FPS FPS limit FPS FPS limit F-16CM 52/53 64 CPU bound rendering/main thread shaky 53 56/60 CPU bound rendering/main thread extremely shaky F-15E 50 56/60 CPU bound rendering/main thread extremely shaky 50 53/56 CPU bound rendering/main thread extremely shaky F-18C 52/53 64 CPU bound rendering/main thread shaky 53 56/60 CPU bound rendering/main thread extremely shaky F-14B 50/51 60 CPU bound rendering/main thread shaky 50 53/56 CPU bound rendering/main thread extremely shaky