Pete Dowson

FSUIPC4 cannot have anything to do with it unless you've registered it (i.e. paid for it) and are using the axis assignment options incorrectly. If it only a problem with AirHauler I think you need to go to Airhauler support and ask them. FSUIPC automatically gets the blame for everything and is very rarely the cause. However, make sure you are using an up to date supported version -- for FSX is it 4.50 or later. Pete

I hope someone else picks this up. I'm afraid I know nothing at all about Java. Pete

If you are referring to FSUIPC, then, no. They are different products. V4 was a complete re-write, the first time since FS98 days, because FSX is so different. Pete

It isn't possible. You need to restore focus to FS. Pete

By "splash screen" you mean FS's opening selection dialogue? FSUIPC cannot do anything whilst FS is in a dialogue -- dialogues are MODAL which means nothing else in the whole process happens! Why don't you simply set FS to run directly into your default flight? The selection screen has always been optional. Here, if you don't know how: Change this in the FSX.cfg under the [sTARTUP] header SHOW_OPENING_SCREEN=0 (change this from 1 to 0) Same for FS9 and most versions before. If you want FS to start up with your flight already loaded, start it with the flight name in the command line, something like: FSX.exe /FLT:flightname I think. Or maybe just FSX.exe flightname Try it. Regards Pete

No, you are writing one byte 0 and one byte rubbish to 3F00: BYTE operation = 0; // 0 to simply load the specified flight/situation. if (FSUIPC_Write(0x3F00, 2, &operation, &dwResult)) Obviously "operation" needs to be a WORD not a BYTE! A byte is 1 byte long, not 2! It would also be much more efficient to do the two writes, in that order, with one process call to send them. There is very rarely any need to do more than one process call per cycle. Always group reads and writes to save frequent process switching. Where's the FSUIPC logging with IPC Writes enabled showing that you successfully did anything? Please please please use the tools provided, especially the logging, to help you develop things. I don't want to see code -- next time show me the log if you don't understand it. Regards Pete

No, sorry. Why not turn the sound down a bit? Regards Pete

Strange then, because assigning to the PAN_VIEW axis in FSUIPC generates pretty much exactly the same sequences in FSX as assigning in FSX itself. The timing is slightly different (because of the asynchronous SimConnect interface). There must be something odd in SimConnect when in replay mode. Regards Pete

Ah, there have been odd problems with FS and Kensington mouse drivers for many years. It used to be one of the first questions I used to ask when FS tended to hang when opening dialogues like FSUIPC's. I've not seen an oddly corrupted display like yours before so it didn't connect. As far as I know, all of Kensington's mice work okay with the standard Microsoft drivers in any case. Maybe you lose some fancy facilities, but they are not worth the pain of such problems, for sure. Thanks for letting me know. Regards Pete

What version of PFCFSX.DLL are you using? Please check and if necessary update to the latest available. Let me know. The Updates announcement above contains version 4.34, which is the latest. I have provided this to Mr. Schiratti too, to replace 4.30 on his website (www.schiratti.com/dowson), over 5 weeks ago, but unfortunately he doesn't appear to be updating it these days. :-( Regards Pete

Strange. I know nothing about FSFlying School and I don't know anyone who does, so they are probably only referring to using FSUIPC, not their product. Pete

Well, it would be nice to know what it is running in your "non-Gaming mode" which is doing this. Not something like "Window Blinds" is it? That and a few other utilities like it can mess about with other folks dialogue windows. Regards Pete

Win2K still? Phew. There are more and more things not compatible with that these days. You have to wait a few seconds? That's a sure sign something is wrong -- or do you have a very large FSUIPC.INI file? No, I've never seen anything like that before. The dialogues are standard Windows API-drawn so I don't understand how they could avoid appearing. there are a few things I'd like to check though: 1. Full screen or windowed -- both the same or not? 2. Tabbing out and back -- does it fix it or not? 3. Video drivers -- have you access to older or newer ones you can try? 4. Could any other add-ons you have be corrupting run-time memory in FS: what is also running in FS at the time? 5. Can you Zip up your FSUIPC.INI file and send it to me at petedowson@btconnect.com, in case it is related to some parameters. Ah, hiso not a new user, exactly! ;-) Have you not visited this Tab before, or has it been okay then suddenly gone this way? If the latter, do you know what you changed? Regards Pete

You set i = 1 and when it is 1 you create a connection to FSUIPC. So, when do you change i? I don't see a place where it is changed. You keep trying to create a new connection to FSUIPC every loop. The second and subsequent ones will be, er, problematic. You should open your connection to FSUIPC just once, at the start of the program, and close it at the end, not continually reopen it all the time, nor opening and closing it (not that you appear to have thought of closing it). Regards Pete

You don't understand 32F6 at all. It controls user access to FSUIPC options, nothing else. It doesn't change anything whatsoever in FS. No. In the FSUIPC options you can check an option checkbox for that (provided 32F6 isn't set to gray it out to prevent changes). When it is checked, the number tells FSUIPC how long to allow the battery life -- 0 forever or a multiplier of normal discharge time. Please please do refer to the User Guide which explains the user options in detail! That question doesn't apply because there is no such parameter. 2^6 = 2 x 2 x 2 x 2 x 2 x 2 = 64, but that is completely irrelevant to your needs. Stopping the user setting or clearing an option does nothing to the battery. If you want to change the battery voltage, to stop it discharging, you need to write to the battery voltage, at 2834. Regards Pete

That is a matter for them, surely? You do not need to register FSUIPC unless you want to use its features. That registration has absolutely nothing whatsoever to do with FSUIPC. If you want to buy FSUIPC you must go to SimMarket and purchase it. No. You are evidently very confused. Doesn't the "FSFlying School" program come with any instructions at all? Don't they have their own support place for your questions? Pete

Well, i did say it must be something you've set, but you said "... I should delete FSUIPC.ini and let the program create a new one, which I did without results", so I assumed that meant you'd tested with default settings -- i.e. FSUIPC effectively doing nothing. Good. Regards Pete

Sorry, I've no idea. I don't have their aircraft. Really they are the only folks who are likely to be able to help -- but try their Forum if there is one. Regards Pete

You can probably re-enable it now. I am not sure what it does, actually, but I think it is used by some scenery files for some sort of activity. If you notice nothing different without it then it probably isn't relevant -- it may be a hangover from something you installed at one time and forgot about. It certainly isn't part of default FS. Regards Pete

"Clr Ignor" is only usable if you've already told the assignment tab to ignore any axes, else there's nothing to clear! I don't think that is at all relevant to FSX, which was designed with Vista in mind and works better if it knows it is running under Vista. The problem with setting compatibility mode is that Windows then lies to the program about what version it is, so any version-specific code does the wrong thing. You might need to use compatibility mode for some older add-ons which aren't Vista-aware, but otherwise I'd recommend you leave things be, as the designers intended. :-) Regards Pete

Thanks for the Registry export file. Did you not notice that you have been looking in a different place to that I requested? Here's a line from it: [HKEY_CURRENT_USER\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput You are looking in HKCU (HKEY_CURRENT_USER) not HKLM (HKEY_LOCAL_MACHINE) as I am logging and as I requested. Now, this is actually a big clue, and one I should have noticed straight away! Mea culpa. Windows XP stores the entries I need in HKLM whilst, at least on all the Vista systems I've seen, Vista stores them in HKCU. You are using Vista, and certainly the correct entries ARE in HKCU, yet FSUIPC is looking in HKLM. This means that FSUIPC (and therefore FSX) thinks you are running on XP, not Vista. So, tell me, have you, for any strange reason, told Windows to run FSX in some sort of XP compatibility mode (via right-click properties)? If so, why? Try letting it run knowing it is running in Vista, please -- when running in XP a lot of the registry and disk paths are different. Otherwise, somehow, FSUIPC is not getting the correct Windows version number from your system. [LATER] Before "correcting" the settings for FSX (which is, after all, fully Vista-aware), please try FSUIPC 4.514, in which I've tried HKCU when getting nothing from HKLM. If it succeeds it subsequently assumes it is running on Vista so that other differences won't mess it up! ;-) http://fsuipc.simflight.com/beta/FSUIPC4514.zip Regards Pete

I was thinking more of setting a bit in the Virtual buttons offsets (3340 following) to activate a "button" which could then be programmed in FSUIPC to do anything you liked. I've always found it more flexible to operate facilities this way rather than directly. That's one way, certainly. If you write to any of those axis value areas they will be seen as Joystick #16 axes in FSUIPC's Axis Assignments, then you can assign them to throttles and calibrate them in FSUIPC, or just have them go direct to FS controls. I use this method for my GA28R driver (a Piper cockpit from Aerosoft Australia). Alternatively, if FS2Phidgets can write 8 bytes you could consider sending the appropriate axis controls and parameters via offset 3110, though this seems less likely. Regards Pete

Ahwhy? That may be the problem. Can't you configure them as normal throttle axes? And why write throttle 1 via the disconnectable offset, 089A, but throttle 2 via the direct offset? The correct pair would be 089A and 0932! And, in any case, PM is disconnecting real throttle axes, not some program interface writing to offsets. No, it is not a common problem. I don't understand how you have an interface program for offsets which can do one thing but not another. Most throttle implementations would use joystick axes in any case. And it would only be about three or four lines in Lua, and much more elegant. I added Lua plugin facilities deliberately so that folks could do clever things for their cockpits etc. It is better than continually making the offset interface more complicated and adding options to the user interface or INI. But 310A has to be refreshed every few seconds. Actually that argument doesn't wash -- one button can do many things, you don't need to use two. The problem you have is not the writing to 310A it is the continued re-writing to 310A. How are the throttle values being written to 089A and 0924 (or, better, 0932)? Not a program? Regards Pete

Really? I don't think you are figuring that out correctly. It is only because i work so hard on maintaining compatibility for such applications between such completely different versions of FS that you can use those without paying again for complete re-writes in any case. Do you think FSUIPC4 and WideFS7 are merely renamed versions of FSUIPC3 and WideFS6? Think again! For every version of FS I have had to work full time for many months to get the interface for applications working, and this has applied from FS2000 through to FSX and ESP. I only started asking for payment for any of it with FS2004 and subsequently, despite all that -- and this is unfair? If you are unhappy about it don't buy it. See if you can do it some other way. :-( Pete

I'm not really the right person to ask, as I have had three different Garmin GPS's and none of them have accepted either NMEA inupt or Aviation (AV400) data. However, i do understand others have got it working -- there are threads in this Forum which explain this and how. USB connections are usually okay though it may take some experimentation to find the correct port name (as example is given in the docs), and you have to stop the normal sync program grabbing the port. Search on Garmin or 296, here in this Forum. Or as a last resort perhaps even try looking at the brief documentation which comes with GPSout and FSUIPC4, both of which mention explicitly mention the Garmin x96 series and provide information on USB links? Pete