TAW_Impalor

I can assign a joystick axe in settings, and see it move there, but it does not rotate the knob on radar altimeter. Button assignments are not available either. Not sure how to show this in a track )) And before this topic gets marked [Already reported]: I did not find a way to search one forum (on mobile) with the new interface, so looked through it manually.

I flew a multiplayer mission yesterday, hostile Mig21s and friendly JF17s were all IN LAR squares on my HUD and yellow HAFUs on my radar/SA, SCS Depress or not. Just tried today in single player, JF17 is till a square IN LAR, but now green semi-circle on radar (how could that be?). Track attached. Also, why does the range circle on HUD disappear sometimes? It happens in this track when HAFU changes to cross on radar. Yesterday I could not get it back whatever I tried. And my radar could not switch to vertical scan most of the flight, except the very end. Are these bugs or features? )) jf.trk

Thanks for caring! Mouse wheel is not bound anywhere in DCS, it just works. Sure I can turn the dials with my actual mouse and trackpad. Other keys are sent no problem. NumpadMult and Div are indeed bound by default to zoom in and out in UI Layer, General and for each aircraft, but deleting those bindings had no effect on mouse wheel not working. Autohotkey should hide the original keystrokes and replace them with new events, but it does not happen with DCS. It receives both KP5 and RWin KP5, for example, thus pressing the UFC button 5 and recentering the view. Other programs on my PC do receive only final events, and mouse wheel works there. That is why I think DCS processes keyboard and mouse interruptions on some lower level. If the script turns dials for you, is it on Stable or OB? I found another potential solution. I can bind wheel up and down to keyboard on UI Layer. The only problem, each keypress turns it by a small amount. Is it possible to repeat send down+up events in a loop while the original key is held?

Yes, it scrolls outside DCS (Opera, Explorer etc.) But neither in 2D nor VR DCS ((

Hello Rob, thanks for replying! Unfortunately, changing the code did not make a difference. I tried send, sendplay, sendinput with different delay values. I think blind is irrelevant, but I added it as per your suggestion. Currently, the code looks like this: NumpadDiv:: { sendplay, {blind}{wheelup down} sleep, 250 sendplay, {blind}{wheelup up} } return NumpadMult:: { sendplay, {blind}{wheeldown down} sleep, 250 sendplay, {blind}{wheeldown up} } return I fly in VR. The Idea is to zoom in-out in external views and to turn dials in the cockpit then the mouse is hovering over. Maybe you could test it? It does not make a difference if I keep Num/ and Num* bound to slow zoom, or clear them. About the KP5 (sorry I called it F5 in the message above), my UFC is pressed fine (waits until I release the key), but the VR view gets recentered. The piece of code is as follows: ;For some reason NumpadClear is not k-hook and have to use * *NumpadClear:: SendInput, {RWin Down} Sleep, 1 SendInput, {Numpad5 Down} Sleep, 1 KeyWait NumpadClear Sleep, 1 SendInput, {Numpad5 Up} Sleep, 1 SendInput, {RWin Up} return

Say, I want to lock a moving target, but fail. How do I go back to slewing the TPOD after PTRK mode? Pressing Sensor Control Switch right once or more times may or may not help. I find it very clunky (and undocumented)! Usually my TPOD stays stuck and does not react to TDC (cannot show this in a track). Sometimes it even jumps back to the waypoint I used as TGT to find the AO, so I lose the moving targets location. I don't want to press Undesignate for the same reason. Attached track shows TPOD resetting to TGT waypoint after SCS right. flir.trk

I searched, but did not see this reported. TPOD in FLIR mode behaves differently in VR vs non-VR. I cannot find targets close to a burning vehicle - my FLIR just goes white when I zoom in at any brightness/contrast combination. Replaying/playing on a monitor does not have this problem. Confirmed by other VR players that I asked, puts us at a disadvantage in CAS missions. Track attached - watch it in VR vs. non-VR mode. lmav.trk

Why does the title still read '[NEED TRACK REPLAY]'?

Hello. I included a short track where I try to target some warehouses at the end of the pier. In 'cross-hairs' mode on FLIR the HUD diamond is showing above the target. After I do TDC depress the HUD diamond jumps below the target and starts crawling away. The diamond on FLIR is also crawling, so I must constantly correct it until it runs away completely. I did not touch the baro setting in this track, but it also moves the HUD diamond. flir.trk

The screens in CV1 still refresh at 90hz, so no flickering like at 60

Also tested on PG, same observation. I don't know if wrong diamond location on HUD and vertical dependence on baro setting on Syria map are related. The baro setting 29.92 in that mission is correct to weather. Changing it do something else does not make sense, and does not correct the problem. I see diamond displaced horizontally as well as vertically. TPOD gives correct coordinates for GDAMs, for example, so the problem is only with HUD. No idea why.

dorianR666 do you not reproduce this bug, or just assume it's not there? While true that F18 air starts unaligned (what?), this is not what is causing it. I attached more screenshots and encourage everyone to try for themselves!

Not to start a new thread... My ahk script outputs both key presses and mouse wheel up/down. Running AutoHotkey as admin, only key presses get through to DCS. Mouse scrolls in all other apps fine. ONE time I managed to get it to work inside DCS (to turn dials) without changing the script or anything I can think of, but never since. Running DCS not as admin does not make a difference. I think DCS processes keyboard and mouse interrupts on some low level, because F5 is always recognized, even though I replaced it with RWin-F5 in ahk and TARGET's Event Viewer sees it so. Also, key presses in DCS repeat faster than 500 ms delay system-wide (i.e. outside view zoom). Any insight on how to consistently turn mouse wheel in DCS from an ahk script? I don't want to change my TARGET profile into a script just for that purpose...

Instant action - Syria - Bekaa Valley Strike. Always see the diamond in the wrong place via HUD after finding a target with TPOD. So gun runs are problematic. In other missions too has noticed this problem, but I think only on Syria map. Not sure if it's a Syria map bug or a Hornet bug, so feel free to move into another forum. Track exceeds 5Mb, can't attach... Update: cannot reproduce on PG and Caucasus, so it's definitely a SYRIA map bug!

I almost got used to the (updated) new look! Dark mode is my favorite feature. The only thing I still hate is that to get to the last page of a thread I must scroll to the bottom of the first page (((

Bestware just sent me an email that Europe is not getting any G2s for at least two more weeks (((((

I disabled all of them, but still get notified of comments to old posts

I never had any notifications, but now am getting them for all the threads I ever replied in the past. Must "Dismiss All" every day. In the settings they are not selected, but still appear whenever someone replies. Very annoying. And the look of the new forum has too many empty spaces, I do not like it.

Sooo... what's your latest guess on delivery date to EU? Amazon.es now says 1 November (was 1 October). Bestware: 'till end of November'.... I hope HP is not timing it with FS2020 VR support!

Thanks for your reply! If WOD should ideally be 25-30 knots, what value on LSO screen should we target in this case?

This is not what I see on LSO screen! If it were linear, the wind over deck would be much smaller.

Hello Devs! What formula do you use to calculate true wind speed at deck height (60ft)? I am trying to make sense of the LSO screen's wind over deck numbers. I made a simple mission with CV going upwind at 15 knots, and depending on true wind speeds I see the following WOD on LSO screen: W33 WOD 3 19 5 22 10 30 15 38 20 45 This implies the following true wind speeds at deck height, along with ratio to wind at 33ft (ignoring angled deck for now): W60 Ratio 4 1.33 7 1.40 15 1.50 23 1.53 30 1.50 The ratios seem high and, moreover, depend on the wind speed itself. I would expect some constant proportion, based on wind gradient theory here: https://en.wikipedia.org/wiki/Wind_gradient I noticed in the ME wind at 1600 ft automatically depends on wind at 33 ft at roughly 2.1:1 ratio. This implies Hellmans exponent a = 0.19. Applying this gradient to 60 ft we should be getting W60/W33 = (60/33)^0.19 = 1.12, i.e. wind at deck height must me stronger than wind at 33ft by only 12%, not 50%! Leaving it as is seems unrealistic. Thanks!

This happens to me recently in MP. Call 'Salute' to vaicom and use F menu 3-4 times before they finally start kneeling ( Edit: did some more tests with Supercarrier launch mission. Salute keybinding definitely has no effect. Menu F8-F6 and Vaicom work, but sometimes kneeling animation is delayed until the engines spool up (and sometimes they kneel at idle). On some occasions I had to spool up and then give salute... I think the devs need to investigate!

Hello! Did not want to start a new thread, but I think this "desync" issue is far from "RESOLVED". We experience a different kind of desyncing in our squad, where client 1, client 2 and the server all may experience completely different sequence of events! Example 1: our 2-ship flight is engaging a 2-ship AI flight. We sorted targets left/right and launched one AIM-120 each. My lead's tacview then showing both missiles going after the left target. In my tacview I see both heading to the right target while the left bandit is blowing up on its own. Server, apparently, knows that the lead's missile kills the left target and triggers it to blow up. But because my version of the events has the lead's missile still flying, it loses its target, pitbulls to mine, kills it, thus leaving my missile trashed with no target. Then that right bandit resurrects and kills me. Example 2: my lead drops 3 GBUs on his first pass, and 1 on the second (as proved by his tacview). I see him doing a dry run on the first pass and dropping all 4 GBUs on the second pass 15 (!!!) minutes later. Then he gets killed by a SAM with no warning, because the launch only happened on the server and not on his client PC. I do not have mission files and tracks, only tacview screenshots from different players. I can not pretend to know how the syncing is done, but I assume only some key trigger events are exchanged between server and clients, while the simulation is running independently on them all. These triggers seem to get lost/delayed/repeated when an omission is detected. My connection is 300/300mb with the ping to server of 30, so I doubt we can blame the ISP/covid etc. This bug now seems to affect every single mission we fly in MP and causes huge frustration. Like the OP of this thread did, I'd like the situation acknowledged, issue reopened and some assurances given on how it will be resolved. Thanks in advance!

I think it takes bogeys from Datalink, so the radar can be off