funkyfranky

Thanks Snacko, that's good to know. I don't have problems but was wandering about the best procedure as I am about to retrain everything after a fresh windows install. The question is basically if the trained profile depends on the used mic or mostly on the speakers voice. I would guess that with every mic the recognition is a bit different. But if you have no probs by training once and use different mics, it sounds like the effect of the mic is negligible. Thanks again :) I'll check the location. I downloaded the "Speech Recognition Profile Manager Tool" here. It looks like it's working okay in Win10 but I did not test it extensively yet.

MS Recognition Profiles Hi guys, I got two mics in use. One for 2D flight and one for VR (the rift mic obviously). So M$ supports different "Recognition Profiles" which you can train individually. Question 1: Is it necessary to have and train a profile for each device/mic? I would guess so but am not sure. Question 2: How does this work when training the VAICOM keywords? Does this also have to be done for each profile/mic? Question 3: Is the training data stored somewhere? Ideally so that it can be saved and reloaded after a windows install? Or is this already even stored in the profiles? Thanks!

Seit dem man per Skript die Koordinaten der Markpunkte bzw. deren Text der F10 Karte auslesen, kann, kann man schon sehr interessante SP Aufklärungsmissionen fliegen. Die Mission kann dann etwas so aussehen, dass man den Feind zufällig irgendwo spawnt und mit z.B. der Viggen auf die Suche geht (ohne, dass man selbst wüsste, wo man genau suchen muss). Sobald man den Feind aufgeklärt hat, kreiert man an der Koordinate einen Markpunkt und schreibt ins Textfeld "Artillerie feuer". Und schwups eröffnet Deine Ari das feuer und neutralisiert den Feind. Ähnliches kann man mit einem AI Strike machen.

Danke für den Hinweis :thumbup: Ich hab es gestern mal kurz angetestet, konnte in einer einfachen Freeflightmission aber keine großen Verbesserungen erkennen.

Hi guys, and sorry for the late reply but I have not been lazy ;) The code has been enhanced with new features and added as an own Moose class. The scripting part on your side is, however, significantly reduced and you have convenient user API function available for customization. Please revisit the first post for further info, new code and and an example mission featuring two rescue helos at different carriers :)

Danke für den Bericht @ram! Gibt mir schon mal ein gutes Bild was mich erwartet. Nutzt Du ab jetzt die Pimax für's fliegen oder gehst Du doch eher zur Rift zurück?

I wonder whether trains can be spawned dynamically by now? When I tried it, it said something like replacing by "Leopard-2" or so.

Hi Vincent! Sorry, my reply was aimed at Seance12, who had "Commute" with a lower case "c". Your script with the capital "C" is correct. You actually have another issue. Believe it or not, a C-130 is too big for Creech AFB. It has nothing to do with RAT, it is a DCS setting. You can try to place a C-130 to takeoff from ramp at Creech AFB and you will see that it snaps to another airbase.

You are welcome for the tracks. You still need more?

fa18:[b][color="Red"]c[/color][/b]ommute() Commute needs to start with a capital "C". You got it right for the C-130 but lower case for the F-18 and the Huey. Lua is case sensitive. So this crashes the script.

:gun_sniper: :D

Steht als "known issue" in den Patch notes. Passiert wohl wenn die CE II libs geladen werden.

:thumbup: And the icing on the cake would now be if deployment of the expendables would alternate between chaff and flare every second in R+F quick release as the manual suggests. Just because we are at it, the Grime Reapers uploaded a vid about CM yesterday. I did not watch the whole thing. But at 13:00 you can see the C+F coming out at the same time.

Just tested quickly and it drops chaff and flare in R+F for me. But both at the same time. Manual p. 124 about quick release states: In R it only drops chaff and in F only flares.

AFAIK, flares are only dropped in quick mode. The chaff/flare selector (CFS) switch has mainly impact in quick mode as well: R=Chaff only, R+F=Chaff+Flare, F=Flares only. Here is a table of how I read the manual (some time ago): https://github.com/funkyfranky/MyKneeboards/blob/master/AJS37/AJS37-Warfare-190.png If not using the quick mode, chaff/flare selector should probably be in R or R+F. No sure if it is supposed to work in F as well. Does it? Are chaff not dispensed when you use the Quick Release Button (QRB) and have R or R+F selected? (sorry, cant test right now)

+1

@JAR or anyone who knows: I was wandering about the dimensions of the black and red boxes shown in the mod. My findings are in the picture. Black numbers refer to glideslope error (deviation from 3.5 degrees) and blue to lineup error. Red box: upper glidesope is 1.5 degrees and lower -0.9 deviation from 3.5 optimum. Lineup error is +-3 degrees? Black box: upper glidesope is 0.8 degrees and lower -0.6 deviation from 3.5 optimum. Lineup error is +-1 degrees? Under which conditions (glideslope & lineup error) would a pilot be waved off by the LSO? Thanks!

+1

That is something I found very irritating already a couple of month ago! On the forum they said to me, they will update the download link "soon". Again, that was about half a year ago. I don't understand why they still have the old version online, which most new users will use first until they realize they need to go to the forum and ask for a version that actually works. They are very helpful on the forum, that must also be said. I did get very prompt replies to all my questions.

Here is some info on that https://forums.eagle.ru/showpost.php?p=3669118&postcount=16

Ich hatte die List aus Matts Video auch mal aufgeschrieben https://github.com/funkyfranky/MyKneeboards/blob/master/FA-18C_hornet/FA18C-Kneeboard-090.png

Rudel, can you share your script when this happens? Maybe I can give a few tips how to avoid that. What MirabelleBenou said is a good point! Additionally, you can try SetTerminalType(AIRBASE.TerminalType.HelicopterOnly) for the helos. But not all airports have special helo spots. To explain, the script should check, if parking spot is already occupied and not use it. However, if two aircraft are spawned exactly at the same time, the first one is not in the game so that both "think" the spot is free and they land on top of each other. Therefore, one can also play around with the spawning delays and intervals to de-conflict the situation.

Beim Flip-Flop spart man sich sich LB1 und geht direkt zu LF1. https://github.com/funkyfranky/MyKneeboards/blob/master/AJS37/AJS37-Procedures-090.png @Gladius Sollte (laut Manual) eigentlich so funktionieren, wie Du es beschreibst. Hab's aber auch schön länger nicht mehr gemacht.