mue

Am I the only one who find it ridiculous that when I bought the software (respectively a time unlimited license) to ask ED at regular intervals (it doesn't matter if its days or weeks): "Please...am I allowed to continue to play the game...please!" ?

I'm using a big rear projection screen. I mounted the trackir cam on top of the screen and the vector clip on top of my head phones. See the first two pictures in this thread: http://forums.eagle.ru/showthread.php?t=89624.

No, I haven't worked further on it. Actually now I'm using the warthog hotas (with center mounted extended stick). Although now I don't have force trim I like the feeling of the metal grip and the long lever of the extended warthog stick. The magnet heating is not that big of a problem. I would suggest a simple construction without reversing the magnet clutch logic.

Ok, I should have searched this forum better before asking. I found the solution here: http://forums.eagle.ru/showthread.php?t=120111

Same problem here after updating from 1.2.3 to 1.2.7 (yes I know, I was a little bit lazy regarding updates :smilewink: ). I already deleted the dcs folder in my "saved games" folder and reassigned the hotas axis. But still no luck :(. And yes, I'm sitting in my aircraft and the game/sim mode is correct.

Yes: Disable the center trim method AND set in FMOptions.lua HelicopterTrimmerTauInverse=0.0

Ok, here are my panel overlays: IL2: SF2: DCS Black Shark (I'm not using it anymore, because now I use the 3D cockpit with my touchscreen):

Mostly I fly/play DCS:Black Shark, Il-2 1946 and Strike Fighters 2. The panel overlays are nothing special. Just printed on paper and then made holes for the switches and buttons. If you're interested I can make a picture of the overlays.

Of course, it should work just fine. But two things to consider: 1.) The touch screen driver should support left click, right click, mouse wheel, ... . I don't know if windows 7 native touch support can do it. If not you can use some script tools (e.g. autohotkey) to translate mouse gestures to left click, right click or mouse wheel... 2.) Regarding TrackIR: You have to hold your head steady while clicking in the 3D cockpit. But it's not that difficult and you get used to it.

I'm using a single touchscreen setup: 63'' 1920x1080

Enable the TrueView option in your trackir profile.

I've done this for the ms flight simulator 9 before. I intercepted and altered the view/projection matrices via a proxy directx dll. Unfortunately the matrices only had an effect on the terrain and scenery. But runway lights, the sky and clouds were unaffected. But I don't know how the dcs graphic engine works. You just have to try it. I recommend first to do a simple test: alter the fov via directx intercepting and see if all of the graphics are affected.

Try to run the trackir software as admin. But if you have the latest trackir software, it should request admin rights anyway if you start the software.

This behaviour could be caused by the trackir trueview option. Have you trueview enabled in the trackir software? Then disable this option and see if the problem is still there. If trueview is the cause but you still want to use trueview then try to lower the curves for the lateral axes (x,y,z) in the trackir software or reposition the trackir camera.

I'm still in doubt about a rift version in the near/medium future that is usable for serious flight simulation where you have to read gauges, mfds, huds,... . As others (e.g. Mnemonic) already pointed out you need for that big fov ( ~90 degrees) at least a 2K resolution per eye. For the rift design it means you need a 5.5 - 7 inch 4K display. When do you think such displays are available? Probably an HMD design with 2x 2K displays (and some mirrors or other optics) are more likely in the near/medium future for achieving the needed resolution. What do you think?

Unfortunately just selecting FFB mode doesn't work if you don't have a FFB device connected to your computer. optocoupler: sfh610a-4 http://www.vishay.com/docs/83666/sfh610a.pdf (notice: in comparison to my schematic the pins 3 and 4 on this optocoupler are swapped) relay: sy-12w-k http://www.fujitsu.com/downloads/MICRO/fcai/relays/sy.pdf magnets: its-ms-3025 12v http://www.red-magnetics.com/download/datenblatt/redmagnetics-datenblatt-its-ms-3025.pdf R1: 330 Ohm R2: 1 kOhm LED: standard led (U=1.6V, Imax=20mA) D1: 1N4148 D2: 1N4001 Yes, correct.

By unchecking the center trim method option the "old" trim method is used. With the old trim method there is a short delay (fraction of a second by default) until the trim setting takes effect after releasing the trim button. By changing the HelicopterTrimmerTauInverse value you can change this trim delay time. With HelicopterTrimmerTauInverse=0.0 the trim delay time is set to infinity. That means the trim setting never takes effect and you are not forced to center the joystick. However the autopilot will still be set by releasing the trim button. Unfortunately I didn't make a picture from the dismantled joystick where I soldered the wires to the circuit board. I connected one wire to the electrical ground. The other wire I connected to the proper pad (joystick button) on the circuit board in the joystick grip where I get a voltage of 3.5 - 4.0 V (I don't remember the exact number) if the trim button is pressed and 0 V if the trim button is unpressed. With that signal you can not drive the magnets directly (the magnets use a voltage of 12 V and the needed current for both magnets (0.6 A) is to high to be powered by the joystick). Probably you can use this signal directly to control a relay that turns the magnets in the 12 V circuit on and off. However I added an optocoupler between joystick and relay to further minimize the current load on the joystick: forcetrim.BMP

Sorry for being not responsive, but real life cropped up: the birth of my daughter :). I will try to answer your questions within the next days.

The resolution is not the problem. The problem is that two views must be rendered instead of only one.

You have to disable the trueview option in the track ir software. See this link: http://forum.naturalpoint.com/forum/ubbthreads.php?ubb=showflat&Number=55123#Post55123

Yeah, the future of smartphone gaming:

Its more immersive to manipulate the virtual cockpit controls "directly" with your fingers. That is why most people that use helios use it with a touch screen and not with a mouse. For doing this with oculus rift you would need a device/tracker that scans your arm/finger position (in three dimensions) and translate them into the virtual reality. To achieve a realistic mapping from the real world to the virtual world the tracker has to scan an area around you that has the size of the real cockpit. This is where leapmotion fails. Leapmotions interaction space is only 8 cubic feet. I think kinect can scan an area of this size but lacks the ability of recognizing small motions eg. finger motions. Thus, waiting for a kinect-leapmotion-combined-device ...

Correct.

If we assume that the monitors in your example have the same aspect ratios (which they haven't), then yes. Of course the lowres monitor cover a smaller FoV than the highres monitor. That means the lowres monitor can display only a part of the picture that the highres monitor can.

Using the mouse in this setup would kill the immersion. Probably the next version will have a resolution of 1920x1080. But the horizontal resolution is split between both eyes. That means 960x1080 per eye. My feeling is that this is still not enough. Maybe with the nonuniform pixel/degree-fov distribution: it could work. No. What really count is pixel per degree (or arcsecond) FoV.