doveman

I've tried installing VC 2013 now as well. First I tried the x64 version, DCS OB still gives the same error. Then I tried adding the x86 version, same error. Perhaps someone could advise what DCS OB actually requires?

Haven't tried it myself yet but with The Witcher 3 a way to eliminate stutter was to run borderless windowed, cap fps and enable vsync in-game and also cap fps with MSI Afterburner. This worked because BW forced triple buffering, whilst capping with AB kept a steady frametime as well as framerate, whereas the in-game cap only affected the framerate. So might be worth experimenting with those.

Might be related. When I mouse-click on the command category drop down (All, axis, etc) I find that the first click doesn't always register and I have to click again.

OK, I see from the other thread that I need Visual C++ 2013. I'll try installing that. I presume the Steam install doesn't include that among the 7 pre-requisite packages it installs? I can understand it being left out by mistake initially but would have thought it would've been added along with one of the hotfixes.

OB standalone works fine for me in Win8.1 but if I boot to Win10 I can't launch it. I originally had errors about missing MSVCP120.dll and MSVCR120.dll, so I searched my C: partition and found them installed by another program in it's own folder and copied them to Windows\system32. That stopped those error popups and I get this one about (0xc000007b) now instead. I ran the vcredist_x64.exe from the OB\dist folder and let it repair. I also have OB in Steam, so I tried launching it from there, which made it install 7 required packages but then it just doesn't launch at all when I click Play and it didn't help with the standalone. Tried verifying integrity of files as well and that didn't help. Programs and Features shows I've got the x86 and x64 versions of: Visual C++ 2005 Visual C++ 2008 Visual C++ 2010 Visual C++ 2012 There's actually two versions of the x64 2012 installed, v11.0.50727 and v11.0.61030. Only the latter is installed for x86.

I'm using the one with the silver/grey buttons on the base and the red trigger. I've got one of the other models as well but it's packed away at the moment, so I can't check with that.

I didn't test the hotfix with the invert x-axis setting as it's not needed with my FFB2, so I'm confused as to why you need it? I'll test later though to check whether it unticks when I press my radio menu combo or swap seat position.

Tested again after today's Hotfix 2 and it's still OK, even after I open the radio menu with RAlt+\. I don't understand why some people need to use Invert Axis with their FFB2, as I only need Swap Axis for it to work correctly.

I'd like my current waypoints/flight route to be shown on the F10 map. The Abris can only show a small part of it in sufficient detail to read and I find it confusing looking at the F10 map and trying to work out where the route is on that. Surely IRL you'd plot the route on your map before setting off?

Ideally DCS would listen for commands on UDP like radio/flight/cover me and then the voice activation utility could just send that when you say "Flight Cover Me". That would need the utility to be written/adapted to do that of course, as currently they all just send keyboard commands but it's a much easier and efficient way of doing things than using menus and F-keys.

Hmm, now it seems to be working OK mostly. I'm only using Swap Axis as that's what works in Stable and now it seems to work in OB. Tested with both the KA-50 and Uh-1H. I did clear all the button mappings for all my devices (not keyboard) though, so anyone who's still having trouble might want to try that. I just have a few joystick buttons mapped to keyboard commands with Xpadder for now but you can just press T to test the trim. I also had to unmap my Edtracker device from pitch, yaw, rudder, throttle again (for each aircraft), even though I did that already last time I tested. It seems to think it's a new device each time and keeps adding it back but I'll see if it happens again next time I test. The Mi-8 was a different story though. That didn't respond to my FFB2 or Saitek pedals at all, no response even on the Control View. I haven't really used the Mi-8 much though, so just did the Auto Startup and maybe there's something else that's needed to engage the controls?

After today's update FF on my FFB2 isn't working at all. I tested with the KA-50 and Uh-1H and with both, trimming with T I hear the click but it doesn't trim and the controls indicator shows that the stick is trimmed to the centre position. I tested both with "Swap Axis" (which is what works for me with 1.2.16) and with both axis inverted instead.

When I installed 1.5OB, I went through and installed each of the modules I own (they already showed up on the Installed tab but on the Modules tab they still appeared with the Install button until I installed them again). After I updated 1.5OB today all my modules were uninstalled again, other than the A-10C and F-86F and the Install buttons were back on the Modules tab, so I had to let it download and install them all again. I can't be sure it was caused by the update as I haven't run DCS in the last couple of days since previously testing but I can't think what else would have caused this.

I bought my Dad a Benq VA monitor to use with X-plane and night flying looks fantastic, with inky blacks whilst stars and clouds remain clearly visible. I do find that text (in general, not x-plane) is a bit blurry and I think that would bother me, although the effect may be aggravated by the fact he uses increased DPI (150% I think). I think I'll have to wait for OLED to get the best parts of both IPS and VA. I'm currently using a 24" 1920x1200 Dell IPS and it's hard to imagine going down to a 1080 monitor, which rather limits my options anyway.

I'm crossing everything I can ;) Your method of dynamically configuring the boards on the fly does sound much easier (for users). I don't pretend to understand how that's possible but I don't really need to, so don't waste your time trying to explain it to me when you could be coding :) If your approach doesn't work out, you might want to look at the Edtracker GUI, as that is able to upload code without the Arduino IDE. I'm not sure if it's open-source though.

Absolutely agree, I'm just imagining a happy future where we can use one program for all our sims :) I'm not sure from what you've said whether we're talking about the same thing. What I meant is that there needs to be code uploaded to each Arduino for the various controls attached to it and it would be great if this code could be generated by DCS Integrator (or some other program) after the user tells it what controls are attached. If that's the idea though, fantastic!

If it's not too difficult it would probably be good in the final to have three options, windowed, borderless/fullscreen windowed and full screen exclusive, like ArmA3 has. Then users can select whatever suits them best.

Very happy to hear you're working on this ohall. I can't code myself but a while back I suggested a system with a program that lets the user map physical controls attached to Arduinos to sim cockpit controls, with switchable profiles for different aircraft. Eventually it could even be used for other sims like X-plane, which listens for commands and sends data on UDP. Obviously everyone has different physical controls, so even though the Arduino only has to output a generic signal for the PC program to translate, the Arduino code will be different for each person. I imagine it would be possible to have a program that lets the user fill in the necessary info (e.g. 2-position switch connected to pin 5) and the program generates the necessary code to upload but that's probably the most complicated part due to the number of possible setups it would have to accommodate. There's only a finite number of controls and ways of connecting them though, so it should be possible to identify them all and accommodate them.

Oh certainly. I was approaching it from the point of view of a player but I sympathise immensely with our content creators who generously donate so much time and effort and then find they need to give even more to fix things, with some players thinking they're entitled to expect them to do so :(

Unless someone can come up with a batch utility that can update them, I think you're probably right. There's nothing more annoying than spending an hour flying a mission only to find it's broken and can't be completed!

I think it would be terrible if they did go under, as despite their driver problems (which any DCS owner is only too aware of) they still have made decent GPUs available to people who couldn't afford Nvidia prices, which are only likely to increase in the absence of competition.

Suprisingly I didn't need to install any files before my Edtracker appeared in Controls. I also have a TrackIR column as a result of using Opentrack so I unmapped the Edtracker column but presumably either would work.

I had some problems with my FFB2 at first as well. It turned out that the button I was using for Trim (mapped to T with Xpadder) was also mapped directly to Trim in DCS. Now I've cleared all the button mappings in DCS it seems to be working OK. As with v1.2.16 I have to tick "Swap Axis". Before I unmapped the buttons, that didn't help but for some reason ticking "Invert X" and "Invert Y" instead did make it work, at least until I re-opened the Controls settings but it seems that was just down to having the button mapped to Trim in two different ways.

I tried copying all my modules under aircraft/ from the stable to open beta but whilst it showed them as installed in Module Manager, I was unable to use them. Starting a mission would just put me in an external spectator view and I noticed the training missions weren't showing up either. I tried Repair but that didn't help and in the end I had to Install each module again under Module Manager. After I installed each module, the option to Install that module, so clearly they weren't properly registered as installed even though the Installed tab listed them.

With my MS Sidewinder X4 keyboard, the \ key is not recognised by DCS as \ but as OEM102, so I have to go through each module and find any default mappings using \ and change them. I had the same problem with the stable DCS, so it's not a new bug but thought I should report it as I don't have this problem with any other program/game, so it seems that DCS must be using an unusual method of reading the keyboard. I'm running Win 8.1 Pro but I'll check if the same thing happens under Win 10 when I get a chance.