Jyge

Yeah, I got it gradually figured. I have already packed my Rift in the box and stowed away. In due course, I will sell it. The picture quality is significantly better than in Rift. Particularly the readability of the cockpit gauges. Well it is not too comfy, but I sat today in front of the sewing machine and made few straps that allow me to wear it like a hat, the damn collar is not squeezing my brains any longer. I just fear that one day they release a fix and my lenses go suddenly all slanted and I need a multioptipupiloptomy...

Odyssey or Odyssey+? Got myself O+ last Friday and felt blessed cause I did not have "The problem" - I have fear, however that when they try to fix it, they might break it for some, as well. For that reason I am not immediately going to put my rift in eBay. No, I played last night about 7 hours back, I had no problems - damn shame, great picture quality in comparison to rift.

Do you know if there is a simple tool like the cross in Rift for getting the IPD right? What benefits do you get out of the motionvector parameter? Still not sure about Pimax doing more than increasing FOV, as it features less vertical pixels as O+, so might be that O+ will serve well enough for 2019...

I also got myself O+, I think I got it roughly setup now. I think I put it to 200% under the video and left the application alone. Anyway, I have seen some people also upping the PD in the game. Once I did it up to 1.4 I start getting some lag in tracking. There is also a little bit of hesitation with 1.0, with that I get solid 45 fps, with 1.4 it went to 27 fps, no real visual difference. I have GTX 1080ti and i7-8700k + 32 GB RAM. Anyway, I already packed the Rift away and I am going to sell it after awhile I think, if nothing adverse pops up - thankfully I do not have any cross-eyed probs. O+ is not revolutionary better, the cockpit is a bit clearer and some things like HUD are actually bit less sharp, but I think I can do something about it. I think I can still improve things once I get to know O+ a bit better.

I think 15 pages of "VR improvements" clearly hint that that there are quite a few wishes to satisfy the VR crowd, other than merely "give me 90 fps, or I will shoot the rabbit."

In fact odyssey+ features a higher vertical resolution as Pimax, so it is actually a good question if Pimax is going to provide any improvement in instrument readability over Odyssey+ or Vive Pro

Getting motion sick in VR is in the nature of things and has little to do with fps. Many professional pilots do experience sickness in the professional set-up, also in a half-dome kind, it is not something new, popping up with VR. It is a simple matter (or actually pretty complicated) of your sense of balance not agreeing with your eyes. It is equally nauseating in instrumental flight your gut not agreeing with your instruments. So do not expect finding a universal cure in fps. Some people are always going to remain prone to nausea, whatever the fps.

I think I am not that far yet. I am going through the basic set-up and confused about all software parts. I found this I am a bit confused. I did not take (consciously) the step for steamVR beta and I installed something else for windows virtual reality as the software mentioned in the video. Nevertheless DCS was running. I guess "sitting setup" is good - the curtains sometimes disturb me in Rift. I need to check some things - I am back in front of rig tomorrow - it might be that the settings changed and the motion blur got switched on, or something - or I am running Rift software parallel and it is tracing headset that is in the drawer (my rift sensors) are still connected... I saw the tweak post, but could not even find the setup until I saw this video: So I guess, I gradually have the missing pieces. Start steamVR from steam window top right and DCS Over skatezillas manager (I think there is a rift checkbox there I need to deactivate too) Also, for Rift for adjusting the distance between eyes there was this cross ' could not find anything alike. Then, the steamVR home tutorial or so I could just look around there was a smashed tv on floor but I could not really do anything (controllers were there, none of the buttons did anything and nothing was said - strangest tutorial, I have to say), a bit confusing, all of that.

I got myself an Odyssey+ and now I get bits and pieces here about tweaks and steam and so on. I have had a rift for awhile and now I got confused with different virtual reality home screens. One from Windows, I think and then there is the second one from Steam? I was able to start DCS and get a picture, and now I am off for weekend, so I have no time tweaking. I managed to notice that I have serious lag in head movement, in comparison to rift, so I assume some setting is not right. Maybe my Rift sensors are mixing with it as well? Are there step-by-step instructions for Odyssey+, what to install, in which order and where to set-up pixel density and stuff like that?

I think that is not exactly what I am looking for. I would like to have a text overlay on DCS game window, like fraps does it with frames, showing a short message.

Is there a utility that would give little text messages. I would sometimes like to get some acknowledgement what I just did. For example, I have some SEQ-commands, maybe for different modes or CM profiles. It would be nice if I got a text saying "CM Profile 1", or so, instead of looking it up from Cockpit switch positions, which BTW in VR are not always that clear...

I was not really interested in Mirage but bought it anyway from the sale as I had no better ideas. I absolutely fell in love with it. I flew tutorials, absolutely I loved the âccent, I have worked years with Frenchies, I felt so at home with it. And it is so nice to fly. I love the avionics, the ILS and virtual runway so nice. Towards the end of the campaign I already felt quite confident with it. Couple of mig-29s bring them on, first gets the missile and the second gets his azz chewed with the gun, no sweat, did not even feel the pulse raising. Oh no real problem with VR and Rift. I do not think Mirage is that bad at all. The cockpit layout is pretty clear, not at all the worst one around there - it is rather the VR goggles that I find wanting. I forced myself to get started with Viggen before doing the second campaign, this way I have something to look forward to. One of the best buys for DCS I have made.

I am pretty sure it is RB-04E in that mission. Yes, left side CM pod, right side missile. I tried both IMP and salvo I should think, I struggled quite awhile with it. Ok, anyway, good to know, I will need to test it again...

I downloaded yesterday this navigation tutorial from JohnXX (link in youtube). I wanted to test the chaffs&flares so I reloaded a CM pod for left side instead of the anti-ship missile. Well there is this boat on waypoint 4 and I wanted it to go sleep with the fish, but the remaining rocket would not fire. C&F were working ok. Now, there was something about mixed load-outs and so, but to me it looked more like a bug if CM pod blocks the other side pylon from carrying ordnance... Anyone else with the issue. I did not retest it again...

So first button row ready and functionality checked. Progressing to the second one (brushing up my rusty soldering skills again):

Ah, ok so I am chasing ghosts here. Damn, that's irritating. Well it is understandable in some respects as Viggen is already a bit older I think and the logic with clickable cockpits is still evolving, but yes it would be nice if they patched it to left click - right click logic.

I am stuck with Viggen. Formerly, I did something with Mirage - it was rather easy - I could find the buttons from clickabledata.lua and do my changes accordingly. I am, however stuck with Viggen. The clickable data looks a bit different from Mirage. For example, I would like to have separate On and Off buttons, better to map that way to Warthog HOTAS. One example would be like radar altimeter, Barometer vs. Radar Altimeter switch. It is an On/Off toggle. In clickabledata we have: elements["HojdSI-PTR"] = default_2_position_tumb(_("HÖJD CISI"), devices.FLIGHTDATAUNIT, 3200, 324) In default.lua there is: {combos = {{key = "X", reformers = {"RShift","RCtrl"}}}, down = 3200, cockpit_device_id = devices.FLIGHTDATAUNIT, value_down = 1.0, name = _("HÖJD CISI"), category = _("Navigation")}, I try adding the separate buttons, for example, with: {down = 3200, cockpit_device_id = devices.FLIGHTDATAUNIT, value_down = 1.0, name = _('HÖJD CISI RHM - Radar Altimeter'), category = _('Navigation')}, {down = 3200, cockpit_device_id = devices.FLIGHTDATAUNIT, value_down = -1.0, name = _('HÖJD CISI LD - Barometric'), category = _('Navigation')}, I have been trying up and down putting them both to -1 or 1 respectively, the best I can achieve is two additional keybindings that just toggle the cockpit switch on and off. Would it help to remove the original toggle mapping?

I stared with Viggen today and I want to adapt my Warthog profile for it. I found some additional keybindings but I am missing separate on and off commands for some actions. For example, I would like to switch separately for barometric or radar altimeter and program that to the warthog switch. I found the stuff in in default.lua but I am not able to separate On and Off - the format is little bit different from, for example, Mirage. How do I separate from: {combos = {{key = "X", reformers = {"RShift","RCtrl"}}}, down = 3200, cockpit_device_id = devices.FLIGHTDATAUNIT, value_down = 1.0, name = _("HÖJD CISI"), category = _("Navigation")}, two separate commands for barometric and for radar altimeter? Edit: I took it to Input and Output discussion, it is that general that someone who does not read Viggen subforum can still answer that: https://forums.eagle.ru/showthread.php?p=3754772#post3754772

Is there actually a limit to the number of joysticks that DCS supports?

I do not get the whole thing actually, I got the Oculus Controllers and they are nice and all that, but most of the time I want to have my hand on joystick and can not really let them dangle from the wrist-straps or something - so they are stowed. I defenately do not want to try using them as HOTAS (which option was sort of hinted by ED) - for that I want to a solid piece of joystick with proper sensors in my hand, I do not think the optical measurement will come anywhere near the HALs in accuracy. Glove would be nice, but maybe I would like to switch it off at the moment I grab the stick. I would be happy with one single finger tracking as well (well maybe two - for left and right mouse clicks :)).

So, I already asked this. Would the current resolution suffice for a better picture only if it was rendered better? If we even now had a still image and rendered it in Rift like no tomorrow, would we then see the picture more clearly with no SDE? Apparently, Samsung is somewhere near enough with resolution, actually providing more vertical pixels as Pimax, so foveated would bring the boost as the necessary quality can be reached. I think HTC Vive Pro has about the same resolution as Samsung?

I could easily afford Cougar, that is not at all the issue, maybe I just like the hassle ;)

I am afraid they seem to be working a little bit slower on that one since the video. Apparently, they got re-prioritized to light-weight entertainment on standalone sets like Go and Quest. For pushing that approach, the Quest intentionally does not feature a PC connection and has own processing for its own games. The Rift 2 seems to be pushed back (maybe out of the way, in order not to hamper the standalone strategy), CES 2019 for Oculus is just about Quest-approach.

I got bunch of these: I only need to drill holes for the feet of the buttons to get them through and do some soldering on the back side. The tolerances are ridiculously small for wood. I yet have to see how snugly the buttons sit in the frame. Then I need to make some sort of box for the electronics as well...

I got an inspiritation and started tinkering myself DIY MFDs. I got couple of arduino pro micro controllers and bunch of different quadratic buttons and rocker switches. Now I am doing myself a frame for them. As I am too cheap to get myself a 3D printer I went the traditional way. Here are some WIP photos: Now my only dilemma is, whether I should now paint it black with airbrush or actually leave it and wax it. I mean beech is not that bad as a decorative element. Normally you pay extra for getting some wood on your dashboard in your car as a decoration, so why not in F/A-18...