TAW_Impalor

I implemented all the mods and registry hacks I could find and now happy flying at 45 fps with 100% auto SS, 2x MSAA, and cabin-only shadows. But I have a much older system! So the game engine is really really bad, and there is no incentive to upgrade hardware ((

Any word from devs on allowing the inner values to be set < 1? I played with the tool but failed to make things any better. My G2 came calibrated with inner values at 0.9XX.. and I feel like I would want them even lower. I play with helmet IPD at max and DCS IPD at 45 for realistic worldscale, but see some parallax when looking around. I can't tell for sure if I my helmet can be calibrated better, but would like to test more.

Curious why. How can one cheat by having custom shadows?

Nice mod! Any chance to make it pass the IC?

Did anyone think to just sand off the legs of the original faceplate? I know there are magnets inside, but maybe they can be pushed deeper somehow.

Tried now, still not updating Edit: just a minute later, started! ))

Soooo, are the "better lenses and display" of G2 vs G1 just a higher default SS at expense of FPS? I.e. marketing BS?

Yep, thanks! I disabled those for realism. Bind to buttons does work, but moves too fast )

Ahh, radar elevation is for the search angle? I want to set the floor of radar altimiter warning sound. No such control?

yes, Radar Elevation Control

Has this module been abandoned? 9 FPS after take off in quick intercept Syria mission. And no pilot body still...

Should definitely be optional. 4.5 years into the VR age, I now refuse to fly modules with no pilot body and static reflections!

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...