Avalanche110

I was trying to add client slots for mirage f1 to a mission. I noticed irregular behaviour that only effects the mirage F1. The mission editor condition "UNIT OUTSIDE ZONE" works with all other modules, but not the Mirage. Also noticed problems when using MOOSE to script a moving zone around the client. It works for all modules except the Mirage. I made a test mission that illustrates the issue. two units parked on the ramp, both inside a trigger zone. A message will appear if either unit is outside the trigger zone. Selecting the F-16C slot, No message is displayed. Selecting the Mirage F1, a message is displayed on mission start. TEST MISSION.miz

That worked. looking forward to trying this out. Thanks Rudel_chw

Does anyone have a working link to their discord server? All the links I have found come back invalid.

In OB 2.7.11 some of the western side of the map has been removed. I have no issue with this, except that any late activated groups that were located in the region that has been removed are no longer accessible. The Units are still there, just cant physically scroll to there location in the ME. not an issue if its just a handful, But I have over 2000 late activated groups located in a region of the map that I can no longer access.

Tested again in 2.7.11 Ground vehicles still unable to follow a route smoothly when using "go to waypoint" task. No complaints, just thought I'd bring it up again as its been a while since I reported it.

@JeffreyC @Scotch75 The link to the modified file isn't working for me anymore. I will post a copy the modified LUA file. Replace the me_logbook.lua file in your C:/EagleDynamics/DCS World/MissionEditor/modules Directory me_logbook.lua

Hello @Scotch75 I have fixed the F/A-18 Follow me vehicle blocking the runway in mission 1. I checked the rest of the missions, it seems it was only the first mission that was effected. Thanks for letting me know. The updated file can be downloaded here. https://www.digitalcombatsimulator.com/en/files/3313504/

Hello Scotch75 Can I ask what aircraft you were flying?

Just went through the patch notes for 2.7.9.17830 It mentions there is a new key bind for "Minigun Fire", however I cannot find this in the list of key bindings.

I am unable to fire the minigun in the gazelle. I have armed the master arm switch. Taken the gunners seat and toggled the "fire gun/rockets" key bind however nothing happens. is anyone else experiencing this? Also, I believe it was once to be possible to move the minigun with the mouse in VR. having the gun locked to your head movement is undesirable. Thanks.

Hello JeffreyC. I have updated the Campaign for compatibility with 2.7.9 I have updated the MOOSE file, changed the airbase names and modified all of the "Follow Me" vehicles. The vehicles were disabling the runway for the instructor. I have also made a number of small changes to the clouds and changed the Tanker frequencies. Thanks again, It makes me very happy to know people are still enjoying the campaign. Latest version can be downloaded from here: https://www.digitalcombatsimulator.com/en/files/3313504/

I noticed that AI F-14A/B cannot use Aim-54 recently. I have tried many different options to get them to use Phoenix but nothing seems to work. They will only engage with Aim-7 or Aim-9. I have not seen this reported anywhere, I am interested to know if others are seeing the same thing. Thanks, F-14_BUG.trk f-14 test.miz

This would be a Great addition. Thanks for the update Polychop.

Thanks Flappie!

If a ground unit enters and then exits an active runway, The runway is disabled for about 5 minutes after the ground unit has exited the runway. Not sure if this is a Bug or a feature but this started occurring in the latest OB 2.7.7 RUNWAY TEST.miz RUNWAY DISABLED.trk

@Flappie i noticed a distinct change in the ground units path tracing in the latest OB 2.7.7 If you try the test mission I attached, you’ll see the ground unit path tracing is not smooth between waypoints. It jerks around and appears to defy physics at times. if you run the same test mission on stable, you’ll find it completes the course normally. The waypoints are issued Using the task “go to waypoint 12, go to waypoint 13” etc. when the units are following a normal set of waypoints ie. 1-2-3-4 path tracing is normal.

In the latest OB update. Ground units are unable to complete a simple course when the waypoints are defined using the "go to waypoint" option in mission editor. This is not an issue in 2.5.6 Stable. PATH TRACING TEST.miz

@Flappie as I mentioned earlier, this is becoming less and less frequent in the last couple of updates. If I ran the mission 20 times, it might happen once. Several updates ago, it was a lot easier to reproduce. There is still some weirdness in the current build, just enough to irritate you but not enough to nail down what causes it. The best way I can describe it is on occasion, random units will "Break". Physics stops applying to them, their triggers and scripts do not execute normally and this can occur to both air and ground units. Also doesn't matter if the units were scripted or part of the ME. the mission I used is a monster, and not Ideal for reproducing bugs. Should you wish to try, PM me and I'll send you a dropbox link along with instructions on how to make the mission work. Thankyou and all the best!

Hey @Flappie I tried renaming the DCS saved game directory, and multiple slow repairs. Neither was successful. reinstalled graphics driver, Pitool, and steamVR and that seems to have solved it. Thanks for your help

DCS crashes when loading main menu in VR. 2D loads and works normally. Crash Log attached. Was working fine in VR on current OB now all of a sudden it crashes. Thing I have done: Uninstalled shader mod. DCS cleanup and repair. Deleted App data. Any help is greatly appreciated dcs.log

This concern has become far less frequent over the past few updates. I was having trouble reproducing it. However I managed to get it to re-occur. I do not have a trk file for it, however I do have the tacview. At the very least it will illustrate the issue myself and others are experiencing. Unit ADVERSARY#001-02 is scripted to Follow another group, however shortly after take-off, the unit "Breaks" Physics no longer apply to the unit and it fly's off uncontrolled. The Sim still recognises it as a unit, and a patriot battery shoots it down. In game, the unit is hit, and is visibly damaged however it continues to fly on the same course and speed. in the tacview the unit is destroyed. This was in single player on the Current OB. dcs bug.acmi

@JeffreyC Just confirming the instructor does engage in the 2v2 and 4v2 ACM missions. The delay does seem excessively long though, I might shorten it a little. Thanks for the feedback. If you have another concerns, please let me know

Yes I have experienced this many times also. it only seems to happen to units that are Scripted and occurs on dedicated server and single player. I have seen units that were supposed to orbit over Kutaisi end up in Syria when reviewing the Tacview recording. The 3d models break when the fault occurs and the units appear locked in a 2 dimensional frame of reference. ( Hard to describe. I will try and get some screenshots) I will try and get more information so we can substantiate a proper bug report. But for now, I'm just glad that I'm not the only one experiencing this.

Thanks @JeffreyC In the ACM missions, there is a delay between the instructor switching from following you and engaging the adversary's. This is to prevent him from shooting the adversary's before the merge. I believe the delay is 2 minutes from calling "Ready". I will test the Viper in the 4v2 mission to confirm it does work properly. Might take a day or 2. Thank you and take care

Hi JefefreyC. Last time I tried the 2v2 and 4v2 BFM missions the instructor engaged as intended. Can I ask what aircraft you tried and and which mission you were using. I.e BFM, ACM, BVR Thanks