backspace340

It doesn't look like contacts detected by donors only are appearing in the build we got - only contacts that have also been detected by ownship are appearing (so first and third of your statements work, second isn't). Not able to get a track for you at the moment - but will add one in about 10 hours if someone else hasn't got there first.

As long as you start pickling on station 8 then it works, if you're on a different station to start with it might go wrong.

You don't need to cycle between JSOWs on that station - set up a PP1 and PP2 for each station, so you'll have 8 total (they can all be different targets). Then step through and make sure every station is on PP1. Then you can drop 4 JSOWs with four pickles, and when it cycles back to the first station, switch to PP2 and pickle, and repeat that for each remaining station. You'll drop 8 JDAMs/JSOWs on 8 targets.

You can use this in the meantime: https://github.com/Santi871/DCSWaypointEditor/releases Captures mission coordinates from the F10 map, and then enters them into the Hornet for you (you can choose if it makes waypoints, in sequences if you'd like, or if it makes PP missions for the JDAM/JSOW). Great little program. Doesn't break IC either, so compatible with MP.

I've definitely seen elevation matter with JDAMs/JSOWs, so a bit perplexed by that too.

Yep, sounds like you were entering DDMMSS.SS coordinates into a DDMM.MMMM format, which is why they ended up not matching and being nowhere near the target. They changed the default from DDMMSS to DDMM.MM on the HSI the last patch - I kinda wish they'd change it back so we don't have to change it every time.

The Hornet should have the ability to make markpoints, just like the A-10C. It uses the MK# button on the HSI page, if the aircraft has a target when it's pressed it takes the target's position, if not it takes the aircraft's position. I can't paste the picture cause of the rules but read section 24.1.3.9 MK Option in the NATOPs, the behaviour is described there. You should then be able to flick through them like you do in the A-10C, the main difference is that you'll have to WPDSG each one before launching a weapon at it in TOO, which you obviously don't need to do in the A-10C. I don't think this is implemented yet though.

Prescription lenses have existed for a long time - you need to give your distance prescription. The headset's lenses are focused at 2m or so in front of you.

It's definitely going to be inside out tracking - their website talks about being able to go to your friends or office and play with their 'new' tracking system: https://www.vive.com/hk/cosmos/

I don't think I was misleading - as I said that's the rendered FOV and the visible FOV is different. Up till now people have been claiming the Index is a 130 degree FOV headset but it's now clear that's wrong, it's a 110 degree headset with no extra FOV from the game rendered over the Vive. For me that's actually a plus - it means it has better PPD than the Rift S and it should be no more taxing to run than my Odyssey as its the same resolution and rendered FOV.

Someone's made a gif comparing the rendered Index FOV with the OG Vive: https://m.imgur.com/J0KzdM8 Index is the one with a gap in the middle, as you can see its basically the same (Index is a bit worse off for vertical FOV, but horizontal is basically the same). Obviously you'll be able to see much more of it in the Index than you can in the Vive (unless you're one of the people that replaced the face mask to get closer to the lens).

There should be a Summer Sale in a few days on Steam or on the ED store, you should be able to pick FC3 up for €23 or so, that'll give you the J-11.

So for me it didn't do anything, I can play VR all day, but I still get motion sick in a car if I don't look out the window. They're very different types of motion sickness though - VR is where you can see movement but can't feel it, in a car if I look down it's the opposite, I can feel movement but I can't see it - so I'm guessing the brain deals with the two differently.

So as I suspected, it's a 110-degree (or close to) FOV headset, only it helps users see all of the FOV instead of users generally only seeing about 90 FOV on average due to lense distance etc. Finally a no-BS statement that it doesn't have a magical 130 degree FOV without sacrificing PPD over a 110 degree headset. People might be disappointed that it's not a 130 degree headset, but for me this has finally become a contender...

It's already been reported - edit the mission and change the date to 2000 and it'll work.

Just follow these rules for adjusting to VR and you'll be fine: Stop as soon as you feel remotely nauseous Don't start playing again until you feel completely normal NEVER try to push through - if you do, you can end up associating VR with being sick and you'll never adapt I wouldn't even bother with ginger/anti-nausea pills (I didn't), just give your body time to adapt.

Pretty sure it's a USB power issue - try plugging a powered USB 3.0 hub between the headset and the PC.

I mean, if it were me, I'd definitely try 1809 to see if there is a difference - it's pretty consistently reported in WindowsMR reddit that 1903 has an issue for all WMR headsets including the Reverb. You might just not know what you're missing out on.

Have you tried it in anything other than 1903?

And what would the map / tgp with ranging / guy with a fitbit tell you to help input the elevation in the Hornet? If they say they're at AGL 0, how does that help you?

And right now, assuming they take the advice in the last sentence, the Hornet will have no way of precisely knowing where it is and so wouldn't be able to input coordinates for the JSOW. Obviously that changes with the TGP, but it's not here yet.

The Hornet supposedly only got elevation data with TAMMAC in Lot 23, which isn't modelled in our version of the Hornet. So while your fitbit might know the elevation of every spot in the world, the Hornet being modelled doesn't.

I'm not sure what you're trying to argue to be honest - if the elevation is entered as AGL, then it *has* to care where the ground is, otherwise it'll have no idea where to go. If I enter the elevation as '1' at a point on top of Everest, and then '1' at a point in the valley next to it, how does the bomb know where to fly? One is going to be tens of thousands of feet higher than the other.

Join one of the servers where people speak and missions matter - e.g. Persian Gulf at War / Georgia at War for PVE, Blue Flag / DDCS for PVP, and ask people in voice comms what you should do / where you can be helpful. I play a lot of DDCS and the first thing people ask is 'what do you need?' and they get given a mission that fits their preferred aircraft/mission.

You can use AACQ (Sensor Select Right) to skip straight to STT.