All Activity

Personally if you're investigating hand tracking, especially with DCS you should also consider usability and how hand interactions in VR work. If you check the hand tracking feedback (for DCS) a lot of it is very mixed because something that sounds ideal in theory ends up being a pain in practice. Mostly because: 1) The distance between your 'virtual' hand and the virtual switch you are selecting can create additional 'unwanted' movement, meaning you often have to lean forward, backwards, twist etc. With a VR controller you can hit switched on the other side of the cockpit by using the 'laser pointer', but if I have to move my physical hand over to the location which is virtually away from me its not ideal. 2) A lot of buttons can have multiple functions, like a push up, down, middle or a twist left or right. Its often quite difficult from just a hand position to know which one of those inputs is performed. 3) Reaching out to a busy cockpit can sometimes result in you pressing 3 switched you did NOT want to press, and only 1 you did. You need to be able to have a separate gesture to know if the user wanted to action the switch is at their hand position. Preferably you'd want a hybrid approach so that your real hand can be used a VR controller and / or a mouse with the same / similar functions so that users gain the benefit of using hand tracking to enable them to interact with their virtual environment without having to keep picking up the VR controller and swap between that and their HOTAS. Something like a 'finger gun gesture' as the pointer, and then maybe hand clasp as the 'action', with a left / right twist as turn left / right etc. I've been using PointCTRL for about a year now and it is excellent in its simplicity in that it does everything you need in terms of cockpit interactions without being forced into awkward physical actions or having to keep picking up a cumbersome VR controller.

In the navigation tutorial video the method to set up the PRMG is vague. I can complete the tutorial training mission and understand the methods to use it to land the aircraft. However I cant work out how it is set up in the mission editor. In one of WAGS videos he sets up an RSBN car channels 3 and 5 at airbases. However when landing at the airbase the ILS channel is set to 6. So obviously these cars are not used for the ILS guidance and just as RSBN beacons. In the tutorial video however I see he has another unit on his recovery AB with channel 6 and a heading 181 degrees. Is this the unit he has used to give out a PRMG/ILS signal? If so this has not been explained and is this just a RSBN car? Also in the video he sets up his ARC-19 frequency but does not use the ARC-19 from what I can see in the tutorial. I have set my ARC-19 inner and outer Freqs for Maykop Khanskaya but this does not effect the needles on the HSI. I see in the mission editor forMaykop Khanskaya on Caucasus map there is a DG channel 36 for the airfield approach. again tried this channel on the MIg but still no signal received. Can anyone give me some guidance on this I've been trying to understand this for hours now but cant work it out.

Not sure how that works. Do you have any info on that? Here's a video of what's happening in the game. It's odd that the tone is intermittent despite steady state conditions:

I'm glad to see you went through. Now you have to figure which technique and settings for doing "visor" effect. But what is the second check box ? is it the one to display technique in VR only ? It should work also. The purpose of this feature is to have the technique only for the VR view and not on the mirror view, to save resource. So when you tick it, effect should disapear from 2D view but reamain in VR view (maybe the "refresh" button need to be pressed.

yes, sometimes its reversed or act like toggle button

RCtrl + Enter does not work

AI SU-25s and SU-25Ts, when set up to start up from the ramp (cold or hot), randomly fail to take off from some airfields on the Syria map. The same does not happen on the Caucasus map, for example. SU-25 SU-25T TO SYRIA.miz SU-25 SU-25T TO CAUCASUS.miz SU-25 SU-25T TO SYRIA.trk SU-25 SU-25T TO CAUCASUS.trk

I had to research it, but that seems like the type of upgrade I was talking about. It makes me wonder why they didn't try to reintroduce it in the late 70s, especially if it could allow the existing APQ120 to be retained. For the record I'm not suggesting that this would have kept the F-4E relevant as a fighter but rather that it would give it more "teeth" when pressed into a fighter role or when forced to defend itself on an A-G mission. More situational awareness of potential threats, etc.

I mean, is it a bug that Petrovich can see targets during the night at all (regardless of moon state)?

If you get a chance, try this process and see if it works. After Aekran Test, Engine Start, and Fast Alignment, and with the Ground Power disconnected: Clear controller mappings for Pitch and Roll from all controllers. Flip the AFCS switch and allow the BIT to complete (Takes about a minute. Stops a couple of times during the test) Wait until Damper Off warning shuts off. Remap the Pitch and Roll Axis. This isn't a permanent solution, but it's the best I have so far.

It's unusable for me in VR. With Pimax Crystal Light I see half of it as tinted, half not, and all sorts of artifacts... honestly, it's literally tearing my eyes out... :/

This. Nor is the air itself perfectly still. (Well in DCS it can be, but that's unrealistic in itself)

It can bank either way. They are not perfectly made nor perfectly balanced in weight.

It´s not a bug, I had the same problem. They have integrated a new setting in the menu. Look in your settings and tick "Controllerless mode"

Flap Switch Binding works as intended on first spawn, but upon RTB and touching down flap switch binding reverses for flaps up and takeoff flaps. Binding still appears correct in controls. Stays like that until you respawn.

This is an issue with every FFB joystick I'm guessing. I have a Sidewinder FFB2 and have the same issue. My custom cold start checklist currently has the following entries after Ground Power Off: "Unassign Joystick from X and Y Axis" "Turn On AFCS and wait for BIT to finish" "Reassign Joystick to X and Y Axis" Works every time if I do it this way (and get all the other steps correct of course,) fails every time if I do anything else.

Derya Yıldırım & Grup Şimşek - Cool Hand

Yeah, sounds like the most boring and redundant thing they could have come up with. Hopfully there is a plan to develope this for all maps and different timeframes as well as MP.

Ok, so the aircraft is supposed to bank to the left after successful AFCS test and take-off?

He's saying that the lamp and sensor work for some range that's considered neutral. It is not a precise point that'll give you hands-free flight and it's also not the trimmer's job. Use AP instead. This comes up for every module and it's just misunderstanding of the trimmer function. Hence the trim sensitivity workarounds because people apparently want their aircraft to fly on rails

Interesting project! Are the two Arduinos automatically recognized as two different Windows game controllers? Until now, I have been using Leo Bodnar boards. However, these are quite a bit more expensive than the Arduino Leonardo boards...

Agreed. If they really want this to be a Cold War map, they shouldn't have set the default date to 1999 to begin with. Apparently, according to their sources, several aerodromes in Normandy also had ICAO designators back in 1944

Do you use VAICOM/VoiceAttack?

VR Pimax Crystal OG + Quad-View Foveated + Eye Tracking I also have slight banding and flickering in VR. I don't use Pimax's internal Dynamic Foveated Rendering & QuadViews. I use the conventional version: mbucchia -> Pimax-OpenXR mbucchia -> Quad-Views-Foveated TallyMouse -> QuadViews Companion That's why I don't think it's because of the Pimax update. ED: Can you please check this, we had a similar problem a few DCS updates ago. Thanks and greetings Tronix