unipus

Thanks all! And yes, I saw Heatblur's post -- it was motivating to get me to hustle up and finish this, since I first started plucking away at the idea a while ago. Given the positive response (much more than I expected!) I guess I'll have to make more!

Tried this out for a bit - noticed that very often units are spawning close enough to each other to immediately collide on mission start. Player and AI units alike.

I'm sure I will do some more at some point, although I think whatever I do next will be rotary.

Got motivated to put in some real time on this video I'd been meaning to do. Thanks to those of you who helped me work on my lacking bombing technique a bit! Yes, I forgot to jettison tanks. No wonder so many brave pilots didn't make it back!

Well that's a relief. I thought I was taking crazy pills. As it is I can now usually get it close enough for guesswork and hit some targets, but it's sure not ideal.

Update: still no luck on making this work. Selective malfunction. Sensor mode hat, weapon selector, cage/uncage all work perfectly fine on the exact same device. DCS detects trigger stage 2 in binding screen. Weapon will not launch. Master arm on, A/A mode on, SHOOT cue on HUD. Have not yet tried A/G weapons (of course that's a different button).

Having the same issue, but only with a few. Mostly unimportant stuff like oh... GUN FIRE. Can bind it, DCS clearly detects it... simply doesn't work in-game. This is after applying the cb13 fix described elsewhere to get my bindings back but as said, I can clear out the binding and reset it and nothing changes.

Agreed. When you wait many months for a product you paid a chunk of money for, any issue is frustrating -- but on the whole I've been more than satisfied with my GF/MCG Pro and the level of customer support.

Related question: is Vegas ever going to get, y'know, Vegas lighting? Pretty hard to feel like you're really flying anywhere near the brightest city on Earth when it isn't. I know this is a pretty fringe thing but hey, it wasn't my call to make a Nevada map!

I've been trying for the past two hours to do the ol' DCS_updater.exe update @openbeta Every time (after downloading about 4gb of data, usually) I get the following error: 00043.745 INFO : INSTALL Bazar/shaders/metashaders/edterraingraphics.conf 00044.786 STATUS: Shutting the torrents down... 00044.787 INFO : Kill timer set to 30 seconds... 00044.844 INFO : Torrents have been shutdown in time. 00044.844 INFO : Kill timer reset. 00044.850 ERROR: Can't move F:\DCS World\Bazar/shaders/metashaders/edterraingraphics.conf to F:\DCS World\Bazar/shaders/metashaders/edterraingraphics.conf: (2) The system cannot find the file specified. I tried running a repair as well and had the same outcome. I've disabled anti-virus, I've restarted, I've repaired ownership and permissions on the entire drive DCS is installed on (not my C drive). No luck. Out of ideas, other than deleting everything and restarting, and not even sure entirely about that working.

I'm pretty curious about you guys running touch controllers at all. What are you using them for? How so? Seems like fumbling around for them, taking hands of HOTAS, while blind would not be super fun. It's already bad enough reaching for the mouse now and then but maybe I'm missing some technique.

You're right, I did it earlier in most of these runs. I'm not sure this explains losing the HUD entirely, though. Like I can generally watch it slide off the top or bottom of the glass in a hurry. The only thing I see that you're doing differently is the degree of dive, which here looks like about only 10-15 degrees (that low I'm surprised you didn't hurt yourself with low drag bombs!). I've been coming in anywhere from 30 to 70 degrees. Edit: I see two other systems differences, one is that is you switch your HUD to low mode. I thought high mode was to be used for dive bombing. The other is that I have not been disabling target motion ranging (221), but again I doubt how that would have a drastic effect like this on the HUD display.

After flying a good bit of Viggen, I ended up taking almost a year off from DCS until 2.5 released. Now I'm back at it, and having a problem I don't remember having before, at least not nearly this bad: the HUD data is often sliding way out of view. I know this is to some degree inherent in the design but here's what I was seeing yesterday: Trying to do dive bombing. Weapon selector DYK, radar mode ANF, target waypoint set, QFE set. I see the target waypoint O in my HUD. I climb, roll out, then go into a dive with trigger safety released. And the HUD slides right by at the exact moment I need it. More often than not I'm looking at a completely blank HUD after about 8 tries at different degrees of dive. Checked Chuck's guide to make sure I wasn't missing something. Watched videos. Really not sure what I'm doing wrong, or is this a new bug?

Dunno man, all I can tell you is that I found it very difficult to effectively use a few readouts (such as the distance to waypoint) that can be pretty important. Zoom certainly helps but not with everything, and it's slow so using it in tense situations is not ideal. I'm currently up at PD 2.2 and don't have this problem anymore -- of course now I have different ones. Still, it's all worth it.

This is the page I found that covered it all in detail and was exactly right. http://forum.vkb-sim.pro/viewtopic.php?t=2883 If mine backs out again (this took about 50 hours of use to manifest in the first place) I'll just Locktite it.

Do you want the player aircraft to have waypoints to the FARPs? It sounds like part of the point is plotting your own course. If that's so, then I'm not sure I see why you need to select any of them at all... just tell them which to use and it's up to the player to sort it out. I suppose you might want a trigger zone activated over the correct FARP or the incorrect ones to provide feedback; that's easy enough to do but let's understand the intent better first.

Depends on the aircraft and your pixel density. Get it up above 1.6 and almost everything is readable if you lean in a little. Below that and you will have some problems even with zoom in some aircraft. The Gazelle is the one I recall having functional problems with -- also one of the best cockpits for VR aside from that issue though.

Yeah, I've used it in the past on another machine; didn't love the experience and don't love not knowing what things are bound to from within DCS but oh well.

That one looks like VKB's other 8-ways. (personally I don't care for 8-ways, but they're not bad) I'll continue to follow the news on this one though. I own two of VKB's other products and have by and large been very impressed, I'm sure this will be no different.

Picked up an X-55 throttle for super cheap while I wait to see the outcome of the Virpil/VKB offerings, and for the price I'm definitely not disappointed. However, the thing is literally covered in knobs and dials -- none of which I can seem to get DCS to recognize as valid axis. Is this something I have to do through external software only? So far I've managed to avoid that but having 5+ controls at my fingertips doing nothing is prodding at me.

If you don't really need something right now, I'd wait. I expect there will be some major announcements about new hardware from Oculus and probably others, coming out before the holidays.

Very good review. I've also had one of these since release. I notice the same tendency with the grip extension for the stick to want to lag slightly rearward on the Y-axis, which concerned me at first but doesn't seem to have any practical impact in flight. Even hands off stick I see no issue. One thing that did happen to mine recently was the base of the grip became loose and it gained about 10 degrees of clicking back and forth. Not good. This turns out to be a documented issue of a screw inside the grip backing out over time. It can be fixed in about 10 minutes (assuming you have a screwdriver that is long enough and narrow enough, I had to go get one) but it's a shame such a basic problem is occurring on a high-end piece of gear like this. In any case support was very forthright and helpful about this and any other issue I've seen. I also have the Mk IV pedals plugged into the black box and highly recommend those as well. Super solid.

Excellent, thanks. Only just discovered the whole Set Option section, which really feels like it ought to be a lot more prominent given how many critical options are in there! But now I know where to do tweak some very handy settings at least!

Follow. I'm anticipating a new generation of VR hardware announcements by end of year, but in the meantime I prefer CAS to CAP so it'd be great to get any advantage here.