backspace340

You will also need this: https://store.steampowered.com/app/719950/Windows_Mixed_Reality_for_SteamVR/

Yep just rearm before you takeoff.

Could be worse, think I once had '148,000 feet, scratch that, 1,000 feet'.

Have you played the mini-campaign that ED did? Just go to Campaigns and F/A-18C and you should see it - called Task Force Challenger I think. Those are all hot starts. For the M2000 campaign, you can auto-start, and stick 120s on if you like - just use the radio and pick ground crew and rearm/refuel and pick 120s.

I'm not actually 100% sure the Block 50 F-16CM could carry these in 2007 but it seems like it *may* have been possible, so this is more of a request for some of the SME maintenance guys to chip in and confirm either way. From a bit of detective work, I have found these photos of block 40 USAF Vipers carrying the laser Maverick over Iraq in 2007: These are from the 4th FS from Hill AB, and the middle shot with a laser maverick is serial number 89-2143 (if that matters). As far as I can tell, these birds had the CCIP upgrade at the time of the photos - this link says 'Hill's 4th Fighter Squadron was the first to fly CCIP F-16s in combat in August 2007'. The question is, if a Block 40 CCIP Viper could carry and fire Laser Mavericks in 2007, would a Block 50 CCIP Viper be able to?

Wags said in Youtube comments that the version we're getting has an IR seeker, but it'd make no difference to how it works in DCS - the version we're getting just has 'scene-matching' (which I'm guessing means it'll compare against a reference picture of the target to improve accuracy). They're not going to bother modelling it, as it makes no difference to accuracy in DCS and they've got bigger fish to fry (I'm paraphrasing).

PSVR is 120hz

Patriot can too, Roland is currently not engaging successfully in OB: https://forums.eagle.ru/showthread.php?t=242191

Not completely sure that's true - the Command Center object is used on DDCS and only certain weapons can damage that. Generally 1000lbs and up (though the bigger Mavericks, and Kh-29T can kill it too). 500lb bombs don't do anything (even if you drop multiples).

Yes just change the drop down to both - this isn't a bug.

Yes and I guess it's the same label for either, in this instance it'll be the Litening.

Two things - 1. You don't have to run any BITs or fire tests or anything (assuming you have random faults off), there are no negative consequences from skipping them in DCS. As long as you press the T/O Trim and FCS Reset button on a field and set your flaps to half, you don't need to do anything else to have a perfectly normal take off. 2. You can cause a 'mad climb' by setting your flaps to auto before takeoff. I'd suspect the problem lies there - but a track would help confirm what's going on.

Wags has given us a preview of this in his new video: First 30 seconds or so:

Rolands are used as a valuable Blue point defense system in multiplayer matches (with the SA-15 Tor being used as their Red equivalent). Until very recently, these systems were fairly closely matched in their abilities to engage missiles fired at them or near them. However in a very recent patch (possibly the last OB update), the Roland has stopped engaging missiles. To reproduce, set up a Roland group with 1 EWR and multiple ADS's, set to Excellent AI (you'll see the same behaviour on all AI settings), and then fire one missile at them. The Roland doesn't engage (it looks like it tracks the missile sometimes, but doesn't fire). I've even added the task to engage air missiles in case that changed anything, but it doesn't. I've attached two tracks - one with a single HARM fired at it, one with a single Kh-58u. Neither is engaged. rolandHARMs.trk roland.trk

If you use it on an axis it can be used to basically pick your landing spot - I've got it set to the Y-axis on the mini-joystick on the TWCS throttle, so can just apply as much / little as needed. Really useful.

They're both 4m apparently (only 3.5m for the pre-release ones the reviewers all got), but I sit clear across the room from my PC when I play and have 10ft extensions on my 4m Odyssey cable, so will definitely need it for the Reverb. That guy on reddit did say it's a heavy cable and not very good for roomscale.

Yeah hopefully - I've run the Odyssey at 1.5PD and that was fine, so I'm quietly confident it'll be okay. I'm mainly waiting to see how that guy gets on with extensions - I've got to extend any VR headset by 10ft, and the Reverb QA guy said that couldn't be done, but that guy on reddit is going to try it. Really hope it works so I can get the Reverb!

This guy has it and plays DCS:

That's kinda what's happening here - the person charging for lessons is a Youtuber, the person offering them for free (Lex) is a genuine ex-Hornet pilot.

There's a couple more things that might be handy to know - when you're in the cliff house you can move around with your mouse, just hold right-click and a teleport circle will appear, move it where you want to go, mouse-wheel moves the little arrow on the outside and changes the way you'll be facing when you let go. You can rearrange any of the floating windows (like Desktop, SteamVR) by clicking and dragging the top bar, if you mousewheel while holding left-click it'll move the window closer/further away.

You can normally fix it by re-running the set-up (which doesn't need you to shut anything down, you can run it while DCS is running). Go to WMR's app, then run setup, pick seated, look forward and click centre and it'll snap back to 6DOF.

#5 doesn't happen if you launch the game from inside the headset - press the Windows menu in the cliff house and bring up the Desktop from Apps, then launch the game. You'll never see that issue ever again (even without the sensor covered). If you get used to just using the virtual desktop it also makes #2 a little easier - as you can re-run the setup to get 6DOF back without taking the headset off, just alt+tab and press Windows to bring up the Cliff House & Desktop, then run the set-up, then click the SteamVR window and Alt+Enter to go full screen. I don't even bother turning my monitor on anymore, just switch the PC on, stick the headset on and run everything from there.

https://discord.gg/ctBxdJu

The difference there will be the FOV - 'Normal' FOV in the Pimax is supposedly 150 or so, it's smallest is around 125, the Rift only has 110. The Pimax is a lot more taxing on your system because more of the game is being displayed and so more objects need to be drawn.

I can see why players would want that (especially for MP balance), but I'm not sure there's much of a reason for ED to do that. They can't ask everyone to pay again / extra for FC3 in order to pay for engineers to do it, and there's nothing broken about the modules, they're just lower fidelity simulations (which is what FC3 is meant to be anyway).