Anubis_94

Hello, Adding a question to this thread : 5. If the real AC allow it, will we be able to modify STNs via UFC (like the f16)? More pratical when SA is clutered than trying to get the correct TUC

Hello, A bind to a sun visor from the helmet, or glasses, to help in such situation would be great

I just want to back this up in the wishlist. Even without the dangerousity of such clouds at beginning, for scenery ...

Thank you

I really like your feedbacks . Is it possible to complete these two benchmarks with a run on the CCD1 only (CCD0 disabled) ? In order to have the perf on natural 7950, "vcache" 7950 and "freq" 7950.

Nice, thanks

Nice, thanks for your feedback. Do you have any hint on what ccd was used ? vcache or regular one ?

Hello, Issue found. Gremlin doesn't deactivate the virtual axis when using a modifier on it. And I have buttons on the slew axis with modifier. Example : Use axis, slew press modifier while slewing release the slew while modifier is still pressed slew will continue I won't blame Gremlin, it does what it says : axis input is conditioned to the modifier, so when I press it to button press too quickly ... the axis input "back to zero" is discarded. Issue solved by forcing axis to 0 when pressing modifier What is weird on DCS side is that the axis input (the slew) isn't displayed in the control screen. I can play with the axis on this screen while the issue was happening, the issue will resume when going back to cockpit.

Hello, Last time we check, the harpoon launched in R/BL go straight for the target at the time of launch. No idea if this is this the real behavior, but it feels weird as the weapon system could deduce an interception bearing (for a weapon mode that allow to select a specific moving target, it would makes sense). The seek range is an independent setting that may mitigate this and get the harpoon back on target, but isn't related.

Hello, I encountered an issue with the TDC drifting without any visible input from my side. With the TGP, SA or RADAR (AA and AG). So I would assume the issue is related to the input control and not the systems. In the video below, I am playing with the TDC at 37sec, and issue is visible at 47sec (TDC is drifting right without input). Controls are visibles at 50sec. I have no other bind these axis (that are deadzoned at 5%), and keyboard inputs are deleted from all devices (I do not show all columns in the vid). I am using an Orion2 with gremlin. Gremlin doesn't see any input from the physical or virtual devices. Winwing SimappPro neither with the physical device (as displayed in the capture below, taken at video end when lifting the helmet). (the ones at ~33% are the throttles) Another detail is that, even if I am unable to say it is a VR only issue, I cannot reproduce without VR. Attaching the track in case it is possible to see any wild input. TDC_DRIFT.trk PS: VR recording from SteamVR is half FPS, don't ask why

Did it, nothing changed with the visib range. But still new elements There is an error in the OP: I though we encountered the issue with CAVOK meteo, but I certainly confused with a light scatered. Following tests, with extreme visib range (settings at video end), show the issue with a meteo, light scatered, and no issue, with no meteo. Issue with SCT LIGHT No issue with no meteo SLAMER_110Nm_SCT_LIGHT.trk SLAMER_110Nm_CAVOK.trk

Hello, We encountered a similar bug yesterday when mate hooked the CAT1 when I, host, was waiting LB extended on CAT2 (but still not hooked) https://imgur.com/a/9C4Tijm The track is big (the whole mission) 50MB, but the issue happend only after 10min. Maybe it can help. http://server.3rd-wing.net/public/Anubis/BugReport/server-20220615-210445.trk EDIT: In fact, I remember a similar issue on a previous flight 2 days ago too. https://imgur.com/a/KNGvyeC Track, big again, because we didn't restart the mission, but still, here is the file. Issue after 9min40. http://server.3rd-wing.net/public/Anubis/BugReport/server-20220613-211415.trk

Here it is. Tests were done on flatscreen, but issue happened also in VR.

Maybe they should knock knock the PR of Raytheon

Hello, TLDR: While using the SLAMER in F18 with DL13, a fog seem to be present at 105Nm range from shooter. Details (and little history): at first the issue of a "blank", "too bright" DL13 was reported. We assumed the new FLIR would fix the issue, but we encountered again the issue in my squad last week. Investigation shown that, if the missile was far away from ~100Nm from the shooter, display was lighten, maybe in an attempt to indicate the missile was too far for comm. But the fact that, target was still visible and sharp when missile was about to hit (<1Nm) was odd: it wasn't a distance issue. So, next test: A hornet in active pause, 125Nm from a target. SLAMER activate at 60Nm, FLT LOW to see the ground. A fog seem to be present at 105Nm range from shooter. Attached a track/ACMI/Video showing the issue. The fog can be seen starting at 2.30, and range is mesured at 3.30 Target is, as previously, visible when missile is about to hit (<1Nm, at 4.13) Extract from the video, where the lake is masked by the fog Issue was observed on Persian Gulf and Syria, with various weather (incl. CAVOK) (EDIT: memory error from author) SLAMER_1msl_125_actv_60Nm.trk SLAMER_1msl_125_actv_60Nm.acmi