nick_thain

See my post below @Rainmaker, I think I fixed your (and my) issue.

@hansangb I owe you a beer of beverage of your choice! This video finally solved it for me, as well as a little more tinkering, and I now have full MR with Quest 3 with 3 MFD displays. For others who are still suffering: Warthog Project guy (in above video) uses Helios for his MFD/display exports into his sim rig. As a result, his monitor.lua format is very different to the monitor.lua for those of us using Cubesim or WinWing MFD displays. We still need to add the extra lines to the bottom of our monitor.lua as he does to allow MFD export during VR. Even with this I was still gettitng the blocked bottom-right DCS Menu GUI issue, and was getting the in-sim footage in my MFDs (not the exported MFD screens). After further tinkering, I fixed the above 2 issues: In Virtual Desktop I disabled 'Use nominal resolution', as it was cropping my 5120x1440 screen down to 2560x1440. This cropping was breaking my monitor.lua, regardless of if I set res to 2560x1440 or 5120x1440. Soon as I disabled 'Use nominal resoltion, Virtual Desktop used the full 5120x1440 res, with no noticeable impact on performance. I also turned off a 'spare' 4k monitor is it was being constantly moved around by Virtual Desktop. With those changes, my full VR DCS Menu GUI is clickable, and the MFDs are being exported correctly during VR. Full disclosure; I am yet to get the Open Kneeboard pass through working, I first wanted to get DCS VR MFD export working, Open Kneeboard is next ;). Cheers, hope this helps someone else! And thansk again @hansangb, Love Your Work!

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!