Wicked.-

No problems here when ramp starting or starting in the air.I'll try the M2000 next.

I noticed a huge difference in the mirage but I can't see any change in the A10C. I typically use 45 but I've tried from 45 to 64 and don't really notice any difference. Is it just me?

After much reading on the Oculus forums, the cert that expired is the one that tells Windows it's authentic... make the new cert available for DL and provide directions for installing it. Nope, it has to go through Oculus which probably means a new .exe. Ridiculous.

I couldn't agree more.. I'm in sales and I'm expected to deliver on what I promise. Being held hostage after paying to own a product is theft. Unfortunately I had just installed VaicomPro and rebooted to start fresh and the Oculus went down. I'm like, son of a bitch! Hopefully Hollywood forgives me for thinking it was his software... I totally feel like an ass.

Roger that. I deleted my bitching post. My apologies Hollywood.

So, even if I didn't install anything new Oculus would not work and that just happened today? I've been flying everyday for the last month with no issues.

Roget that! I didn't know, thank you sir.

Yep! That's what it was. Radar Elevation was defaulted to slider on my Warthog and it was not in the center. It's working now. Thanks,

Yes it is. While using the radar in the M2000 in any mode, the radar elevation will NOT remain where I set it. Most of the time I want it straight ahead scanning an altitude zone from 25,000ft down to 0 feet and my altitude around 12000. This should be no problem. However within 30 seconds to a minute, the heads down display shows the radar is now scanning -66 -66. Or 66 feet below ground over 66 below ground. I can reset it by centering the radar or TWS unlock but it will not hold center for more than a minute.

I am.

For whatever reason my radar will not stay centered in either RWS or TWS. It also doesn't matter what bar scan I use. I'll be flying along and it will trash out for no reason and show -100 over -100. I have to keep centering it or hitting TWS unlock to get it back to the scan hieghth like 40k over 5 or whatever I'm scanning depending on distance. The range holds steady wherever I set it. Am I doing something wrong or I'm I bugged? Thanks for any help.

Stutters for me. Reverting back.

It changes the size of the world around you. In other words, it makes the cockpits the same scale as your perception would be in the real jet. I ended up setting mine to 45 and now the Mirage feels like I'm wearing it which is how it should be ;) . My Warthog stick and throttle are in the same place in the real world and the virtual. Hope that makes sense lol.

I downloaded the offensive weapons and also the whole user made manual and will go at it again tonight. The radar altimeter not giving an accurate read makes sense and that's what I thought all along. That being said, the F16 is totally different and more automated and I'm guessing because it is truly a digital jet (unlike the A10C) and can process the radar returns quicker giving a more accurate solution. I mention this because I'm coming from BMS and old habits die hard. All I know is I'd like to hit something! lol it's pretty sad when I can't get an 87 close enough to take out a squad of infantry on an open hillside..

70 degree dive angle! Lol nice!

I can understand the bomb won't hit in the middle of the X but I would expect them to land within a couple hundred yards. Otherwise what's the point in carrying them? Every hit would risk collateral damage.

Thanks for the responses gents. I'm dropping dumb bombs. CBU87, CBU97 and Mk82's. The last time I used laser guided all worked. I'll try the BAL/ORP settings tomorrow. I also get crazy release angle drop lines with CBU97. The line wants to stay slanted 45 degrees like I'm dropping a nuke lol.

If this has been discussed before sorry for the new thread. I've been flying the A10C missions and for whatever reason I cannot get a good hit. I've read the instructions in the manual multiple times and understand it. I've flown Falcon for 18 years and I know how to use CCIP and CCRP. To the best of my knowledge I understand how the A10C is modeled at least according to the manual and I am doing everything exactly how it says. But, no matter what setting I use (CCIP, CCIP CR both 3/9 and the other and CCRP) the bombs fall short. I've tried different altitudes and dive angles, setting SPI and using CCRP. Doesn't matter; they always fall short. I have to designate past the target and make a guess on where it will hit. Can anyone tell me what I'm doing wrong? Or is 2.5 bugged in this regard? I'm using a Rift BTW. I've spent 4 days reading the manual and trying everything I can think of. I'm using the stock missions that come with A10C and many times I start off in the air. I know how to make the standard changes to the profiles but am I missing something else? Many times I'm bombing on hillsides. Would this have anything to do with it? I would think that CCIP and CCRP both take into account the radar altimeter when calculating the release. Any help is appreciated.

Hmm. Food for thought. I have the Asus Strix 1060 and have been trying to find a 1080ti but I may consider the 1070.

Yeah, but I will be flying! Anyway, I'm good with the Rift. The weird thing is, the Rift I picked up today can't handle the settings of the one I took back Saturday but it's more comfortable. Go figure.

Yep. Took the Samsung back today and got another Rift. I'll work on making it more comfortable.

Thanks for the reply but I don't use Steam. I use the desktop version of DCS World. I'm thinking the Windows Mixed reality HMD's are only good for Steam.

Are all of you using Steam? I use DCS World locally on my computer and the Odysey does not work like the Rift. Basically I'm sitting in the VR living room with a window hanging in front of me running DCS. With the Rift, it fires up and I'm in a hangar standing next to a Mig 29 that looks like I can touch it lol. I've looked for settings to change this but no joy other than the VR tab which is checked for using VR as a display. ?? Unless someone else knows how to fix this it's going back. I'm using 2.5 beta as well. Any help, is appreciated.

I bought the Odysey today but had to reset the PC because the mixed reality app would not start. Gave me an error code of H0002000-0. After some searching, many people with this issue got it to work by updating Windows. No joy for me so resetting Windows now which was the other fix. I'd planned to do this anyway as I'd been having weird issues from all my tweaking. I'll update once it's installed.

Great write up! I bought my Rift Thursday and after a good several hours of flying with it I'm ready to take it back. I got to where I dreaded putting it on. I have to pull it down so far to focus, it kills my nose. If I could move it away from my face it would be good. Luckily, Best Buy will take it back no questions and the MS store is a half a mile away lol.