Flagrum

Despite the supposed bug fix, I am having issues with the rocket pods. I tried this with pods on each station, i.e. only the outer ones, only the middle ones, only the inner ones and also with rocket pods on every station. The very first volley goes off okay, but subsequent trigger presses seem to do nothing. I can't say what caused it, but after several seconds (was checking the pods from the F2 view, checked cockpit settings - but didnt change anything, etc.), I could shoot again until the pod was empty. Having unlimited ammo active, I waited until the pods were reloaded. But since then, I could not fire off any rocket anymore. When I had rockets loaded only on the inner pylons, I had GUVs at the other stations. I switched back and forth between rockets and GUV and while rockets where making troubles as described above, I was always able to fire the GUVs, even after an unlim.-auto-reload. This happened on 2.1.1.9459.269 NTTR (+ NS430, if that matters).

That is Neo-Caucasus as well, isn't it?

No, I understood you correctly, I think. But I am pretty sure that the RIO will be very tightly integrated into the F-14. A F-14 RIO would be pretty useless in a L-39 as the fighting in both aircraft would be very different. The "radar" part in RIO is the keyword here... Yes, looking outside the cockpit could be applied to both aircraft, but that probably makes "only" half of the capabilities of what the AI RIO is supposed to have. A RIO is not a GNS430 ... ;-) Instead the AI RIO is just another component in the F-14 cockpit as any other avionics device or sensor.

Well, how could a AI F-14 RIO be proven to work well ... without a F-14?

I believe, _( ... ) is a function call which returns the localized/translated text.

IF you have purchased the module. ;-)

https://support.garmin.com/support/manuals/manuals.faces?partNo=010-00139-11

... and that is about the time when it will be revealed to us, how the transistion is going to happen (give or take 2 weeks).

The thing is, you are not forced to purchase it now and waiting until some more info shows up seems to be a viable option ...?

It is already implemented - since one or two patches ago. It was buggy at first, but I just re-tested it briefly (Nevada) and now it seemed to work. But I bet, it is still WIP - at least there seem to be two issues with that. Use Advanced Waypoint Actions / Perform Task / go to waypoint OR ... / Perform Command / go to waypoint You see the issues I mentioned already: a) the action appears twice (but both seem to work ok) and b) the text does not match the other texts (different wording, no capitalizing ... perhaps missing translation?)

Well, what do you expect us to say here? Other than ... "Welcome to DCS World!" ? :D

Trim the helo.

Uhm, you don't have a DCS screenshot as background image and the info bar is part of that ...?

I am confused now ... the patch notes, dated 23. August, are not meant to describe the DCS patch that went live on 23. August?

Persönlich geht's mir dabei gar net mal so sehr um die bisherigen Erfahrungen mit AvioDev. Aber ich bin es echt leid, mich auf Dinge zu freuen, die erst in vielen Monaten, wenn nicht Jahren wirklich erst akut werden. (Vgl. auch mein Thread von vor ein paar Wochen "Ich warte" ... ;-) Da sind mir eine F-4, Mi-24, F/A-18 oder ein Harrier buchstäblich "etwas näher".

:dunno: 2020 (und die 2sitzer Variante nicht vor 2022) ... und ich warte schon auf so viel Zeug, das irgendwann mal gefixt oder implementiert werden soll ... Ich denke, ich passe hier.

To me it seems as if it is related to the (active) radar and the number of objects it (potentially) detects. I started in the air somewhere over Normandy and got baaaad stutters (--> radar had to check a lot of ground objects all at once?). An other mission, air start over the water - coast barely visible. Turned on radar and stutters were almost non-existent. Then i turned towards the coast and while I came closer, stutters increased. Then I reduced the radar range and stutters got better. But in any case, the stuttering was not as bad as in the first example (slowly adding new ground objects to be checked as I flew towards the coast?) Third test, now over Nevada (far away from Vegas): occassional stutter, but playable after some seconds (--> almost no ground objects at all?) Note: every time there were no AI units involved. Only the map, the Viggen and myself. To me it looks as if the radar code iterating through all (static) objects within the LOS of the radar causes this.

Strange. What is the reasoning behind that?

The declutter switch of the HUD seems to be only doing something if in A2A mode. It then removes everything except the aiming reticle (only briefly tested with guns). In A2G mode (again, just tested for guns), it does nothing. Is that supposed to be like that or is this just WIP/a bug? It would actually help quite a bit, if the FPM would not obscure the target at times, for example ... :-) But I also found that the switch acts as if spring loaded: you have to hold the switch in the "declutter" position or otherwise it would disengage immediately. This seems to be clearly a bug - performing attack runs one-handed is not exactly easy. :-D

I think, he is refering to the issue that weapons will not reload/re-equipped automatically when expended if the "unlimited ammo" option is enabled. (see also the bug thread that I linked to in my previous posting)

Ability to record (and ofc play back) macros. Some new functions in the controls setup, available in every module, to start and stop recording of a macro and to play back a macro. Recording should just preserve the timing of button/switch/any-clickable-control activations - quite similar of what is already done today when recording a .TRK file. Ideally the recorded macro would be saved somewhere in the Saved Games folder as editable text (i.e. probably a .lua) file for later, manual adjustments and tweaks. MP guys probably want this feature to be server-controlled to prevent "cheating"? Would make it easier to set up your cockpit for example (i.e. seat height, lighting and other personal prefrences). Or would also allow for a user-defined autostart sequence - according to one's personal startup sequence. Etc, etc ...

For reference: https://forums.eagle.ru/showthread.php?t=182138

You guys realizes that AI targeting capabilities were tuned down a couple of patches ago? It is supposed to be a fair bit better/realistic now ... or is it still so bad?

Austria, according to his forum profile.

Same for 2.1.1.8491