GCarty

That could help except that it's in C++ -- what things do I need to change in my C gauge programming to convert it to C++ (other than to change the .c extensions on the files to .cpp)?

How can I interrogate the left-right position of the joystick? I want to make some gauge code that will record the bank angle when the joystick is centred and maintain it until the joystick is moved a given minimum deflection away from centre, as part of some code for simulating autopilot Control Wheel Steering. Which parameters do I need, either native C parameters, or XML parameters I can get in C using execute_calculator_code? Thanks a lot, if anyone can help, George

There's no occurrence of (A:LIGHT LANDING,bool) or anything else resembling gauge XML code in the MDL file -- I was imagining I'd be looking for offsets similar to those used by FSUIPC...

How can I use a hex editor to fix an .mdl file where the anti-collision strobe light has been erroneously assigned to the landing lights switch instead of the strobe light switch?

TBL1503 has N2 RPM as a function of throttle position and reciprocal air pressure for stationary operation, while TBL1504 has the same data for high-Mach operation. Use these tables to set your N2 values.Once your N2 values are correct, use TBL1502 to set N1 as a function of N2. You'll probably want to use a spreadsheet program to work out the data before copying it into your AIR file editor.

As I indicated in the original message, I didn't write this code. Does anyone have any ideas for how I can write code which fulfills the same purpose, and which works in both FS9 and FSX

Why no replies? Is my request impossible?

I have the following code in some FS9 gauge source code I was able to get from someone (and which I'd like to make work with FSX too). It determines whether or not the panel should play sound (it checks that FS sounds are enabled, that the aircraft is in an internal view, and that FS is not paused or in slew mode).It doesn't work in FSX because GLOBAL.DLL does not exist in that sim. How do I modify it to make it compatible with both sims? case PANEL_SERVICE_CONNECT_TO_WINDOW: RXPGLOBALHANDLE = GetModuleHandle("GLOBAL.DLL"); if ((RXPGLOBALHANDLE) != NULL) { SimSound = ((UINT32)(GetProcAddress(RXPGLOBALHANDLE,"Linkage")) + 0x0B20); // sound control SimPauseOrSlew = ((UINT32)(GetProcAddress(RXPGLOBALHANDLE,"Linkage")) + 0x0B24); // sound flag SimView = ((UINT32)(GetProcAddress(RXPGLOBALHANDLE,"Linkage")) + 0x0D48); // 2=tower or spot view } else { SimSound = 0; SimPauseOrSlew = 0; SimView = 0; } break;case PANEL_SERVICE_PRE_DRAW: if ((* (unsigned char *) SimView) != 2 && (* (unsigned char *) SimSound) == 1 && (* (unsigned char *) SimPauseOrSlew) == 1) { SoundFlag = TRUE; //enable sounds } else { SoundFlag = FALSE; } By the way, I've already got a BOOL in the code called IsFSX, which does exactly what it says on the tin...

What do want tan(x) for?tanh(x) has completely different behaviour...

I want to add an "easy load" option to an INS gauge, which loads the GPS waypoints from the current flight plan into the INS. How do I access the latitude and longitude of all GPS waypoints within a C gauge?I can't find anything in GAUGES.H - are they available in XML to be grabbed with execute_calculator_code?

I have written an FS2004 panel with a single big custom GAU file. It works in Windows XP, but not in Windows 98 or Millenium. What could be the problem? The panel uses DirectSound for gauge sounds.An earlier version of the panel (with several small GAUs instead of one big one) did work in Windows 98, but I no longer have the source code for that as I've added a huge amount of additional functionality since then.Any ideas? Is DirectSound to blame, or does Win9x have a limit on the amount of complexity in a single gauge?

Actually, it's easy to customize lift and drag for flaps in the aircraft.cfg, by using three separate flaps tables as below (sample data only). The first table gives the degrees settings displayed on the panel, while the second and third set lift and drag for each flap setting.// this table is for displayed flap settings[Flaps.0]type=1span-outboard=0.500extending-time=11.000system_type=0damaging-speed=250.000blowout-speed=300.000lift_scalar=0.000drag_scalar=0.000pitch_scalar=1.000flaps-position.0=0.000, 0.000flaps-position.1=20.000, 0.000flaps-position.2=30.000, 0.000flaps-position.3=40.000, 0.000flaps-position.4=50.000, 0.000//this table sets flap lift[Flaps.1]type=1span-outboard=0.500extending-time=11.000system_type=0damaging-speed=250.000blowout-speed=300.000lift_scalar=1.000drag_scalar=0.000pitch_scalar=0.000flaps-position.0=0.000, 0.000flaps-position.1=34.300, 0.000flaps-position.2=44.500, 0.000flaps-position.3=47.200, 0.000flaps-position.4=50.000, 0.000//this table sets flaps drag[Flaps.2]type=1span-outboard=0.500extending-time=11.000system_type=0damaging-speed=250.000blowout-speed=300.000lift_scalar=0.000drag_scalar=1.000pitch_scalar=0.000flaps-position.0=0.000, 0.000flaps-position.1=5.000, 0.000flaps-position.2=10.000, 0.000flaps-position.3=30.000, 0.000flaps-position.4=50.000, 0.000

I've managed to get in touch with the original author (Steve Weiher), and it looks like I might be able to get the source code after all! He suggests an FSSound problem is probably to blame too...

Yes, the DC-8 panel does use FSSOUND. However, the new gauge I added to the panel also uses FSSOUND, and it works fine whereas the old gauges don't.

>>I'm afraid that that isn't possible, for reasons which I>>can't explain here.>>No need for mystery.>>A request like this (hex editing) with all the mystery seems>more like you are trying to hack someone's work.>>Really, if you want help, you would need to post more info,>like the panel you are trying to edit, who's panel it is, or>frankly, all you are doing is violating whatever license>agreement you have to use that freeware.>>Just because it is free does not mean it is public domain and>that you have any right to modify it in any way. The original>author holds the copyright, and if you cannot contact them,>then you are out of luck, it is a copyrighted work not in the>public domain.OK, I'll give some details...I am trying to get the Historic Jeliners Group (http://www.simviation.com/hjg/) DC-8 panel working in FSX.I am a member of HJG myself, and made HJG's Boeing 707/720 panels for FS2004 in their entirety, as well as doing a "shunt engineering" job on their FS2004 DC-8 panels - replacing the engine gauges to be specific to each marque of DC-8, as well as adding automatic smoke effects, plus water injection on the DC-8-10 (which I simulated as afterburner).I have now got the 707/720 panels working in FSX (although the new versions haven't yet been released), but DC8SW.GAU (the main gauge of the DC-8 panels) will not appear in FSX (When I tried to run the panel in FSX, the only gauge which appeared was the extra one I programmed myself). From my "shunt" job I am aware that the engine gauges use complex internal workings rather than simply reading FS variables (I ended up making my own gauge only display a background image, while the existing gauge displayed the needle).