Dachs

I think it's very individual what distance will work the best. I had a 46" TV before, but I couldn't get the screen and virtual horizon far enough down with my setup, and therefore had to look up a bit all the time. That literally became a pain in the neck, and so I switched it out for three 40" instead, wich for me hits the sweet spot. Viewing distance for both the 46" and 40" is around 90 cm/3' As for picture quality both sizes worked fine for me, although running without good AA and AF were close to a nogo on the 46" Both running 1920x1080.

+1

Oh, that could be cool, it looks like the software is using the forcefeedback output to drive the transducer. That means no more vibrations from all kinds of external sounds and radio communications, just vibrations originating from the aircraft. I wonder if there is any contact between ED and the Simexperience guys?

Hi Isegrim, no nothing to do with barrelchange it is/was just standard (Danish) combatdrill. I think now a days, if the first round dosen't hit then you lase the target again and fire one more time. If it still dosen't hit, you aim down a half MIL for the second shot and then up one MIL for the third shot. If there is still no hit, it's probably about high time to pop smoke and hit reverse :P Anyway, I'm a dinosaur, I was gunner on the Leo1A5 for the better part of 7 years almost a decade ago, argh, I feel old! Maybe the thermalsight on the Leo2 you used is better, although I heard from the guys that it's pretty much the same as on the Leo1. The flash from a hit could be clearly seen, both in thermal and daysight. But, I dont believe I observed tracer using the thermal sight other than with the slow HESH and longrange shots with APFSDS (3000 m or so) and of course MG. But, conditions vary, we usually had a lot of dust on the range! Well, enough of that, I guess the tank modelling in DCS still has some way to go.. Sorry to the OP for the hijack

Corrections while shooting APFSDS can be done using standard proven values, like aiming low by a half MIL on the second shot for instance, and going up by one MIL on the third. Provided you have the correct distance this ought to produce a hit! Again, you are very seldom able to actually observe the APFSDS shot due to dust and smoke. The only thing you can be sure to see is the flash of a hard target impact. Of course the dust part is very variable with regards to terrain,be it dry or wet conditions. Using the thermal sight for observation of impact is, in my experience, not very usefull either, the tracer is not all that easy to spot and if the penetrator just hits dirt, there is not much of a heat signature at all and then there is nothing to base your correction on. What we did have some succes with, was getting observations from a wingman who had a clear line of sight to the target and was able to see the tracer when it passed the target. All this is for fast APFSDS rounds, slow HE rounds are much easier to work with, at least observation wise, hitting targets with them though is somewhat harder.

Well, IRL it's very likely you won't be able to see your tracer when firing APFSDS rounds, due to their high velocity. By the time the smoke and dust from firing settles the round will probably have impacted already, unless fired at very long distances. Atleast 2500-3000 meters or so. However, if you get a hit on a hard target, the flash from the impact can usually clearly be seen through all the smoke and dust.

So true, actually I thought of exactly that phrase when I sat there trying out different things. :D There really is a lot of ways to reach the same goal with this AHK thing.. I just took a quick peek at the info on the Command List page for Send, but it seems like Sendinput or Sendplay is the recommended ways to send keystrokes? I did wonder if it was allright to just use Send, rather than SendEvent, but I couldn't see any difference in Foxy keytester. But, I do remember that Foxy and games didn't always "see" the same characters though..

Hi PeterP, thanks a bunch for helping me out here, and sending me in the right direction. Now, I probably mutilated your script, but after experimenting some I ended up with this: I haven't got the faintest idea if the #NoEnv line and the three lines under there are necessary, but Cubpilot's VAC script had it, so it seemed like a good idea to incorporate those. A quick question, the "up" and "down" is used to prevent stuck keys, right?

Just found the great AHK scripts for VAC and TIR by Cubpilot, and now I want to see if I can make a simple script that sends the Eject command. I was hoping to just modify the VAC script, but I can't figure out how to send CTRL+E three times in a row? There should probably be a slight delay between the three key presses also..? Any hints and help appreciated! (I'm way better at woodworking than this blackmagic programming stuff) :cry::crash:

Hi Deigs, I moved the radio menus as per PeterP's instructions, wich can be found here: http://forums.eagle.ru/showthread.php?t=88996 amongst a lot of other good stuff for multimonitor users. For actually using the comms menu, I use VAC (voice activation) [url=http://forums.eagle.ru/showthread.php?t=88996][/url]

Nighttime version? Loz, have you given any thought to maybe do a night version of your panels? I did a night refueling hop yesterday, with the lights in the room turned off, and the touchdisplay was rather annoying with all it's brightness. While I did turn the monitors hardware brightness control all the way down, it was still much to bright for nighttime. I wonder if it's possible to darken out all the inactive bits of the Helios dash and put some sort of green filter over everything else? A simple hardware fix for it would be to put a dark green transparent sheet of sorts in front of the screen, provided that the touch function don't go bonkers over that.. I can't fire it up to check right now, but the panel and instrument light rheostats don't have any effect on the Helios dash, they just dim the lights in the "in-sim" virtual pit, right?

Oh, it does support Vesa 100, it's just that the springloaded leg or stand is not removable. Well, not without taking the monitor chassis completely apart anyway.. When mounted the leg can be folded flat against the back of the monitor, but it then protrudes about 5 cm beneath the bottom of the screen.

Yep, I pretty much came to the same conclusion. It turns out it's not really in my way when it's mounted anyway, and this way I can just put it on a shelf to the side of my pit, when setting up for racing. It's pretty good for displaying the telemetry too.

Hi Loz, I just wanted to say thank you for the profile. I just got done setting Helios and your profile up, and it's really a work of art. That would likely have taken me forever trying to figure all that out, so I most definitely owe you a beer! :beer:

I just bought the ACER T231H and now I'm wondering, have any of you found a way to remove the springloaded rear support leg, short of taking the whole thing apart? As far as I can tell, the leg is screwed on from inside the cabinet ?

When I assign a mouse button in TIR to activate pause, the Warthog throttle radio button also activates TIR pause. It turns out that DX4 corresponds to Mousebutton 4, same for the rest of the mouse buttons.. :cry: Has anyone else observed this or is it some fluke with my rig perhaps?

Ah, ok, too bad then, because I don't want to run in windowed mode because of the fisheye effect. Funny thing is, the CDU actually do get exported using the "windowed" settings, although it ends up in the upper right corner on the right screen, where in windowed mode it would be in the lower left corner of the left screen. Also, it's display size seems to be double..

Is there a way to set this up with an eyefinity triple screen setup, when running in fullscreen mode/3 cameras - 5912x1080. I want to export the CDU to the outer, lower corner of either the right or left side monitor, however I can only get it to work when not running fullscreen, no matter how much I fiddle with the monitor configs. Any ideas?

A router will give you much cleaner cuts, but you have to use a jig (I think thats the name for it?) in order to make straight cuts. It's not really controlable when using it freehand. For curvy things, you will have to make a model first, using the jigsaw, and then you can make perfect copys of that, using the router with a ... copy ring? attached. <again, not sure what it's called in english... It does make quite a mess though, as it cuts up more material than the jigsaw, but then again, you won't have to sand so much after you're done cutting.

+1

This is quite a project, and a time consuming one at that! I know it's a lot of work getting it all to fit together. Thank you for sharing! Now, get back to work ;)

Is there any way you can get the fuelstate and remaining weapons info from your wingman/flight? If not, it would be nice if it got included in the comms menu, so one could simply ask them.

Thanks, now it works :) A suggestion for future versions: I'd really like a version with on 1 page just the UFC and radios, and one page with the CDU. The reason is I have the MFCD's exported to two small 8" screens with the TM MFD's on, so all I really need is the radios, UFC and CDU. I know you can't possibly cater to everyones needs and ideas, but hey, just thought I would throw it out there.. Oh, on another note, am I the only one who finds it extremely fiddly to get the frequency's tuned in right, using the apps touch rotarys? Maybe it's just my 10 thumbs? Otherwise a great app :)

^^^^ Me too :)

Had to go around on the first try at Batumi, but nailed it the second time around. Very disorienting, not to mention downright scary, when on final and hoping the lights will materialize out of the fog, preferably in the right place..