fitness88

I will try taking notes to post next time I have this issue, I play around and it sorts itself out. Not sure if it's the sequence at which you open DCS and Oculus and minimizing Oculus.

+1

Why then if that's the case, buddy lasing techique isn't used instead of the current spot lase?

NATOPS is it...I'll PM the link

Can someone please explain why we need to lase a target from our plane after LST searches and finds a buddy lase?

Update 2: I have a .lua file that needs to be placed directly into the DCS folder [OVGME works well in this case]. It seems that this particular .lua file is ignored when placed into the saved games, there are many .lua files that of course are seen in the saved games folder.

Update: I placed the mod files directly into saved games with the original folder structure instead of using OVGME [which places the files directly into DCS folders] and it now works again. You can't use OVGME to place sound files directly into the DCS folders.

Yes this is what I'm saying...:cry:

RE:latest version OB 2.5.6.45317 So my in-cockpit sound mods are once again broken. With the last update that introduced sounds.edc I was able to use the saved games folder but I'm not sure that will work again. Any info would be appreciated. Thank you.

What jeff_peters said...you must manually create a saved games folder and allow the file/folder structure to load into it. If you screw up as I did the first time by not creating a saved games folder you need to change your shortcuts as well as an entry in the registry. If you hate the messy look of the relocation you need to take a backup of the saved games folder and do it manually. The Windows registry HKEY_CURRENT_USER/Software/Eagle Dynamics/DCS World - Path value

I start with Oculus already up and running and have no issues until I approach a tanker or carrier then all starts to break down. So far I have seen this only when flying MP on the Aerobatics server none others so far and never in single player.

Anyone know what this is about? Oculus not responding...window out of focus Thank you.

Previously posted: Oculus does not show up as a device in the NCP and therefore cannot be adjusted as monitors can but... The earlier NVidia drivers allowed for color changes/vibrance to be made by using a monitor on the Oculus port for purposes of changing the settings then plugging the Oculus back into it. Worked very well until Nvidia disallowed this form of tweak by not allowing the port to remember settings but instead made the device responsible for it. So now when you change back to Oculus after the tweak the port no longer carries the settings you just made with the monitor. You can enable the graphics card setting in NCP to perform at max.

It would be nice to have that tweak back again for sure, that's what I told the Nvidia tech on the phone after he explained it. If it were in the .reg...where would be the big question.

Oculus does not show up as a device in the NCP and therefore cannot be adjusted as monitors can but... The earlier NVidia drivers allowed for color changes/vibrance to be made by using a monitor on the Oculus port for purposes of changing the settings then plugging the Oculus back into it. Worked very well until Nvidia disallowed this form of tweak by not allowing the port to remember settings but instead made the device responsible for it. So now when you change back to Oculus after the tweak the port no longer carries the settings you just made with the monitor.

No, it didn't for me.

Thanks for the modelled test results. I find full wheel brakes w/antiskid off causes uncontrollable swerving unless you pump the brakes, but then you're doing your own antiskid application.

Do you notice a difference in stopping distance over just braking?

Actually I wanted to know if it was in fact modelled into the DCS FA-18? If so can you quantify it a bit?

I read in the forums pulling back on the stick gives you better braking after touchdown. I've tried it several times but can't really tell if it's helping. Any input on this would be appreciated. Thank you.

Too bad it was so easy but I hear ya...back to work:book: Thanks! edit: btw, I never had to press the on button only the AP select and the mode I wanted...to disengage entirely from the AP system I just had to pull the (Paddle) Switch, [Autopilot/Nosewheel Steering Disengage (Paddle) Switch]

There is some flight control behavior that is different as described, try pressing only the AP select button without pressing a mode button.

I had a similar issue with Rift, make certain all shortcuts including start menu & dcs.exe has 'Run as Administrator' enabled.

If by AP channels you mean ATTH / HSEL / BALT / RALT, I don't engage these, I just press the AP button on the UFC. For small subtle inputs only, this gives better control. Yes I understand if I practice without AP I would be able to get more comfortable but it would never be as controllable as with AP [with no channels engaged]...so why wouldn't you want to make it easier?

I wouldn't have thought that would be a fringe benefit.