Habu_69

DCSW 2.5.5.35461. In ME AFAC at 9000 FT and 2 NM from vehicle group shows NO LOS. Same whether group is stationary or moving, AFAC orbiting or not. Edit: Above issue was with a mission developed in June 2019 on PG theater. Developed an entirely new mission and No LOS issue did not occur.

See post #60. You realize the VR kneeboard enlarges substantially when you focus on it? that is, look at it and move your head towards it. One old fart to another.

Used both for years without conflicts.

I have military radio experience and have done many SOUND TO recordings for my missions and for others, as well. USA English accent. Use Goldwave filters to simulate radio distortion.

I had Rift and know exactly of what you speak. I simply flew the red ball best I could. Resolves somewhat in close, but sometimes too late to adjust. I upgraded to HP Reverb and ball is now much more clear.

The PointControl devices invented and distributed by MilesD (see New VR Device thread) appear to go far towards the ultimate haptic feedback goal.

OK. Uninstalled all mods, did repair, more testing. Still get the "hold position" nag. Do finally get launch permission, but only after several "U" requests. Still some bug, I think, but at least it is workable. Another track attached. TY for your troubleshooting. Launch Test 3.trk

Clean mission, same behavior. PG theater. Flying VR. Track attached. Launch Test.trk

DCSW OB 2.5.5.35461. 2-ship cold start from Stennis parking slot. After start-up pilot taxis to cat 3, -2 taxis to cat 2. Immediately on taxiing tower continuously repeats nag to "hold position." When in position on cat 3 pilot must wait a few seconds after -2 launches or he never gets permission to launch. Requesting permission too quickly, "U" key, ticks off the tower and permission never comes, despite repeating launch sequence. Impossible to launch. Track attached. Failure to Launch.rar

This might be helpful to someone. I moved kneeboard from virtual pilot knee to the right leg well where it is a little easier to focus on. yaw = 9 px = .13 pitch = 40 py = -0.4 roll = 0 pz = -0.25

Search for Goldwater Range in this thread. Open the .miz file with a zip or RAR program. Find the MOOSE script. Should be some help to you.

Maybe a good price on used windows tablet on EBay.

I believe VRK only works with Windows currently.

How does one access pages in a PDF doc?

I have no problems with this mod and latest OB update.

Well, it is the Surface pinch-to-zoom that I can't get to work. Swipes work fine. Perhaps need driver reinstall.

Yes, your corrective lens prescription. Without a prescription, one could test common "reader" glasses from any pharmacy to determine the correction needed and provide that to VR Optician. They do not require an optician's written prescription.

I now have VRK working nicely on my Surface. Little trouble with zoom gesture, but I am sure that is my problem, not the program. I have feature suggestion: A method to hide/display the kneeboard. Then one could put the kneeboard anywhere in the cockpit and hide/display as desired.

I too have wasted WAY too many hours trying to make AI execute a SEAD mission properly, using every method described in these forums. Thing is, OCCASIONALLY but rarely, they do it. In frustration, I have resorted to scripting the destruction of the AD units, sometimes with a random factor. After all the AI SEAD work is transparent to a human pilot. Poor work-around, but better than banging my head against the proverbial wall.

The DCS user manual is your friend.

Got my VR Optician inserts. They are GREAT!

Create a moving zone on one of the units with the desired radius. When unit enters zone, do something.

I use it with HP Reverb and can read 10 pt text readily. This mod is very useful and easy to use, especially when combined with Voice Attack to control displaying, changing pages,etc.

Success! 3.08 installs and runs on my Surface Pro 3. Will smoke test in DCS later. Many thanks.

Setting user flags to boolean values has proved unreliable for me. Try setting the flags to numeric values. Also might be a problem defining timer_1 function after calling it. Try moving the function definition before the scheduler.