nick_thain

Gudday @Thundersmoke, I'm having the same issue as you with the mouse being blocked from the bottom right of the DCS menu/GUI, did you have any luck with this since you last posted? I'm currently using a workaround where I'm using a mod to change the displayed ordfer of the module icons so that the modules i want to fly/test are furthest left, and using 'escape' and 'enter' on the keybaord as I can to navigate in and out of GUI screens... not ideal ;). FYI, my monitor setup is a 5120x1440 monitor with 3 800x600 USB monitors (from Cubesim) top right of the main monitor. Cheers! Nick

@prestonflying I was actually tracking this in the other thread, it’s amazing the progress you’ve made! First thing I can think of would be scratchpad, like in the AH-64 and F-15E? I’m loving my ICP for the F-16, but it feels like a crime to have it folded back behind the UFC when I’m using that Hey I know this has been asked earlier in the forum, but I’m currently mapping my controls for the A-10C II, so I feel I must check again; what’s different about the A-10C II module that only allows the 5 static displays and the blinking MC? Don’t get me wrong, I love this mod! Just seems like there would be so much in the A-10C to export!

Yup, Knew about your pinned message @MustangSally. Given that your pinned message was posted Sep 2000, @brettt777's question was posted 3 years later in May 2023, and @speed-of-heat's response was not focussed on WinWing's SimAppPro, I thoguht I could be of some use. Thanks for piling on.

@MustangSally Ok… I’m not seeing the pinned post here though. Just trying to help this guy in this thread.

@ANDR0ID Couldn't agree with you more mate, I love this community as well. For me, it goes a long way towards replacing the community I had while I was serving in the Aussie Air Force (that's me in my profile pic getting some back seat time in the legacy F/A-18B). Retired in 2013 after 23 ridiculously fun years, and it took me a while to figure out that DCS is more therapy for me than hobby. Love being a part of forums like this where we're all helping eachother out. FYI, my issue earlier was operator error; I was in the DCS Open Beta folder, not Saved Games. Once I figured that out, back up and running Thanks again! @prestonflying, send you a message to arrange getting that F-4 in your hangar

Hey @brettt777, I know this thread is pretty old, but I had the same confusion recently with SimAppPro and figured it out, so I'll drop what I found here just in case: The 'Max' in SimAppPro is NOT what you would normally call 'Mil'; it's the absolute maximum top of the throttle axes. The way I found this out was by just looking at the Orion 2 throttle; it's clearly labelled next to the throttle axes. I then recalibrated the Rx and Ry axes, this time pushing them both past the 'Mil' detent all the way to the top. I then recalibrated thre Afterburners bu pushing both throttles past the 'Mil' detent to the top (which I think makes no sense, but whatever). When I then tested the throttle axes in SimAppPro, they looked nad acted like they should. Same goes for DCS; before, the 'Mil' detent acted as 100% in the controlls settings when editing the axes. Now they behave as you'd expect. Hope this helps yourself or anyone else! Cheers, Nick

Y'all are very welcome! I'll keep an eye on the forum and if I see a hint of 'I'd love to try that but don't have the module', then I'll jump in ;). I just updated DCS to the 'one unifying' version, and the universal UFC's are no longer working fo me.. anyone else having this issue? When I went to re-copy the WWT folder back into the Scripts folder I did notice that the 'standard' wwt folder was not there.. related? Thanks in advance!

@prestonflying, @ANDR0ID, @Wostg, Stumbled upon this tonight, outstanding effort gents, love your work! Serious question; what’s the number 1 DCS module each of you would like that you’re missing, either to work on for this project or just to fly? Let me know and I’ll gift each of you, this is amazing work and I want to say thanks in the best way I can. Cheers! Nick

Just like the title says! Still in pristine condition, I just could not get used to the no toe brakes thing so I broke down and back ordered a set that has them. Cheers! Nick

Ok, huge 'Doh!' on my behalf. Defintiely not a coder and did not realize I had to grab ver 0.7 from Github, now that I did the Rotary Encoders are working well :). It wiped all my 0.5 plugin work, but rebuilding that will get me familair with @Thx1137's syntax. Hope this helps you @Ehrenfelder ! Cheers all, Nick

Gudday @wombat778, @Thx1137, I am loving this plugin, finally I can use my Loupedeck and its rotary dials with DCS. The axes and buttons are working well, but I'm having the same issue as @Ehrenfelder, the syntax that @Thx1137 wrote for the 'Encoder' and 'Encoder via Button Press' is throwing back an 'Unknown Option' from Loupedeck. I've copy/pasted it straight from the Github page. Any ideas on this, has the sytax maybe changed as @Ehrenfelder asked above? Thanks in advance for any help you can offer! Cheers, Nick EDIT: I downloaded and haver been using the 0.5 version from this forum thread that @wombat778 posted Feb 27, I've just now downloaded the file from @Thx1137's Github site, I'll try that and post back results here..

Hi all, I have a working profile for the Ka-50, but it's not working with the new Black Shark 3 module. Is there a quick fix to get the 'old' Ka-50 Streamdeck profile working with the new Ka-50? Thanks in advance! Nick

Apologies, That description was a little brief, I should have been more specific to better explain; I’m very familiar with DCS’s auto-mapping issue, and in this situation, I’ve cleared all of the controllers, then mapped them all from scratch (I didn’t use the lua provided by Total Controls). If I leave the MFBB dials unmapped, my WinWing device axes are dead center when I check them in the DCS controls. If I map a function to the MFBB dials, and then rotate them away from center, then re-check the WinWing device axes, they are now showing as being way off center. Weird. What’s even weirder is that, even with the WW X/Y axes being pushed off-center, the WW-mapped pitch and roll are only affected in some DCS modules; the warbirds are only slightly affected and easily trimmed out, but the Viggen is unflyable, even with trimming… Regardless, It sounds like you’re not having this issue, which is good news for you I’m just glad that I isolated that the MFBB is the cause, was driving me nuts trying to figure out why my WW X and Y axes were showing so far off-center, and only in DCS, and only when MFBB is mapped and dials are off-centered.. Total Controls are working with me to get a fix. Cheers!

Hi all, I know this is an old thread, but have any of you MFBB owners had any issues with MFBB mapped axes (dials) throwing other axes off center? For me, when I map an axis to an MFBB dial and turn the dial, my WinWing stick axes are thrown off-center... If the mapped MFBB dial(s) are all centered, the WW stick axes go back to center again. Even with the WW stick and throttle axes showing as being off-center, it only effects a few DCS modules in flight (the Viggen is the worst).

Hey @skypickle, I know this is an old thread, but have you had any issues with the MFBB mapped axes (dials) throwing other axes off center? For me, when I map an axis to an MFBB dial and turn the dial, my WinWing stick axes are thrown off-center... Also, with your luas, I'm curious; isn't that the default behavior for the MFFB dials? I've been able to assign axes to them since the start...

@DrGonzo94 Can I ask a huge favor? I'm still having trouble getting my Mirage screens and viewports sorted, and some of the issue might be the age of these posts, given that the Mirage had a significant update recently. Given that you had success pretty recently, would you mind sharing your lua files here? I still can't get the VTB to budge from my Right MFD, not can I get any of the other Mirage displays to show on my external displays, even though all of my other DCS modules are exporting their displays just fine. Thanks in advance mate! Nick

Gudday Strut, Could I put my hand up for one of those PMs to your RAAF Mirage skins? Had this module for ages but only just now getting into it, feels very wrong as a former RAAF officer to be flying it without RAAF skins! Cheers mate, Love Your Work Nick

TLDR: Is there a way to COMPLETELY reverse the System-Wide OpenComposite install?? Further than re-selecting SteamVR in the OpenComposite window? Does anyone know the exact dll's that are downloaded during the System-Wide install? I REALLY want to to get this up and running after reading about all you lucky buggers and your improved DCS VR , but I'm having some serious issues, in summary: I followed the first post to the letter up, to the OpenXR Toolkit step (thanks @nikoel, great clear directions!). I got DCS working with WMR and no SteamVR just fine (YES!!), albeit with some bugs: Reverb G2 screen would go black randomly then come back during a DCS VR session. When Reverb G2 woke up, my other monitors would disappear, and Tobii Eye Tracker setup was wiped clean (weird!). When I switched OpenComposite back to SteamVR, SteamVR started having issues, saying it was missing some files. Google Earth VR (SteamVR-only app) crashed with a Fatal Error. Non-VR DCS is also now CTD during launch; the crash log refers to 'D3D11 Create Device' returning 'E_OUTOFMEMORY'. I'm trying to troubleshoot this, I've even uninstalled WMR and SteamVR, trying to get Non-VR DCS back up and running, but the D3D11 error continues. It's more widespread than my DCS OpenBeta install as well, I have a Stable DCS in Steam that I use to troubleshoot when OpenBeta is flaky, and it's also now CTD'ing on launch and getting the D3D11 Error in its crash log.

Hi all, I've been trying to get the Viggen Radar and EP-13 sight to export to some external CubeSim monitors, but have not had any success. I tried using the archived files at the forum link below, but they're also not working for me. Has the procedure or lua edits to export the Viggen Radar and EP-13 sight to external monitors changed since the below 2018 fix? Thanks in advance!

Sir, I LOVE Your Work! I noticed a big FPS drop a few days ago, and lucked upon it being Stream Deck lines in the export.lua. Then found this thread, read through it, tried your fix, and voila - silky smooth DCS again. Would never have tried this fix myself, so thank you kindly mate! Nick

Gotcha there, very familiar with where to put the mod folder, but you have an entry.lua included outside of the S-30MK-SFM folder, what do I do with that?

Hi all, I just read through all of the posts looking for an answer to this, and I apologize if this is a dumb question, but where do I put the entry.lua file? It's the first mod I've seen with that file being outside the mod folder.. Thanks, Nick

Gudday all, Just went through and remapped the A-4E-C to my new HOTAS and panel (fun but not fun), and noticed a few oddities, many of which I can live with given that development is ongoing, but thought I’d mention this one if it can be fixed/improved: - I’ve mapped all 4 of the lat/long dials, which is great, but they won’t work unless I click the dials down with my mouse. - Any chance we could get the lat/long dial ‘press’ also added as a key mapping? One more, both the Doppler radar and Nav rotary dials map to my controls just fine, but they don’t respond in cockpit when pressed on HOTAS/panel. Cheers! Nick

When mapped to HOTAS controls, the ODUs do react to commands from the HOTAS, but do not animate.

Is there a way to force the VTB to the Left MFD? Due to the M-2000C VTB export happening via the bound key in controls, when I enter the cockpit the VTB is yet to be exported, and the RWR is already on the left MFD, even though in the lua I have it set for the coordinates of the right MFD. I guess, because the RWR takes the first available MFD on start, regardless of the lua, and the left MFD is empty on start until I hit the VTB bound control, at which point the VTB takes the next available MFD, which is the right MFD?