eaglecash867

I understand aerodynamics well enough to know that it doesn't have anything to do with how IAS is derived in an airspeed indicator, and that stall speed on that indicator is not on a sliding scale based on altitude. You are free to believe what you want to believe, and post false information all you like. This is only a sim site, so you're not going to hurt anybody by doing that. When someone here goes out and wants to learn to fly in the real world, they'll find out very quickly what IAS is and how its derived. So, no harm done. You're not the first person to get IAS and TAS and/or CAS confused, and you won't be the last. Its all good. :thumbup:

Which is exactly what you are doing. :)

Well, I'll take my 27 years of experience with certifying and troubleshooting these systems any day of the week over vague mentions of unnamed engineering books. :smilewink:

The FAA is absolutely correct about IAS, for the reasons stated in my last post. :thumbup:

Yup, IAS doesn't vary with altitude or temperature. The airspeed indicator measures differential air pressure between the aircraft pitot system that is connected to the inside of the diaphragm, and the aircraft static system that goes into the airspeed indicator case. Any change in barometric pressure will be seen on both the pitot side and static side of the indicator, so it results in the barometric pressure having no influence on what is indicated on the instrument. Its a really simple device that makes it so the pilot doesn't have to make the calculations in his head. If his stall speed is 62 knots, it will always show as 62 knots on the indicator, no matter what his altitude is. :)

Like I said, if you understand how an airspeed indicator works, you'll understand how IAS doesn't change. Temperature really isn't a factor in IAS. :smilewink:

They should be able to open another ticket for you without a problem. They understand how tricky it is sometimes to catch something broken long enough to troubleshoot it.

If you understand how an airspeed indicator works, you would know that your opponent is correct. Now...can we all just get along and discuss things without getting personal? :D

Sounds like a USB power issue to me.

+1,000 :thumbup:

Or, it could just be that his brake pedal calibration got borked, which he figured out, fixed, and posted about two pages ago. :music_whistling:

This is all true. Test pilots train for a completely different job than regular pilots, and they have a completely different skill set and way of approaching things. That being said, a real world A-10 pilot is going to be a more reliable source of info than any of us posting on a sim site about what we "know". Seems to me the OP just had his aircraft overloaded. If you put a realistic load of weapons and fuel on the DCS A-10C, I think it performs just fine.

As it applies to the DCS mod, I think the TGP and MAV images come from the same basic area in the sim's code. So, if one is modified to show color, the other one will follow. Just a WAG on my part. :D

The mouse cursor in VR will always follow your head movement, until you move the mouse. When you have "use mouse" checked, the mouse cursor shouldn't even appear until you move the mouse. Once you stop moving the mouse, it should follow head movement for a few seconds, and then disappear until you move the mouse again.

I've experienced the same thing with mine, just because of how it settles into my face and puts the lenses too close to my eyes. I fixed it by applying adhesive-backed weather stripping foam to the face pad.

Looks like a classic case of the left hand not knowing what the right hand is doing. This sort of disconnect between what is being represented, and what the truth actually is, unfortunately is getting all too common.

The consumer and business warranties are the same as it turns out. The consumer side of the house was in the process of getting a replacement sent to me, but then they finally figured out that it was the pro and transferred me to their business division. Oddly, their business division is wanting to troubleshoot things by sending me a replacement cable...which appears to be on eternal back-order. The good thing about dealing with the business side though is that it is usually people in your same country, so successful communication has been a lot easier.

That's how they get ya. :ufo:

That's what I do too. To bring it up and page through it, I use my Xbox controller that came with my CV1. It sits happily next to my keyboard, and stays put when I interact with it. The Xbox controller is simple enough that I don't have to see where my fingers are to operate it.

Yup. If I'm really looking to be unhappy with something, and I put my Reverb on, I'm going to see the mura. But, what actually happens when I put my Reverb on in DCS, and can even run it at 4X MSAA in DCS with glass-smooth performance (tried it yesterday, and was amazed), any "mura" fades into the background of how awesome everything looks in the DCS world. Not even noticeable. Still waiting for my replacement cable from HP that seems to be on eternal back-order, but it was only affecting sound to the built-in phones. I have my wireless Sennheisers that I'm using now, and will probably continue using even after the new cable arrives. The cable is definitely troublesome though, especially when paired with the idiotic way that WMR has for dealing with screen burn-in. It doesn't just turn off the displays (which other, non-WMR HMDs also do), but it also closes whatever app it was that you had running in VR. So, when that incredibly finnicky connector on the headset gets unplugged when you're at low-level, whipping your head around to dodge the SAMs and gunfire, you automatically get kicked out of DCS. This is very annoying, so I'm going to experiment with the old cable and see if I can get a relatively cheap, but reliable CPC connector to work. I doubt very seriously that it will, but I'm going to try it anyway, and I'll post my results here. Might be a really long time before I can do that though, so don't anybody hold their breath, but I will be working on making this thing more reliable in hairy situations in DCS.

I paid roughly 1/10 the cost of an Xtal for a Reverb and although I got a much smaller FOV, the horizontal and vertical resolution are fantastic in that space. I also have MUCH better performance in DCS than I had on my CV1. I don't have any personal experience with the Pimax, so I can't comment on how it compares with the Reverb, except that it costs more. I have heard from people who have tried the Pimax that it does have performance issues, so I guess I would consider that a "scam". But, I also don't know what configuration settings the people who reviewed the Pimax headsets are using. The Xtal has a lot of impressive technology built into it, which seems to include all of the things that other VR developers have only had in prototypes. As the saying goes, you get what you pay for. I find my poor man's version of it, the Reverb, to be acceptable for the price. One thing that would concern me about the Xtal is all of the moving parts that have to all work in unison to give you basic functionality. When they all fly in formation, I'm sure it will be like a dream come true. But, if they don't, due to some bugged release of drivers (which we all know NEVER happens), you have a much more expensive paperweight for a couple of weeks while they fix the driver bug. It seems a lot like a helicopter in that sense. As long as all of those moving parts keep flying in formation, you'll be just fine. That being said, if everybody sat on their money with the Xtal and waited for the price to come down, or waited for the ultimate Holy Grail of HMDs (which is what the Xtal looks like it has the potential to be) there wouldn't be much reason for them to some day develop VR for the consumer market at a more affordable price. Its too rich for my blood, but I salute the OP for his pioneering spirit. I'm sure he'll be very happy with it from everything that has been published. The rest of us who are buying into the cheaper, consumer products are keeping that advancing as well. As others have already said, if everybody had a "its not ready yet" attitude, it would never be ready, because there would be no reason for developers to keep working on it for the consumer market. I look at this like investing. Although we may not necessarily be seeing a physical dividend, the money we invest in these products will eventually make them better and cheaper, which is money in the bank. The more of us there are that do this, the quicker that will happen. "No bucks, no Buck Rodgers." :D

Again...spoken like someone who hasn't even tried VR. Just flew another VR mission in the A-10C with my Reverb, and it was an amazing experience as always. So much better than anything you could ever get on a pancake. :D

Statements like this are always made by people who have never tried VR. The HP Reverb gives us incredible visual clarity, and the performance on the same GPU and CPU has actually increased because we no longer have to use super-sampling or increased PD factors in DCS. The only "scam" here is just like Wormeaten said. It fools you into believing you're actually sitting in a cockpit, when you're not.

If money isn't an issue, you can always get an Xtal. :smilewink:

I've gotten exactly the same shimmering/flickering of the text in the menus when I was using my Rift CV1, but it seems to me that it was brought on with a DCS update, and later fixed by a subsequent update. I found that when I had the shimmering/flickering of the text in the menus that I could make it go away by turning MSAA off. But that was a long time ago. I thought that issue was fixed. Try turning your MSAA off, just as an experiment, and see what it does.