snuffles

C'mon guys..it's not *that* difficult, is it? I've only just begun to get serious hours in the A-10C's pit and FLIR isn't a headache. I didn't fly the A-10 in 1.2, so I guess I wasn't spoiled by bad graphic representations.

Think about the physics of it, though? It's very likely the only hotspot of the tank you're looking at will be the exhaust and engine sections, and those are concealed as well. In any case, it's just my two cents. Life is hard, Sims are supposed to be hard, too.

Thanks dude, I'll give it a go as soon as I'm back from Work. Cheers!

lol that is totally cheating if you don't remove that in MP. For what it's worth gents, you're playing against an enemy force that employs camouflage. Secondly, the hotspots of an operating vehicle are not the same as you see in games like ARMA. The problem you are facing is not a bug; you're lucky the FLIR is so clear to begin with. The problem here is that you're getting used to a more realistic representation of thermal camera limitations. Sure it's difficult, but not impossible.

All good. The latest 1.5 release, not bothering with 2.0 unless I have to

bump?

Thanks Col! That's made progress, but not fixed yet. The main monitor isn't displaying correctly, but the Client is now seeing MFCD information. Screenshots attached: Server: http://puu.sh/mo3cF/faf075cab3.jpg Client: http://puu.sh/mo3kZ/426db97b38.png You can see that the Client is getting its' info from the output on the far right of the Server's image. What's next? I've rolled back the changes for now. Cheers,

New User I couldn't find this problem in this thread yet - The Client and Server are working, but the Server isn't giving the correct output on the client MFCD's. The lumatek.lua file doesn't generate, and I don't see an error for that. Client (Yotaphone2 Android L) and Server are v1.3.1 Client output: http://puu.sh/mmVVa/321288e775.png Server output: http://puu.sh/mmVuu/7de17fac51.png I use TrackIR as well, will the change in camera angle affect the software's ability to display the MFCD's? Settings are for 1 monitor (1920x1080), with the intention for the MFCD info to be displayed on the client device (1080x1920) I would tinker around, but it's not my software and the last time I did that, it got me in hot water.. I tried the setting for two monitors for a combined resolution of 3000x1920, couldn't easily access DCS' OK/CANCEL buttons for a good while..

This isn't a bug, it's the lack of presence of a third party file.

dude, it's 2015 upgrade your rig or update your sig.

I've always thought it was just plain odd that this wasn't an option. Pretty much the reason why I don't fly any of the US Airframes at all.

My bad habit is always flying something else...

I would expect that it's part of the completion project for FC3, so yes. Just - in good time.

I don't have a problem with the openbeta sounds. It sounds like I'm wearing hearing protection, which I can appreciate. On the other hand, I'm not opposed to improvements in ED's audio work. The SU-27 just sets the standards quite nicely high, which we have always come to expect from them :)

no, just the thread seems departed from the topic of takeoff, in the '109.

talking about AIM-120 in t-minus...

I believe that under the folder /mods/aircraft/controls there is a headtracker folder - copy that from a mod where freetrack works, and paste it into the K4 folder. Solved the problem for me, and I didn't have to go through the papercuts of remapping manually for a new mod

I have a Tefal FV9920

I think Fri13 has a good point - we're putting a lot of faith into EDGE being an improvement, and we're speculating too much on how much of an improvement it'll be. Afterall, there's little information to go on as it is. And yet, still zero benchmarking for DCS. It isn't harmful to question the concept. Daisies might still face up to the Sun, but their roots are still in shit.

No worries man. Christmas is coming for someone out there

nice idea, but don't forget that there's a certain level of assumed knowledge required for a study-sim like DCS. Besides, having to bind these buttons to actions manually is actually quite good - customised and even much more efficient layouts are quite common

If you're going down the FreeTrack/FreeTrack route, don't skimp on your webcam - or, do your research at least. You will need it to sample at a decent resolution at 30fps minimum. Resolutions above 720p are ideal

Glad that you've done what was needed and copied-in the headtracker.dll. A shame about the freezing issue, though. What version of Windows are you running? I found I had similar issues under Win8.1. I changed the Compatibility settings for FreeTrack to Vista SP3 with RunAs Administrator. WTB FreeTrack Software Support

This is true - so without verified ballistics data readily at hand we can only make educated guesses. meh!

I'd like to see it working, too. That would be a really nice touch :)