Phobon

First of all: Thank you for this awesome plane! Everything from systems to flight modelling feels extremely detailed and convincing. Regarding the removal of NWS, I think what we really need is one of those blue shirts (check 6:15-6:34): Simulating that is probably impossible with DCS right now, but maybe allowing NWS (maybe even toggleable per mission?) would help get around the fact that we don't have ground personnel to help us turn.

Sorry, I'm not at home right now so I can't show you my working file. But your version should contain a large list of similar looking lines. Just drop it somewhere in there :) If you did that and still have problems, your editor might have messed something up while you were editing it. In that case, I recommend repairing DCS to get the original file back and then try again with Notepad or even better Notepad++ I will post my complete file in a few hours when I'm back at my computer. default.lua

As a temporary fix, you can add the following line to your "DCS World OpenBeta\Mods\aircraft\AJS37\Input\joystick\default.lua": {down = 3006, up = 3005, cockpit_device_id = devices.NAVIGATIONPANEL, value_down = 1.0, value_up = 1.0, name = "T1 Fix (Hold)", category = "Radar"}, and then map the new command "T1 Fix (Hold)". I've used this for the first detent of my Warthog Trigger and it works fine there.

I'm not sure if this is the correct place to post this, but I have noticed that in the external view of the A-10, the engines look blurred only for the left eye, while the right eye sees the blades sharply like when they are standing still. Not a huge problem, but it looks a little strange when looking at the model in the external view using VR. Edit: Seems fixed in latest patch, together with grass and the popping in of land at the peripheral vision. Great work ED!

There is a long-existing bug in the oculus runtime which does not set the IPD (distance between the eyes) correctly. So if you have an IPC which is not the average of 64mm, everything feels either too small or too large. For me, all cockpits in DCS look like they're not even 1m in width since I have a relatively small IPD. So we can only hope Oculus fix this problem soon or ask ED to implement their own IPD adjustment option like some games have already. Links to bug reports on the Oculus forum for those interested: https://forums.oculus.com/developer/discussion/40662/ipd-lens-spacing-is-not-being-used-for-video-displayed-in-hmd https://forums.oculus.com/developer/discussion/33209/bug-ovr-getrenderdesc-always-returns-default-ipd-64mm-until-slider-is-adjusted

I had the same behaviour when I installed 1.5 and noticed that I had another controller bound to the Thrust-Axis. After removing this duplicate binding, everything worked perfectly. Might help to check your axis bindings...

As soon as you radio the tower you're inbound, they turn the lights on. (At least they did for me when I tried yesterday)

To those with the "can not resolve hostname"-error: I've had the same problem but was able to install after manually setting a different DNS-Server for my internet connection (I've used Google's 8.8.4.4) and then flushing my DNS cache ( Open a command line as administrator and execute ipconfig /flushdns ) For those where dcs_updater crashes: Exception c000001d is an "ILLEGAL_INSTRUCTION" exception. Maybe the new updater uses some SSE4.1 extensions or other "new" instruction set your CPU doesn't support? EDIT: Or maybe you have a 32-bit CPU or OS? If so, make sure not to run the 64bit-Version of the updater. (Though DCS is 64-bit only from now on if I heard correctly?)

This has recently started to happen to me as well. Every minor damage I receive results in all three wheels completely gone. Seems kinda strange, considering there are never any blown tires, as there were before, and it happens no matter where I get hit. I'm starting to get quite good at landing on the struts but I kinda miss the regular emergency landings with at least a few functioning wheels... :smilewink:

+1 Especially in the CAS missions of the A-10 campaign (with CA) it would be immensely helpful to see where the ground troops are supposed to end up. Adding custom annotations to the map would be even better.

The HSI rotation only aligns to the heading you have entered manually (100 in your case). But runway 10 does NOT mean it has an exact heading of 100. There is a pdf with all the airfield infos including exact heading for the runways somewhere in the DCS folder. (EDIT: under \Doc\Charts\) The only ILS info you get in the HSI is the line inside (don't know what it is actually called) which shows the ILS course deviation. That is perfectly aligned in your picture.

Same problem here Just wanted to say that I've got the same problem. The game itself is running pretty stable but whenever I exit a mission, it just crashes to desktop. I'm also running Windows 8 64 bit. Before updating to 1.2.1 I had no crashes whatsoever. dcs.log.txt me.log.txt DCS-20121023-204522.crash.txt