Boagord

Hello, In MP there is some bad synch between Pilot and RIO : The pilot can see the inputs of the RIO (on TID) whe the RIO is typing but when the RIO press enter: ALT, RNG and BRG remains at 000 from the pilot's point of view. From the RIO point of view there is nothing wrong. When the pilot designates the IP visually on the HUD, as there is no offset from his point of view, the target is merged with the IP. I am using this : http://www.heatblur.se/F-14Manual/weapons.html#computer-initial-point I've tried several times, as a pilot and as a RIO and I am able to use the "Computer Initial Point" effectively in SP with no problem.

Thanks for the answers, I cannot add [No Bug] to the thread's Tittle. What shall I do ?

Yes, I agree it is a game. And more over a not so stable game. If your DCS or a wingman DCS crash you have to coldstart again. Which is a waste of time. Envoyé de mon SM-G930F en utilisant Tapatalk

I tried the first three missions with some friends, Pilot and Rio First one: A nice one, but a bit rought in the air, a lot of aircrafts. Second : Very well, nothing to say, a real pleasure! third : Nice but there is no briefing, and the voice doesn't correspond to the text, we had to relisten the .ogg to understand the push time @ 1614

Hello there, If you are goint supersonic (ie M1.2) you can go very high (too high). I was able to reach angel 90 the first time ( ran out of fuel) and 100 the second time ( stall). Tacview : https://cdn.discordapp.com/attachments/527941690540032010/576772963257286669/Tacview-20190511-153512-DCS.zip.acmi

So it's not a bug but a feature! If I understand, Case 1 above the sea should be done with the pneumatic altimer. Envoyé de mon SM-G930F en utilisant Tapatalk

In my cockpit, when I am above the sea, the radar altimeter point an altitude under the "F2" altitude. Is it normal? With a good QFE set, my pneumatic altimeter works well.

Hello, I tried to do something like your EWRS script in moose environment but without succes. I would like something like EWRS but including borders intruders. With tasks, moose can do something close but there is a lot of menue and submenue in the f10 menue. I would like to do something as playerfriendly as EWRS. I had this Idea for cold war scenarii, if someone is better than me with the lua code :)

for me it works well. Here is a video I found :

Hello, I tried the SEAD EVASION test mission but it doesn't work. What should I do? Is it because of the new version of DCS world? https://github.com/FlightControl-Master/MOOSE_MISSIONS/tree/master/SEV%20-%20SEAD%20Evasion/SEV-001%20-%20SEAD%20Evasion

Hello, First thanks for your awsome program. It is now a must have! I wonder if It should be possible to record communication with the SRS serveur. It could be nice to listening radiocom later, analyse data with tacview or making great videos. Maybe a file per radio frequency. I don't know if my request is reasonable or not. Thanks! Envoyé de mon SM-G930F en utilisant Tapatalk

Je m’intéresse depuis quelques temps aux scripts, et le fait que ça soit en Français est un plus. Je vais lire la doc de ce pas! :)

Hello. Je vais voir ce que ça donne dans mon petit groupe Envoyé de mon SM-G930F en utilisant Tapatalk

Do you know this? http://jboecker.github.io/dcs-mission-planner/planner_client.html

So, the mirage2000 INS is totally wrong. There is different value with the distance on the F10 map and the INS. The difference between calculated distance ( like in real world) and F10 distance seems to be: F10 Distance = calculated distance / COS(grid Deviation)

Sorry, I misspoke, and I agree with you. I edit my post!

I am studying the True vs Grid North( wip) https://forums.eagle.ru/showthread.php?t=191995

Hello, I am learning the C++ and as a practical work I am making a tool for DCS. It has several function as QNH / QFE conversion ( Viggen bombing), BullsEye to Braa conversion and the problem is with the last one : I would like to calculate the bearing/distance between two point ( latitude / longitude). I managed to calculate the exact bearing between two point with the grid correction: The "master" meridian is the 33°E, it is the only one pointing grid North. On the Caucasus map, If you go east or west of the 33°E meridian you will have some deviation with this grid north. To calculate the deviation at the A point the formula is : A longitude - 33 * sin ( A lattitude) To calculate the bearing between two point, you need to calculate the departure and arrival bearing. To do so, have to calculate the bearing from A to B, and the bearing from B to A +180°. After that, calculate the average value and you will obtain the bearing calculated by DCS. To calculate the distance between the two points I use this formula : A-B = arc cos (sin ϕA sin ϕB + cos ϕA cos ϕB cos dλ) * 6 371 But I have a deviation between the result and the distance calculated by the INS of the M-2000 and the F10Map: The 2000's INS is more readable than the f10 Map so I used it and tested some value: Latidude (fix): W00 N 40:00.00 W01 N 40:09.99 <-- 09.99 and not 10.00 because of a bug changing automatically 10.00 to 09.99. longitude : On both WP ( W00 and W01) I use the same longitude value to have a true south to north vector. Longitude Distance (Nm) E 30:00.00 9.74 E 33:00.00 9.82 E 34:00.00 9.85 E 42:00.00 9.88 E 45:00.00 9.94 E 50:00.00 10.07 E 78:00.00 11.68 E 80:00.00 11.84 E 90:00.00 12.86 I hope you understand something at what I said. I have trouble expressing myself in English.

Thanks! I will try to go further during the week! :)

Caucasus 1.5.7 It's very very simple, I don't know if i understand the philosophy. I would like to creat two cap flight at first.

I tried the demo mission and there is no cap or intercept on the red side. I read the documentation, I am not a fluent english reader, but if I understood it should work but it does'nt work. https://github.com/FlightControl-Master/MOOSE_MISSIONS/tree/release-2-2-pre/AID%20-%20AI%20Dispatching/AID-200%20-%20AI_A2A%20-%20GCICAP%20Demonstration I didn't touch anything. Next I tried to build my own with this tutorial : http://flightcontrol-master.github.io/MOOSE/Documentation/AI_A2A_Dispatcher.html#AI_A2A_GCICAP I made this very simple mission to learn but I don't understand why it doesn't work. I think I miss a lot of things. https://drive.google.com/open?id=0B4saJUWmL8SvMTRTUWw0bHBhMXc

Hello FlightControl I would like to try your tools for mission editing. I am not use to .lua files but I would like to give it a try. When I launch the AI_A2A - GCICAP Demonstration mission, there is no interception. What should I do? I loaded the last moose.lua today ( 2.2.0 pre) Thanks!

This night we were testing the last update version : 1.5.6.3930.271 The mission was very simple, two mirage in a head to head duel, but from time to time, my opponent (Droopy) was invisible. Invisible on my serval, radar, and visually. My opponent was able to see me visually and on the radar. Here is a link to a folder containing the mission, the track and tacview of my opponent and I. https://drive.google.com/open?id=0Bxcg169VfKlAYU9OeG9GQkRpams On the Droopy's tacview, we can see a bug : His last plane do not disappear when he respawn in another one.

Prep is the editing mode. You can select all the waypoint, the waypoint 00 is your current position. You can have precise data about this waypoint. On Dest is the waypoint send to hud and hsi by the PCN. If you select the waypoint 7 on Dest and you want some precise data, you should select the waypoint 7 on prep. If you double clic on prep, it Will select the waypoint selected with Dest. So you can have the waypoint 7 on Dest AND prep. (And vice-versa). Envoyé de mon XT1072 en utilisant Tapatalk

The PCN display the prep waypoint, the dest waypoint is diplayed on hsi (nav mode) and hud. Envoyé de mon XT1072 en utilisant Tapatalk