vctpil

Thanks to you to change it to REPORTED.

To be sure about the problem, I call the JTAC once after take-off, restart the mission and hold over ADDER before calling the JTAC. The result is the same, the JTAC always give me the point FORD and a bearing/distance at 40nm from targets position.

Thanks for your screeshoots. Is there a way to modify the viewpoint? Is it still in WIP?

Just tried the mission several time. The offset function cannot be used with the informations given by the JTAC. The offset waypoint is far from targets (+/-40nm) because referenced to FORD, that does not exist. Any help appreciated. Thanks.

Hi, I have just created a very simple mission for purpose (see attachements). The AV-8B with a single waypoint, 13nm from targets and a JTAC. I also have an initial point ADDER. At first contact with the JTAC, the pilot report 28nm south of IP FORD. This point does not exist as you can see in the mission. The JTAC report the correct ADDER point and distance/bearing to the target. A bug ? Thanks, Vincent Test AG2.miz

Hi, Sorry, I don't know how to make a video. But here's two screenshots with my head very close to my computer screen and look at the symbology size displayed. What is happening to the Harrier is similar to all other aircrafts, except the F/A-18. So, is the HUD technology of the F/A-18 different ? Thanks.

Hi, In my pilot knowledge, parallax is when your reading an indication on an instrument on the side, not in front. So, the information may not be correct. But I probably make a terrible mistake with this post, the HUD is effectively focused to infinite. I think that the size of the symbols are too wide. Plus, I cannot get very close to the HUD, which is possible with the Harrier. Any idea how to solve that ? Thanks anyway, Vincent

Hi, Is someone can confirm that is still WIP, please ? Thank you, Vincent

Nobody has the problem ?

Hi, Sorry, I didn't find the search function on this new forum to look for the same problem. I only use the trackIR and when I am approaching the HUD windows, the symbology of the A-10CII and AV-8B maintain the same size (infinite view), but the symbology of the F/A-18C is following the forward-rearward head movement (see attached tracks). That sound not correct to me, so, is it still in work in progress ? Thanks, Vincent AV-8B HUD zoom.trk A-10 HUD zoom.trk FA-18 HUD zoom.trk

Thank you.

Hi, Is it possible to enter the UTM coordinates to create a waypoint offset ? I can use range, bearing and elevation, but is UTM working ? Thanks, Vincent

Unplugging and re-plugging has no effect. I rename the DCS folder according to another forum and it works. The only things you have to do is to copy and paste missions, mod, etc and setup the flight controls again. Now that's working perfectly. Thanks anyway for your suggestions.

I have just deleted joystick and key file to erase all binding, but the problem is still the same. What the **** is happening ? I have never had this problem before.

Hi, With the OB, the throttle n°2 aft function does not work in the aircraft, but it is working in the control options. See the screenshot, the aft function is in a different color. Only one function is bid on this button. How can I solve the problem ? A repair does not change anything. Thanks. Vincent

Hi, I don't know what is the problem exactly with the the selection of COM1 with the HOTAS Warthog throttle. The coolie hat n°2 (the one on the side) has 4 positions : Up : 3 Down : 5 Forward : 4 Aft : 6 I obviously use the realistic COMs and I am able to map any function to any position of the coolie hat, either COM1 or COM2. The button is also functionning correctly because if I push the button on the control adjustment menu, the function is displayed. But the COM1 does not comes with the forward coolie hat n°2 on the throttle. Here's some tests and tracks. Test 1 Up_Dwn ok.trk : BTN 3 up display the COM1 menu and BTN 5 down display the COM2 menu. Test 2 Fwd_Aft not ok.trk : BTN 4 DOES NOT display the COM1 menu and BTN 6 display the COM2 menu. Tested with the F/A-18C and the AV-8B Harrier with the latest stable version. Anyone have an idea to solve the problem ? Thanks, Vincent Test 1 Up_Dwn ok.trk Test 2 Fwd_Aft not ok.trk

Hi, Same problem here with the both version. Vincent

Hi, Find how to have the problem again. SEQ does not work on "Takeoff from parking hot" and doing as follow : MAPM -> MAP -> OL2 -> SEQ. The problem does not appear in flight, so I wonder if SEQ is also supposed to displayed on ground. See the track attached. Thanks, Vincent AV8B SEQ.trk

Hi, I tried several times, but I am not able to reproduce it. In the meantime, I will open a new threat about the position of SEQ waypoint. Thanks anyway, Vincent Edit : reported already : https://forums.eagle.ru/showthread.php?t=285556&highlight=waypoint

I can't, the file is too big! Screenshot maybe ? I can download the file, don't know what is wrong.

I wanted to say, now the AV-8B in DCS is taking another speed for reference, which is not correct. That could explain why the speed carret is not showing the correct speed. If you follow the ground speed as indicated and not the carret, that works.

https://forums.eagle.ru/showthread.php?p=4509987#post4509987

I found something after another test. If you follow the ground speed (lower left on the HUD, labelled S ---), you can arrive on the predetermined time over the waypoint (see the both screenshots). The predetermined time was 18.49.00 and the given speed was 364 knots ground speed, so that works perfectly. From this test, I may suppose that the speed carret does not indicate the correct speed, according that the ground speed is the correct speed to follow. Vincent

Just tried this morning to understand the use of TOT and TTT. I have the same issue with TOT.

Hi, just a quick question : is the app working for the OpenBeta ? It is working for all module in the stable version, but not in the OB. Thanks, Vincent Disregards, I re-install the srcipt, do the update and it is working again.