April 24, 201214 yr Moderator Hi Steve, are you still looking for testers? I'd love to try it out on my MCP Pro. Let me know if I should just PM my email address. And thanks for helping the goflight users, I'm sure everyone is very appreciative of your efforts. Cheers, Pete I9-13900K, RTX 4090, DR5-6000MHZ, CORSAIR ICUE H150I ELITE, ASUS PRIME Z790-P, THERMALTAKE TOUGHPOWER GF3 1350W, WIN 11
April 24, 201214 yr The public beta is released on AVSIM * Orest Orest Skrypuch President & CEO, UVA www.united-virtual.com
April 24, 201214 yr Moderator Hi Orest, thanks, I can't believe I missed it. Just found it in the library, thanks for pointing me in the right direction. Cheers, Pete The public beta is released on AVSIM * Orest I9-13900K, RTX 4090, DR5-6000MHZ, CORSAIR ICUE H150I ELITE, ASUS PRIME Z790-P, THERMALTAKE TOUGHPOWER GF3 1350W, WIN 11
April 24, 201214 yr Author Oops, my bad. I shud've remembered that as you mentioned it here clearly. I will keep my hands away from P8 and 46 too, just in case. One thing to add, even though the modules fail to respond, any changes to the MCP from the sim reflect in the hardware, you just cant change them in the hardware itself. Hi Steve, First a big complement for the driver. Realy fabulous. My question: any news yet on an update for the P8 prob? As I have 2 with functions assigened to them, when I push a button the driver stops working ( as mentioned above ) and I no longer have any GoFlight module to work with. A little auckward but I know it's temporary. Hi Both, I finished the code in the early hours of this morning. It turned into a huge job because I wanted users to be able to dynamically allocate data from the NGX to determine the light states on GoFlight devices. So you can do some clever stuff now and the light state will show the actual NGX state and not some arbitary state because you pushed a button. E.g. I have also added multi-threading capability to the updating of the hardware so the core of the program has been altered. Because of this I'm going to Alpha test it first so if you two want to be part of that, drop me a PM and I'll send it to you later. I need to do some more testing and tidying before I send it out for Alpha testing. The good news is that because of the way I designed the P8 support I can easily extend the code to support T8's and RP48's so all those device types should be available by the end of the week. Best wishes Steve Steve: Any hopes the mcp (not the pro) will be supported? Thanks Chemanuel Yes it's on the list. Stephen Munn
April 24, 201214 yr Awesome Work, Steve! Looking forward toi your completed project very much! (So far, no problems w/beta release, on 4 flights since I installed it). Jim BlakeCaptain, SWA Virtual AirlinesReal World C172 Pilot, AOPA #06034701
April 24, 201214 yr I don't touch the mouse view commands at all in this Interface program. What happens if the interface is not running - does the issue go away? Hi Steve, I tried again tonight and it worked fine with and without your interface running...not sure what the problem was before but it doesn't seem to be reproduce-able. Thanks again! Dave Current System (Running at 4k): ASUS ROG STRIX X670E-F, Ryzen 7800X3D, RTX 5090, 55" Samsung Q80T, 64GB DDR5 6000 RAM, EVGA CLC 280mm AIO Cooler, Brunner CLS-E NG Yoke, Thrustmaster Warthog HOTAS & Stick, Thrustmaster TCA Quadrant & Add-on, VirtualFly Ruddo+, TQ6+ and Yoko+, GoFlight MCP-PRO and EFIS, Skalarki FCU and MCDU
April 25, 201214 yr Moderator Steve, I just wanted to say thank you for your efforts I don't know how long it's been since I was able to use my MCP Pro and EFIS with PMDG. Thank you, thank you, thank you!!! Cheers, Pete I9-13900K, RTX 4090, DR5-6000MHZ, CORSAIR ICUE H150I ELITE, ASUS PRIME Z790-P, THERMALTAKE TOUGHPOWER GF3 1350W, WIN 11
April 25, 201214 yr Hey Steve, just a follow-up on my MCP lagging issue. I watched the procs for spikes but there were no noticeable spikes when the MCP locks temporarily. If I continue turning the altitude knob, for example, eventually the MCP just freezes, then comes back about 10 seconds later. All the while, the NGX VC continues to adjust unaffected as if the MCP never locked. Also tried setting the task scheduler priority to high but still no luck. Interestingly I just started getting OOM errors that started occurring after I installed some ORBX products last night. So maybe I've been pushing up against the memory cap. I'll play around with scenery complexity and see if that helps. I'm also wondering if it could be a power issue. I have the unit plugged directly plugged into a USB port on the computer, but I also have a lot of other things plugged into the onboard USB slots. So if I get a chance, I'll try a separate powered USB. Regardless, I highly doubt it's anything in your program. And I can happily live with it as is. Again, wonderful job. Love how intuitive you made the interface! Tony
April 25, 201214 yr Author Hey Steve, just a follow-up on my MCP lagging issue. I watched the procs for spikes but there were no noticeable spikes when the MCP locks temporarily. If I continue turning the altitude knob, for example, eventually the MCP just freezes, then comes back about 10 seconds later. All the while, the NGX VC continues to adjust unaffected as if the MCP never locked. Also tried setting the task scheduler priority to high but still no luck. Interestingly I just started getting OOM errors that started occurring after I installed some ORBX products last night. So maybe I've been pushing up against the memory cap. I'll play around with scenery complexity and see if that helps. I'm also wondering if it could be a power issue. I have the unit plugged directly plugged into a USB port on the computer, but I also have a lot of other things plugged into the onboard USB slots. So if I get a chance, I'll try a separate powered USB. Regardless, I highly doubt it's anything in your program. And I can happily live with it as is. Again, wonderful job. Love how intuitive you made the interface! Hi Tony, My mistake, I misunderstood what you meant by lagging. What you have just described is the MCP PRO lock up issue. There are two sliders on the MCP PRO tab called write delay and cmd delay. You will need to increase one or both of these slightly until the problem goes away. Just try 5ms increases at first, but it shouldn't need much more. Best wishes Steve Stephen Munn
April 25, 201214 yr Hi Steve, Finally getting to try the GoFlight PMDG Interface with my MCPPro (A22 firmware) and EFIS. Much smoother compared to the LUA script. I unintentionaaly induced the "lag" twirling the Altitude knob too quickly. Figured it was the MCPPro lockup issue since the VC panel/display changed and after a moment things were normal again. (Have rarely experienced the lockup issue in the past using the MCPPro almost exclusively with the LevelD 767.) Will try your delay adjustments, but the easier solution may be to just twirl the knob a bit more slowly. Can not induce the delay with any the other knobs. Keep up the great work! Regards Claude Regards, Claude Franklin
April 25, 201214 yr Author Hi Steve, Finally getting to try the GoFlight PMDG Interface with my MCPPro (A22 firmware) and EFIS. Much smoother compared to the LUA script. I unintentionaaly induced the "lag" twirling the Altitude knob too quickly. Figured it was the MCPPro lockup issue since the VC panel/display changed and after a moment things were normal again. (Have rarely experienced the lockup issue in the past using the MCPPro almost exclusively with the LevelD 767.) Will try your delay adjustments, but the easier solution may be to just twirl the knob a bit more slowly. Can not induce the delay with any the other knobs. Keep up the great work! Regards Claude What we found during Alpha testing was that the MCP PRO could easily become overwhelmed with data which caused it to freeze or lockup when both the dial was turning and the display was being written too. By inducing the delays it throttles back the number of reads and writes so that the MCP PRO becomes stable. You must adjust the sliders until it stabilises. We thought that the sweet spot had been found for the silder settings but obviously it needs a little more delay adding to it. You must do this though because once its correct, you won't get any freezes. I will eventually hard code in the delays once I know what works for everyone. Best wishes Steve Stephen Munn
April 25, 201214 yr You must adjust the sliders until it stabilises. We thought that the sweet spot had been found for the silder settings but obviously it needs a little more delay adding to it. You must do this though because once its correct, you won't get any freezes. Ok! Didn't mean to suggest I wouldn't try the adjustments. I'll experiment with the settings and report. Claude Regards, Claude Franklin
April 25, 201214 yr Thanks Steve. I actually did play around with the sliders but in more extreme increments than 5 ms. I couldn't find the "sweet spot" but let me play with it a bit more using smaller adjustments. Tony
Create an account or sign in to comment