ckovoor

Okay! 😀

I am referring to the the latest version of the FSL A320X (32-bit) meant for use with FSX: FSLabs_A320X_FSX_v1.0.1.310 released only a few days ago.

Hi Andrew, As I had written, I have upgraded to the latest FSX version and I had tried the two alternative sets of codes you have provided for the P3D versions. They do not work in the latest FSX version. Regards, Chakko.

Hi, I have just upgraded to the latest FSX version of the FSL A320X: FSLabs_A320X_FSX_v1.0.1.310 The following controls, which used to work with version FSLabs_A320X_v1.0.1.197_FSX, no longer work now: -- Engine 1 Master Switch ipc.control(66587, 78187) -- lift ipc.control(66587, 78189) -- down ipc.control(66587, 78186) -- shift -- Engine 2 Master Switch ipc.control(66587, 78192) -- lift ipc.control(66587, 78194) -- down ipc.control(66587, 78191) -- shift I have listed the controls and parameters in the format I use for FSUIPC-LUA scripting. I tried using the controls/parameters that are listed for same switches in the P3D versions (available in the downloads section of this forum), but they do not work either. Would anyone be able to confirm this, and if necessary, list the updated controls/parameters. Thanks, Chakko Kovoor.

Hi everyone, I have the PMDG 747-400 QOTSII in FSX. I wonder if someone could clarify whether the same 2-D popup panels are available on the new 747-8 in FSX: i.e. all 6 DU's, 3 CDU's, Radios, MCP and ISFD. And is there a separate 2-D popup for the EFB? Thanks,

Hello, I run the PMDG 747 v3 (QOTSII) on a multi-monitor touchscreen-equipped Server PC (FSX SP2, WIn7 x64) and display the scenery on 7 networked Client PC's, using WidevieW-X, and also use WideTraffic-X to 'see' the AI traffic spawned by VOX ATC. The system has worked well with a variety of aircraft including the PMDG 747 v2, FSLabs A320X, AS CRJ700, DA Fokker 100 and Majestic Dash8 Q400. But with the PMDG 747 v3 (QOTSII) I get severe periodic stutters on the Clients whenever I switch on WideTraffic-X. Switching off WideTraffic-X (effectively rendering the AI aircraft at the clients invisible) immediately restores the frame-rates. The PMDG 747 v3 is the only aircraft in my collection to cause this behaviour. I am hoping that there will be other WideTraffic-X + PMDG 747v3 users within this form with whom I can compare notes. Thank you!

Thank you for this clarification, @Qavion2 ....... I am familiar with Alternate Action. However, I do have a question about whether this Autostart switch is, on the basis of its electromechanical design, momentary contact (physically non-latching or springs back to non-depressed location on release of pressure) or maintained contact (physically latches into a depressed position when pressed on). Interestingly, I had the same confusion with nomenclature while building an AFCAS+EFIS for my (Digital Aviation) Fokker 100, which might be of interest: Pushbutton switches on EFIS and AFCAS Thank you!

I thank you, @kevinh, for the clarification .

I thank you, @PMDG777 and @Iceman2 for your explanations. What I found puzzling about this 'customer option', at least as depicted in the PMDG version in my screenshot, is that the AUTO selector (SINGLE/BOTH) remains even after the momentary AUTOSTART switch is removed. Anyway, after activating the option via the FMC, all is well as far as I am concerned.

Dear Chris, Thank you for your prompt response to my query. It is as you say......I believe you must know this simulation like the back of your hand...... Thanks again,

Hi everyone, This is a screenshot of the Engine Start Panel on my GE model (PMDG House livery) 747-400v3 (QOTSII): I was under the impression that all GE models would have a (momentary with annuntiator) Autostart Switch, in the area I have circled.. Could someone please clarify. Thanks, Chakko. (FSX SP2 Win7x64)

Hi everyone, I am coding some LUA scripts to interface the PMDG 747 v3 (which I purchased last week) to my hardware, using the published SDK and FSUIPC offsets. I have a question regarding replicating the various states of the electrical panel. I will illustrate the problem with some screenshots and the associated state variable (FSUIPC offset) concerning the Battery Switch: (1) Cold and Dark: Battery switch is BLANK (FSUIPC offset, type, name) ("644C", "UB", "ELEC_Battery_Sw_ON") = 0 (2) Here I have the engines running: Battery Switch displays "ON" ("644C", "UB", "ELEC_Battery_Sw_ON") = 1 (3) Here I have switched off the Battery and all the Bus Ties and Gen Cont 1: Battery Switch displays "OFF" ("644C", "UB", "ELEC_Battery_Sw_ON") = 0 The problem is that the published offsets allow for only 2 states of the battery switch, but there are 3 possible outcomes = ON/OFF/BLANK. How is one to determine programmatically when to get the Battery Switch to display a BLANK? I tried using the A:var (A:CIRCUIT AVIONICS ON, bool) but to no avail. The Battery Switch is only one instance of the problem I am facing. Almost all of the other switches on the Electrical panel have this third state which does not appear to be determined by a published offset. Thanks,

Hi, Could someone please list the 2-d popup (panels) available with the PMDG 747 QOTS II. Are they the same as are available with the PMDG 777 (CDUs, MCP, Radio Panels, PFD, ND)? Thank you,

Hello Mike, I know this refers to an old post, but I want to thank you for this information. I was having trouble getting the Level-D B767 acknowledge the existence of (FlyTampa)-VHHX in the FMC, and then, with the help of this post, found that I had used tabs instead of spaces in the relevant wpnavapt.txt file. Replacing the tabs with the correct number of spaces solved the problem. Regards, Chakko Kovoor.

Hi, Another way of solving this problem is to modify the LUA for use with FS2Crew: (1) Remove the call for After-Landing Flow; it is unnecessary. (2) Only precondition for computing and setting T/O Flap is that aircraft should be on Ground. Remove the condition that the engines should be running. (3) Only precondition for computing and setting Landing Flap is that aircraft should not be on Ground. So here is how to modify the LUA: Open the original LUA in Notepad or Notepad++ and search for this text: --returns 1 if on ground and engines not running, 2 if in air and 3 if on ground with engines running function GetState() local onGround = GetOnGround() local enginesRunning = 0 local eng1 = GetQ400Value(56911) local eng2 = GetQ400Value(56888) if (eng1 > 0 or eng2 > 0) then enginesRunning = 1 end if (onGround == 1) then if (enginesRunning == 1) then return 3 else return 1 end else return 2 end end and replace it entirely with this text: --returns 1 if on ground, 2 if in air function GetState() local onGround = GetOnGround() if (onGround == 1) then return 1 elseif (onGround == 0) then return 2 end end and then save the modified file as Q400VspeedsFS2C.lua in the Modules folder. You should now be able to select and assign this new LUA from your FSUIPC4 menu. Let me know if you have any problems with this mod. Chakko.

Hello Mike, Thanks for your response. I am aware of Ryan Maziarz's post, and I am familiar with the whole 2-D panel discussion, but, in any case, thank you for reminding us all of the restrictions. The 2-D panels you have referenced are, unfortunately, far from adequate for my requirement, as they contain only the a part of the captain's main panel and a small part of the overhead. I would require bitmaps covering all the simulated areas. Nevertheless, thank you again for the suggestion. Regards, Chakko.

Hi everyone, I am very keen on creating my own set of 2-D panels for the PMDG B777 for use on my 14-monitor touchscreen setup (6-monitor cockpit + 8-monitor visuals). It can be done using the FSUIPC offsets that Pete (Dowson) has just released for this aircraft. However, before I can proceed, I would need to find a good high resolution 2-D panel bitmap of the cockpit. Rather like the cockpit layout posters one can purchase (in paper-printed form) from Avsoft: http://www.avsoft.com/index.php?q=node/157 I would be grateful to anyone who can provide one or help me locate one. Please PM me if you have any suggestions. Thanks so much. Chakko Kovoor.

Thank you for your pointers. I am in the process of writing and debugging ( ............. :o) my linked XML and LUA scripts, and so far, everything has worked well. Thank you!

Hi everyone! This is with respect to the freeware Jeehell A320, which I have just discovered. As you may know, this is a cockpit-builder's software, but there are several 2-d panels and popups available. l'd like to adapt it completely for use with my touchscreen-based simulator which comprises 6 touchscreen monitors across which the 2-d panels can be distributed in their correct relative locations. To do this I am considering creating the remaining 2-d panels by (i) utilising various available 2-d panel bitmaps for the A320 (ii) creating xml gauges (mainly korry switches and knobs) to be mounted on these bitmaps (iii) linking these xml gauges to the FSUIPC offsets which Jeehell has published With respect to step (iii) I understand that an xml gauge cannot write directly to an FSUIPC offset, but I also understand that an xml gauge can store information about its state in an L:Var and that L:Var can be read/written to by FSUIPC. Since I would be creating the L:Var, identifying it would not be a problem. The sources for this information are: http://www.fsdeveloper.com/wiki/inde...toring_Strings and http://forum.avsim.net/topic/299204-...g-string-data/ Would anyone be able to comment on the correctness or otherwise of my understanding? Thank you very much for your time and trouble! Regards, Chakko.

Hello Ray, I have used 3.5 mm jack splitters and successfully used two (and even three) headset-mikes on the same pc audio output with voxatc and other voice recognition-dependent programs. You might want to check if there is some hardware issue affecting your equipment. Chakko.

Hello, It is possible to use ADE or AFX to edit the airport "AFCAD" to open/close individual runways for take-off/landing. I have done this at several airports and the AI follows the restrictions imposed. Regards, Chakko.

Hello Johan, I have been successful in using 0.5.2 to 'cut out' portions of a panel window and display them elsewhere. I find that this is not possible anymore with version 1.0.3, with which the entire panel window must be broadcast, and not just a portion of it. Could you confirm that this is correct, and clarify whether this feature will be available on the multi-channel payware version. Thanks, Chakko.

Sir, I am honoured that you should have contributed to my thread! Yes, I can see how your suggestion will work, as would increasing the touchscreen area (monitor size), and hence the panel size and gauge size (while maintaining aspect ratio). Let me see how this works with some of my payware aircraft. I am concerned about how changing gauge size would affect associated bitmaps, and positioning with respect to other gauges on the same panel. I have sent you a PM with links to photos of my setup. Regards, Chakko

Hi, You could use FSXSpy; have a look at this thread: http://forum.avsim.net/topic/365861-viewing-instruments-on-remote-computer/?hl=fsxspy#entry2301659 Regards, Chakko Kovoor.

Hi, I run a multi-monitor touchscreen-based setup, with FSX and FS9 (both with registered FSUIPC) on Win7 x64. I have been experiencing an annoying problem with the undocked 2-D cockpit panels on my touchscreens. Sometimes, while attempting to right-click on a button or knob I 'miss' the location, and touch an adjacent area where there is no clickspot, thus invoking instead the right-click context menu, with the options: Undock Window (ticked)/ Close Window/Hide Menu Bar, as seen in the screenshot: A second (inadvertent) click on this will untick the option "Undock Window" causing the panel window to re-dock, thus upsetting the panel layout. I don't know if others have also experienced this while operating FS. I am wondering if there is any way (lua script or xml gauge or windows registry edit or anything else) of managing the FSX Right-Click Context Menu to solve this problem. Possible strategies might include: (1) disable or toggle availability of the FSX right-click context menu, (2) edit (add an item to) the right-click context menu, so that the first item is "close the menu". I would be grateful if others could share their thoughts or ideas about this. Regards, Chakko.