mhe

When quoting imperfect tracking, people usually refer to the tracking of the handheld controllers by the HMD. The headtracking itself is perfectly fine as far as I could find comments about it. So don't conflate these two, you might end up skipping an amazing HMD for DCS.

This right there. My personal "definition" of a 2nd gen thing would be resolution high enough to read any and all text in a DCS cockpit, no screendoor effect whatsoever, no god rays, a FOV of 130+. Since slightly above 4k makes sense, I guess this is what we will be seeing. I also wouldn't mind VirtualLink as the interface. For our specific applications, the tracking mostly concerns the head. But I'd be freakin thrilled if the expansion bay in the front of the Index would accomodate something like a Leap Motion but a bit better. Then we can click and flick switches in the cockpit without a mouse which I'd describe as DCS VR Nirvana.

Thank God for my bog standard 64mm IPD... so with Wags' announcement of the VR performance boost, this res actually might become manageable!

Definitely. But for those lucky enough to not be limited by their budget, it is all about the specs. Also, we don't know what the Index will be sold for, it might end up having a quite impressive price/performance ratio, even though I have no doubt that it will not be as affordable as the Oculus products which clearly target the mainstream.

It all comes down to what the SteamVR API in that leaked video assumes as 100% resolution. Iirc the Vive headsets have a default render resolution 40% higher than their render resolution. That would not necessarily need to be the case for the Index. The low res screengrab of the dev stream alt-tabbing showing 90% res being 1913 x 2125 would mean that the 100% res would be 2126 x 2361. If we assume that the 100% res is the panel res as well, then the 2 most likely displays would either be the BOE 90Hz panel doing 2160 x 2376 or the 120Hz JDI one doing 2160x2432. However, if we assume that the 100% resolution actually is the same 40% higher than the panel res as is the case with the Vive Pro, we would end up with the exact same panel res as the Vive Pro. In my opinion this would be highly unlikely: 1.) Gabe was unhappy with the HTC products so far 2.) The significant rise in FOV (rumored to be around 130-something degrees) would make the pixel-per-degree res LOWER than the Vive I think that the panel res equals render res for the Index - if the same 40% additional rendering res would be applied to these assumed high natives resolutions, we would end up with 3024 x 3404 and 3024 x 3326 per eye respectively. I can't see any current-gen GPU rendering anything at these resolutions, let alone at 90 or even 120fps. My money still is on one the BOE or JDI panel. The only thing that I find a bit contradictory so far is the minimum requirement of DP1.2 if the leaked PCBs showed chips capable of dealing with DP1.4 streams and bandwidths - which would no doubt be required to panel such beastly panels in any case - UNLESS that chip can also do scaling (which would add latency). I am very much on the fence for the Index and can't wait to get my hands on conrete info, but so far I don't see this releasing with "just" Vive Pro res, Reverb res or better would make so much more sense, especially for the rumored targeted FOV.

Nope. It will be most likely be higher. The circuitry analysis of the leaked PCB pictures shows DP 1.4 signal processor chips. I guess Valve just listed the bare minimum spec to run it, which will be DP 1.2 but that does not necessarily mean it unleashes the full potential. I think resolution will be on par with or better than the Reverb. You can run these at half res and have the HMD to some scaling methinks, which would solve the bandwidth problem for the lesser DP revisions. Also, this is Valve's own thing, everything we know about all the previous stuff with HTC etc does not apply here. And they want to make it the launch platform for the next Half Life in all likelihood. Valve don't need the money (they are one of the richest company per employee capita in the world already), they do it for the sake of doing it because they want to.

Update: Seems to be shipping on June 15th See https://uploadvr.com/valve-index-vr-headset-listed-on-steam-apparent-june-15-ship-date/

Can we PLEAAASE, after all these years, have this thing as an official module or baked directly into vanilla DCS? I'd even pay for it to not have to mess around with updates, export scripts and all the things that come with it being a mod instead of an official module. Please, ED, make it happen. Pay the man.

It will work but I advise you use CaptZeen's export.lua The profile itself you can have here: https://www.dropbox.com/s/fv05bvdhtobm33z/Loz%20SM%20v2.1.rar?dl=0 Be advised you should also install the font it uses onto your system, that would be this one: https://www.dropbox.com/sh/b43q2ybbbpwsqaq/AAAMxquT4nu9wO-qW-JGaKnma?dl=0

Ok, so I have it running ALMOST perfectly now. However, the AMPCD still gives me a headache. I tweaked the MDG_strokesDefs.lua with the values recommended in https://forums.eagle.ru/showpost.php?p=3555460&postcount=117 and that works great for the DDIs. However, to affect the thickness of the AMPCD fonts, I have to tweak other values in the same file: -- Currently is used for DMC generated fonts black outline DMC_outline_thickness = stroke_thickness * 3 DMC_outline_fuzziness = stroke_fuzziness * 0.5 DMC_stroke_thickness = 0.4 DMC_stroke_fuzziness = 0.18 The values themselves are not the issue here, I can get these to be ok, my big gripe is that if I optimize for values that look good on the export, they look like crap on the 3D cockpit view and vice versa. Is there a way to have a nicely readable AMPCD both on the touchscreen and in the 3D cockpit at the same time? Running a 4K main screen and a 1080p touch underneath it.

Thanks for doing this, runs like a charm so far and I am super happy about Helios being developed further again!

You just put stuff like the scripts that modify the aircraft instruments into mod packages (works with JSGME or OVGME). When a DCS update comes, you don't update but hit "Later" instead. Stop DCS, open your preferred mod package manager, disable all mods, run DCS updater and let it do its job and once it's done, you re-enable the mods again with that mod manager. It is really not that hard but saves you a lot of time. Also, I got the bug with the super thick lines again on the AMPCDs and the MFDs. This seems to only happen with 4k resolutions for the main screen.

Get well soon, you can and will beat this!

You shouldn't do CASE 1 patterns in CASE 3 conditions (night).

What kind of chair is it in the previous pictures? Not the mat, but the chair itself. I am looking everywhere to find a seat with a stick cutout to fit to my Obutto.

Running a 4k screen by any chance?

Probably related to the bug were the DDI fonts were rendered weirdly if playing at resolutions of >1440p? I have the blurriness as well but I use a 4K screen.

Very interesting, thanks!

That is what the T/O trim button on top of the rudder trim knob does and it is correct and realistic for land takeoffs.

Does the AIM-9X do anything different to the M version in the absence of JHMCS? Or is that stuff almost ready as well?

Is there no way to just disable the Pimax tracking? TrackIR side is easy, just set to 1:1 and you should be golden.

Also, will the analog mini stick be pushable? Hornet for example requires ability to depress the TDC. Will that be a thing?

Glad that there is someone out there sharing the experience! I wasn't using OB at the time of 2.1, I only started using it again for 2.5 so I can't say what caused it. All I know is that at some point in time, the LUA stuff started to cause a massive performance hit making using stuff like Helios a lot less viable than it used to be. And that is a bummer, because I freakin LOVE Helios.

And the ISA standard atmosphere actually assumes 0% humidity. If somebody is interested, the quick n dirty formula for calculating Mach 1 speed is 38.95 x sqrt (ambient temp [°K]) => Mach 1 as TAS in knots. Not super scientific precise but for practical purposes (and passing any kind of aviation exams) more than good enough. Going to km/h from there is simple enough not to need an explanation methinks.

Only the binding that goes on the mouse is called TDC. The one that allows mapping for the analog ministick of the Warthog throttle is called "Throttle Designator Controller" vertical and horizontal axis respectively. So just no acronym but it works well.