d.woody

Thanks, that does what I want, but didn't have to do that in FSX. Zorder is a configuration parameter in panel design.In the panel.cfg file for each window, zorder=2 overlays zorder=1 for two different 2D panels.

How can I bring the standard P3D ATC window to sit above the 2D Main Panel? It appears OK in the VC but in the 2D it is layered below the main panel. Is there someway I can apply the equivalent of ZORDER as in the layering sequence in 2D panels. The ATC seems to work OK as does the 2D panels.

I wanted to be able to set the increment so that the Event ID K:INC_COWL_FLAPS1 (or 2) could be used to increase or decrease the flaps setting. The actual settings as used in the VC gauge are: 0 2048 4096 6144 8192 10239 12286 14333 16380 These are about 12.5% increments I didn't want to use K:COWLFLAP1_SET each time the mouse is clicked. I still don't know where the settings are specified for the increment.

Can anyone explain how the cowl flaps increments are set. I am trying to create a gauge to use in a 2D panel that will increment/decrement the cowl flaps by the same amount as the VC. It wouldn't matter except I want to use different BMPs instead of a rotating knob, for each step to match the equivalent gauge in the VC. These BMPs have been created from screenshots of the VC and are ready to go. If I use K:INC_COWL_FLAPS1 (or DEC) in the 2D gauge, I get increments of 10%, but the VC gauge (inbuilt in model) gives 12% (about) increments.This means that I cannot display a particular BMP for each step. My question is really ......where does the sim get the amount of increment? The increment for trailing edge flaps is set in the aircraft.cfg file under the appropriate [flaps] section, but I cannot find any mention of the cowl flaps. Nor are they mentioned in the AIR file. It seems that different aircraft (that are fitted with cowl flaps) use different increments. I don't need any help with the actual gauge as I have done several before but always using a rotating lever or knob. Ant comments welcome.

ORBX FTX Hervey Bay YHBA, (Australia), causes any aircraft to crash on take-off roll. Other airports, (ORBX, default or freeware), have not shown any inclination to do this. The default start-up flight at Hervey Bay loads OK and the aircraft will start correctly, but shortly after beginning the take-off roll the aircraft crashes. It is not a "failure" crash caused by misuse of the engines etc. If the realism setting is set to "ignore crashes and damage", everything is fine. Taking off from a nearby airport and landing at YHBA, causes an aircraft crash on touchdown. Note that this is an aircraft crash NOT a system "crash to desktop". It is almost as if there is a runway elevation problem. If the ORBX YHBA scenery is disabled, and the default scenery is used, there is no problem. However YHBA is my home airport and I would really like to get it working. I have no idea where to look to even begin to solve the problem.

Ops center is not showing Livery Manager or Livery Downloader for 737NGX P3D. Does this mean there are no liveries available for the 737NGX? The 777 is showing both these options.

I have just downloaded the iFly 747 and apart from adding Doug Dawson's EVENT LOGGER gauge, the aircraft is as downloaded. However the event logger gives me the following events that just keep firing repeatedly. The aircraft will still function except that none of the functions below will function normally, and therefore will not fly. iFly 747-400 BOEING AIRCRAFT B744 620 KEY_ELEVATOR_TRIM_SET 0 620 KEY_AILERON_SET 0 620 KEY_RUDDER_SET 0 620 KEY_ELEVATOR_SET 0 620 KEY_RADIO_DME2_IDENT_DISABLE 0 620 KEY_RADIO_DME1_IDENT_DISABLE 1 620 KEY_RADIO_ADF_IDENT_DISABLE 1 620 KEY_RADIO_VOR2_IDENT_DISABLE 1 620 KEY_RADIO_VOR1_IDENT_DISABLE 1 620 KEY_SPOILERS_OFF 0 Apart from the obvious restriction to operrating the affected functions, the memory is being used up and eventually causes aan "out of memory" failure. As the gauges are .GAU files I cannot edit them as I could .XML files. Any ideas .....?

Thanks I also played around further and found that <Gauge Sizes="XX,YY"/> Also works. The background colour can be determined in the text section for the string as.... BackgroundColor="Black" (which would be transparent)

I recently came across an XML gauge for a digital readout that did not use a bitmap file as a background. The gauge displayed as a row of numbers on a clear background. I am familiar with making digital gauges to display all types of readouts, but I have always used a background bitmap either opaque or clear. I would normally use something equivalent to the following..... <Image Name="DigBkg.bmp" ImageSizes="100,20"/> I cannot remember (nor can I find the particular gauge) that shows me how to create the same gauge without the bitmap but ending up with a clear background. From memory it was something like..... <GaugeSizes="100,20"/> Can anyone offer any suggestions.

Thanks Spokes Not finished yet but just some fine tuning of times etc. I now have a full autostart procedure for 4 engines including setting of park brake, master battery, mixture, throttles, cowl flaps, props, fuel valves and tank selectors as well as magnetos and starters, that takes about 90 seconds. This is probably faster than the real thing but slower than Microsoft's "autostart", and has the appropriate starting sequence (3,4,2,1). I tried incorporating the primer switches into the sequence but met with some issues regarding the on/off aspect of the primer function, so just left them out (at this stage anyway).

I am trying to build an "autostart" switch that is similar to the standard MS autostart (Ctrl E) function. The standard Ctrl E function starts engines 1, 2 ,3 then 4, and that is generally not the sequence in which multi engines are started. I also want to include other functions such as setting the park brake and some lights etc. I have set up an XML coded switch that works fine with all appropriate functions happening. The problem is that for all intents and purposes they all happen at once (there may be some delay if used on a slow computer). So I need a delay between each function representing the time taken to move your hand between the appropriate switches and levers, and also to simulate the appropriate time between starting each engine (engine 3 then 4, 2 and 1). I have searched this and other forums and found lots of examples of timers and delays etc but I cannot get any to work as I want them. Instead of using a macro I just placed all function actions in the <Mouse> area. I am assuming I need some coded delay function between each action that can be set at an appropriate length. I have tried (P:Absolute Time,seconds) then (P:Absolute Time,seconds) 5 + etc. the switch just seems to zoom past the delay. <Mouse> <Tooltip>Fast Autostart</Tooltip> <Cursor Type="Hand"/> <Click>02 (>L:DW_sound_id, number) (L:DC4AUTOSTART,bool) ! (>L:DC4AUTOSTART,bool) (A:Brake Parking Indicator,bool) 0 == if{ (>K:PARKING_BRAKES) } (A:Electrical Master Battery,bool) 0 == if{ (>K:TOGGLE_MASTER_BATTERY) } (A:Master Ignition Switch,bool) 0 == if{ (>K:TOGGLE_MASTER_IGNITION_SWITCH) } (A:Light Beacon,bool) 0 != if{ (>K:TOGGLE_BEACON_LIGHTS) } (>K:STROBES_ON) (>K:STROBES_ON) (A:General Eng Fuel Valve:3,bool) 0 == if{ (>K:TOGGLE_FUEL_VALVE_ENG3) } (A:GENERAL ENG GENERATOR SWITCH:3,bool) 0 == if{ (>K:TOGGLE_ALTERNATOR3) }......................Continues Thanks for any help?

Finally found the culprit that was triggering the event. After working through every gauge I found a section of unwanted code in a fuel/air mixture ratio gauge that should have been deleted. Removed it and everything works as required.

Downloaded and set up Doug Dawson's event logger gauge. It appears that there is a 2 (>K:FUEL_SELECTOR_2_SET) event being issued from somewhere. 2 represents LEFT tank and there is no "LEFT" tank. My gauge does not have this Key Event and I cannot find any gauge or anywhere else that it could be coming from. 333488 KEY_FUEL_SELECTOR_2_SET 2 333488 KEY_FUEL_SELECTOR_2_SET 2 333489 KEY_FUEL_SELECTOR_2_SET 2 333489 KEY_FUEL_SELECTOR_2_SET 2 333490 KEY_FUEL_SELECTOR_2_SET 2 333490 KEY_FUEL_SELECTOR_2_SET 2 333491 KEY_FUEL_SELECTOR_2_SET 2 333491 KEY_FUEL_SELECTOR_2_SET 2 333492 KEY_FUEL_SELECTOR_2_SET 2 333492 KEY_FUEL_SELECTOR_2_SET 2..............................just keeps going

Thanks guys Just like to repeat that this gauge works fine for engines 3 and 4 but NOT 1 and 2. Maybe something in the aircraft.cfg or somewhere else. I have tried other similar (rotrary) gauges in this aircraft and they do the same thing. phjvh Never set up a debug gauge before. Is there anything else required in the coding? Or is that all? How does it tell you what is happening. n4gix I know the sdk has a colon, but some gauges I have seen do not use one for fuel selectors. I tried both ways - no good. Thanks

Need help on a set of fuel tank selector knobs for a 4 engined DC4. I have 4 tanks referred to as Left Auxilliary Right Auxilliary Left Main Right Main but called in AIRCRAFT.CFG (to agree with MS naming configuration) Center1=0,-10,0,1000,10 Center2=0,10,0,1000,10 LeftAux=0,-20,0,800,10 RightAux=0,20,0,800,10 I am trying to set up the selection process so that the tank that feeds each engine can be manually selected. This means that EACH tank can supply EACH engine. By using CENTER1 and CENTER2 instead of LEFT MAIN and RIGHT MAIN the burning sequence set up by Microsoft, will be ignored, and if a tank is emptied, the next tank in the sequence will NOT be followed and the respective engine will stop. The gauge is part of a full Engine Control Unit and the selectors are a set of 4 levers that move vertically between 5 positions (off and 4 tanks). The attached gauge coding seems to work exactly as required for engines 3 and 4, but the selectors for engines 1 and 2 do not work. When selected the lever just jumps and then returns to some default position about halfway between the OFF and LEFT AUX positions. The coding I am using is the same for each selector (except for the number) <Element> <Image Name="Fuel Tank Lever.bmp" ImageSizes="26,36"> <Axis X="0" Y="10"/> </Image> <Shift> <Value Minimum="0" Maximum="7"> (A:Fuel tank selector 1,enum) </Value> <Nonlinearity> <Item Value="0" X="208" Y="5"/> <!-- Off --> <Item Value="4" X="208" Y="20"/> <!-- Left Aux --> <Item Value="5" X="208" Y="75"/> <!-- Right Aux--> <Item Value="6" X="208" Y="40"/> <!-- Left Main --> <Item Value="7" X="208" Y="60"/> <!-- Right Main --> </Nonlinearity> </Shift> </Element> I have used .....SELECTOR:1 etc as suggested by MS Sim Variables (FUEL TANK SELECTOR:index) but there is no difference. [similar coding for selectors 2-4 follow] <Area Left="208" Top="26" Width="26" Height="14"> <Tooltip ID="">Engine 1 Fuel Selector Off</Tooltip> <Help ID=""/> <Cursor Type="Hand"/> <Click>(>K:FUEL_SELECTOR_OFF)</Click> </Area> <Area Left="208" Top="40" Width="26" Height="17"> <Tooltip ID="">Engine 1 Fuel Selector Left Aux</Tooltip> <Help ID=""/> <Cursor Type="Hand"/> <Click>4 (>K:FUEL_SELECTOR_SET) </Click> </Area> <Area Left="208" Top="57" Width="26" Height="17"> <Tooltip ID="">Engine 1 Fuel Selector Left Main</Tooltip> <Help ID=""/> <Cursor Type="Hand"/> <Click>6 (>K:FUEL_SELECTOR_SET) </Click> </Area> <Area Left="208" Top="74" Width="26" Height="17"> <Tooltip ID="">Engine 1 Fuel Selector Right Main</Tooltip> <Help ID=""/> <Cursor Type="Hand"/> <Click>7 (>K:FUEL_SELECTOR_SET)</Click> </Area> <Area Left="208" Top="91" Width="26" Height="15"> <Tooltip ID="">Engine 1 Fuel Selector Right Aux</Tooltip> <Help ID=""/> <Cursor Type="Hand"/> <Click>5 (>K:FUEL_SELECTOR_SET) </Click> </Area> <Area Left="236" Top="26" Width="26" Height="14"> <Tooltip ID="">Engine 2 Fuel Selector Off</Tooltip> <Help ID=""/> <Cursor Type="Hand"/> <Click>(>K:FUEL_SELECTOR_2_OFF)</Click> </Area> <Area Left="236" Top="40" Width="26" Height="17"> <Tooltip ID="">Engine 2 Fuel Selector Left Aux</Tooltip> <Help ID=""/> <Cursor Type="Hand"/> <Click>4 (>K:FUEL_SELECTOR_2_SET) </Click> </Area> <Area Left="236" Top="57" Width="26" Height="17"> <Tooltip ID="">Engine 2 Fuel Selector Left Main</Tooltip> <Help ID=""/> <Cursor Type="Hand"/> <Click>6 (>K:FUEL_SELECTOR_2_SET) </Click> </Area> <Area Left="236" Top="74" Width="26" Height="17"> <Tooltip ID="">Engine 2 Fuel Selector Right Main</Tooltip> <Help ID=""/> <Cursor Type="Hand"/> <Click>7 (>K:FUEL_SELECTOR_2_SET)</Click> </Area> <Area Left="236" Top="91" Width="26" Height="15"> <Tooltip ID="">Engine 2 Fuel Selector Right Aux</Tooltip> <Help ID=""/> <Cursor Type="Hand"/> <Click>5 (>K:FUEL_SELECTOR_2_SET) </Click> </Area> [similar coding for selectors 3-4 follow] Any help ith this will be much appreciated.