Search the Community

English: Hello Everyone, I'm NF2, Main Mission Editor of the Rising Squall Campaign. Here we're going to release the bugs and questions list we've collected about the mission through various channels, as well as their feedback. As this campaign adopts some innovative production methods, I am also worried about the problems caused by the changes of the game version. We expect to minimize the number of bugs in the campaign, and hope to eradicate the problem of "Stay at a some level and cannot continue the game", which often occurs in campaign of DCS. We also recommend that you try various "possible" or "impossible" game methods to help us improve the "robust" of the missions. Please attach TRK files or TACVIEW files (highly recommended) when describing your problem, so that we can analyze the problem. You can submit your problems to us through forum, email and other ways. Thank you for choosing our campaign. And look forward to our future opus. 中文（概要）： 如果你需要提交BUG，建议附上 TRK 或者 TACVIEW 文件（强烈推荐），以便我们可以追踪查询问题。 Date of collection （收集日期） Priority （优先级） Description (问题描述） Resolvent （解决方案） State （状态） 2021/1/31 Improvement and optimization （改进与优化） M00: A change based on the future. 一个未来计划的改动 Update by DCS 2.7 ver 2021/1/31 Improvement and optimization （改进与优化） Add "watch plot animation" tips for each Mission. 为每个任务增加一个观看动画的提示 WIP 2021/1/31 No impact on the process （不影响游戏流程） M05: When the task is finished, a long conversation in Bishop has a conflicts. 任务结束时，Bishop 的一句长对话出现了冲突。 Need to adjust the conversation time 调整对话时间 Need Check 2021/1/31 Improvement and optimization （改进与优化） M07: When MIG-29 appears, a prompt needs to be added to show that the planes are not hostile. 当 Mig29 出现时，需要一个提示说明它们不是敌机。 WIP 2021/1/31 Improvement and optimization （改进与优化） M07: It is suggested that the rhythm of the music be adjusted after the end of the air combat and reduce the tension. 建议在空战部分结束后降低音乐的紧张感。 Re-edit the music No Guarantee 2021/1/31 No impact on the process （不影响游戏流程） M09: The "mission success" tips is Chinese 英文版中任务结束提示为中文。 There are two duplicate Tips, one of which is wrong and remove. 有两个重复的提示，删除了其中一个错误的。 FIXED OpenBeta 2.5.6.61527 2021/1/31 No impact on the process （不影响游戏流程） M06: It's too late for smoke signs and flares to appear at the target airport. 降落机场的烟雾和信号弹出现时机太迟 Adjust and shorten the trigger effective time. 调整了时间。 FIXED OpenBeta 2.5.6.61527 2021/1/31 No impact on the process （不影响游戏流程） M09: When Reef's Convoy was destroyed, part of the follow-up plot still played, leading to dialogue conflict. 当 Reef 的车队被摧毁时，一些后续剧情对话仍然被激活，导致一些对话冲突。 Add the judgment of mission failure to prohibit the follow-up plot. 增加一个判定以便任务失败时不再推进剧情。 FIXED OpenBeta 2.5.6.61527 2021/1/31 Frustrated with the game （对任务产生挫折） M04: When the mission is completed, landing to the carrier, it will accidentally activate a group of enemy aircraft that should not exist, leading to mission failure. 一组意外的飞机在降落航母时被激活，导致任务失败。 need to add a decision to avoid activating the problem planes after the player takes off. 增加一个判定以在起飞后不再激活那组问题飞机 FIXED OpenBeta 2.5.6.61527 2021/1/31 Improvement and optimization （改进与优化） M11: Add Tips for way-point number of the base. 增加返回基地的导航点提示 FIXED OpenBeta 2.5.6.61527 2021/1/31 Improvement and optimization （改进与优化） M11: Add a Tips for remaining number of target bombers. 增加目标轰炸机剩余数量提示 WIP 2021/1/31 No impact on the process （不影响游戏流程） M12: Conflict of "last warning" dialogue in Aegis-3. 主角的“上来就是最后一次警告”这句对话有冲突 Trigger conditions have been adjusted 调整对话时间 FIXED OpenBeta 2.5.6.61527 2021/1/31 No impact on the process （不影响游戏流程） M12: Lose liveries for Aegis-2 “revolution”. Aegis-2 在反叛后缺少涂装。 FIXED OpenBeta 2.5.6.61527 2021/1/31 No impact on the process （不影响游戏流程） VR perspective and TrackIR do not work properly in some missions. VR 与 TrackIR 在某些任务中视角不正常。 It may have something to do with the Trk file of ED. Need confirmed. 推测是预录制动画的原因。 Update by DCS 2.7 ver 2021/1/31 Improvement and optimization （改进与优化） M05: The prompt of joining Aeigs1 formation at the beginning of the mission is not clear enough. 任务开始时需要与Aegis-1会合的提示不明确。 FIXED OpenBeta 2.5.6.61527 2021/1/31 No impact on the process （不影响游戏流程） VR binocular settings need to be turned on by default. 预录制动画需要打开VR的双眼渲染 Update by DCS 2.7 ver 2021/2/1 No impact on the process（不影响游戏流程） M02: After the checkpoint is executed, the waypoint is different from the dialog. 检查点执行后的路径点名字与对话有差异 Correct 2021/2/1 Improvement and optimization （改进与优化） M04: (and CP)Remove the gunboats around the CVN 移除航母周围的“炮艇” Use invisible static objects instead 使用隐身物体 No Guarantee 2021/2/1 Frustrated with the game （对任务产生挫折） M04 NoSC: The wrong version of the game file causes the wingman not to follow the player in the task, and triggers the victory condition ahead of time. 检查点文件是错误的 Need to upload the latest file again. 重新更新了一次 FIXED OpenBeta 2.5.6.61527 2021/2/1 No impact on the process （不影响游戏流程） M01: A dialogue for aegis-4 has been conflict Aegis4 的一句对话冲突了 Change trigger timer 调整时间 FIXED OpenBeta 2.5.6.61527 2021/2/2 Frustrated with the game （对任务产生挫折） M10: Miss BGM when push WP2 过 WP2 后丢失 BGM。 FIXED OpenBeta 2.5.6.61527 2021/2/2 No impact on the process （不影响游戏流程） M10: Task of Yard need more detailed tips 堆场任务目标提示增加 FIXED OpenBeta 2.5.6.61527 2021/2/2 Improvement and optimization （改进与优化） The function of custom label 定制标签功能 Update by DCS 2.7 ver 2021/2/2 Improvement and optimization （改进与优化） M01: Increase the probability that the target will be displayed on the data link SA page 增加更大的概率让目标显示在SA页面上 Change location of AWACS. 预警机位置更靠前了 FIXED OpenBeta 2.5.6.61527 2021/2/2 Improvement and optimization （改进与优化） M12: After adjusting the threat range of Chainmail flight, they will be more reasonable now. Chainmail 机队的威慑范围被扩大了一些，让他们的反应更合理。 FIXED OpenBeta 2.5.6.61527 2021/2/2 Improvement and optimization （改进与优化） M06: Add checkpoint function before landing. 在降落前添加了一个检查点 FIXED OpenBeta 2.5.6.61527 2021/2/2 No impact on the process （不影响游戏流程） M03: No mission failure conditions. 丢失了任务失败的条件 FIXED OpenBeta 2.5.6.61527 2021/2/2 Improvement and optimization （改进与优化） M10: Reducing the interception probability of air defense system to missile 降低了导弹被拦截的概率 FIXED OpenBeta 2.5.6.61527

The MiG-29G HUD displays distance to the next waypoint in kilometers, although the speed and altitude on the HUD are in knots and feet, respectively. However, the HSI waypoint distance indicator, which is labeled "KM", displays the distance in nautical miles. This is pretty confusing, and I suspect incorrect - the book Luftwaffe Fulcrums: The MiG 29 - From the East German People's Army to the Luftwaffe says that the indication of all instruments was changed to feet, miles, and knots as part of the upgrade from MiG-29A/UB to MiG-29G/GT when the MiG-29s transitioned from East German to Luftwaffe service. If that's true, many other cockpit indications in our MiG-29G should also be changed, but the waypoint distance is the most confusing since the HUD and HSI disagree and the HSI is mislabeled. The radar range, target range, and target elevation are also given in kilometers, which is confusing because the units for these aren't indicated, so it's not apparent what they are. My understanding from that book is that these should be in Western units instead (which would be more intuitive since it would be congruous with the other HUD indications); if so, that should be changed, and ideally mentioned in the FC3 MiG-29 manual to avoid the ambiguity. Here's a screenshot to illustrate - the HUD reads 18.5 (km) and the HSI reads 10 (nm):

Just discovered that they exist and works as advertised. Can light them individually and the jettison button works. Problem is the only way to get them is to set a checkmark in the Mission Editor. But then, if used, they do not "come back" either by rearming or even after repair. Of course they should be reloaded on rearm, just like brakechutes gets "repacked" on rearm.

Hello. Take a look at the tackview track I posted. Im facing a problem now where the F14 launches the AIM54s, at a very close distance (25/30 Nm???!!!), with no launch warning . Tha is expected because I guess AI is using the TWS launch mode. BUT, I should receive a RWS warning once the AIM54 heads activates its own radar. That is how it should works, how I think it was working at least 3 weeks ago. But now The misil is being lauched to me, and I get absolutely no warning at all. In the track I point my nose directly to the misil on purpuse to be sure that my RWS is on the same plane than the misil is. I got no warning at all PD (I have cut the track so it is shorter, my pkane is the SU27 HANSO3D) Tacview-20201226-001359-DCS-TF-74-Flanker_first.zip.acmi Im flying DCS-openbeta, fully updated

Bug or not. Manual states: Nothing happens when clicking (left or right button) but gyro adjusts with mouse wheel. Manual erroneous or push-in feature missing? Tag as "Directional Gyro" (tip popup and ADJUST CONTROLS naming differs).

"OFF" position is non-existent graphically in game and in manual. Did it exist in real life? If not, delete "OFF. Disconnecting the fuel supply from external fuel tanks." line from manual, page 62. Would being able to shut off auxiliary tank separate from not selecting it on "Main Fuel Selector Valve" make sense design wise? Picked in-game-name for tagging: "External Tanks Fuel Selector Valve". ed/add 20 may 2021. Added obvious generic, extremely useful tag "drop tanks", resisted, for now, adding "external tanks" tag

Wrote it in FC3 bug thread but it seems pretty inactive. So I will repeat it here in the module subforum. MiG-29 A/G/S happens in both latest versions DCS 2.5.6.61527.3 Stable and DCS 2.5.6.61527.3 Open Beta Speed indicator (IAS) in cockpit is bugged for me, it always shows 1 instead of blank when under 1000 km/h so now speed reading is 1000 + current and if current speed exceeds 1000 needle just stops. HUD indicator is working properly.

If a landing request is made while an AI plane is taxiing to catapult 3, the catapult personnel will clear the area, waiting for the incoming jet to land. This can cause the AI attempting to take off from catapult 3 to get stuck waiting for the flight deck personnel to hook them up and shoot them, but the AI isn't smart enough to realize that it's fouling the landing area, so they just sit there waiting for something to happen, while the planes in the pattern are just burning fuel in wave-off after wave-off. This bug is easiest to catch when a large number of AI are attempting to land and take off from the boat simultaneously.

Fresh DCS install, no mods whatsoever. Made a 15 sec track. Spitfire is my absolute favorite. What I describe below is new behavior I'm quite certain. This bug is specifically about the electric starter, not the whole starting sequence. Description. 1) Spawn Spitfire on airfield as "Takeoff from ramp". I.e., engine stopped and cold. 2) Flip open start and booster covers 3) Hit starter button and engine turns over. Release starter button. Hit starter button again, propeller doesn't move. This is what my short track shows. Now the weirdness. This only happens when the first starter button press is very short (less than a second). If the first starter button press is longer, say 5 sec, it will not happen. Also, it will only happen once. Meaning, if I "Quit -> Fly again", it will not repeat. The autostart sequence (Right Win + Home) seems to always work when applied after spawn. But ... if autostart is tried after a failed manual attempt (as in the track), autostart will not move the propeller either. Modules: [I-16] [Normandy 1944 Map] [WWII Assets Pack] [Bf 109 K-4 Kurfurst] [UH-1H Huey] [F-86F Sabre] [Flaming Cliffs 3] [Spitfire LF Mk. IX] [P-51D Mustang] Free Mariana map NOT INSTALLED. Version, latest as of today. openbeta/2.7.16.28111/ Downloaded my track (above) and confirmed it runs as described. Spitfire manual start fail.trk

Hello, VR user (don't know if that has anything to do with this or not). I am seeing spontanious SD-10 launches as I click around the cockpit performing non related functions. It's happened as I select a new Wp VIA the UFC, it's happened while scaling the right MFD VIA button press (versus joystick bind) and it's happened as I sat satisfied with myself in transit to the objective doing......nothing. Am I off my rocker? My VR hand controler isnt active unless I grab it, so I don't think it's inadventant/mistaken hand controller input as I am unaware there is another way to fire SD-10's other than the mapped joystick button. Off my rocker or known issue?

The other day I found this strange bug doing the taxiing and takeoff tutorial, while I was taxiing behind the humvee I crashed with him and damaged the plane which turned off, i began to repair it and connected the external power, meanwhile when waiting for the repair i started to check some switches, and then when i activated the INT/KONT switch it made the canopy closing sound, it seemed very strange to me so to check what was happening I restarted the mission and did exactly the same thing, the bug was still there, I checked the files and removed the mods but it sems like is not a problem on my end, im gonna try to provide a video showing the problem but right now I don't have access to dcs. pd: english is not my first language im sorry if some things dont make a lot of sense.

When a DCS server fails to authenticate with the central DCS authentication servers and is displaying the modal window indicating that fact; DCS will max a single CPU core in the background. Below you can see a server which failed to login on restart and was not reset for 3 or so hours and the effect it had.

This behaviour was observed in our MP session today on both the F-16 and the F-18. The replication instructions below are for the F-18. Start with an F-18 with a TGP (I was using the Lightning). 1. Create a waypoint, hereafter referenced as WP1. 2. Take-off. Turn on Radar and TGP and wait for warm-up. 3. Enter A/G mode. Have the TGP on one MFD and the Radar on another. 4. Waypoint Designate WP1 The status as this point is that WP1 is designated and both the TGP and Ground Radar are slaved to it. 5. Select the Radar and move the Designation Cross to a new point 500 meters west of WP1. I am calling this poing AP1 (Aim Point 1). At this point the TGP will now be pointing at AP1. However the radar's Designation Cross does not move and is still pointing at WP1. These two sensors are now desynced by 500 meters. 5. Select the Radar and move the Designation Cross (Which is still on WP1) to a new point 500 meters west of WP1. I am calling this poing AP2 (Aim Point 2). AP1 and AP2 should be the same offset from WP1, given the wierd current logic, and the TGP and Radar should both be looking at this location if they were synced. However in reality At this point is: * The Radar Designation Cross has snapped back on WP1. * The TGP is now looking at a point 500 meters west of AP1/2 because when we slew the radar based on an offset of WP1 the TGP will slew the same amount but from AP1 instead of WP1. If we drop a bomb at this point it will hit WP1. So there are two bugs here. A. The Ground Radar Designation Cross snaps back to the Waypoint and targetting systems will use this as the drop point for things like bombs in CCRP. B. The TGP does not stay slaved to the Desicnation Cross. Things not tested: * What happens if you switch to the TGP, does the Radar Designation Cross start following the TGP? Properly or using the wrong base offset?

When Cold starting the new Gazelle, found that the Sight is powered in spite of the Battery, Alternator and Generator switches being Off:

Hi, I'm updating my Mirage F1 CE missions, to adapt to the latest changes of this Module, and on my testing found that the Oxygen supply does not seem to be working properly: - The Flow indicator does not blink in normal operation (it does when pressing the Oxy Gauge test button). - The Oxygen Selector, on the left side of the ejection seat, does not work. Here is a short video, highlighting this issue: This video is on the latest DCS Openbeta, MT version, but on Single Thread happens exactly the same. Have not tested the F1EE version to see if it behaves the same, will do it later. Best regards, Eduardo

Quoting old thread: Ground Power is for starter, what I always assumed, makes perfect sense. But ... I've noticed many times, engine refuse to turn over, battery seems low, after repairs. Connecting Ground Power doesn't help. So I did a simple experiment with P-51 and with Spitfire (Summer +20'C). 1) Spawn "Takeoff from runway" (This assured engine temp/oil pressure was up, no damaging engine by turning over cold) 2) Shut off magnetos (engine stops) 3) Spun the starter until battery drained (prop stopped moving) 4) Attached Ground Power and attempted to start. P-51 started (as it should). Spitfire prop didn't turn over at all (voltmeter showed 5V (down from initial 14/15V), whatever that means *1) If Ground Power is for starting, which again makes perfect sense, then this is a simple well defined bug. Ground Power should power the starter in an undamaged aeroplane. *1) Would ground power really bypass the voltmeter? If it does, be that as it may, the important point here is that ground power doesn't power the starter.

1) These Controls are interchanged. How they list in Controls tab: RShift + B controls "Emergency By-Pass" and RCtrl + B controls "Deluter" They're inverted. ~ 2) Oxygen is not replenished by refuel/rearming. The only way to replenish oxygen is by doing a repair. 3) There is no way to shut off oxygen completely (to save it).

My force feedback joystick works totally fine when I play using my monitor, but I get no force feedback at all in VR. I've tried multiple aircraft - no difference. I found a Reddit thread where others were having the same problem (https://www.reddit.com/r/hoggit/comments/a6amfx/no_force_feedback_while_in_vr_vive/), and someone found a solution for the Steam version of DCS: make sure DCS and SteamVR are closed; then launch SteamVR, and then DCS (in that order). This solution is a little annoying, but works perfectly for me with the Steam version. However, I recently switched to the standalone DCS version (so that I'll be able to take advantage of ED Miles), and I haven't found any way to get force feedback working while in VR with the standalone version (I don't think I can launch standalone DCS from SteamVR?). If anyone knows a workaround, I'm all ears! But would be good to address this bug so force feedback works in VR regardless. I'm using a Microsoft SideWinder Force Feedback 2 joystick and a Samsung Odyssey+. DxDiag.txt dcs.log.zip

Engine breaks immediately after repair because of bounce. This happens a lot. Every 3rd repair maybe (just a guess). I finally noticed more precisely what happens. 1) Start Repair. Spitfire is raised straight up. 2) Fuselage gets angled tail down, nose upwards 3) When Spitfire is lowered after repair, tail wheel goes underground 4) Because tail wheel is underground tail shoots up like a rocket. 5) Propeller hits ground and breaks, engine also broken. If no 2), the fuselage re-angling tail down didn't happen and Spitfire was just lowered straight down, the bounce wouldn't happen and propeller wouldn't break. Video recorded of offline track. Easy to recreate I think. Happened twice in a row, first attempts. Spawn CW Batumi RWY, stand on brakes, powerup and let it nose over. Repair.

What is the logic that DCS uses to determine the active runway? Is it generic or do individual airfields have different logic? We were flying on Persian Gulf with the wind 010 and 2m/s which, based on wind, should mean Runwas 31L/R are active. This is what the humans ATCs were using, it is what DATIS and OverlordBot were reporting. However the in-game airfield ILS was only active on runways 13. Is this a bug or does DCS use more than just wind heading to determine the active. Man it sure would be nice to have an `Airfield.getActiveRunways` or `Airfield.getActiveRunwayHeading` API

Key command to open fuel valve (Ralt + F) closes it (pulled out) and key command to close (Rwin + F) opens it (pushed in). Couldn't get the engine started until I saw on a video that the lever is pushed in when opened, not pulled out (which makes more sense practically, out of the way for the pilot). The only bug here is the wording in the ADJUST CONTROLS window. Switch Open & Close.

Link this inside a top sticky in every bug report forum: https://forums.eagle.ru/showthread.php?t=147710 Make it easily available. Even though I had bookmarked it, I forgot where to find it or even having bookmarked it.

A little amusing bug. On repair Spitfire gets moved to tail wheel outside deck position. Proposed cause: (Nose wheeled) carrier jets gets pushed back to main wheels near deck edge. Very short track: -Air start -Belly land -Repair Track 100% default installation, no mods (main folder repaired, forced new Saved_Games folder). ed/add. Though I can (once at least) start engine, pull fully onto deck and even take off, plane is damaged. It takes damage after every repair when rear fuselage hits deck.