Ourorborus

... Because apparently founders edition isn't coming to Australia!! Sent from my F8331 using Tapatalk

Before I converted to VR, I used Opentrack. It used my existing webcam (with blue and red filter stuck over the top), I then made a small bracket to hold three IR LEDs and 9v battery of the side of my headphones. It worked very well with 6DOF. Initial tuning took some time getting it adjusted but after that the only issue was replacing the 9v every few weeks (or sooner if I forgot to turn it off) I would have changed it to a researchable battery but I found a VR HMD on sale and never looked back. Not including the webcam (which I already had) the whole set up cost about $6AUD. :)

Agree. Sent from my F8331 using Tapatalk

Give us the option to put it in the corner and the yes..... Please don't put it in front of instruments or controls. Sent from my F8331 using Tapatalk

This... If effort is expended on the comms menu. Having only the agency you are tuned to is the absolute first step. I have always wondered who dials atc and then tries to talk to a jtac?!? Sent from my F8331 using Tapatalk

I use the warthog and would buy it again in a heartbeat. Perhaps I'm lucky and don't have any sticktion issues but it is worlds better than any cheaper plastic alternative. Virpil and vkb review well here but in Aust the cost is prohibitive and from what I've read the springs are much lighter than the wh. Strong springs are one the best bits of the wh and I would never pay more to go back to something light. Sent from my F8331 using Tapatalk

Thanks for the confirmation. I only used pimax as an example although it is high on my list as fov is important to me. Who knows what will be available when it comes time or how powerful the new gpus will be Sent from my F8331 using Tapatalk

Too expensive for me. I will wait until amd launch rdna2 and grab the card with the most vram I can afford. Sent from my F8331 using Tapatalk

I currently use a Lenovo Explorer which despite its shortcomings I find a great match for my GTX1060. My upgrade path is to get a higher end card toward the end of 2020 once the dust has settled from the Nvidia/AMD releases. following that I will probably look to upgrade my HMD next year. HMDs are very expensive in the antipodes so I don't have a lot of cash to try the various options. However I have, in theory come up with a concept to get an idea of the FPS I would achieve with a different HMD before purchase. When you adjust the steam VR PD/SS slider, it displays the effective resolution as well as the percentage. So if I set 100% I should get the 2x1440x1440 of my current HMD (or 4,127,400 pixels). If I set Steam SS to 1930x1930 then my pc would be processing 7449,800 pixels before downscaling to the HMD. If I ran this with my current HMD, would the FPS be roughly what I could expect from PIMAX 5k which has 7372,800 pixels? If it does I could make similar adjustments to test FPS on a range of HMD potentials without purchasing.

We do have that. It is called VIACOM PRO, and works very well. I wouldn't fly in VR without it. (And i wouldn't fly without VR). Even with my Australian accent, there are few phrases that aren't recognised. When they aren't I can simply say "take x" which is the verbal equivalent to pressing an F-key. ("take 1" = F1 etc). It is this reason I still have the comms menu appear instead of totally disabling it. And as far as buttons go you just map each radios PTT to the HOTAS, no need waste HOTAS buttons on F keys or wheel selections. Would it be great if this was part of the core sim? Hell yes but VIACOM is relatively cheap and I would much prefer to see ED devote time to fixing the horrible AI and ATC. I cannot comment on the Jester wheel in F14 as I don't have that module, but given how it looks I would disable it in a heart beat. The last thing I want in VR is a big wheel appearing in the middle of my view. As a military aviator/ATC of over 20 years, I want to maintain my scan while talking and holding a PTT down. I would support updates to the comms menu as long as it stays unobtrusive.

I have noticed a similar problem on some missions. Requesting the ground crew removes the wheel chocks fixes it.....

I fly exclusively in VR and use VIACOM PRO. The only reason i want to see the comms menu is for when VIACOM can't handle my Australian accent and I have to resort to "take x" commands. Hence I want it as subtle as possible. I get non viacom users might like the wheel, hence I suggested making it optional.

+1000

While it is true that complete darkness doesn't exist outside in real life, there is a definite difference between flying at night and walking at night. On any but the most overcast and moonless night far away from light polution, human eyes can adjust enought to walk around safely. However even on a fairly bright night, the visual horizon is not particularly discernible in the cockpit. On a dark night the horizon is completely invisible. This is why Night VFR is an endorsement part way between VFR and IFR. NVFR navigate by reference to the ground but use the AI/AH instead the natural horizon. There are also several dangerous illusions created in night flight due to the lack of a visual horizon. A good night effect is achievable in DCS but like everything lighting related the balance between inside/outside cockpit/ light sources/cockpit displays is screwy and appears to be different based on hardware.

If this is implemented please, please, please, make it optional. The Wheel is far too visually intrusive. The current design gives a "there if you need to look at it" effect. Especially so in VR.

I too found this a little weird but figured it was like that in the real jet. It wouldn't be the first odd HMI decision by Boeing.

A trick long known in the motorcycling community is to clean the inside of your visor with dishwashing liquid. Just put some on a damp cloth and wipe it on. leave for a few minutes and then wipe off. Could be worth a try on your HMD......

The biggest thing you should get with FFB is realistic trimming. i.e you hold the stick in place and then trim until you don't require any force to hold it there. This polar opposite to the normal simism of trimming whilst bringing the stick back to centre. Sadly I have never actually seen this implemented, hence why I gave up on FFB years ago.

GPS Altitude is only accurate to 10-20 metres (35 to 70 feet) and that is with a modern GPS. The standard for an IFR barometric altimeter varies around the wordl but 25ft accuracy is common. (with 50feet for VFR altimeter) So a correctly set Altimeter should be far more accurate than the GPS altitude. Hence why Baro alt remains the requirement for RNP......

Good find. The aircraft systems should be using the sensed altitude. However I wonder if the systems are calculating Density Altitude, which would be slightly different to Pressure Altitude as displayed by the Altimeter. Someone with more knowledge of the ME might set up a standard ISO day and test if the variance is gone. Of course I don't know if you can adjust the temperature gradient in the ME.

+1

My point exactly. They are not declaring BINGO they are declaring empty.

That's for base.... You still need $350AUD or more for the grip!!

Hell yes. I recently picked up a set and love it. Also have a num keypad mounted between them as a poor mans UFC. I have added small silicon bumps just inside the centre buttons on each side to help the feel. Then I just have to be a bit anal about positioning them before you put the HMD on. It took a few flights to gain the required muscle memory but wont look back now. I tap away on those buttons faster than I can type on the keyboard...

I found the MFD buttons were already mapped in both A10 and F18. Obviously the AMPCD is not mapped, but I use a spare assignment on my throttle as a press and hold "left ALT" . then all my left mfd buttons with LALT are mapped to the AMPCD. Since the F18 DDIs dont have topcorner rockers, I have the top rockers mapped to other useful functions. (Left Top left = AA/AG modes; Left top Right= BINGO setting; Right Top Left = HDG, Right top right = Course)