ckovoor

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.

I have deactivated the following in Samsoft-TheVerySingaporeX/scenery:AFXWSSS.BGLairbuilding.bglCGRD.BGLCHAGIFREIGHT.BGLchangi_grd.bglCHANGIGATE.BGLCHANGITERM.BGLCHANGITREES.BGLI have no problems or conflicts so far, but would be interested in knowing what others have done.Thanks.

Hi,I operate FSX on a network of 7 computers (using FSUIPC4, WideFS and WidevieW X):(1) Server PC: FSX, FSUIPC, WidevieW X Server, WideFS Server: 4 touchscreen monitors: used for Instrument panels exclusively(2) FIVE Client notebook PC's: FSX, WidevieW X Client, FSUIPC: used for Outside scenery views exclusively: driving 5 widescreen monitors across a 180 degrees f-o-v(3) Client PC: WideClient, Jeppesen Navigation Suite: 1 touchscreen monitor: used for Jeppesen Nav Tracking only.My question is about the HUD in 737 NGX. My understanding is that since the HUD is an extension of the instrument panel, it would be possible to display it only on my Server PC. However, the HUD is really a superimposition on the 0-degree (forward) external view generated by my central Client PC networked through WidevieW X. Is there any way I could get the 737 NGX HUD directed to that single client PC?Thanks,Chakko.

Hi,I am having exactly the same problem with my networked FS9 installation of ASE. Could you enlighten me on what you had done wrong initially, so I could check if I am making the same error?Thanks!

Hi,I have RCv4.3 installed on a networked Client PC connected via WideFS. The RC sounds are delivered on the Client PC's speaker. I am finding the (relative) volume of the Chatter too high for comfort, and wanted to reduce it vis a vis the ATC/Co-Pilot conversation. How might I achieve this?Thanks!