Draken35

Add them to units/fortifications and we will be able to make them immortal

Ah! I was thinking on terms on CASE 1's approaches ...I don't have much experiences with case 2 or 3 but I'll look into it. Thanks! No worries. I know it but others might not.

I was reading in the new manual (ch1-ch15) that the Tacan Offset can be used for LHA approaches but it doesn't says how and I can't think of a way. Does anybody knows? (Yes, I know how to use vanilla Tacan , without offset, to get in the boat)

Figure that would be the answer... One day, DCS will model it...I hope.

Good Job indeed! Question for you, how will the friendlies mark their position at night? And, would they use IR to mark the target?

Sounds like fun... Waiting for 2.0 to jump on it

Like new, in box, used for a couple of hours, just enough to setup, test and discover that it is not for me. The mount arrived after I tested and decide to sell, so it is brand new and it is headset agnostic. $90 shipped to the Continental USA. Paypal friends or you cover the fees.SOLD

Yes, I was actually in a orbit centered on the port and scanning it from about 15000 feet with the TPOD (I'm paranoid about SA-18's )... The real "issue" is identifying the red infantry, specially since the blues are about 400 feet from the reds. In a real situation, with troops in contact well inside danger close distance, I doubt a pilot would drop ordnance without a reference point. Anyway, as I said, when I was satisficed enough of who were who, the blue guys took out the reds without my intervention ...

I just completed mission 1 after a couple of attempts to get used to your mechanics and pass the language barriers. Must say that it was fun! I have a few items that I think are worth mentioning: 1) Air interception. The first information we get about the bandits is that they are at flight level 060 (6000 feet). After that, any information that the frigate gives is in meters. I grew up with metric system but live with imperial so I can work both without issues but others might have issues here. Also, the mentions "coordinates" but its is given a BRA (Bearing, Range, Altitude) call and it is not clear, if the BRA info is from the frigate or relative to the player aircraft. Suggestion would be to use the same messages as the DCS AWACS BRA calls and be consistent with the system of measurements used. 2) Infantry attacking the Marines at the port. There is no indication of where they are exactly but they are in close proximity of friendly forces and by the time I finally located an infantry group that looked like the enemy it was taken care of by the Marines. Suggestion, you already have a marker on the ground (blue smoke) so give a cardinal direction (not a bearing in degrees) and a distance (approximated) from the marker. Finally, I want to mention that I like a lot the way you are handling the wingmen! It is really great (for us SP) having useful wingmen!!!

YES! Welcome back Luiz and thanks! I'll be testing this version later today

Hands are tracked in the visualizer but do not show in DCS (started on VR) dcs.20211103-223349.crash dcs.20211103-223349.dmp dcs.log

Is the Harrier leap motion compatible? And, if not, will it be in the future?

This is the gamepad I got: https://www.amazon.com/gp/product/B07PQ62D7V/ref=ppx_yo_dt_b_asin_title_o01_s00?ie=UTF8&psc=1 And the idea came from here:

@gdotts Yes, the gamepad is just another independent controller in DCS... I haven't mapped anything to it yet, but it is recognized automatically by DCS ( as a matter of fact, some modules map some axis in the gamepad by default and I had to clear that).

It is flexible but it does takes some force to flex it... To be honest, I'm impressed with the quality and presentation of that $17 mount

and not too expensive ... for a welcome change Kudos to @bradmick and @fargo007 for the ideas!

I'm using this mount: https://www.amazon.com/gp/product/B07P2VK93P/ref=ppx_yo_dt_b_asin_title_o00_s00?ie=UTF8&psc=1 Feels really good and it should work with wired gamepads too

Just added the Winwing collective and the gamepad (for the TEDAC)

Well, every time I get an alert about battery level for the Quest 2 or the controllers while in a cockpit in DCS, I get severe screen tearing, FPS drop and the "shaded" area at the bottom of the field of vision. Tearing and shaded are persist even after exiting DCS and they go away only after closing link/ Virtual Desktop

@Apar much appreciated Sir! For anybody interested, I ordered these from Amazon: https://www.amazon.com/gp/product/B07NN8RSL1/ref=ppx_yo_dt_b_asin_title_o00_s00?ie=UTF8&psc=1 https://www.amazon.com/gp/product/B0791NB4FM/ref=ppx_yo_dt_b_asin_title_o00_s00?ie=UTF8&psc=1 \

@Apar That looks fantastic! Would you mind posting a parts list and where did you get them? For the bracket and the spacers at least please ?

I fly the Huey regularly, currently learning VFR with it and I got the KA-50 to train my "mindset" for attack helicopters ... I setup a practice mission with my two main jets (Harrier & Warthog) and the KA50, attacking an insurgent stronghold in a coastal city of Lebanon. Several targets: camp, HQ, roving patrols, fast boats, road blocks, some AAA and MANDPADs. Nothing fancy but it is an eye opener regarding AH tactics vs fast mover tactics. I not too worry about flying skills or particular systems, since all that will be different with the Apache anyway, but the mindset is totally different (not surprisingly!).

I had the same issue with the Harrier, quickly realized what it was and cleared out the Oculus controllers axis and it, indeed, fixes it. I haven't experienced any drop of fps (knock on wood).

I had another incident... Same symptoms, Syria, A-10C ... But this time I also got a "battery low alert" from the head set... Sure enough,, it was almost a 0% even through is was connected through link... I wonder if this whole issue is related to battery level... Check your level when it happens please

Thank you! This is actually quite cool! They show as controllers in the control tab when you are in VR. Also, there are a couple of new checkboxes in the VR tab to enable/disable the use of the stick and throttle with VR controllers. But is this in the change log? If so, I totally missed it !