massdriver

Great, thanks a lot for your suggestions! I will keep testing this.

Motivated by your comment, I just re-tried this (with a plane, not a helicopter) and can confirm it is definitely not working for me. Attached is the .miz file with my test mission. The AI plane takes off from Batumi and simply continues to follow along the original waypoints, even though the above script is set to run when it crosses waypoint 1. There is another trigger in that script to confirm the script is actually run: trigger.action.outText("script runs now", 10) Any ideas? Thanks in advance. set_command_test.miz

Hi, I was wondering if someone can help me shed light on how to use setCommand() and setTask() / pushTask() properly. I have spent may hours on this but cannot make it work. Specifically, I am trying to use the SwitchWaypoint/GoToWaypoint commands. All of the following examples have no effect on the unit/group in question: 1) via group local g = Group.getByName("Aerial-1") local c = g:getController() local switchWaypointCommand = { ["id"] = 'SwitchWaypoint', ["params"] = { ["fromWaypointIndex"] = 2, ["goToWaypointIndex"] = 5, } } -- the following has no effect c:setCommand(switchWaypointCommand) 2) via unit local u = Unit.getByName("Aerial-1-1") local c = u:getController() local switchWaypointCommand = { ["id"] = 'SwitchWaypoint', ["params"] = { ["fromWaypointIndex"] = 2, ["goToWaypointIndex"] = 5, } } -- the following has no effect c:setCommand(switchWaypointCommand) 3) using a WrappedAction task local g = Group.getByName("Aerial-1") local c = g:getController() local wrappedActionTask = { ["id"] = "WrappedAction", ["params"] = { ["action"] = { ["id"] = "SwitchWaypoint", ["params"] = { ["goToWaypointIndex"] = 5, ["fromWaypointIndex"] = 2, } } } -- neither of the two following work or do anything c:pushTask(wrappedActionTask) c:setTask(wrappedActionTask) All of the above equivalently do not have any effect when GoToWaypoint is used for ground units. ----------------------------- As a side note, the following similar, and possibly related issue puzzles me: a) consider I create a series of LandingReFuAr waypoints for a plane unit in the mission editor b) if I run the mission at this stage, everything runs fine, i.e. the plane flies from airport to airport and lands, refuels, and rearms c) however, if I - via triggered script - then deepcopy the plane's mission task (as defined from within the mission editor) and reassign it using setTask(), the plane will keep flying along the route of waypoints, but not land anymore. I have checked the original mission (extracted from the .miz file) against the one that I set and confirmed that they are 100% identical Can someone help me better understand the inner workings of setTask() and setCommand()? Thanks.

Hmmm, I understand this would work but this is not CCRP, just "pseudo-CCRP" by using CCIP to emulate a CCRP-like behavior. I acknowledge there are workarounds but I was rather wondering if either something is wrong with the CCRP or if I am not doing something properly. Thanks for the suggestion though.

Thx to both of you. @Sinclair_76 That's what I thought as well, and I think in the Track file I indeed had the auto-step enabled. But then I tried this again with it set to manual and exactly the same thing happened, and it ruled out the auto-step as a possible cause. @b0bl00i What's the combined CCIP/CCRP mode? Or are you referring to the CCRP mode?

@Aurora juutilainenHi! Thanks for your response. Yes about the MAGV, I know this is technically incorrect, but I do this so that I can use the headings on the F10 map as if they were magnetic and do not have to recalculate them all the time. It does not appear as if the MAGV setting would cause the CCRP to misbehave though. With regards to the low and steep pass, I was thinking a similar thing and tried the same thing again after this track, with a less steep pass which was also a bit higher, but the result was the same.

Hi guys, Can somebody help me explain what is going on with the CCRP in the track file provided? The CCRP line moved away just before I reached the target and I could not release the bombs. Thanks in advance for shedding some light on this! CCRP Problem.trk

It was an on-the-fly mission that I have already discarded by now. After watching the video @Falconeer posted above, I feel motivated to try again and assume that what I experienced was due to my lack of experience with the radar. Should this remain a problem, I'll create another test mission and post if here. I appreciate your offer though. @SFJackBauer Thanks, good to know.

@Falconeer Thanks a lot for the video link. I watched it and will re-try the same scenario with my newly gained knowledge.

Thank you again for this - I indeed used the wrong radio for the JTACs. So, #5 appears to be solved. However, sadly the tower at Kutaisi (134.00 on VHF) is still not responding to me on the ground when I request taxiing.

@SFJackBauer Thanks for your reponse. This one: https://www.digitalcombatsimulator.com/en/downloads/documentation/viper_flight_manual_en/ I am not sure, how can I tell? I am using the Steam version FYI. I can see your point. However, the aim was to not yet create single tests for each of the 10 items, as I am trying to find which of the described issues are bugs and which are features that I may not understand properly. There is a limit to the time I can spend in DCS, as well, for real-world reasons. If you watch the track, even if it is not perfect, you will still see something very weird going on with the GPS which should be curious in any case. The problem is that some (perceived) bugs can be hard to reproduce as they appear at seemingly random times, just as with the GPS in track 1 that I uploaded. As I work my way forward and with more information collected become able to hone in more closely on any particular oddity, I will provide a single test that isolates the issue. @Falconeer Interesting, thanks for the feedback! Indeed that's what I meant. Thanks, good to know it's a known issue. @WHOGX5 Interesting, I will look into this - thx! @5ephir0th I tried this with both Mav D and H. The radar issue remains curious. I am wondering if the following is normal. I just placed 8 (unarmed) MiG-29's on a map in a furball, about 40 nm away from me. My radar only sporadically picks them up while I fly directly towards them. Sometimes, not always, it shows one or two of them at the same time, but then they immediately disappear again and so obtaining a lock is difficult. This is in RWS, but I also tested TWS fwiw. The behavior does not change when I come closer to 20 or 10nm. Is this expected and realistic behavior? Thanks.

Hi, I've just uploaded the next track file. It shows two of the aforementioned things: - None of my four JTACs responds (#5 above) - setting a steering point to valid GPS coordinates flies me there, but the GPS information shown on the HUD is completely off (extreme case of #1 above) Thanks for your feedback in advance! Bug_or_Feature_Track_2.trk

...and: 10) When "starting from parking hot", something is very wrong with the GPS. Note how in the attached track file, I look at the coordinates of ramp 21 on Kusaiti. In the top left corner it reads that they are N 42 10 14 / E 42 28 08, which I then enter as steerpoint 1. Flying to that steerpoint then leads me somewhere else, somewhere significantly south of the airport. My intent was to demonstrate the CCRP "bombs drop to the left" issue by aiming at the center of ramp 21, but then this GPS issue popped up. I will try to create another track file for the CCRP issue. --> Update: I realized that I made a slight mistake by not properly converting the GPS seconds to decimal minutes, but nonetheless this should not have caused the steerpoint to be that far off (I tested this afterwards with the correct decimal coordinates and the coordinates I entered, "N 42 10.140' E 42 28.080'" would still be relatively close to ramp 21, and not as far off as the steerpoint that can be seen in the track file).

Hi guys, Thanks so much for your responses. Let me address the things you mentioned: @Florence201 Interesting, could you let me know what that is supposed to do? I have tried switching it on and off, but did not notice any difference when using CCRP (I have attached a .trk file to this post where I am trying this as well, more about the track below.) Please note that in the attached track file, I was not able to reproduce the "bombs always drop to the left of the steerpoint" behavior, which happens for me at times that appear random. All on Caucasus. #4 can be seen in my track file below. The tower only ever responds when I start taxiing or take off by myself (when it kind of retroactively clears me for both). Sure, I will create one a bit later today and provide it here. Yes, the entire Maverick AUTO vs MAN including ground boresighting is done in the track file below. I will aim to provide a track file for this later today as well. It appears that it is not. I still need to try whether it does so in CCIP mode. If so, I am wondering why it would not work in CCRP but only in CCIP... @Dawgboy It does fire and work, but I need to hold it all the time, which can be a bit impractical while maneuvering the airline over the drop zone. I was wondering about the Second Detent firing of the laser, which is supposed to automatically fire it for 30 seconds (at least in CCIP mode, as per the manual on page 178). Bug_or_Feature_Track_1.trk Oh, and I forgot to mention: 9) The HUDs always seems to need a brightness adjustment anew when each page is visited for the first time. This can also be seen on the attached track. Thanks for your help.

Hi guys, and many thanks for your help in advance. I have noticed quite a few things that do not work as expected with the F-16C or in general in DCS: World. As I am not sure if any or all of these are: (a) unreported bugs, or (b) bugs that are already known and being worked on, or (c) user error on my part, I was wondering if you could help me shed some light on this to classify the below into (a), (b), or (c). Here is the list: 1) the CCRP is often off to the left or right, i.e. flying straight towards a steerpoint and seeing it in the HUD, the vertical CCRP line will be drawn to the left or right of it, and aligning it with the flight path marker then consequently makes you not fly directly over the steerpoint anymore 2) possibly related to #1, dropping bombs with CCRP, and aligning the flight path marker perfectly with the vertical CCRP line, always makes them hit "to the left" of the target, whereas left is meant as in relative to the direction of your flight path 3) when playing a coop multiplayer game with two players with the same coalition, the ILS system of an airport sometimes does not work for player 1 while it works for player 2, for the same airport, i.e. it just seems to be off for them 4) similar to #3, again in a two player coop multiplayer match, one player is able to contact and talk to the tower, but the other isn't (frequencies checked to be equal etc.) 5) JTAC's sometimes do not respond to any request via radio, even though they are confirmed alive, close-by, and set to the right frequency (we have tested this with four different JTACs on the same map, each with their own frequency, different call-sign etc., but none responded) 6) Maverick AUTO hand-off does not work, i.e. one always has to make the Maverick SOI after the hand-off and also lock in the target there or it won't have a lock, and won't fire (it remains stuck in REL when firing, with a flashing flight path marker, as there is no lock) - it does not make a difference whether AUTO or MAN is set on the TGP 7) the F-16 radar seems to be enormously ineffective and almost never spots anything unless it's right in front of the plane and in close range (<5nm) - which we have tested quite a bit. For some reason, this is not an issue in the training missions 8 ) TGP laser fire first detent, which is supposed to fire the laser for 30 seconds, as per manual, does nothing / does not work Thank you very much for your help, I am looking forward to your responses. Should you agree that something in this list sounds odd and is not already known as a bug, I will be happy to provide track files and more info on it.