sohei

No, I'll give that a shot. I just thought DCS would automatically choose the Rift for sound.

Hi everyone I've been gradually getting my Rift up and running, and I'm loving it so far, but have 2 questions which I would really appreciate some help with : 1. I'm not getting sound over the built-in headphones on my Rift. I have to use my regular headphones or speakers, which I would prefer to avoid. Do I need to configure anything or is this just normal behaviour for Rift implementation on DCS at this stage? I'm using 1.5.3 and 2.0 at this point. 2. Do I configure pixel density via the Oculus Rift SDK debug tool, or is there another method for DCS? Thanks in advance for any advice :) John

Thanks for that, much appreciated :)

Hi all Due to a house move and a delay in the provisioning of my broadband service I'll be recieving a Rift today but will only have a very limited internet connection to set up with. To get round this problem I'm downloading the steam DCS files to my USB hard drive at work and will copy over to my gaming rig when I get home. Is the Steam DCS good with Rift, or should I aim to get the standalone version installed instead? Sorry if this is a dumb question, I just want to get up and running as quickly as possible! Thanks John

Mine arrives tomorrow; I'm literally quivering with anticipation! I've not been able to fly for some time due to work and a house move, so I'm a bit of touch. I have DCS on steam, but also NTTR. Which has the best support for Rift?

Thank you kindly. :)

Hi everyone Following the excellent advice I've found on this forum, I've managed to setup my two MFDs to my second monitor in BS2. I'm now trying to find out how to move various other instrumentation gauges to this monitor as well. I think I just need the names of the relevant instruments for the '.lua file. I've had a look round the forum, but don't seem to be having much luck. Could someone please point me in the right direction? Any help gratefully recieved. :) Regards John

Could it be sand clogging the engine perhaps? Was dust protection on? I imagine it's more likely to be a physics bug, although the local kids can be real hellraiser, or so I hear.

Perhaps ED modelled global warming as well?

Ahh, I'm finding Spyda's use of the clickable mouse wheel to be the most effective yet. Many thanks one and all.

Aha! That was most helpful. Thankyou! It really is amazing; not only do I have the best flight sim ever, it also happens that the development team are a superb bunch of guys too! You guys have earned my loyalty as a customer.

Oh wow, that is impressive. Time to get making stuff, I suppose. How much did it cost you to put together? Credit to Alan Davies for the sig ;)

I don't have Track IR though. Is it possible to remove the joystick, or have a close-up view of the panels?

Hi all, How are you guys getting around the fact that the joystick obscures the Targetting Display Control Panel, and the Landing Lights and Voice Warning ['Betty] Control Panel? I can't see what I've selected on some of the switches!

http://www.ocztechnology.com/products/ocz_peripherals/nia-neural_impulse_actuator

I read somewhere that BS pilots trim the controls for about every 25 knots of airspeed change, so the sim is probably pretty accurate.

This is a common and much discussed problem. Here is some help. http://forums.eagle.ru/showthread.php?t=35052&page=4 As for the issue of feedback relating to general flight conditions, I heartily agree, but there doesn't seem to be anything we can do right now. More technically minded people may come up with a solution in time. In the meantime, I've disabled FF for my Saitek Cyborg Evo Force as I find the current FF trim method too awkward.

Well, I'm not really after the same degree of stiffness that is available in the Saitek stick at max, but at the moment it is just proving to be a nuisance to get set up right, so some option for greater adjustability would be most welcome, whether or not it's truly represantitive of the real thing. A minor complaint about a great sim, all in all.

Thanks CyBerkut. I checked, and the setting was enabled, but I ran it once with it hashed out, then reenabled it, and it came on, although very feebly compared to how powerful the FF really is on this Joystick. I'll work through the recommended settings until I've got it.

Options-Gameplay Check the 'use these settings for all missions' box then go to... Options-Controls Drop down the list to highlight 'Axis assignment' in red. Assign Joy_z to the collective. That sorted it for me.

Well, I finally sorted out the throttle problem with help from a few people here. I overlooked checking the 'use these settings for all missions' box in Options-Gameplay. Whoops, silly me. At least it's sorted though. For any Saitek Cyborg Evo Force users, it's Joy_z (credit to EtherealN) The FF thing continues though. I'm working through the suggestions posted elsewhere, but they seem to relate to weak FF in the game as opposed to no FF whatsoever. Strange, as the FF is strong enough to make the joystick dance off the table when I'm testing it in Windows. Ah well, back to the drawing board.

I'm at work now ( :( ) so I'll have to do that later. Here's what I've done so far. 1. Tried going through all the slider axis assignment options and looking for movement in the axis calibration window. No effect. 2. Unassigning all axes from the collective option. No effect. 3. Assigning Joy_z to the collective. This gave a response in the callibration window, but none in game. All of the above steps were done in sim mode. In game mode, it seems to work regardless of what I assign, even if I leave it blank!I'll confirm this when I get home this evening. I also downloaded the LOMAC demo, and found that the throttle works fine straight away. Still loving the game, btw :) Any suggestions about the complete lack of FF?

UPDATE Well, I tried using Joy_Z as the collective control, with odd results. When I used the axis callibration option under Options-Controls-Axis assignment, the control was recognised and moved just fine. In the game however, it still didn't work. Strange, but I'll keep tinkering and see what I can do. I also ran update for the drivers through the Device Manager, to no effect, sadly. This may seem like a dumb question, but should I be using the SST software to set the stick up?

Wow, thanks for all the helpful suggestions guys and girls! There seems to be a variety of issues so far, but in my case the stick is definitely functioning fine outside of BS. I can actually use it in game, as it gets no FF at all, and so functions as a normal joystick with the centering spring in use. I can trim and release the joystick and it works ok, so the game is just not identifying it as FF. I'm going to try messing about with drivers in the meantime, but I hope a patch from the devs will sort this out. EtherealN, I'll try your collective setting and see what happens. Sohei out.

Same here with the throttle problem. I found how to mess about with the different axis settings, but none of them seem to apply to this joystick! Aaargh, this is so frustrating!