Warthog_Farmer

No issues for me - Intel + 980Ti latest drivers

Static AAA emplacement was invisible to me yesterday on a user mission. Could see it cycling F6 and see/hear the rounds. No track I'm afraid. Will try to reproduce though

I had a stationary AAA shoot at a large cylindrical gas tank as it was between me and him... Both me and my wingman had a good chuckle at the resulting explosion. Silly AI...

I agree. I'd love to see the gunsight removed for formation aerobatics.

Reviving this thread... Any further forward on this project? I follow this and your F18 HOTAS project very carefully and will most likely be one of the first customers on both products should you get them on sale! Cheers!

That line has always been there but grey in colour. It is part of the model and part of the real aircraft - not sure what it is for though. It would appear to be green to you because of the flood lighting illuminating it. A little excessive, perhaps, but probably not a priority for ED ^_^

Someone must have cut the vodka budget and now they are aiming straight...

+1 was wondering why this hadn't already been reported but never got round to doing it myself yesterday. My rig is in sig...

Hey, I think it's probably already known but I am getting clouds breaking through the cockpit wall in 1.5 Beta. Specs are in the signature and I can grab you screenies or whatnot tomorrow after work if required. Thanks

Same here for the low FPS on title screen with animation. Yet to try it static. For what it's worth it was showing 30-35 (nVidia ShadowPlay counter) and is a pain because gSync causes some slight flickering. System: 4670k i5 at 4.5Ghz plugged into Asus Maximus Vi with latest BIOS and chipset drivers 16GB Corsair RAM at 1866 EVGA GTX980Ti at stock settings Runs on its own Samsung 850 Evo SSD Windows 8.1 up to date ROG Swift 1440p

Hey folks, This is a truncated version of a Sticky in the forum on using the Autoupdater and applies to those with DCS OpenBeta (not steam) already installed but it's not picking up the new beta straight away. Credit to SkateZilla for the technique Navigate to the folder where DCS Open Beta is installed, LEFT SHIFT and RIGHT CLICK the "bin" folder and then click "Open Command Window Here". Then type "DCS_Updater.exe update" then hit enter. Et voila!

Folk who can't get it to update. Navigate to the folder where DCS Open Beta is installed, LEFT SHIFT and RIGHT CLICK the "bin" folder and then click "Open Command Window Here". Then type "DCS_Updater.exe update" then hit enter. Et voila! (Thanks to SkateZilla for the above work)

Looks like the server is under strain now. Started off at 10MB/s and now it's pootling along at 2.2MB/s.... Glad I got some in before the floodgates opened haha :) See all you guys "up there"

I'm over 2/3rds downloaded xD

I can't wait to try the PMDG NGX in EDGE! The wait is killing me!

Ok so there is a maximum.. At least our stick has a lot of buttons! I am guessing the throttle will be similar then? And as such no chance of fitting s rotary or two on there for radar controls? Cheers

Hey! I've followed this post for a while now, intermittently. It's been in my Firefox favorites bar since I first came across it! My question is - and I don't believe I've seen the answer - how will this interface with the existing hardware? I'm not a novice when it comes to hardware and software - but I am certainly no expert. I can kinda see how the stick will be easily replaceable - it'll slot into the same (what looks like) PS/2 connector in the base. Does the base have the brains inside it as to what buttons are being actuated or does it just act like a passthrough for custom USB drivers on Windows (To allow more/less hats, more/less buttons etc)... or is the limitation the number of hats/buttons already existing the default A10C stick? That should be the easier one I think... When it comes to the throttle base: I assume some user disassembly will be required. It doesn't look too difficult but is there any way of a quick switch system (for those who have been inside already). Secondly - a similar question to above - are we limited to the buttons which already exist or will there be a possibility to add rotaries etc to control radars etc... Thanks for your time

If it has the odd bug or two.. whatever... It's a beta for a reason. A release with a list of known "features" would be better than waiting another month in my opinion. Like many people here I've been waiting for this release since it was announced. I was super hyped this time last year as I thought "By New Year I'll be on EDGE". I've know these guys want to push out high quality products - but people need to remember a beta is a beta. It doesn't matter if it's a little bit broken - especially if they know about it! That's my 2 cents... I have pre-ordered the L39 and desperate to get into it...

Hello, I have recently got a friend into DCS and we fly together quite a bit now as we get the hang of the A10. However, occasionally we will get disconnected randomly. This follows fresh reinstalls on both sides using both the Public and Open Beta. We will connect without issue but after 5-30 minutes there will be a dropout of the client. The server will continue to run - but occasionally in order to rejoin the server the client must shut down the .exe and reopen. Port 10308 TCP/UDP have been forwarded correctly both ends. Failure to do so on the host side will prevent the client from joining (however it would appear the client doesn't necessarily need to do this - it doesn't have any impact to the joining/frequency of dropout) All the dcs.log file comes back with is: INFO NET: Lua: Disconnected client [2] "Bee" INFO NET: remove: client 2 Interestingly - the log shows that the client connects on a different port (63659) I think and something changes it yet again: NET: Lua: Connected client: id = [2], addr = x.privacy.x.x:63659, name = "Bee" NET: [2] UDP port changed from 63659 to 63590 When hosting the server I have the port set as 10308. Just wondering what the above ports (which seem variable) are for and where they have come from. Any ideas folks?

Anyone else immediately disappointed when receiving the TFC/ED email and then opening it to find it's not the 1.5 beta release? Haha! Oh well - looks good though! Congrats on getting it to the selling stage!

Take up flexwing microlighting. They have a set up you're used to!

GTX780 Classified (Non-Ti) I run everything on high and mirrors and runs at 60 most of the time. Maybe you could push a bit harder on the eye candy =p especially when EDGE comes out! Compared to my old HD7970 which struggled to push 30fps at medium and took massive stutter fits... I'm afraid it's sold - plus I'm an entire ocean apart from you my friend...

Hey! I bought a DK2 a couple of weeks ago to try out in DCS and a few other things. The technology is absolutely fantastic. The head tracking is fantastic without a doubt and I'm glad I had the oppurtunity to try it (and made a profit in the resale) but in retrospect I wouldn't buy a DK2 only for DCS... My greatest experience was flying the Huey low and fast or in the hover... It seemed to work fairly well. But for other aircraft I had difficulty with stuttering in the pit. It seemed the cockpit stuttered on a different schedule to the world outside stuttering - and I have a decent rig I'm not sure it was lack of horsepower causing it. I think the P51 was the worst for this nauseating effect. If you'd like the DK2 to try out all the tech demos available and just to try out the kit then by all means you'll enjoy it - but if it's mainly for DCS I doubt you will keep it for more than a few weeks (especially with the bidding war for the gear on ebay) Happy I got to try it - waiting on a release with a decent screen though...

Yes you are quite right for using the QNH in that example. 1:30AM isnt the best time for thinking straight Anyway - to try explaining again - the QNE is not a pressure setting it is a figure in ft which gives the airfield elevation above 1013 on the subscale. It is used where you cannot wind off the altimeter low enough in extreme low pressures (Not QFE

Just to be picky since you picked other guys up ;) - but back when I was a trainee controller we were taught of this mysterious QNE and, of course, have never needed it since... QNE is the altimeter reading when you are on the airfield with altimeter set to 1013/29.92 depending on your IQ ;) Standard Pressure Setting (SPS) is a better title for the definition you gave... Or in laymans terms we use Pressure Altitude or Flight Levels (for separation by altitude) I believe QNE is mostly used in high elevation airfields where your sub scale cannot wind off low enough for the QFE or if you're unfortunate enough to have your altimeter frozen on 1013 on arrival at destination - not that this is relevant at all to the OPs question but that's what happens when someone mentions Q codes