Gizzy

Its a windows thing... In Windows 10, 8, 7, and Vista, hold down the “Shift” key while right-clicking the item in the taskbar, then select “Move“. In Windows XP, right-click the item in the task-bar and select “Move“. Use your mouse or the arrow keys on your keyboard to move the window back onto the screen. Hope this helps....

Hope this helps...

Yes, no problems, good appropriate response. Russian year holiday period can be long and kicks in late.

As I understand it freq does not necessary effect travel through free space but does effect object penetration and the size of both receiving and receiving antennae. So flying low and being masked by terrain will often result in the loss of effective 2 way comms with the size of antenna used (especially helos) no matter the transmission band.

Good job Lens62, thanks for sharing.....:)

What is the mission? Create a hot start from RAMP at any airfield or FARP and all should be good... Some missions scripted for a spawn ON GROUND a/c can explode if positioned on a FARP or rough ground - same as for some other airframes...

Just in case... apologies if you know this backwards... Click 'clear' Click 'set' Then push the button on your control that you want to use... the device name and button should now be visible..

A higher PD helps, rig dependent of course. One workaround I use a lot is to have Camera Position UP/DWN & IN/OUT mapped to spare hat. In the Co-Pilots seat I move the 'camera' position forward and down a bit.... with PD of 2 in 1.5xx and 1.5 in 2.2xxx works well for me. An alternative is to set up a snap view to a close in view as possible (in VR snap view only relative to camera in/out left/right up/down... your head still moves as normal) and then just jump in and out on a toggle using LWIN + NUMKEY...

Yeah the Xbox controller works okay for this anyway.... use the left and right triggers and the joysticks and you'll soon have it cracked. I have no touch...

Oh yes, for Oculus Desktop to work you need a FREE displayport. It was only when I made on available that the oculus home desktop functionality worked... Hope this helps...

You need the beta version of oculus running.. You need a controller - xbox one will do... In oculus home, the horizontal tool-bar select oculus desktop and whatever monitor if using multiples... It will appear.... Use controller to open, say, acrobat file, use controller to drag it off the desktop (try the left trigger), it is then in its own window... lower bar icon pin to experience using the right trigger... Start DCS.... the window will be wherever you placed it... Use the lower button on your remote do-dah to switch between DCS and Home for, say, to scroll the pages or move the window etc...

Start in Home, drag your windows app (acrobat) off the desktop into a separate window, position it where you want it, use the 'pin' icon to pin to 'experience'.... start DCS.... Home screen disappears, your app window stays... even within DCS... Hope this helps

Cracked it... for me anyway.... you need a spare display port for the pull outs to work in DCS.... so presumably uses pseudo monitor voodoo / stuff.. Unplugged one of my monitors, In home pulled out TS from a monitor view, scaled and parked it where I wanted it.... Fired up DCS...and there it was no issues, no discernible FPS drop.. You can not move or minimise it however, you need to pop back into home to do that... Would be fine for certain circumstance / airframes... i.e. a window such as TS or a map or even google maps on the rear bulkheads of helos... Using an XBox controller and 980Ti EDIT: You need to pin the pulled APP to 'experience' then you will see it in DCS - if not pinned it will only show in home...

In Home screen you can have your monitor screen (or screens) moveable and positioned wherever and pull apps such TS or a browser from a monitor screen and place them where ever.. 'oculus dash' google videos will give many examples. There was mention that you could use these 'pulled' apps inside VR games... as if in DCS, you could pop up say a TS window, position it where ever, minimise etc but as yet, for me, no... The remote button can switch your rift screen between the 'home' view and DCS... which is more useful than alt+tab etc..

Certainly the Oculus Home bit seems to work works fine, most apps can be pulled out and positioned with a few exceptions BUT has anyone managed to engage an app from within DCS environment? Switching between DCS AND Home and its screens is just a button push so thats fine.. and much better than ALT TAB'ing

We too upgraded our main server tonight and no PTT was working at all. Tried Ciribobs 5.189.162.17:5012 and all was good... so it looks server side for us at least. I suspect TCP side... I ask the server contact to look into it and only come back if there is a problem... Thanks a lot for your continued support CB... it is truly invaluable to us all.. :):)

Not that I aware of. You can use snap views to a camera position in the cockpit i.e. up / down / left / right / forward / back but the FOV remains the same the view not being static as in 2D. Checking six is awkward as in RL... think clearing turns and wingmen

I believe these are 2 different issues... In VR with the rift anyway, recently you can get a 'shimmer' when you move your head... this is not consistent and comes and goes but disabling ASW cures it immediately. Flickering shadows could be another issue but I suspect settings and equipment used have a lot to do with it.

Disagree... There are many with VR & the RIFT that I fly with who recently experience the same issue. Disabling AWS sorts it. In 2D at 4K with everything Max'ed it is 1.57 rock stable.... maybe it is another issue you are experiencing.

I experience it with the latest NVidea drivers and the Rift. In DCS just hit RCTRL + NUMPAD 1 and that should sort it... sometimes RCTL + NUM1, then RCTL _ NUM4 then RCTL + NUM1... Its related to AWS... official function of those keys... CTRL+Numpad1: Disable ASW, go back to the origional ATW mode CTRL+Numpad2: Force apps to 45Hz, ASW disabled CTRL+Numpad3: Force apps to 45Hz, ASW enabled CTRL+Numpad4: Enable auto-ASW You can of course roll back to earlier drivers... August did not have this issue... Hope this helps...

It occasionally occurs with several airframes not specific to the Gaz and more prevalent with slow speed crashes (if you're going to crash, make it big! )... probably Rift related - never experienced it in 2D.

No, if FBB is ticked and you are using a non-FBB stick then it screws with stuff making the Gazelle uncontrollable. :( Good luck in getting it sorted .... :thumbup:

If your mappings are good then an obvious place to check is DCS main menu, MISC / Force feedback. Make sure it is NOT selected.... unless using FBB of course. The Gazelle is as expected in 2.1xx for me...

Upgrade your computer and or graphics card or lower your settings. Full zoom in & out is .75 sec in 1.5xxx for me with most settings on high and PD of 2. It can be reduced to .5 with silly low settings. Snapview's can change the camera position in cockpit. You can be instantly moved in / out / left / right / up / down whatever but the outside cockpit view, the 'distance' you see remains the same. SNapviews can be be good in VR when looking for fine detail on TV screens such as found in A10, Ka50 Garmin 430 etc - it counters the inherent resolution. They may be good for those who PC's have performance issues running VR / DCS and have to use low PD or low resolution cockpit textures.

In your default install directory... 'C:\Program Files\DCS-SimpleRadio-Standalone' for me... 2 files, clientlog.txt and serverlog.txt