SenorRaj

Hi, I couldn't find any section in my saved flights (which I presume you were referring to) which had a section called LUA Display. Apologies for not getting back to you earlier. I'll a few flights, log LUA and key presses and do some of my own research before I get back to you. Regards, Paul

Sorry Pete, it's FSX I'm using. I will try your fix in about 10 mins or so. Thanks as always for the prompt feedback. Regards, Paul

Thanks guys, Love this script, I consider it an essential part of my FSX flying experience now. Cheers, Paul

Hi Pete, Since upgrading my 24" 1900x1080 main monitor to a 34" Samsung curved 3440x1440 I can't see the output of a modified Lua script of yours that I was using. The script was 'Display Vals' I think (I don't have access to my desktop at the moment). It was assigned to a keyboard key and I had added my own output/input values I wished to monitor. Since switching monitors they are nowhere to be seen. I have tried your original script Pete as well with the same results. I also previously used another Lua script which placed the info in the bottom left corner of the monitor which I have lost since a complete reinstall FSUIPC and WIDECLIENT are both working as normal otherwise. Do you or anyone else have any idea of what to modify? If I could remember the script that moved the text I'm sure I could modify that, but unfortunately I took about a month break from FSUIPC, which is plenty of time to forget even the basic knowledge of Lua scripting I had. If you, Pete, or anyone else can help needs any more info please let me know, as I will be at my desktop later. Thanks for anyone who can offer some ideas. Regards, Paul

Sorry, my god, I must have been exhausted when I sent that email. I was referring the MFG Crosswinds. All is good, it was actually a setting in my BIOS (Intel USB 3 XHCI) that I had to disable to get his own calibration software to stop crashing and just work. I can still assign of course and fine-tune the calibration in FSUIPC. Sorry for posting such a pointless message. I need an editor for posting before my morning coffee!

Hi Pete, I'm sure i just need to assign axes through Windows after calibrating these pedals. However I've become so used to doing all my assigning and calibration in FSUIPC. Is ignoring them in FSUIPC fine or would it better to just send them straight to Windows in FSUIPC. Same difference isn't it. I apologise if you're not familiar with the pedals but all the calibration is stored on a chip in the pedals. Sorry for dumbing down your Saturday! Paul

Thank you so much Paul, you really couldn't have been more thorough, but that seems typical of you. I don't want to go overboard, but you truly are an invaluable asset to the Flight Sim community as far as I can tell in my 8 or 9 months since I got serious about FSX. I honestly don't know how you manage 8 or 9 modes on the one plane- I had to print out a diagram of my yoke and quadrant for each of the 3 modes when I first implemented your method. And it was after seeing what was possible by delving into the more advanced depths of FSUIPC. Just out of interest, you seem to come from a Naval background- is the where you learned to program or are you self-taught? Funny that you ex-wife lives near Loughrea, if you've ever visited you'll know that it's only about a 20-30 min drive from Galway. I'd be interested to hear if you ever visited our little coastal town. Quite a contrast to California, weather-wise in any case. I've never made it to the West Coast myself, Chicago being the furthest I've managed. I love my ocassional visits over there, I've been to Flushing Meadows for the tennis twice- I'd take it over Wimbledon any day! Anyway, I've rambled on as usual, so I just want to thank you so much again. I may have a follow up question or two, but I'll definitely print it out and study and experiment with it long and hard- it's the only way to really learn (says the guy who straight out asked for the code in the first place!!). Best wishes and I hope to chat to you again, Paul

Hi Paul, I have read your many posts on this forum as well as a couple of others. I cannot thank you enough for all the knowledge you have imparted selflessly on a regular basis. I use your offset 066C0 method of conditional button programming on a couple of jets I fly, but 3 is about the limit of button states I can just about remember. i know you posted some time back about how you use a snippet of code to display your new controls on screen when you switch modes. I have tried various ways of implementing this, but with absolutely no success. I have modified one of Pete's examples to display certain feedback info on screen but cannot for the life of me adapt it to work with offset button modes. I would really appreciate it if you could share the code you use to perform this highly useful function. Hopefully, Paul

Hi Mike, Does this include all the variants of the 737 PIC EVO? Does the FS2Crew add-on remedy the problem at all>

I was wondering about how it ran on the same machine as FSX, so it's a relief to hear that would be the ideal way to do it. Because Simconnect and Plan-G.......words fail me. I've shared and streamed files across my home network for years, so I've have to familiarise myself with what is going on under the hood to know where to begin troubleshooting. I got off to a great start with Plan-G, it built it's database on its first run- I thought this is going to be a breeze...never have I been so wrong. I tried every available configuration, rebuilt my tcp-ip stack, endlessly tried to get a working Simconnect.XML, used the simconnect config tool and all of this was with all firewalls turned off, and I don't run any anti-virus....but never the twain did meet!My mate then showed me over Skype how to do it the smart way. As soon as he ticked 'the send WideFS data' box in FSUIPC it connected almost immediately with the already running wideclient.exe on his Plan-G laptop. And Plan-G immediately centred on his aircraft location. So, needless to say, WideFS7 is my next FSX related purchase. And I look forward to seeing what else I can do with it. Just out of interest Pete, what flight planning software do you use? Anyway, thanks for the reply Pete, Take care, Paul

After reaching the end of my tether with Plan-G and Simconnect, I have decided to purchase WideFS7 to go along with my favourite FSX add-on, FSUIPC. Just wished I'd bought the bundle for when I purchased FSUIPC, but of course, hindsight makes these things seem obvious. I was also hoping to justify the cost for when I get around to purchasing Active Sky Next, as I was under the impression that it used WideFS for network connections. However apparently that stopped with FS9. I was just wondering if it can still be made to work if you use the correct port numbers and protocols in the ASN.ini file or network settings? Or is it definitely a no-goer? Hoping someone can confirm this for me one way or the other. Thanks. Paul

It looks very pretty, but can it be used in full-screen mode?

Thanks very much on the updated code for the displayvals.lua Pete, more effiency is always a good thing! Apologies again for unnecessarily wasting your time. Will be more thorough in future before posting a problem.

Apologies Pete, it's working now. I think i must have tested displayVals.lua before I had setup the offset modifier correctly in the aircraft.ini file. Apologies for any of your time wasted. And thanks again for your fantastic program and support! Paul

Hi Pete. What I meant was that I used the same syntax you use in DisplayVals.lua, ie mode = ipc.readSW(0x66c0) and then adding mode= to the ipc.display list. I've successfully done this for rudder trim, etc values, but as this is a button state I'm assuming I need to use a different query to get the mode state (1-3, or 0-2 to be exact). Thanks.