Diac

Bump.

Hi, The LoSetCommand function in Export.lua - can this be used to set a specific stick position etc. from e.g. an external script? From Export.lua located in the install folder: function LuaExportBeforeNextFrame() -- Works just before every simulation frame. -- Call Lo*() functions to set data to Lock On here -- For example: -- LoSetCommand(3, 0.25) -- rudder 0.25 right -- LoSetCommand(64) -- increase thrust end I am trying to make a more sophisticated autopilot for the MI-8, and I was initially planning to do it by extracting data by using the LoGet...() functions and send it to a python script, and use a virtual joystick to provide control inputs to DCS. If i can provide input to DCS directly by using LoSetCommand functions, I think that may be a better solution.

I remember reading about a terrain avoidance radar mode for the Hornet. Is this still planned to be implemented at some point?

Very interesting, thank you for your insight! Since the scope doesn't show relevant terrain when the elevation knob is set to the middle snap position, but has to be adjusted slightly downwards, I would guess that there is a bug causing the middle snap position to not be 0 deg relative to the aircraft axis, and that this is the reason why. Would you agree? Edit: I just re-read your answer, and it seems to me that your opinion is that the lack of relevant terrain on the scope is due to the fact that you have some positive alpha in level flight, correct?

I messed around with the terrain avoidance (TA)/obstacle detection radar mode tonight, and noticed something: It seems like what happens when the radar is put in TA is that the radar beam is narrowed in the vertical plane (tested by adjusting the elevation both in and out of TA mode), which I assume is what is supposed to happen. However, I also assume that the radar is supposed to be locked to boresight when TA mode is active, so that what shows up on the scope is only terrain/ojects at your altitude. This does not happen. The way I tested this is as follows: 1. Bind the radar elevation axis to a rotary control with a middle detent (the viggen manual states that the elevation potmeter has a middle snap position). 2. Set radar in A1 mode, and turn weapon selector to AKAN (or any other mode where radar elevation is indicated on the scope). 3. Adjust radar elevation to the middle snap position on the elevation axis and observe that the middle does not correspond to boresight, but rather slightly above. 4. Fly towards a mountain or other terrain at your altitude. 5. Set radar in TA mode, and observe that nothing shows up on the scope. 6. Carefully fine-adjust radar elevation downwards (axis is inverted), so that terrain shows up on the scope. 7. Disable TA mode and go back to normal A1, and observe that radar elevation is now set to boresight. So, TA mode seems to be working as intended, as it does narrow the beam in the vertical plane, however, the radar is not locked to boresight upon engagement of TA mode, so that manual fine-tuning of the radar elevation is needed in order to properly display terrain on the scope. Is this a bug? Or is the problem/bug that the middle position of the elevation axis is above boresight? In addition, it also seems to depend on which weapon mode is selected. Does anyone else share a similar experience?

:megalol: :megalol: :megalol:

Hi, I've noticed that when moving the throttle e.g. from idle to mil or vice versa, it sounds like there are discontinuities in the engine spool up/down sound. Is it just me, or is this actually the case? I.e. that the sound is not continuous/"linear" but that it "steps" up/down in frequency when a certain throttle level is reached? I don't know if it has always been this way, but in this video: from t=6s to t=25s, when he alters the throttle, in-cockpit view (I realize this is a video showcasing a sound mod, but only external sounds are affected by the mod AFAIK), it sounds like the sound is the way it is "supposed to be", i.e. continuous throttle movement = continuous sound frequency changes. I am relatively new to the Viggen and DCS in general - I have flown the Viggen since summer 2018, and the sound has been unchanged since then AFAIK, so the weird sound frequency stepping was all i knew - until I watched the video linked above, which is from 2017. So, my question is, in essence, is the fact that continuous throttle movement |= continuous sound frequency changes in the Viggen a bug? And if so, has this bug always been present, or has it appeared at some point between release and now, as the linked video indicates? I think it's such a shame that Heatblur has not chosen to prioritize the sound design of the Viggen the same way as they have for the F-14 - which IMO is the best sounding module in the DCS, especially in regard to engine sounds, bar none.

Can't tell if troll or not...

Aha, I see. It would be awesome if that was the case.

What does that mean? Is that a user mod?

I believe I once heard something about a complete sound overhaul for the viggen - which, imo, is very needed. The viggen is the module I enjoy the most of all the available modules in DCS. However, the engine sounds of the viggen really breaks the whole immersion thing for me. Don't get me wrong, I like the fact that there are sounds for every button click etc., but the sounds of the engine are really lacking. I can't seem to find a sound mod which modifies the engine sounds for the viggen either. So my question is, is it correct that the sounds for the viggen is supposed to get an update sometime in the future?

Thanks!

Hi, The last thing we heard about air-to-ground radar modes was in a hornet mini-update dated 12-18-2019. In this mini-update Wags stated that: "In February, much of our air-to-air radar development will shift to air-to-ground radar development. This will use the air-to-ground radar API that is already being used by 3rd party developers." I was just wondering if there is any news on this? Can we expect to see any AG radar action any time soon? And I know, "it's ready when it's ready", but I'm just extremely excited about getting a functional AG radar... :joystick: