Hippo

Maybe all the aircraft are reluctant to take off because aircraft are coming in to land in the opposite direction? ;) Takeoffs appear to be from 03, landings into 21. Sorry, but I was intrigued by this choice. My understanding is that take offs and landings are (almost) always into wind. Or maybe it's actually this way in real life, a sort of military aviation game of "chicken"? Kidding aside, loving this campaign as I fumble my way through it. The missions AND pdf briefings are excellent. Great work.

Hi, this one has nagged at me for ages. I use VAC for comms and it would be really helpful if the same key was always assigned to the same command. e.g. on one submenu on the A-10 "abort takeoff" is assigned to F3, but on another it's F2. This makes it impractical to assign an "abort takeoff" command, as it won't work in all menus. Another example is the "rejoin formation" command, which gets a different key on flight / wingman menus. I do realise that - this is a very specific request - there may be practicalities I'm not aware of that make this impossible - it may make things worse for people using the keyboard However, I thought I'd ask anyway - don't ask, don't get and all that.... Alternatively, does anyone know if is there a way to change the key assignments? Cheers. As ever, great sim, many thanks for all your efforts.

I did exactly this for someone just the other day and it worked fine, I had no issues with activation.

I may be misunderstanding you, but this is how I dealt with this issue: Rather annoyingly, for the A-10C assignments for the first two MFDs are forced on you. To change them to whatever you want delete the following two files: \DCS World\Mods\aircraft\A-10C\Input\A-10C\joystick\F16 MFD 1.lua \DCS World\Mods\aircraft\A-10C\Input\A-10C\joystick\F16 MFD 2.lua (NB if you do this I think you will need to reassign all the OSBs, etc again)

I believe it should be called whatever the reference is in the file: "\DCS World\Mods\aircraft\A-10C\Cockpit\Scripts\CDU\indicator\CDU_init.lua" In my installation it's in the line "vp = env.ED_A10C_CDU" so I use ED_A10C_CDU You might want to look at my earlier post (in this thread) to see where I got versions of the *init.lua files from, they all work for me. I can also confirm that the latest update has resolved this issue for me - many thanks ED.

"Where did the HOTAS In and OUT install? IN HID, Other devices... and in the Universal Serial bus controllers.. as mine did?" In Universal Serial Bus controllers.

I would suggest you try what I suggest above. Not sure about JSGME (I think this is a patching tool), which I don't use. I'm also using my own profile. To summarise, install a clean Helios, copy the loz profile to my documents/helios (IIRC this profile might need a bit of extra setup, see the readme), and copy the export.lua (try the version I suggest above) to the Scripts folder in Saved Games.

please ignore

It is working for me (only tried A-10C so far). However, I am getting VERY ANNOYING stutters every few seconds when I turn Helios on. Is anyone else seeing this / have any suggestions how to fix it? ** EDIT ** Stutters seem (could be intermittent) to go away as long as I start Helios before starting DCSW (and don't start it whilst already flying). I have just done a clean install of Windows 10 (I was on W7 until a few days ago) and of DCSW 1.5. I installed Helios, then copied my old "my documents\helios" folder from my W7 backup. I also had to copy my old export.lua to the following location: "C:\Users\USER_NAME\Saved Games\DCS.openbeta\Scripts\Export.lua" (Note that I had to create the Scripts folder). I use the export.lua offered in the following thread: http://forums.eagle.ru/showthread.php?t=97222

Getting similar issues. I export screens to a second monitor for A-10C; I followed the exact same procedure* to setup 1.2.16 and 1.5; works well on 1.2.16 but not so good on 1.5. *1. Add the following file "D:\DCS World OpenBeta\Config\MonitorSetup\MultiMonitor01.lua" (contents at end of post to avoid clutter) 2. Set the displays to MultiMonitor01 in options 3. Set resolution to 1920x2160 in options 4. Replace the appropriate *_init.lua files with those from here (BTW, many thanks to whoever posted these). 1.5 I get this: Or this on the ground: [ATTACH]122948[/ATTACH] (note that by this point I have stopped the displays showing in the 3d cockpit). **** _ = function(p) return p; end; name = _('MultiMonitor01'); Description = 'MultiMonitor01' Viewports = { Center = { x = 0; y = 0; width = screen.width; height = screen.height / 2; viewDx = 0; viewDy = 0; aspect = screen.aspect * 2; } } Ekran = { x = 1212; y = 1220; width = 119; height = 90; } PVI = { x = 1520; y = 1330; width = 300; height = 150; } Shkval = { x = 568; y = 1099; width = 600; height = 400; } ABRIS = { x = 568; y = 1552; width = 466; height = 583; } ED_A10C_LEFT_MFCD = { x = 20; y = 1095; width = 450; height = 450; } ED_A10C_RIGHT_MFCD = { x = 1450; y = 1095; width = 450; height = 450; } ED_A10C_UHF_REPEATER = { x = 582; y = 1159; width = 140; height = 31; } ED_A10C_CLOCK = { x = 1175; y = 1108; width = 150; height = 155; } ED_A10C_CDU = { x = 1520; y = 1820; width = 320; height = 243; } --[[ ED_A10C_UHF_PRESET_CHANNEL = { x = 338; y = 1756; width = 29; height = 29; } ED_A10C_UHF_FREQUENCY_STATUS = { x = 221; y = 1842; width = 132; height = 29; } ED_A10C_CMSP = { x = 1302; y = 1771; width = 270; height = 60; } ED_A10C_RWR = { x = 521; y = 1082; width = 233; height = 233; } ED_A10C_CMSC = { x = 829; y = 1118; width = 293; height = 70; } --]] UIMainView = Viewports.Center

PLEASE IGNORE JUST SEEN AN OLDER POST REPORTING THIS Not a big deal, but this does not happen to me in 1.2.16. I have some controllers with long descriptions, and as I scroll right the controller name text overwrites. So, from this... to this as I scroll...

I've just gone from 7 to Windows 10 and have had quite a few problems getting Foxy working, however, I believe I now have it working correctly. I have lots of files I've worked on over the years and am perfectly happy with Foxy, so can't be bothered to relearn and switch to TARGET. Anyway, this is what I did to get it working.

There appear to be new (well a few days old) drivers that mention changes / fixes for the MFDs / Windows 10. http://ts.thrustmaster.com/eng/index.php?pg=view_files&gid=1&fid=3&pid=298&cid=1 Haven't tried them yet, so don't know if they improve things.

RE HOTAS Cougar getting Foxy to work downloading files etc, in Win10 This worked for me: Unplug Cougar Installed old drivers (2007_hco_vista_64_rc1.exe) - http://ts.thrustmaster.com/download/accessories/pc/hotas/exe/HOTASCOUGAR/2007_HCO_VISTA_64_RC1.exe (Assuming you're using 64-bit) (Foxy is included in this installation, so need to download and install it separately.) Plug Cougar back in In device manager Thrustmaster HOTAS Cougar (IN) Thrustmaster HOTAS Cougar (OUT) appeared as devices without a driver (yellow triangle) told device manager to update the driver for each of the devices and pointed it to \<cougar driver install folder>\drivers\ This makes the above devices work properly and I was then able to download files, etc. Hope this helps. Good luck

# -------------- 20130802-194305 -------------- # C0000005 ACCESS_VIOLATION at 40327FCF 00:00000000 00000000 00000000 0000:00000000 40327FCF 0030F020 0000:00000000 40328BAE 0030F050 0000:00000000 40322185 0030F140 0000:00000000 ED474D30 0030F220 0000:00000000 ?process_@ActionDispatcher@@AEAAXUActionEntry@@W4ActionOrigin@@I@Z()+60 ED474EF6 0030F260 0000:00000000 ?dispatch@ActionDispatcher@@QEAAXAEBUActionEntry@@W4ActionOrigin@@I@Z()+16 ED4751D6 0030F2C0 0000:00000000 ?feedToDispatcher_@ActionSource@@AEAAXAEBV?$vector@VInputAction@@V?$allocator@VInputAction@@@ed@@@ed@@@Z()+D6 ED475645 0030F320 0000:00000000 ?processInput_@ActionSource@@AEAAXXZ()+75 403056C2 0030F3B0 0000:00000000 403081BD 0030F410 0000:00000000 4031E444 0030F440 0000:00000000 4031E31B 0030F470 0000:00000000 403B2AC8 0030F4E0 0000:00000000 403B407E 0030FAE0 0000:00000000 403B6CCB 0030FB90 0000:00000000 76F4652D 0030FBC0 0001:0001552D C:\Windows\system32\kernel32.dll BaseThreadInitThunk()+D 7707C521 0030FC10 0001:0002B521 C:\Windows\SYSTEM32\ntdll.dll RtlUserThreadStart()+21

I've just come back to BS2 (latest DCSW version) after a few months away. Does anyone know if these (considerable) comms changes have been documented anywhere by ED (in a readme perhaps)?

Hi, loving the P51 - as always outstanding work from ED. I did have one concern regarding DCS World, though. It appears that apart from the controller options, the other options appear to be universal for all aircraft. I would have preferred to have the ability to set (especially graphics) options according to aircraft: surely something like the A10 with multiple MFDs and beautiful 3D cockpit must require more processing power than the Su25T.

Quite right about the door, thank you for replying - not sure what I had done wrongly before. However the ABRIS increase / decrease I really would like to have working on a button, and I cannot find a way to do this so that it works acceptably.

Hi, I realise that these aren't a big deal, but it would be nice if they could be looked into and fixed if it's not too much effort. 1. I have several TM MFDs and a Cougar, and try to not have to use the mouse / keyboard if at all possible. When I try to map rotating knob functions, e.g. the ABRIS select knob, or the HUD brightness knob, to buttons (or even the keyboard) they are too sensitive - i.e one press of the button equates to many turns of the cockpit knob. 2. The following functions don't appear to work when mapped to buttons (and it would be very useful if they did): the frame rate display, and door open/close. Thanks for looking.

Here's a screenshot of what I was getting. It doesn't really do the issue justice, since there was flashing and spiking and it could get a lot worse than this.

Just in case anyone else is affected, I just thought I'd post an update. After being extremely irritated by this and being unable to resolve it, I rang up the GFX card vendor who seemed certain it was a fault with the card. It was RMA'd and (after 28 days!!!) I got a replacement. The good news is, the issue is resolved. The card is a Palit nVidia GTX 580, 3GB. The problem I was seeing was intermittently I would get flashing black triangles / lines. It seemed to get worse the more graphical options I turned on. The strange thing was that it only happened with A10C. I had played other graphically intensive games (e.g. Crysis 2) without a single glitch, and didn't see a problem with any other of my flight sims.

"Looking pretty promising for the new driver. Flew for 1/2 hour, overclocked, cpu between 50-60C, gfx at 80C, didn't see the issue at all." Nope, it's happened again.

Looking pretty promising for the new driver. Flew for 1/2 hour, overclocked, cpu between 50-60C, gfx at 80C, didn't see the issue at all. I'm not sure if I'm imagining it, but have all the colours just got a bit less intense?

Installed the new driver, and the problem did not occur. Don't think this means very much, will need to run for longer, but on first impressions looks promising.

Hmmm. Problem appears to be related to gfx card temp, for one thing it appears after a while. I also tried running the fan speed at 100% (instead of auto). This kept the temps a bit lower; the problem did still occur, but a lot less often and it was less severe.