Razi

For the price ($190 CAD), I'm perfectly content with the Explorer. For me it is meant as a entry into VR to hold me over until the next Gen of hardware comes out. I got lucky (I guess, depending on how you look at it!) because my unit came with a dead pixel in the right lens in the bottom left side. I submitted a return request, but instead I got a full refund and was told I can keep the Explorer! So I actually got it for free and thankfully the dead pixel is far off to the side and I only notice it when I try to look for it in dark scenes or menus. Setting up the Explorer on Windows with the Mixed Reality Portal is simple and straightforward. Getting DCS to work was not what I expected and not as straightforward as I assumed it would be, but simple once you figure out what your supposed to do. DCS (even the non-steam version) has to run through SteamVR. So Steam and SteamVR have to be installed. Then "Windows Mixed Reality for SteamVR" has to be installed in Steam. Lastly, you have to enable VR in DCS. Now every time you start DCS, Mixed Reality Portal starts, then SteamVR starts, then DCS starts. Not what I expected, but it is also just a sign of the infancy of VR to me.

No, sorry. I just mean that IPD is one of the settings that you can adjust after you've loaded a mission and are in the cockpit using the menu there (with ESC) and don't need to exit the mission to go back to the main menu. The benefit to this is that the IPD settings change takes effect immediately, as in the moment you type any numbers in, the scale of the world changes instantly. It just makes it easy to see the difference and adjust the scale without having to reload the mission every time.

Interesting. The change is definitely noticeable to me, particularly if I adjust the IPD in the cockpit with the ESC menu, rather then in the main menu. Going from say 65 to 40 is pretty dramatic to me. At 65 I feel too big and at 40 I too small.

It appears to. The whole DCS environment feels more natural to me and less toy like.

It is bugged still. I just got into VR and the Su-25T is amazing! So much fun to fly for some reason. Having a FFB stick really adds to this aircraft (along with the P-51D!) and is such a nice addition to VR. It would be amazing to see the Su-25T autopilot modes work properly like the Su-27 currently does!

Thanks guys. Good info to know. The difference in feeling, to me, is not the size of the cockpit itself, I'm not surprised to hear the cockpit is larger, or just a different size than the others - I sort of assumed each cockpit would be a different size. It is the size of the elements within the A-10C, the toggle switches/throttles/stick, etc., that are significantly off (tiny), especially now that the scale is set very closely for the other aircraft. (Which what @Deano87 said) I flew the SU-25T, F/A-18C, and P-51D last night after getting everything scaled properly and syncing my pit to the Hornet and the experience was astounding! I was taken aback by how much of a difference that subtle scale change made.

I've settled on 50 for IPD after trying a range of values from 40-60. In all the aircraft except the A-10C, the scale feels perfect. Everything just feels more natural, it is difficult to explain, but getting the scale right dramatically improved my experience and comfort level.

The F/A-18C is fantastic now! It even made reading all the labels and the MPCD and DDIs far easier which is an unexpected surprise. The A-10C on the other hand... feels far different from the Hornet, especially now that the Hornet scale is set right for me. Oh well, I'm a Hornet fan to and through and so I'm a happy camper (simmer?)

Thank you, that was it! Playing with the IPD setting as a scale setting instead did the trick! It is amazing how much of a difference that it made. Even though it is a subtle change, the whole experience feels a lot better! I'm still tinkering with it, but I'm also around ~50. Is there a way to independently set this for different aircraft, out of curiosity?

(Sorry in advance, I know this topic has come up before and is somewhat contentious... so feel free to ignore me and just move on ;)) I just received my Lenovo Explorer and am loving VR! I have a replica SJU-17 seat, made from dimensions others have taken with photos and measuring tapes, which seems to get me in the ball park +-1". My stick is centered and my throttle is where the throttle is in the aircraft according to the measurements. I was very curious to see how well this would match up in VR and to my delight it seems to match the F/A-18C in VR exceptionally well! Overall it feels amazing! My throttle is a DIY throttle made from measurements of a real throttle and I positioned it according to the measurements I found and low and behold it matches perfectly in game. The hand position and travel of the throttle are perfect! When I peak under my headset, my actual hand is in the exact same spot. My center stick is just about right, I need to make some small adjustments to its position, by my travel is almost identical. Even when I roll all the way to the right and the in game hand touches the thigh of the pilot, I can feel my own hand touching my thigh and a quick peak show the stick in just about the exact same spot. So with all that said, the size of the switches and stick/throttle/hands themselves, seems to be a bit on the small side. I have toggle switches IRL and the scale of the in game switches seems to be like 3/4 the actual size. Same with my pilots hands, they are like my wife's size. The throttle and stick also seem to me to be something like 3/4 size, it is an odd feeling. It is far more pronounced in the A-10C, the stick and throttle seem tiny. The throttle, compared to the Thrustmaster, seems miniature. I measured my IPD at 63.8 and have set that ingame, but that is barely different from the average 63.5 (Lenovo Explorer is physically set for this IPD, from what I understand) so this all seems good. Overall the F/A-18C scale seems quite good and I'm very happy with it, even if things appear somewhat small. However the A-10C is rather startling, especially the throttle, it is so tiny! It feels like my whole had would engulf it and it would be better to just pinch it with two fingers. In the A-10C I feel like I'm a giant. My eye point is way above the top of the HUD frame about 3-4 degrees, I have to slouch way down to even get a glimpse of the HUD on the horizon (I'm not complaining that the HUD is too large to see, I understand that this is accurate) just saying that I feel exceptionally large and tall in the A-10C. Anyways, not even sure if I'm asking a question or what I'm doing in the post, so like I said, feel free to just ignore me. This is just my initial impressions.

After quite a bit of testing, my specific crash related problems were in fact due to overclocking. I rebuilt my rig due to a crash that corrupted windows system files and while I was at it, I upgraded to windows 10. During the rebuild and because of the earlier crash, I backed off my OC settings, but never tested them, just assumed that more conservative settings would be fine, but DCS routinely crashed at these OC settings. So I stress tested and played DCS for week with stock settings, conservative OC settings, and my original more aggressive OC settings. Turns out DCS seems to be somewhat sensitive to OC settings. I had no crashes with stock settings. Frequent DCS crashes with the conservative settings, though no crashes in benchmarks and stress testing. Lastly, my aggressive OC settings are actually pretty good, no crashes in DCS or benchmarks/stress tests. So I think the problem with my conservative settings was that I backed off the voltage too much and for some reason DCS became sensitive to this. Anyways, I consider this problem solved for me. Hope this helps someone else.

I'm still testing, but so far it does look like OCing has something to do with it. I'll share more after further testing.

As a follow up. I'm going to pin this problem on bad overclock settings. I've make changes to them and that has solved the CTD issues it appears.

I rolled back the nVidia graphics driver to the previous version (417.35) and got 30 seconds into F/A-18C Free Flight (Caucasus) before another CTD. dcs.log-20190128-163022.zip

I've been running DCS for many years on Win 7 Pro, but recently got around to installing Win 10 pro, not upgrading, but a clean install on the exact same hardware. With only mouse/keyboard/logitech 3D Pro attached and a clean DCS OB install, DCS CTDs after a few minutes on any instant action I've tried. Through GeForce Experience, I updated the graphics driver prior to installing DCS OB. Crash log attached. I just tried a complete reformatting of my 2nd SSD (recreating the partition to make sure permissions were set properly) and another clean install of DCS OB on it, also completely removing the DCS OB directory in Saved Games. No change, still CTD after a few minutes. dcs.log-20190128-153403.zip

I would love to have an in-game interface to search, download, and manage missions/campaigns. It would be great to have this aspect consolidated into one space, the space where game content should reside - in game! I don't like having to search high and low for content for DCS in a variety of places, all outside of game, looking for compatibility, also having to manage the files. I think having downloadable content that is easily accessible in-game and ever growing would improve the current feeling of DCS having a lack of content and would be an improved way to promote newly created content for designers.

In the first screenshot 250 is where the course line intersects with the compass markings, but shouldn't be used as an intercept heading. If you want to set a heading to fly directly over the TACAN station and then fly the runway heading, that info is in the top left of the HSI. In the first screenshot you'd set a heading for 235 and fly for 30. In the second you'd set a heading for 248 and fly for 14. If you want to set a heading behind the TACAN station, then you just have to imagine a line intersecting the course line and set your heading. For instance, you could fly 210 for what looks like 20 to intercept the course line maybe 10 nm behind the TACAN. Hope that helps.

I don't think I'm going to offer anymore time into helping you with lua editing as all this information is on these forums already, multiple times over. I think though, that joystick Gremlin or one of the other input mappers would be better for you (which I now use). This lua file will be overwritten on each DCS update and you'll have to manage the file manually or use a mod manager. Again you can find more about this on these forums. Good luck and have fun!

As was said earlier, it is best if you create a whole new command by copying and pasting that command somewhere else in the file. I put all my custom commands near the top under a comment heading I made. You then need to be sure that you give the new command a unique name. In DCS, you can easily search for the new command by the name you gave it. You also need to be sure that you are editing the lua file in: {Your drive}\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\FA-18C\Input\FA-18C\joystick\default.lua

That command says essentially, "when switch is pressed down (or turned to "on") set the value of device_commands.Button_3, called "Main Fuel Switch, of devices.FUELSYS_INTERFACE to a value of 0.0" So if you have an on-off switch you need to add an "up" or off parameter to the command so that DCS knows what to do when you turn the switch off. This is for a two position ingame switch. If a DCS command, like this one, uses a numerical value_down parameter, then you need to add a value_up parameter, which range is typically values of 1.0, 0.0, -1.0, but referring to the existing commands in the lua help you know exactly which one to use. So the modified command for and on-off switch becomes (changes are in bold): {down = device_commands.Button_3, [b]up = device_commands.Button_3[/b], cockpit_device_id = devices.FUELSYS_INTERFACE, value_down = 0.0, [b]value_up = 1.0[/b], name = _('[b]Modified[/b] Main Fuel Switch'), category = _('Pedestal')} Notice that I also changed the name of the command because it must have a new unique name. I didn't look at the lua to see if 1.0 is the off value for the main fuel switch, but it likely is, might be -1.0.

For an on-off switch, just look at the first one, the gear input. down = switch "On" (down = iCommandPlaneGearUp) up = switch "Off" (up = iCommandPlaneGearDown) The original command, found in the same lua, didn't have an "up" part - I added that. The commands for the flaps on-off-on were derived from the original flaps commands found in the lua. You have to search in the file to find the inputs your looking for, then copy and paste them anywhere, I put mine near the top to be able to find them quickly, and modify them while giving them a unique name.

For completeness, here is the track. Bankler-case-1-69-3w.trk

The joystick input "default.lua" is found in the main DCS directory under each aircraft mod. For example the Hornet's is found here: {Your drive}\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\FA-18C\Input\FA-18C\joystick\default.lua Like they said, this file is overwritten on each update. So you either have to keep a backup of the modified lua or use a mod manager (like JSGME). I've done both and currently use JSGME. An example of modified inputs in the lua: [color=#000000][font=Consolas][color=#000000]{ down [/color][color=#000000]=[/color][color=#000000] iCommandPlaneGearUp, up [/color][color=#000000]=[/color][color=#000000] iCommandPlaneGearDown, name [/color][color=#000000]=[/color][color=#000000] _([/color][color=#a31515]'Custom Landing Gear Control Handle'[/color][color=#000000]), category [/color][color=#000000]=[/color][color=#000000] {_([/color][color=#a31515]'Left Vertical Panel'[/color][color=#000000])}},[/color] [color=#000000]{ down [/color][color=#000000]=[/color][color=#000000] ctrl_commands.FlapSw, up [/color][color=#000000]=[/color][color=#000000] ctrl_commands.FlapSw, cockpit_device_id [/color][color=#000000]=[/color][color=#000000] devices.CONTROL_INTERFACE, value_down [/color][color=#000000]=[/color][color=#09885a]1.0[/color][color=#000000], value_up [/color][color=#000000]=[/color][color=#09885a]0.0[/color][color=#000000], name [/color][color=#000000]=[/color][color=#000000] _([/color][color=#a31515]'Custom FLAP Switch - AUTO'[/color][color=#000000]), category [/color][color=#000000]=[/color][color=#000000] {_([/color][color=#a31515]'Left Vertical Panel'[/color][color=#000000])}},[/color] [color=#000000]{ down [/color][color=#000000]=[/color][color=#000000] ctrl_commands.FlapSw, up [/color][color=#000000]=[/color][color=#000000] ctrl_commands.FlapSw, cockpit_device_id [/color][color=#000000]=[/color][color=#000000] devices.CONTROL_INTERFACE, value_down [/color][color=#000000]=[/color][color=#000000]-[/color][color=#09885a]1.0[/color][color=#000000], value_up [/color][color=#000000]=[/color][color=#09885a]0.0[/color][color=#000000], name [/color][color=#000000]=[/color][color=#000000] _([/color][color=#a31515]'Custom FLAP Switch - FULL'[/color][color=#000000]), category [/color][color=#000000]=[/color][color=#000000] {_([/color][color=#a31515]'Left Vertical Panel'[/color][color=#000000])}},[/color] [color=#000000]{ down [/color][color=#000000]=[/color][color=#000000] gear_commands.HookHandle, up [/color][color=#000000]=[/color][color=#000000] gear_commands.HookHandle, cockpit_device_id [/color][color=#000000]=[/color][color=#000000] devices.GEAR_INTERFACE, value_down [/color][color=#000000]=[/color][color=#09885a]0.0[/color][color=#000000], value_up [/color][color=#000000]=[/color][color=#09885a]1.0[/color][color=#000000], name [/color][color=#000000]=[/color][color=#000000] _([/color][color=#a31515]'Custom Arresting Hook Handle'[/color][color=#000000]), category [/color][color=#000000]=[/color][color=#000000] {_([/color][color=#a31515]'Right Vertical Panel'[/color][color=#000000])}},[/color] [/font][/color] **Note you have to create a new and uniquely named command. The gear and hook are on-off and the flaps is on-off-on I've since begun to switch to joystick Gremlin, because I found I can get someone of the functionality of on-on switches without using up more inputs on my GP-Wiz40

This is interesting because the other day I made these two gifs while I was testing this odd nose dive on touchdown. Probably exactly what is happening here, there carrier ends up pulling the nose down due to the inverse ground effect. The first is MIL power just before touchdown and the second is MIL on the ramp. I just realized the throttle movement has nothing to do with the dip on touchdown. I tried it not moving the throttle at all as well as moving it to idle and the same thing in the first gif occurs.

Thanks for these, I'm now using Joystick Gremlin. I like it better for on-off switches than my custom lua.