mhe

Bei Updates kann es eben vorkommen daß sich die Configs bzw auch die LUA Files der Flieger wieder auf die Standardversionen zurücksetzen. Ich hab mir die gepatchten LUAs der A10 für die Exporte als JSGME Mod gepackt, da kann man alle Mods auf Knopfdruck deaktivieren, schnell updaten und danach mit einem Mausklick pro Mod auch wieder aktivieren, macht das ganze updaten relativ schmerzfrei. Sehr gutes JSGME Tutorial von Ebs gibts hier. :)

I suspect that this or next year, we will have either 1080p or perhaps even 1600p, and then we will see 4k and 8k from there within a few years, my guesstimate is about 2015 for 4k and 2017 for 8k in a 7 inch display. Perhaps once panels get small enough, they might even put 2 separate display panels in there and do the screen fusion in the display driver, just like surround and eyefinity do today. The most important aspect is getting software support out there in order to have a huge variety of supported applications for the device so the industry has an incentive to go up in resolution and pixel density even beyond what is needed or does even make a difference in the smartphone market. It is essential that during the timeframe the Rift can share display panels with the smartphone market, it gains enough momentum and market presence to have display panels catered specifically to it once it outgrows smartphones and small tablets - a 4k screen in a device with a 7 inch or even smaller screen doesn't really make much difference to 8k, the dpis are simply so high once you reach that, that the Rift might be the only application where such extreme pixel densities are needed.

Of course it isn't quite there yet, which is why the current model is labeled a developer kit, you have to start somewhere, right? ;) The only "problem" with the concept so far is not being able to see a keyboard (which there are several very nice workarounds available for right now) and people concerned by knocking over their beer. Taking this as reasons not to acknowlegde the potential of such a solution seems a bit ignorant to me, hence the perceived aggressiveness. It is all about the potential and vision, not about the best option for current DCS flying. But it would be nice to get DCS prepared for this technology so it is ready once the better hardware comes out. Preparation and planning... ;)

Metalnwood guessed right... ;)

Well, the Rift is one of the most promising concepts for the future of flight simulation - even the hardcore crowd. Not being able to fathom an alternative for simple things like chatting (ever tried Teamspeak with TARS?) and bashing on the Rift as an unnecessary gimmick is not what I like to think of as a decent discussion. If you don't like it, don't buy it, ever. Unless you try it, you won't ever know what you are missing out on anyway. Earlier in this thread we even had videos of concepts of motion control usable for clicking switches in a 3D pit without ever needing a keyboard. Also you could use mice, trackballs, Leap Motion controllers for clicking and typing. You could even hack a Razer Hydra apart or do something really crazy with an Arduino or similar microcontroller you hook sensors up to. Oh and let me tell you something about the praised 3-screen setup with TrackIR: I had it up and running with 3x27" but after a while I disassembled it and went back to a really large single screen. Why? Well, if you want to fly at a framerate you can live with, you will have to define a large single main viewport instead of using the 3-cam setup. So when you start rotating your head with TrackIR, you will end up looking at one of the side screens. So far so, good, but once you realize that due to the single cam setup necessary, the correct center remains on the center screen, resulting in a pretty distorted view on the side screens. Alternatively you could keep looking at the center screen with your TrackIR while rotating your head, but that would somewhat defeat the purpose then, wouldn't it? Visual immersion could perhaps somehow be quantified by how much visual real estate a display takes up. And you cannot compete with a Wide-FOV HMD in that area, it is basically like strapping an IMAX to your face. Sorry, but I couldn't help myself after reading all these aggressive posts.

This is actually a really simple thing. Since I've had both Obuttos, I can tell you the differences right away and you simply decide which path to take based on that info. ;) 1.) The r3volution weighs twice as much as the oZone. Pieces touching the ground are rectangular instead of rounded, meaning that if you place the oZone on a mat or something like that to prevent if from scratching the floor, it will wobble sideways slightly, depending on thickness and softness of the mat. 2.) The flexibility concerning screen positioning is really far far superior on the r3volution as it comes with its separate monitor stand. On the oZone you can only adjust 2 steps of height on the screen but nothing else, distance is controlled by sliding the seat forward and back. On the r3v, you can basically move the screens in any direction and even rotate them. It will take huge screens like depicted above. It is a bit of a hassle to align triple screens with it, but once set it holds them steady. 3.) The r3v comes with upgrades like a cup holder and the much improved keyboard tray out of the box, on the oZone you will have to upgrade to have these features. 4.) The oZone acrylic table plate will deform over time, meaning it will begin to hang on the sides if you don't bolt it down (it doesn't even come with drilled holes for that to begin with) and you have to remove it and place it somewhere if you want to mount a touchscreen for flying like I did, which increases setup quite a bit. If I had to take that decision again, I'd go with the r3v hands down. And I hope you will enjoy the Warthog center mount! (I'm the guy whose mod it is actually built on) :D

I know it's not really a FC3 aircraft, but it is basically the same concerning detail level, so the question is does it also support the Su-25T? Great tool by the way, just updated! Looking forward to CA support as well, this will make for really great multiplayer sessions...

You wouldn't actually need a QNH given by ATC. If you know your starting airfields elevation above sea level, you would simply need to adjust the altimeter so that it reads field elevation instead of zero. ATC gives you QFE, which is somewhat redundant information if you intend to depart, because you can simply zero your altimeter and read QFE from there. Another story if approaching the airfield to land of course.

Gar kein Problem, da hab ich gar nicht drauf geachtet - ich war nur etwas erstaunt daß im zentralsten Forum über DCS auf meine kleines Tutorial verlinkt wird. Da werd ich ja ganz verlegen. :D Hab mich auch auf Fox' Post bezogen. Also falls ich helfen kann, mich erwischt man auch hier, ich schau öfter mal rein, auch wenn erst seit kurzem in die deutschsprachige Ecke des ED Forums. Aber es wird mehr werden, versprochen. :book:

Gerne! :thumbup:

Yes, but Eagle's incentive would be to sell more DCS modules if they supported the Rift, not vice versa :D It may come down to a hen/egg problem.

I don't think you'd need to tweak the engine so much since much of the output configuration is already in LUA. Don't know about engine internals in detail, but all we'd need is render 2 viewports (one for each eye), which could be done with Monitor Config LUAs right now. Neck modeling is not needed in the binaries (PeterP's mod could suffice), we would only need the barrel distortion shader perhaps as a configurable on/off parameter for a Viewport. And the 60fps issue might be something if you use many CBUs, but given that the current Rift has pretty low resolutions, I think that framerate is perfectly achievable in fullscreen with decent rigs today. Also, keep in mind that EDGE might bring DX11 and a decent performance boost to the table, perhaps even resulting in proper SLI/Crossfire support for those with really beefy computers. Also, the 60fps argument is somewhat questionable. I know you want VSync on to prevent a headache due to the image tearing, but what if the panel refresh is something higher than 60Hz? That would give us some headroom. Think 120Hz. Or 80Hz. With each of those, 40fps with VSync would be doable, resulting in a frame interval time of 25ms for the frame alone, add the 5ms acquiring tracking data and you're still within the 30ms margin that would suffice for some people, but resulting 33% less load on the graphics engine. For the mainstream, 4K is currently very far off because video bandwidth of both HDMI and Dual-Link DVI are not sufficient if you want to have 60Hz refresh.

If you are a Weana Batzi as well, we could all get together for a beer and subsequent flight tests. :smilewink: Just a shitty one, made with a cellphone when finalizing the build and while testing the rig I made for someone. Please forgive the mess ;) Need to take pictures in full flight mode, that will take some time and some decent lighting, artificial lighting sucks. Seawas :D

Well, there is always the open source option. There is a Beta of FaceTrackNoIR somewhere on the web that can abstract the Rift's sensors and emulate TIR input to the running game, basically making native Rift Tracker support available to any game supporting TIR out there. Of course, only rotational control is possible at the moment, but when lateral movement becomes available on the Rift, this way will be the one to go. Why? Simple. 1.) ED cannot be held responsible for someone else using the TIR API via a driver. 2.) We would only need the optics distortion support natively (something not covered bei TIR terms), Immersaview HMD would be an option if ED don't do it themselves 3.) Some Open Source dev on the other end of the world can hardly be sued on the grounds of some american patent or DMCA, especially if he doesn't make any money with it. The only thing Naturalpoint could do would be forcing ED to remove TIR support altogether from DCS, which would only hurt TIR in the long run as ED would then be free to add support to basically every other tracker out there (and once Rift comes to the mainstream, it will be much bigger than TIR). NaturalPoint are the only ones trying to enforce their draconic terms and they encrypt their API to boot (which obviously doesn't help much as you can see). They either adapt their terms to the new situation at hand or simply nobody will implement TIR support any more once the Rift becomes available for the end user masses. Either way, the TIR quasi-monopoly on headtracking in the mainstream is coming to an end.

Oh, the signature... Well, that explains a lot! :D Yes, I already got the 47" screen up and running, works like a charm! It is amazing how much weight the r3v screen holder will take, although I had to bolt it to the floor to keep it from tipping over. Perhaps I really should make a thread about that thing... :music_whistling:

Also paid for Helios back when it was still payware and would gladly do it again. There are still a few bugs here and there, but it is the most functional touchscreen solution for DCS in my book. Of course I'd love to see a few features patched into its current state or even Helios 2.0 (make it payware if it helps), but these things take time. Also, Helios is limited by some missing features on DCS' end like the missing capability to export screens over the network. I tried all the DCS touchscreen interfaces out there and in the end I got back to Helios and there I stayed, for a very good reason. ;)

Found the time to grease mine yesterday, used the LiquiMoly Silicon DX grease. Also found one of the 4 metal poles a bit loose, the screw obscured by the little circuit board had to be tightened. Now the stick feels better than it ever did, thanks guys! :)

tintifaxl, this is an Obutto oZone, it comes full featured for 600 EU incl. all options available for it. You might be confusing this with the larger r3volution model, which is well worth its money. I upgraded to a r3volution from an oZone and I didn't regret it. Didn't have the time to make a thread for it though, but I did some pictures of my r3v rig which even made frontpage news there. Basically the r3volution is much larger, more flexible and configurable in almost every aspect. Given that costs about 50% more with all the upgrades compared to a fully upgraded oZone, I'd say we're definitely in a very reasonable price range. Simply compare it to all the other pre-made multi-purpose pits out there. :)

You're welcome! Great looking pit, did you use an arm to mount the touchscreen? :)

Popular science may not be the best source for this. Dev Kit version 2 will be available later this year and really everything points to a release somtime in 2014. So it might not be this year for the consumer version, but it will be in a not too long timespan rather than years.

1.) Know your tankers frequency, input it in the corresponding radio (usually VHF AM), make sure you have manual ("MNL") mode on the radios selected so you actually use the set frequency instead of some preset setting. Also, make sure your intercom knobs are set to sufficient volume and are not muted (meaning not pushed in). 2.) Try contacting the tanker 3.) Profit!

Camelbak on the back of my seat, drinking tube clipped on my shirt near my mouth. Bam, instant in-flight rehydration system! :D And it takes beer too! But don't combine it with a buttkicker, shaking beer makes it spill all over the place ;) In other news: Somebody beat me to trying a Leap velcro'ed to the front of the Rift. This is the future of flight simming I think:

The updater doesn't modify things located in your saved games/DCS directory as far as I know. So the monitor config lua and export lua stay the same. The only thing you might have to do is patch your instrument init luas (the A-10C requires this, I don't know if it is the same with the Shark). JSGME is the JoneSoft Generic Mod Enabler. You basically build yourself a file structure within a mod directory where you only have the modified files located and you can inject them into your installation with a single click or roll back with another click. Very comfortable, makes updates really painless. Look here for more info regarding JSGME.

nVidia GTX 680 4GBs are my vote then - no VRAM issues and it outperforms any AMD card in DCS so far.

If you line up and apply power while holding the brakes, how can you end up in the grass? Is there any asymmetry in your brakes going on? I'd assume if you just brake to little, you'd at least be going straight.