Cockpitbuilders

Thank you John, I will do this now. Trev

Nevermind, your talking about moving your eyepoint while your flying...

Pete, I am sure you already know this, but in the cameras.cfg file adjust these...

Thanks Thomas, Was trying to figure out where it was coming from. Trev

Hi Guys, While trying to get sound.play and sound.path to work, I was trying to locate if my sounds were playing, and I came across something strange when turning on the "Event Logging" Now, keep in mind I tried searching all of my .lua scripts for the effective controls being sent, but wondered if you were aware of something hammering FSUIPC. Can you confirm the attached log, event logging occurs on your end with the King Air, or is this something that is happening strictly on my machine? What I am referring to is the 2 lines hammering control event logging. 734782 *** EVENT: Cntrl= 65962 (0x000101aa), Param= 19 (0x00000013) FUEL_SELECTOR_SET 734782 *** EVENT: Cntrl= 66523 (0x000103db), Param= 20 (0x00000014) FUEL_SELECTOR_2_SET Please see the attached log, this seems odd to me.FSUIPC7_prev.log Thanks guys. Trev

Enrico, There is a bunch of files in the aircraft directories that have "Defaults Set in them" ie apron.flt Seems there is a .flt file for every "Start point for the aircraft", and it defaults the frequencies. So regardless what they are set to the aircraft seem to revert to these values, I haven't tried, but perhaps if you delete those lines of code in the .flt files, they may not revert. Just letting you know. Trev

Hi Guys, Usually, we complain about things that don't work. Today I might add I am clapping. Turns out FS INTERROGATE Does work with FSUIPC7. Thanks Guys, again for taking the time to make this stuff work so well. Trev

Morning John, The log showed no more TransmitClientEvent failures at all. Was a 2.5 hour Flight and never had a hiccup, unless it was a fluke. I will run it again today and see what happens.

John, I just wanted to Thank you for the new version today. Just completed a 2 hour flight, no disconnects. Everything perfect. Don't know what you changed as a work around but it worked. Trev

No disconnects yet! Looking good so far! Thank you. Better than it was in anycase.

Ok thanks I will try it now Trev

Thanks John, Literally FSUIPC closes completely. disappears from the system tray completely. I have tried adjusting to this TransmitErrorsReconnect=3 to see if it will help. *Here is crossing our fingers* on the next build / patch. Thanks, Trev

I am going to add to this, because this is what I am experiencing. Today was the first day I got to experiment with the new patch, and this seems to happen often. Here is my Log.

Enrico, that’s actually how I had accomplished this. When I saw the cameras.cfg file did that right away. just have to be cautious to see if PM functions will interfere with the built in ones. Ie the MCP fighting with the one in the panel.cfg Trev

Thanks James.... And when For me I have been doing this over 22 Years.... And the fact I am a grandfather, I do qualify as OLD LOL

Gobsmacked. - If I could package up the experience and veterans in this thread right now I would probably fall over. for those of you unaware, this thread is listed with comments from many years of experience. Thanks Pete and John for your hard work on this. James, Torsten, Enrico, Thomas, Pete. we couldn’t have any of this if it weren’t for you guys! Trev

James... Glad to see I wasn't the only one having an issue.. I chalk it up as "OLD AGE" LOL John and Pete.. I am so far not seeing some of the (RED) Unable to write to Generators, Avionics switches, or Radios Offsets that was specified in the attached "functionality Excel sheet" So far the majority of stuff I have been able to test (which is limited due to the frame rate issues) seems to work with the exception of the radios, seem to adjust the Active freq, rather than the Standby Freq function wise. But Will report in more detail as things get repaired with MSFS (ASOBO) Simconnect booboo. Lua scripts all transferred without issue and I was up and running with my Project Magenta within minutes. I will say though, my PM MCP really was having troubles trying to keep the aircraft from proposing all over the place, but I attribute that to the frame rates and simconnect connectivity issues, seems the MCP can't compensate smooth enough at this point. Trev

Pete, My apologies Whilst changing from P3DV4 to P3Dv5 and Running my electric Trim It appears the Coupling between the encoder and Stepper has come loose. With your post Above I thought better of a software issue and re-evaluated my troubleshooting process and found the failure. This teaches us to re-evaluate the issues and don't make assumptions until you have fully verified the causes prior to posting possible Bugs. (With new versions many of us tend to make assumptions that waste others time) again my apologies. Trev

Wonderful, Thanks as always Pete. I will just utilize the ipc.display function for monitoring for now. All I can say is trim works in P3DV4 and not working in P3Dv6 with the same LUA File.. But of course, perhaps My Lua file has something else in it that P3Dv5 doesn't like. I will continue with the troubleshooting. Perhaps, there is something overwriting the Trim Value. I have external Controllers disabled in P3D as I only use UIPC for Controls. Perhaps there is something else holding it out. Best regards Trev

Evening Gentleman, Just to report a couple of issues since installing V6. #1 The following ipc.control for Trim does not seem to have any effect anymore. Would something in the Lua IPC.Control facility have changed with V6? Alas, I however can report that the keyboard assignments still work to change the trim in the Project Magenta FMC, which brings me to the second issue. I thought I would change from the IPC.Control to value = ipc.readUW (0x0bc0); Value = Value + 200; ipc.writeUW ((0x0bc0), value); for Increase Trim. I however wanted to check if the offset was changing with the ipc.control command first to identify what was going on. I decided to Launch Interrogate to make sure that the offset was working, and alas can't run setup fields in the 3-scan locator, due to the following access violation error. I am running the Interrogate facility with administrator privileges. Thanks, Trev

Without John (Now) & Pete (Previous) We would all be in DEEEP Trouble. I am just Glad development and support is still available.

Thanks It just became available.

Morning John, Could you please provide for us with an additional marketplace to Pay the Upgrade price for FSUIPC6 as Simmarket does not have the utility available for purchase. Therefore downloading it and installing it is moot. Thanks

Thanks Pete for the quick response. I appreciate the more urgent needs that are upon us, and I am so thankful for your support over the years. I commend you for your retirement, I still have a few years to go prior to me being able to think about that. I will also thank you for passing the legacy on, so many of us will still be able to benefit from that which has made this hobby a possibility. Please Sir, Enjoy your retirement. In the interim, for those people researching this topic in future, I got around this by abandoning the simconnect window and instead using the lua facilities to write to a text file, then manipulating the text file to suit my needs. Best regards to all. Trev

Hi Pete, With Regard to ipc.lineDisplay(“Failure Message”, -5) Are there any facilities at present to set background color and text color in the simconnect lua Message window? in p3dV4 at this time? I read in the manual ipc.display had colour settings but appeared based on your notes to not be available to V4 at this time. Thanks, Trev