Nagilem

This seems to be only happening with the instant action missions. Other missions work fine. Not sure why.

Just curious - Does this static mapping allow you to set the spawn points? or just the static AC only? I've never worked with the static map before. Any pointers to other threads most welcome... :)

The sensor select switch is the joystick hat that moves the SOI between the hud, DDIs, and AMPCD. Sometimes I could get it to function through target consistently, but not always. I played with the press time for the keys and other pulse methods, but it just never worked consistently. Also have had issues with speedbrake - if I forgot it, it would fill the keyboard buffer... :)

Is anyone else getting a strange flickering and glitching for boats over the water? I have an index running the latest beta software, a 2080ti card, i9900k processor. I have my settings at 90hz, 190% SS in Steam VR, no MSAA or AF turned on and am getting a solid 45 frames everywhere. In SP, I get flicker / glitching when the carrier is 5-10NM away is high. Both the boat and anything around it seems to glitch (move side to side or fade in and out, and includes the rails for my hud glass if the boat is close to the side of the hud). It gets better to a degree the closer I get to the boat. The flickering was really bad with my squad mates the other day - so much so I had to skip landing on the carrier because I couldn't see the deck. I've flown in other MP missions with less flicker / glitching since then so maybe that was a server issue. I don' think I had this issue before the latest update. It only seems to happen over water. The land objects are solid without any issues. I have my water texture on Medium, and changing up or down didn't seem to have any effect. Anyone have some thoughts on what else to check or change to fix?

Tried it tonight and only one jsow tracked. The other one ditched way early. Also had issues pushing too targets to pp mode. Must use step or all programs go to one jsow and no others.

@ Drakoz - Thank you for the suggestions. I do like the capability I was able to achieve with Target, but I have had numerous problems getting all of the fucntions to work. The big one that never worked consistently is the sensor select switch. I got it to work maybe 1/3 of the time. I had to constantly press the button to see if I could get the SOI where I wanted it. Also, Target would ABEND and leave me with no buttons. I moved my config into DCS and those problems went away, but I lost alot of functionality too. I don't think there is a perfect answer. I'll take another look at Target.

So I am working to use TGP and JDAM or JSOW in TOO mode. I can target very consistently with TOO1 and get both JDAM and JSOW to hit. What I am struggling a bit with is how to use TOO2... Can I target 2 targets with TOO1 and TOO2? So far, I target something with the pod and TDC depress, but that changes the GPS coordinates for both TOO 1 and 2. I haven't been able to make those separate into to different coords... Is this WIP? Or am I missing something?

Hi Panther - just tried. I see the throttle but cannot change anything. I only get the remove device option. Right click yields nothing. No other options for advanced settings. I run Win 10. I don't know if something else is required.

I believe in case 1 you stay dirty in the pattern. You turn back to brc for .5nm climbing to 600, then reestablish the pattern. Case 2 and 3 you clean up to conserve fuel.

My squad uses SRS but sometimes Discord to communicate in the jet so having another key on a keyboard for discord isn't an option - I fly VR and cannot see the keyboard to make another key press happen. I agree with SGT Coyle - It uses the generic GamePad4 device for mapping PTT so any device with gamepad 4 has the issue. Thankfully that is a fairly unused OSB on the MFDs and the Recce button on my stick so this isn't a huge deal. Just annoying and frustrating ;). I don't use target because Ive had numerous problems with buttons being intermittent in game. I use direct DX commands in DCS and that has been working fine, but it is limiting. I am trying to understand LUA better to see if I can make things work more consistently / better. This also has the fun of having my config overwritten every patch…. I havent see joytokey before. I may have to see if that could help map 1 key to solve the issue. I am trying to avoid adding more software to solve the problem because I already have a ton that runs. After a while I'll need the full page check list just to open DCS!:megalol: I'll keep digging around and see if I can come up with another answer.

will try again tomorrow. Thanks for the suggestion.

Sorry for the silly question - when I use the TPOD to designate a GPS marker, it puts a diamond on my heading tape that seems to stay no matter what I do after I am done bombing. Is this by design? Is there some thing I am missing that should be done to clear the target steerpoint?

Having the same issue with not being able to get the mod to pop up in VR. Works in regular screen mode, but no window in VR. Not sure why it stopped working.

Strange problem here, I have a warthog stick, throttle, and 3 of the MFDs. I have mapped discord to use my throttle comm hat down (button 4). That works fine, however, button 4 on every other device - stick, and all 3 mfds also trigger the PTT for discord. Anybody know a way to force discord to only use my throttle only for PTT?

@supmua - that is my experience as well. Improved clarity and great experience across the board. This was a great purchase for me.

I have a mission where I would like the carrier strike group to fire on some ships as part of the mission. I can get the fire at point working, but only with cruise missiles. Any way to setup a barrage of harpoons? I see the antiship missile options under Attack group, but the group won't seem to fire. I think I may just be missing something... Any help would be greatly appreciated...

@Rudel_CHW - Thank you for the template suggestion. Would you be able to post your template file? I'd like to take a look at how templates work and it would be helpful to see one configured. @Habu - Thank you for that suggestion to search and replace. That is definitely what I will need to do this time. When I open the miz file, it isn't readable text. Witht the attached file, do I search and replace that whole block? Do I have to use WinRaR or can I use Notepad ++? Have you had any issues with doing this?

Setting up a mission with lots of possible player AC and I want to give all AC the same radio setup on a per plane type. So F18s might have comm1 channel 1 127 and channel 2 288 etc. Is there an easy way besides editing every single AC to get this done :helpsmilie:? I know each AC type will need a setup - This mission will primarily be f18s and f14s so I want to setup the radios for all AC the same per type.

@Alec Delorean - I agree. I can say with a 2080ti card, the headset is pretty amazing. My only minor nit is I'd like to make it just a smidge brighter. Overall though, I am actually very happy with the performance. I'm running it bone stock with 150% SS in Steam(PD 1.0 in DCS), motion smoothing on, MSAA x2 and 16 AF in DCS and I get consistently over 45 frames in downtown dubai @90hz. Turning it up to 120 hz doesn't produce enough differnce for me to notice - YMMV. I would think turning it down to 100-120% ss with a 2080 or 1080ti card would yield very similar results.

After a few days in the Index, it has definitely grown on me. It is comfortable to wear, excellent end to end clarity, decent brightness, excellent clarity and has worked pretty flawlessly. @nrosko - I would do the SS in Steam and not in DCS. I have mine set to 150% and use the DCS MSAAx2. For me that is performing well almost everywhere. I also turned the Motion Smoothing off since that seems to cause me ghosting issues. In Steam, the SS % will give you the 'resolution' being driven to the headset.

I tried it with no issues last night that I saw. its not a strong zoom, and I didn't get any big cross eye effect. What in particular would make it proper vs improper?

@supmua - spot on review. I have the same experience so far. My only minor issue is motion smoothing tends to invoke alot of ghosting issues with fast moving objects. As you said, I think that is DCS rather than Steam. I hope it gets fixed by either future Steam or DCS updates. All else with the index is really really good.

Received my index Friday and finally got some solid time in tonight. After getting it set up, which was much less painful than I expected, i found the experience very good. With 150% ss in steam, motion smoothing off @ 90hz, my experience was good. I found the headset comfortable, the audio superb, and compared to my o+, the headset has about the same fov with the knob cranked in to my eye comfortably. The index seems 20% dimmer, 10-15% sharper than the o+, with the reasonable contrast during day flights. Night flights are not so good, with blacks really looking dark gray. In this regard the o+ really out performs. Overall I like it. Much much better than the reverb in my opinion. To me, the o+ tuned correctly is a great value for a VR headset. I will likely continue with the index as I found the aliasing to also be better. With msaa x2 on, I get mostly shimmer free 45fps in Sochi. Dubai is a bit of a crap shoot in FPS. My only mild complaint is that I do get a lot of ghosting with motion smoothing on. It gets better if I turn it off but only slightly. I think that may get corrected with updates. To answer whether if I’d buy it again, I think i would. It’s not wildly better than the o+ but it is better. I think since i plan to play other games than dcs, the spend is likely worth it.

I think HP really botched this rollout. I think they went to market too quickly and the product wasn't ready.

Sadly, testing tonight has resulted in a return to hp decision. This headset to me feels cheap, is extremely dim, and now is starting to flicker badly. On dimness, the headset is only about half as bright as my o+ with marginally better resolution. Very sad. I’m glad others have had better experiences. The reverb just isn’t for me. Ran at 188% ss in steam @ 90hz. I tried really high gamma and some other things with same results.