npole

Devi usare il tag URL senno' I link si tagliano... :)

...so, next time: do not buy any not-DCS level product/plugin, but instead (if you want to finance ED), buy another copy of your A10/BS and give it to a friend.

Me too... after only 1 day, and after have spent hours to setup it, I had to remove SoftTH because it doesn't supports alt-tab ...a feature that is a way too important for a simulator (at least for me), since often you need to look at external material, docs, whatever .. and you're forced to quit the mission.. basically unusable.

For this reason I've just removed SoftTH, not being able to alt-tab is a big no-no-no for me; sometime you need to look to a chart or just read an email or whatever.. and you need to quit the mission to do so, no way.

Ah the HDR, I've assumed it were working with SoftTH... i have the HDR turned off tho, to gain more FPS.

S/N: #8676 ITALY

Helios doesn't export the contents but the data, so no, it won't export the MFD (it can only duplicate a portion of the screen tho.. when in windowed mode, using the screen duplicator.. but it's laggy and not convenient). What's the problem with the sun bloom?

Without a clickable cockpit I won't pay more than $0, because: 1) We have already free mods with awesome exteriors. They doesn't have a perfect modeled interiors, but I don't see any advantage of having a cockpit that I can't use.. If I want a nice image I can use a picture on my desktop; 2) I don't want to learn thousand of different key-combos. I want to learn the switch position on the plane and use them, like I do with my A10C and like I would do in real life. 3) I plan to use a HMD (today it's the oculus rift, tomorrow it will be something else), I want to be independent of the keyboard, I want to use my HOTAS and use my cockpit.. not to look around blindly for my keyboard. If ED is desperately looking for money, I would be glad to give my contribution (they could start a kickstarter project), but only for the simulative modules (at the same level as the A10C .. *minimum*), I wouldn't pay a cent for anything else.

Some progress. Settings one of these two to "1" solves the issue (no stutters and same FPS as full-screen): compatibleVB=1 enableVBQuirk=1

I did more tests and noticed something odd... I'm progressively disabling the AA and the HDR.. however.. with this config i'm having 75fps in full screen with no SoftTH; with softTH using the same monitor alone and the same config i'm having the half: 37FPS. There's must be something i'm doing wrong, or eventually SoftTH isn't capable of taking advantage of the SLI (as DCS in full screen does...).

Stuttering, the FPS seems fine apparently. I've also tried to use a single monitor configured into SoftTH and the problem remains. I didn't used a multi-monitor solution before, or to be exact I did years ago then I abandoned it, as I use mainly the A10C, and I've already a big monitor (30"), it was ok to move around the cockpit to look at things (ie: the MFD are big enough). Now I exported the MFD to the tablet (the plan is to use it for the CDU l8r), but first I wanted to check the performance with SoftTH, because in windowed mode the FPS drop is a way too high. PS: i'm doing the test with my second monitor (24") not with the tablet, as I wanted to eliminate any possible issue from the equation.

You can use your Android tablet as an additional monitor, properly recognized by Windows. From there on, the other steps are the same you would perform with a traditional additional monitor. In example I've my MFCDs exported to my Android 7" tablet (a cheap 50 dollars one...) and it works like charm, you don't even need to have a cable, it will works across WiFi. There's some small lag, but it won't affect the usage as it is barely noticeable for a MFD. The magic? It's about this app ($3): https://play.google.com/store/apps/details?id=com.avatron.airdisplay Tips: it even recognizes the touch screen! So you can export in example a working CDU using Helios and having it on your tablet (both the screen a the keyboard) and make it working! :)

I started to test SoftTH ... and it gave me a FPS boost apparently, but with a price: heavy stuttering. :( I tried to give a look at what to adjust to solve/mitigate it.. but didn't found anything. Initially I tough it was because of SLI, but it remains even disabling it. I have no problems with single screen in full screen or in windowed mode (no SoftTH). Any idea?

Check if your EAC is functional. It may be disengaged (right warning lights panel).

Al Licheni?

3 days are enough to learn and 1 week to handle the essential functions to flight and weapon engagement. It requires much more to know about every single function of each switch and takes the most of the plane, but this may comes with the time and experience. What's most important: it's not a matter of difficulty, it only depends if you like the simulators or not, because if you expect to be immediately in the air at shooting things, then you may not have the patience for this. Most of the time spent in the A10C is about route planning, weapon handling, instruments settings.. the moment of firing at something is really a couple of seconds (and is NOT the funniest part of course).

I hope they will abandon this semi-arcade route... or having it restricted to FC. I'm playing DCS because I want a serious and 100% simulative experience (where possible), if I want to switch a button to lock and fire I would play with the Xbox nowadays. I wouldn't give em any more money if not for modules that aren't AT LEAST at the A10-C level.

Technically it will actually help to NOT use the keyboard. I rarely use my keyb to be honest, first I have my hotas and second I really like to use the real switch with my mouse into the cockpit (for me DCS is only about sim, no-DCS cockpits are not my affair.. so I fly the A10C), being able to point at them immediately (without the contortionism you need with the trackIR with switches on your side) would give a incredible help, from there you can just click em, you don't need any "glove" or any other futuristic device, it's a matter of see them > point them > click ... no keys to rembers on your keyboard or 75 keys combos (lol) to input a command. :) I can play the devil advocate, but I don't really see any single reason of why they shouldn't implement the OR today. If it was a matter of months I would agree: there's other much import things to finish; but we're talking about a very minimal coding (for a basic implementation) that would give a tremendous boost to this product (if not, on the PR side). Again: adding the Oculus Rift support is no-brainer... we should have it already!

I'm interested too, i'm looking for 2 copies for two friends of mine at a offer price. If anyone's around...

Great job Burner, that's a good workaround until the devs will put an eye on it (whatever we do, a native support would be better of course..).

That argument is child of a (common) bad interpretation: it's not that the human eye cannot detect beyond certain fps, but that the human brain identifies as "animated" something moving at (least) a certain fps. In fact the human eye/brain is capable of collecting a maximum of 240 images per second, so the limit where you won't notice any difference is beyond that number. You don't even need to know the science to demonstrate it, any gamer could easily tell you when a game is running at 60 fps or 120 fps in example, you don't need an eagle eye to perceive the difference.

The question now is: ...after 33 pages, where are the devs? It's not that they have to think much to post a reply with their ideas.

I've followed the implementation (under the technical aspect) of the OR into a game being developed today (dx11), as said for: stereoscopic 3D, distortion, settings (idp/fov), headtracking (2dof).. so a basic but complete implementation, took around 2 weeks (single coder working time). I then expect a longer finish touch and tweaking task, but this is normal (if we look at DCS itself, we're "re-touching" by years already. If you look at the SDK, it's so easy (and cheap) to implement into a game that it is really a no brainer to do so, I do not see any single reason of why a developer shouldn't do it, considering the costs (time) vs benefits. A couple of notes: 1: the story of the 60fps is just that.. a story, you don't really need 60fps to have a nice experience with the OR. However I don't see how this could be a problem, DCS isn't that resource demanding (if compared with today standards). 2: you really NEED head-tracking (I hope they'll add the 6dof in the final version). Playing anything that involves the user control (ie: a car simulator, a flight simulator) without moving your view (with your head) causes much motion sickness (you know if you ever tried Dirt2 via vireo.. you gonna puke after 2 minutes).

I would point the fact that adding the OR support natively it is VERY easy, it requires about 2 weeks of man work (coder) to adapt the rendering engine. It's not really a matter of time, it's just a decision. I believe that any first person view game developed today should take this in consideration, since this is gonna be a major game changer.

It is, if we consider the whole "pack": The TIR is an overpriced piece of hardware, that existed until today because none developed something similar (since the niche market).. that's until someone come up with the facetrack. We need to support better technology, not to pay for something that doesn't improve by 6 years.