Pete Dowson

Looks okay, but I've not analysed every line. why do you think there's a problem with it? Is FSUIPC hetting loaded? I note you are using the FSUIPC4 loader. Why? That's really not a good idea unless it is absolutely needed to solve a problem. You should remove the loader from the FSX Modules folder then re-run the FSUIPC4 Installer. Why "repair FSX"? G3D crashes are usually related to graphics -- sceneries and aircraft. They are nothing to do with FSUIPC. I think you are looking in the wrong place. Try a process of elimination on your graphics-related add-ons. Regards Pete

Doesn't Phidgets come with an FSUIPC interface? Why choose C++? I you sre not already a programmer then that is not a good choice. In fact there really aren't any choices if you are not a programmer. How would a program INItialisation file help control lights? The control for the iFly lights is presumably via iFly2FSUIPC. or possibly by keyboard shortcuts? I don't know, I don't use any iFly aircraft and don't know iFly2FSUIPC. I als don't know anythng about Phidgets. I really think you need to look at the support of one of those places for help. I don't really understand why you would choose Phidgets and Ifly2FSUIPC if you don't know how to use them, and certainly if you need to write a program the first thing to do is to learn how to program. Regards Pete

This is really not the best place to try to learn a new programming language. If you are intent on learning Visual C++ I strongly suggest you get a proper teaching book on the subject. Writing an application for FS is not the easiest way of starting unless you are already a programmer. Pete

Try raising a problem ticket. Pete

Did you forget your account name, or your password? I can't think why you can't find your purchased product information otherwise. It isn't really an invoice you look for first, but a list of purchased products. Pete

Sorry, there's really no way to do that -- the actual codes are bound inextricably to your name and address. I really don't know why SimMarket referred you to me as they do know this. I don't know of any software you can buy which you can transfer. A lot of software might be tied to the specific PC rather than the person, but it is still restricted. With my programs it was felt better to license the person rather than the PC, and allow the products to be used on any PC owned by the person. I really feel that is flexible enough. Regards Pete

Er, you read 0AF8 as you would any other offset. What language are you writing your program in? Have you looked at the appropriate examples in the SDK? Pete

No, there is no such offset. You would have to read 0AF8 and use the value there to select the correct tank offsets of the ones I mentioned. Regards Pete

Programming languages all have different ways of representing numbers in different radices. The Lua (and C/C++) way of representing a hexadecimal number is by preceding it with "0x" not just "x". To most languages, anything that begins with a letter is a name, not a number. The 0 tells them it is a number, and the x says it is in hex. FSUIPC doesn't need this convention because you can't use names, so it simplifies just to x. So your line should be ipc.writeDD(0x3110, 0x00011205) I see you are embodying it in a function. I assume you have something calling that function? Regards Pete

Have you deleted your FS installation? Because if not the Registration is in your FSUIPC.KEY file in your FS9 Modules folder. If you've kept no backup and have deleted your files, the only way is to log into your SimMarket account and look it up. Regards Pete

The links to the place to buy FSUIPC registrations are provided in the documentation, of just go straight there with http://secure.simmarket.com/pete-dowson-fsuipc4 for FSUIPC4 (FSX) or http://secure.simmarket.com/pete-dowson-fsuipc3 for FSUIPC3 (FS9). Pete

There are separate offsets showing the percentage full for each tank, and each one's capacity. So you can read whichever you like. See offsets 0B74 to 0BA8 and 1244 to 1260. Pete

No. The numbers need to be set to give you correct centering, that's all. The further apart they are from each other, the wider the central zone. You need the width set to give you reliable centering for aileron, elevator and rudder, with hands off, releasing those controls from any position. Most controls tend to return to slightly different positions, hence the need for a zone rather than one fixed value. Best thing to do for proper calibration is to follow the numbered steps in the calibration section of the FSUIPC User Guide. Don't worry about the specific numbers. Those are results for FSUIPC to use. The important thing is to calibrate by actually moving the control as instructed. Regards Pete

You completely misunderstand. you said you were NOT using FSUIPC for mouse look! Look, here is exactly what you said: By-the-way FSUIPC Mouse Look is unchecked. And earlier you said: I've just reinstalled the EZCAM and the problem has gone. So you are using EZCAM, not FSUIPC, and your problems need to be addressed to EZCAM! You seem to be very confused over what you are doing. Even using a default aircraft ... and what? I still see no question! I really don't know what you are here for yet! :-( Regards Pete

Hmm. I too wouldn't understand why the version of DirectX causes such problems (each version is supposed to support all previous versions). But I'm glad you got it resolved in the end. Thanks for letting us know. Regards Pete

If you check REV, whether in FSX itself or in FSUIPC, then the values sent by the joystick axis are reversed: ie they go from -16383 to +16383 instead of the other way, when sent on to the simulation engine. You talk only about right rudder action with a left "paddle". What about the other side, does the right "paddle" operate left rudder? I don't know the "Eclipse" pedals -- are they separate pedals, with separate axis inputs by any chance, like pedals for motor car driving rather than flying? Normal aircraft pedals have only one axis, pushing left rauses right to come back and vice versa. I know that some motoring pedals have a switch, or maybe a driver mode, for connecting the two sides as one axis. If so, that's what you would need to enable. You might do better to get help with the pedals -- try www.ch-hangar.com. Why do you quit and restart? Don't you just press OK and test them out? Why? There are simple numbered steps in the FSUIPC User Guide, and in any case even the default calibration would work better than what you describe. It sounds more like a misunderstanding of your device. 4.921 is the oldest supported version. You need to update in any case. Regards Pete

Well, if you are not using FSUIPC for this I don't nderstand what your question is for me. Shouldn't you be asking the EZDOK folks? Pete

Sorry, I can't help with crashing to desktop. That's something outside FSUIPC. But what exactly do you mean that sometimes FSUIPC mouse look works, sometimes it doesn't? What different circumstances prevail? The code is very simple, nothing at all to go wrong. Are you sure you aren't getting interaction with other things? Is everything off in FSX? Have you also got the mouse move option checked? you can, but then a double-clicked middle mouse button will switch. Note that the mouse wheel itself is not involved with selecting the mode, only the associated button. And of course you don't need to use the middle mouse button for mouse look -- that was just a convenience factor. You can assign any key or button. Have you tried, just to make sure you aren't getting additional mouse assigtnments messing things up? Oh, looking back, I see you installed EZCAM! If you are also using EZCAM then DO NOT ENABLE FSUIPC MOUSE LOOK!!!! Use EZCAM! they are bound to conflict! Pete

Ah, yes. The recent pmSounds versions have their own engine sound replacement options. You could remove or severely lower the FS ones in favour of those. Regards Pete

FSUIPC / Lua doesn't hook into FS's sound. That would be a tricky job involving hooking Windows DirectX calls and such. But there are probably three possibilities, I think. First is probably the "correct" way: edit your sound.cfg file to play the right wave files in the right circumstances. Take a look ast it, see all the "Jet Whine" and "Combustion" sections? I#m pretty sure they are designed to control the sounds in different circumstances. Unfortunately, though, that's all I can tell you as it isn't an area I've ever delved into. Maybe there is sufficient documentation in the FS SDK -- after all makers of add-on aircraft do create their own. Second method would be to create your own sound control, using the FS sound files (or your own), using Lua to play the right ones on the right speakers at the right time. That could be quite a big job though. Maybe you could just remove the relevant FS ones and only play your own above a certain airspeed. finally, and maybe the easiest. Just find out which of the FS WAV files which is playing at that time and reduce its volume by using a wave file editor (like Sound Forge). Regards Pete

FSUIPC4 uses the same identical methods as FSX, but it needs the ID number from the Registry, so I expect the Registry entries are not correct for the device. I use Leo Bodnar cards, and there is no problem once they are configured. I haven't done it for a long time, so I don't recall everything, but I think you need to configure the axes using a program from their site, or supplied with the boards. If the problem is with the configuration you'd need to address your questions on this to Mr. Bodnar or his forum. Pete

What you say sounds natural to me, though it would vary with aircraft model. Banking should stop fast when you neutralise the aileron. And the aircraft will gradually straighten up if there is any dihedral. Only stunt planes and some fighters have no dihedral and therefore less self-correcting tendencies. BTW FSUIPC has no influence over any of this whatsoever. You need to look to the aircraft modelling parameters, in the AIRCRAFT.CFG file and in the AIR file. Pete

Ah, you aren't setting GLOBal mode BEFORE setting weather? So when it autimatically switches to GLOB weather it has to use some weather which you've not set before but which just happens to be the default GLOB weather at the time. The received / sent / received strings from your extract are just these: Weather Received (type 4 request, Interpolated): "????&A0 221523Z 30125KT&D900LG 295V307 100KM&B-457&D30936 1CU032&CU001FLLN000N 6CI327&CI001FNMN000L -27/-30 Q1010 " That's just the interpolated weather at your current altitude -- only one temperature (-27/-30 ??), one wind layer. But it isn't the default GLOB weather which would be used to populate as yet unset weather stations. Setting Weather: "GLOB 221523Z 30110KT&D900NG 300V302 30125KT&A900LG 100KM&B-456&D2284 1CU033&CU033FLVN-14N 8CI328&CI018FNVN-14L 18/12&A65534 05/04&A997 Q1000 " Weather Mode now = Global Weather Received (type 1 request, (null)): "GLOB&A0 221523Z 30110KT&D900NG 300V302 30125KT&A900LG 100KM&B-456&D2284 1CU033&CU003FLVN000N 8CI328&CI001FNVN000L 18/12 05/04&A997 Q1000 @@@ 30 6 301 25 | " So the setting is being set. But notice that most of the values are different -- eg QNH is now 1000 not 1010. Your temperatures at your location were -27/-30 (??), but the default global at ground were 18/12. These entries "18/12&A65534 05/04&A997" are odd. There are two layers being set, but altitude 65534 can't be right -- that's probably -2. Are you over a place below sea level? It does seem to have been accepted okay though as the 18/12 was returned ok as was the next layer, 05/04. The default GLOBal weather does not usually fearure layering, so i'm surprised really that there are two temperature layers included here. But I'm perplexed as to why the correct temperature gradient was not applied until you went into menus. that's another FSX weather bug to add to all the rest! There are some possible ways out of this: 1. Set GLOBal mode before trying to change anything. I suspect this won't give you what you expect though. But worth a try. 2. Either use the AWI interface, which does allow you to make individual changes, or the NWI, which is more comprehensive. To be honest, I'm really surprised anyone is still using the FS98 offsets. I have tried to make them work compatibly, and mostly achieved this in FS9, but FSX is a completely different kettle of fish. Sorry. Regards Pete

I've no idea what "autoheading" is, sorry. There is really no way FSUIPC can ever run without producing both a Log and an INI file and no one has ever failed to find these before, not ever, in the 14 years of FSUIPC. I really have no idea where you are looking, but it really does have to be the wrong place. I think you need to do a search. Search for the Install log as well. The filenames to look for are: FSUIPC4.log FSUIPC4.ini FSUIPC4 Install.log An alternative is to re-run the Installer, and save the Install log via its menu entry before clicking the OK button when it confirms it has installed okay. The menu is in the log display, which will be behind the confirmation prompt. Click "Save As" and select a place and filename to save it where you can recoup it. Youwill need to move the log display afterwards in order to press 'OK'. Then show me that log. Regards Pete

Sorry, I've no idea. Can you enable weather logging, in the FSUIPC logging tab, and see what METAR string is being sent as a result of you changing the visibility? (Remember, FSUIPC has to set the ENTIRE weather each time you change one little thing, because SimConnect only accepts the full extended (FSX format) METARs) I would suggest comparing the last METAR read with the one then sent, but they are not directly comparable because the format for reading is different to that for writing!!! Grr. Pete