Rosebud47

I think that has to do with licensing/certifying Pitool for Windows. But as Highwayman-ED said: simply start DCS from desktop instead from Pitool and everything is fine.

voted to prioritize Vulkan implementation - everyone benefits of it and it´s needed to optimize VR performance in particular.

It´s the software to run your VR headset, like Pitool or SteamVR ...

recently I got the impression, that the judder and double images increases with increased pixel density ( PD ) in DCS. Increasing the render target by VR compositor and leaving DCS PD at 1.0 reduced the effect of stutter and double images/ghosting for me.

Understand what you mean ... Once I have read, that there is always a difference in native resolution and the render target resolution of the compositor to compensate a range of IPD values. So far I think, as long as the render target is in anyway increased, there should be no issue with predistortion, warping, different IPD etc., but honestly there is still a lot of mystery for me to understand the whole correlations.

It doesn´t make much sense to nail ED down to the post Wags once made about 50% performance increase in VR. First I think this statement was made euphorically on a personal level here in the forums, not as an argument to promote the sales. Taking this statement and reframe it as a "promise" is the usual selfish reaction, like a child wants something so hard. So let´s see things realistically. Secondly everyone who is a bit into VR and especially with DCS in VR knows, that there are many, many factors influencing the perfromance in VR and there not two similar systems and settings. Finally I observed an improvement in performance and visuals with the related patch, surely not in the area of 50%, but it has become better, not worse. Now, as the community blowed the whole thing massively up, it´s hard for ED to get out of the affair. The sad thing is, that this a great community and great developers, but the misinterpretation of the community, that there was something promised now leads to some distance between the developers and communities, which might show in a reduced communication between developers and the community, what is a sad thing. Just want to say, don´t take a happily made statement by a developer as a promise - I think we all agree, that the developers works on constant improvements for DCS in every aspect. And stay realistic and not like the selfish shitstormes in the internet. @imacken, I know you´re not one of these, so please don´t take it as a reply to your previous post, but as my comment on the situation in general.

Most likely the issue is been effected by enabling ´mask hidden area´ in Pitool. With the former Pitool versions the Pitool settings could have switched, when restarting, but with the newer Pitool beta 144, the Pitool settings could be saved. Another reason could be, if you have set in DCS´ Graphics.lua stereo_mode_use_shared_parser = true It is set to false by default, if set to true , there is a render issue on the left eye with my Pimax, but it is more massive, than seen in the video above. It is unlikely, but maybe it is caused by wrong IPD setting in DCS. Formerly I used to have set a very low IPD setting in DCS to have the world scale larger, but after reading some comments here about it, I´ve reset the IPD in DCS to my regular IPD of 63, similar to the IPD setting with the Pimax and the always observable flickering clouds are no longer present with the right IPD setting. ...I guess it´s the mask thing in Pitool

"Gen 1.5" sounds like it´s about some incestuous offspring :-)))... don´t know who came up with the idea of generations of VR headests?

just double the performance you´re counting for VR, then you should be fine. With VR there are regularly two frames per second rendered ( left and right eye simultaneously ). If you so will, the Index renders at 240 FPS. But please don´t tell anyone, that I have said this nonsense.

That´s all true and the many options with Pitool are appreciated, but is there really a need to adjust such as brightness for the left panel differently from the right panel, as the image in VR will be always perceived as one/ combination of left and right eye? To me it appears a bit like playing around with some easy to implement options, without the absolutely need for these options - but that´s more personal view, than complaining. Ironacilly the IPD setting is not separated for each eye - me too got an IPD of 32 / 31,5 ( eye to center of the nose ). @Icebeat take a look at attached link/spreadsheet for values. A few sides back in this thread, there are some detailed comments on editing the stereo.lua. It´s more experimenting from my side, than well-founded knowledge. With some things I might be wrong, like editing the native resolution of the Pimax in the stereo.lua, but editing the tangents and aspect in the stereo.lua does have an effect on the image. By default it seems to be a bit off for the Pimax, vertically pressed like putting a 4:3 picture on a 16:9 screen, which also has an negative effect on how the 3-D effect appears. But you should try to experiment for yourself and have some own conclusions... would be interesting to read of those. https://docs.google.com/spreadsheets/d/1q7Va5Q6iU40CGgewoEqRAeypUa1c0zZ86mqR8uIyDeE/edit#gid=0 Edit: BTW, sorry for the weird phrasing in the post before ... just wanted to foward a sudden thought on the matter while being busy with other stuff on the PC. While hacking in, some more thoughts came up and the fingers took control over the brain ... like Jackson Pollock style - I wasn´t drunk ... hahaha.

If the FPS counter of the Index shows 60 FPS, it actually delivers 120 FPS for each eye. ASW, Reprojection etc, is not meant to be disabled in VR.

I would say, the VRAM question is obsolete, as it always comes fixed with the graphics card. Choosing the graphics card only depends on your budget to spend. The best performing graphics card is barely good enough for VR. ... I´ve tested the Radeon7 for a week, which got the HBM VRAM, which promises much more faster than the double data rate RAM, but the GPU on the Radeon7 was less performing than the RTX 2080Ti, so there was finally no benefit of the high bandwith memory of the Radeon7 in DCS. The Radeon7 with HBM VRAM might be more preferable over the RTX 2080Ti with DDR VRAM when it comes for Video editing or other use cases than DCS World.

Single Player meanwhile. Neither have the time and focus in life on computergames, nor interest in Internet gossip, what unfortunately collides with online groups. I wish I had today´s technique and my simpit when I was in my twenties, in which Falcon 4.0 and Microsoft Combat Flight Simulator were the best sims on the market.

... ahhh, now I understood what this thread is about :-) Am now since one and half year with DCS -not so long than most others, but did not ever sit in a DCS cockpit without VR and HOTAS ... can´t imagine missing any of these.

That´s a very individual option to adjust with the new Pitool version, i think. Still am wondering about, why Pimax always separate their options from left to right eye? Like brightness etc. is also separated from left to right eye ... the separation would be a funny feature for chameleons, but humans? With vertical offset the viewport could be adjusted more precisely on how the headset is individually fixed on the face by wearing, by moving the viewport vertically, to maintain the natural focus line in VR when looking straight ahead, the viewport in VR should show accordingly and not off set.... nice little feature. Meanwhile I´ve set Pimax to ´normal´ FOV, to save some more performance - the difference between Large and Normal is really not so much and looking forward to a new VR headset, the FOV will be less than Pimax large FOV anyway. Adjusting the viewport angles in DCS´ stereo.lua to large- or normal-FOV tangent space of the Pimax gives me more the impression of an improved image quality, than vertical offset adjustment. Would be also interesting with which FOV the new Vive Cosmos will come. I like very much the idea of an internal ventilation system of the Cosmos, as I always have problems with misted lenses after some time of wearing.

I don´t think, that there is an opportunity to test the Index, but I´m already convinced, that it is a quality product. Will place an order, once it is available and sell my Odyssey+ backup headset to compensate the costs for the Index. Mainly the Index is more preferable over the Pimax is because you don´t have to worry so much with adjusting and optimizing the image quality and performance. Pimax driver and software is a long time work in progress and the fiddling will become more, when they release there driver software as open source. Despite of that, the Index promises a more comfortable handling and less worries about the need to optimize the experience by yourself, which finally gives more time to fly in DCS. About todays hardware capabilities to run at maximum settings in VR, I remember it wasn´t so long ago, since the hardware, respectively graphic cards become capable at all to run games at maximum settings at all. Before that point we had always to sacrifice in game settings to get a good performance with any card for regular 2D monitor games and particular high demanding games. So current situation with hardware and VR is nothing new... or let´s put it this way: regarding the lack of performant graphics cards and CPUs, VR brought us back in a time before the year 2000, in which the discrepancy between the performance need of particluar programs and available hardware was a common issue. That this issue back in time was solved at a certain point and the graphics cars provided the power to run every game with maximum settings and high performance, makes me quite confident, that the same issue now with VR, will be solved in future. To compare, we may imagine, that with VR and DCS, we now are back in 1996 with regular PC hardware and high demanding software titles.

I shouldn´t have posted, now after your replies, there is a 90% tendency that I have to buy the Index, once it is available ... hahaha. But I do appreciate the large FOV of the Pimax very much. @Alec your complaints for the Pimax in comparison to Acer ( or XTAL ) are true, but the difference of the Acer or XTAL lenses to Pimax ´fried egg´ lenses comes along with a huge difference in price tag at this time. Beside the complaints in this comparison, I have to say, that the Pimax large FOV works pretty good with having in backmind, that it always could be better, which then, depends on the price tag. The quality of large FOV, I guess, could be even better then Acer or XTAL, but this as well depends then on a price target. Also just to mention is, that I don´t have cracks in the Pimax. Well, the one I am looking for, would be like Index with large FOV of at least 150° at a reasonable price tag... maybe next year from another company, but the overall quality of image clearly will be better with the Index than with the Pimax. Funny thing with theoretical thinking is, that each time I´m running the Pimax in DCS practically, I´m going to love the experience it gives me.

From the start of VR the reviews of the headset, there was always the same set of arguments to value a HMD, to have more to say about it. For me only the graphics a HMD provide is of interest and I never understood why ´comfort´ or ´audio´ beside the VR controller or the tracking system was given the same value in argumentation than the graphics. Surely there are differences from one to another HMD, but for exampe ´Comfort´ for me is on a complete other level of interest, than the the graphical features. In all the youtube reviews, I always skip 3/4 of the ´blabla´ to hear some impressions of the graphics of the HMD. Totally agree to Brixmis ( also etherbattx :))) ), but you can get a quite good impression of a reviewed headset, when you collect and observe different user impressions. I´m not sure, if I will get an Index, still got it reserved, but coming for the 5k+ the advantages of the Index are not so much a step ahead and in case of FOV even a step back. Again 500,- for headset, which don´t give me more is really questionable. Whereas when coming from a Rift or Vive or a WMR headset of 1st gen. the Index surely is a recommandable upgrade. It would be also interesting to know, if you get ghosting/ double images in DCS or if/how the higher display frequencies could reduce shimmering effects with DCS in VR.

... so true, *sigh* blaming on someone or something works very well in the internet, to give yourself a voice.

Ja, witzig ist auch, dass ATI breits 16GB vom teuren und schnellen HBM Speicher auf ihren Karten verbaut und Nvidia nur 12 oder 13 GB vom langsameren und billigeren DDR VRAM beim Spitzenmodell 2080Ti, dabei die ATI Karte knapp die Hälfte von der 2080Ti kostet.

Das klingt schon fast romantisch, Manitu. Keynes hab ihn selig, aber ich glaube, von der Vorstellung, dass sich ein Markt von selbst reguliert, können wir uns langsam verabschieden. Die Preise werden weiter nach oben gehen, solange, bis sie nicht mehr bezahlt werden (können).

... es sei denn ATI orientiert sich an Nvidias Preispolitik. @Hind, bei allem Respekt, aber das ist Quatsch, was du schreibst. Die Spitzenmodelle von Nvidia lagen seit Jahren immer auf fast demselben Preisniveau mit regelmäßiger Tendenz nach oben, wenn sie neu raus gekommen sind. Erst mit den RTX Karten hat Nvidia jegliche Scham verloren und bittet jetzt nicht mehr nur für neue Iterationen, sondern für Leistung in Form von FPS zur Kasse; dabei ist klar, dass die Folgemodelle immer teurer werden, weil sie mehr Leistung bieten. Wie die Kollegen schon schreiben, ist Konkurrenz gut, aber Nvidia scheint sich herzlich wenig um seinen Konkurrenten ATI zu scheren, solange die neueste Nvidia Karte weg geht wie warme Semmeln.

Executing DCS from Desktop instead of Pitool works fine, without the need to load SteamVR-GUI.

With Pimax VR zoom is overlapping the images from left and right eye. Guess the issue is not so much depending on the canted display design, but more related to parallel projection, which seems to be standard mode with Index, but not with Pimax. Thanks for testing. Always found VR zoom useful for reading the MFDs in cockpit.

Does VR zoom work properly with the Index?