Hippo

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.

Well, FWIW. I haven't had too much time to try things out. I was running my i5 2500k at 4.2 GHz; like you no issues in FSX or other games. With medium shadows I was getting the glitches, I then put the system down to 3.3GHz and the issue went away. I then went to high shadows (still with 3.3GHz) and the problem is back. I get the feeling it's something to do with the graphics card, firstly because I didn't have the engines problem before (it's a fairly recent upgrade), and secondly I've searched the forums in the past because of the (engines) issue and could find no other reports of it. I will be trying the new driver. My CPU temps didn't go over 50C, the gfx card hits 75C. I'd say Crysis 2 hits the gfx harder than A10, and I've seen no problems with that game.

FAO Accipiter "The only other thing I see, is flickering in the cockpit? Like spikes and flashes? I am trying different settings? I will update my Nvidia driver to 275.33 ( just out whql)" I am also getting this since the patch. I will try your suggestions out later (I am also overclocking so will try that also). However, I did want to ask whether you ever (before patch) saw a similar effect when looking at the engines (especially from inside the cockpit). I've had this for some time, and it seemed to be related to shadows and HDR, but I was never able to eliminate it completely. I have exactly the same graphics card as you, btw.

I have also been having very similar issues. I have been playing GOW campaign and have been experiencing random hangs, usually (but not always) at the start of missions just after unpausing. I have been able to get by so far by restarting missions; but I have now got to this mission, and I can't get past it. It always hangs just after I unpause at the start. ATO B.P2.1 I can ctl-alt-del to task manager after which I get Description: A problem caused this program to stop interacting with Windows. Problem signature: Problem Event Name: AppHangB1 Application Name: DCS.exe Application Version: 1.0.1.0 Application Timestamp: 4a7acae0 Hang Signature: c4c4 Hang Type: 2048 OS Version: 6.1.7600.2.0.0.256.4 Locale ID: 2057 Additional Hang Signature 1: c4c4e5a752078d63fcf03949f13636b2 Additional Hang Signature 2: fe4e Additional Hang Signature 3: fe4e7d3ef9f2f921e4e82f261d56d6cf Additional Hang Signature 4: c4c4 Additional Hang Signature 5: c4c4e5a752078d63fcf03949f13636b2 Additional Hang Signature 6: fe4e Additional Hang Signature 7: fe4e7d3ef9f2f921e4e82f261d56d6cf After trying a few things I found that I could eventually get around this issue if instead of pressing pause to start the mission; first press f2 for an external view, then unpause, then take off using the external view for a few seconds - then back into the cockpit - I was then able to continue the mission. So unpause from cockpit = crash; unpause from F2 view= ok. DxDiag.txt Error.log.txt errors.log.txt

Thanks for the reply. 1. Sorry. I WAS using control and alt, not shift - that was a mistake in my post. It does not work for me. Either keys or mapped buttons rotate the switch clockwise in the game. However, in the options screen pressing either the keys or buttons, the correct control is highlighted. I assume from your response that it works correctly for you? In case it's not clear, for me both lalt-f and lcontrol-f turn the rotary clockwise. 2. I only ever use simulation mode. This mapping does not work for me when I map it to a joystick button.

Hi, I've been reprogramming my HOTAS and noticed the following issues 1. On the targeting mode control panel the weapon system mode selector dial (rotary switch). Using either mapped commands or the keyboard (shf - f, alt -f). Both commands turn the switch clockwise only (the other should turn it anti-clockwise). 2. The frame rate counter command does not work when mapped to a button.

I had this problem. It was due to sound drivers. I think it's likely you might have a similar issue. One way you can check this is as follows: Load the mission "Battle", and start the frame rate counter. Once in the mission, as soon as possible put the chopper into a hover and wait. Within a couple of minutes there will be intense battle activity and lots of explosions, etc. On my system when this happened, the frame rate would drop into single figures - which is not right at all. Exit the mission. Now, disable sound in the options menu (don't just lower the volume, unselect the radio button. Start the same mission again and do the same thing as above. I normally do get a frame rate drop when the action hots up but nothing like when I had the problem with sound. From memory, I think I would start the mission with around 50 fps. With the sound issue, this would drop to 5 in places, making the game unplayable. Without the sound issue, it would drop to around 25-30 fps when the action got heavy, but only for very brief moments; so it wouldn't impact on the gameplay. If this happens to you, then you know it's a sound issue. You can then try other driver versions, etc. Since on my soundcard I know that the "GX" mode is to do with emulating EAX, you might try changing options to do with that if you have them in your hardware? I have a Asus Xonar DX sound card with Win7 64 (there are other posts on this and other forums where people with this soundcard have had these types of problems). What worked for me was the following: Install the latest Xonar DX (beta) driver for Win7 - 64, and the latest sound card firmware. There is also a patch on Asus's website for Vista 64. I don't think I've installed it on this ocassion; but I might have - I tried lots of combinations before I sorted this out, and now I can't remember. I'm pretty sure I didn't use it though. When running ensure none of the DSP Mode icons are activated (esp the "GX") in the Xonar DX Audio Center.

Hi, I just bought the TM MFDs and am trying to map the following functions to its buttons ABRIS brightness increase/decrease ABRIS axis increase/decrease The problem is that for one button press multiple commands are sent to the sim, which makes it impossible for me to use this correctly. E.g. for the brightness control, instead of pushing the button and the brightness gradually changing, one button press goes straight from full bright to full dark. This also happens using the keyboard, so I don't think it's an issue with the hardware. I had always used the mouse for this previously, for which this works correctly. Is there any way to tell the sim, that for one button press only one command should be sent? Thanks for any suggestions.

I think you need to point to dcs.exe, not launcher.exe for this to work.