Pete Dowson

I've moved your post to the Support forum, which is where Support is available. For some reason you posted to the "FAQ" subforum which is a repository for the answers to Frequently Asked Questions. You are lucky i noticed it there. How awful! What a spoiler for realism that must be! Can't they get their position reports directly? Hmm. Is this perhaps a video driver problem? You didn't leave your video system to the wiles of Microsoft's own drivers did you? The first thing to do after installing Windows 7 is to go get the latest drivers for your video card. The only other alternative is to only ever run FSX in Windowed mode. Maximised it still gives the same sort of frame rates. FSUIPC won't have anything to do with any of that, I can assure you. The only way FSUIPC can mess anything up is if one of it's client applications does so, as FSUIPC is really basically a door into FS's innards. If you have some actual technical information you can share about one or more of your many problems, maybe they can be dealt with if possible. You'll have to supply a list of all the addons you are using as it is most likely one of those causing problems -- maybe a combination. Just saying " now I am strugging to get back into FSX as before. I also got/get a lot of FFSX has stopped working messages." doesn't really draw any sort of picture. Are you running FSX or not? What does "struggling" mean? If you really mean you can't run FSX at all, that it stops during initial load, then presumably you've looked at the FAQ subforum thread about that and tried everything it suggests? After all you did post in that Forum, so I assume you looked at it? You did say you "have looked everywhere for a solution to my problem". Did you actually look at the places which match your symptoms? More details are needed I'm afraid. Also please state the actual version number of FSUIPC. Was it 4.70 or a later one? The current Installer installs 4.728, and there is a 4.731 now available in the Download Links subforum. Pete

Note that unless you used the Joystick Lettering facilities in your FSUIPC assignments, the numbering of the joystick devices on your new PC might not be the same as they were before, so there may be some editing of the INI file to do. If you've not yet taken down your old system, and are not yet using joystick lettering, it might be wise to do the lettering change first, on the old FSX system. Then there's no mess to fix. Regards Pete

How have you done that? I'm really not understanding what you've done, so I can't comment. Can you expand? Regards Pete

If you mean you placed FSUIPC into the Modules folder, then it won't work unless it is installed. You must run the Installer. Also, FSX is not like FS9 and there is no "Modules" menu entry. If FSUIPC4 is installed correctly it's options are available via the AddOns menu. Please do refer to the supplied documentation, installed for you as listed in the Installation guide. Regards Pete

If the older one was FSX too, then just save and copy the FSUIPC4.INI file from the Modules folder, plus of course any Lua and MCRO files you may have made or installed. Your registration is contained in the FSUIPC4.KEY file so don't lose that either. You'll need to run the Installer on the new PC, but do this after your first successful run of FSX, to ensure all of its files are properly readable. Regards Pete

Sounds like you have got something wrong. That sequence works fine here. Try it with FSInterrogate. Maybe you are changing the starter switch too quickly, so closing the valve before the engine is truly running? Don't change the starter from 1 to 2 until the combustion flag (0894) is set, and N1% reaches 20%. On the real 737 that's when the starter switches reset to OFF and you engage the generators. Otherwise, use the FSUIPC logging facilities to check what you are writing, and the Monitor facilities to check the offset values. That's pretty much all-encompassing, and tries to cope with all aircraft types so cannot rely specifically on N1 and N2 readouts. For jets it does: battery on (281C) avionics on (2E80), tank select (3880) correct pump on (3125), starter to 1 (GND), wait n Secs (about 10 for jets -- not realistic but okay with FS9 defaults), mixture full rich, wait for combustion flag but at least 10secs starter to 2 (GEN) generator on (3B78) Pete

Best to post such questions in the main FSX or FS2004 forum (whichever version of FS it is you are using, as you don't say), or even better in Wilco support. Any problems specific to those aircraft and not on the defaults is likely to be a specific installation problem. However, if you are assigning axes through FSUIPC then you might need to take note of this section in the FSUIPC Advanced User's guide: Regards Pete

Ah, so it was to do with the filtering! (I keep saying -- I don't like that filtering! ;-)). Anyway, I'm pleased that the recent filtering fixes fixed your problem too! I wouldn't have guessed. it took a lot of elimination and logging to work out what was going on! Pete

Glad you resolved it. If it is likely to help others, do you think you could re-post your helpful pix in the User Contributions subforum, please? Thanks, Pete

If it is sending keypresses then, yes, it's more a keyboard than a joystick, or maybe it can be both or either. I did Google it and found a description which includes: Standard USB joystick simulation (6 axis, 32 buttons with triggering support). Now if that is true then all of thsoe 6 axes and 32 buttons should be detected in FSUIPC4 (and FSX for that matter). If they are not then it is likely that you need to do some configuring using the software supplied with the card. After all, it does say: All the I/O are controlled by the provided software which allows either to use the graphical user interface or advanced console type interface. The settings can be stored on the device, so no special software is needed on target system. I see you included the whole of the HidScanner log, which wasn't needed. But there are actually three entries for the PoLabs device: Manufacturer= PoLabs Product= Virtual Joystick which certainly does have 32 buttons and the usual 6 axes: Buttons range 1 -> 32 at indices 6 -> 37 Value U/RX at index 0, range 0 -> 1023, using 16 bits Value V/RY at index 1, range 0 -> 1023, using 16 bits Value Z at index 2, range 0 -> 1023, using 16 bits Value Y at index 3, range 0 -> 1023, using 16 bits Value X at index 4, range 0 -> 1023, using 16 bits Value Thr at index 5, range 0 -> 1023, using 16 bits the other two devices it presents are: Vendor=1DC3, Product=1001 (Version 16.0) Manufacturer= PoLabs Product= Communication Interface which is presumably its programming interface, used by its own software only, and Vendor=1DC3, Product=1001 (Version 16.0) Manufacturer= PoLabs Product= Virtual keyboard Your "virtual keyboard". One point that does come to mind is that FSUIPC only handles the first 16 joystick devices, those assigned an ID by windows of 0 to 15. This is the "joystick number" it uses. I'm wondering now, with all those devices you have connected, whether Windows is actually assigning an ID in the range FSUIPC can handle. Please check the FSUIPC4.INI file. You'll find a section in there entitled "[Joynames]". See if the device is listed there. if so you should be good to go. If not then its either some configuring at the card which is needed, or you'd need to resort to a Lua plug-in. The latter could certainly handle the "virtual joystick" device. Regards Pete

The documentation is available separately in the Download Links subforum (Documentation is the title of the thread in there), but if you have actually Installed FSUIPC already, you will have seen from the Installation guide (the document included in the ZIP file), that it lists all of the documents and other goodies it installs for you, and tells you where they are -- i.e. in the FSUIPC Documents folder inside your FS Modules folder. Pete

Well, carry on using it. I'll release it in the Download Links subforum in any case. I'm reasonably confident in the changes I made, now ... ;-). wider usage would be welcome in any case. Thanks, Pete.

Okay, I already guessed it was due to the mapping. The mapped controls cause an attempted re-entry for filtering (which isn't needed of course in any case) and the semaphore lockout check, er, locked up! :-( Try FSUIPC 4.731 please Regards Pete

I'm actually also using on-board hardware -- not sure if it's Realtek or not, but that's most likely. The facilities for modes are in the "Sound" control panel applet, "Playback device" tab, "configure" button. This is Windows 7 with its own installed drivers. The code already does that of course. It tests the capabilities of the sound device and uses Panning or Positioning as appropriate. I traced through the running code and the card never says it has panning, no matter what mode i set it into. I also tried sending only the stereo panning, irrespective of the capabilities, and that didn't work either. I'll investigate further when I have a little more time.

No, I'm not removing filtering, though I don't like it myself. It should only make things smoother on a rather unsmooth input, so it's very dependent on the hardware and its connection. Yes, but as I found, switching the card to stereo mode seems to destroy any ability to choose a position, which seems totally daft to me. I can only find two ways to position as I said, and neither work in stereo mode. Everything's fine in 5.1 and other surround modes. There must be a way, of course, but it defeats me at present. I'll research it further when I have a bit more time. Not now. Sorry. Set 5.1 or another 3D mode and change the angles to 45 and 315 and it will go to the correct side of your head. I've fixed the double event problem. Once I could clearly map the routes things were taking it was easy enough to put the right check in. Please download FSUIPC 4.731 Regards Pete

Sorry, I'm not familiar with that term, "abend". Can you elaborate please? I looked it up and it said "abnormal termination", so if that's the case it's a crash, and you have details like where etc? So your "abend" is a "freeze" not a termination? Do you mean a hang? FSX hangs completely and you have to terminate it with Task Manager? And it only happens after switching from the 737 to the 747? Can you make it fail without the mapping of the throttles? (I guess you'd have to only use two engines. Sorry). Can you make it fail without the filtering on? Regards Pete

I checked this again. There are two ways of positioning sound: SETPAN for non-3D capable setups, using just left/right speakers, and SETPOSITION for 3D/surround capable setups, using any number of speakers up to 7.1 It seems that some sound cards support only one or the other. In my test case I have 5.1 speakers plugged in and normally the card is set to "5.1". Then the positioning from FSUIPC is perfect. But if i select Stereo mode in the Windows properties for the sound, I get the sound on all three front speakers no matter what position is set. It should let me use "SETPAN", as on a stereo card, but it doesn't, and the SetPosition seems to be, er, ignored. So, please check your windows settings. Incidentally, your Left and Right sounds are much more precisely positioned if you use 45 for right and 315 for left -- then they are precisely on the right and left speakers. with 90 and 270 the 3D effect tries to set them direct right and direct left using rear speakers as well, which make the sound rather more "amorphous". I'm still trying to work out a way of correcting the double event. I can see what it is doing, but fixing it without messing other things up isn't so easy ... Regards Pete

Does FS itself see them? If so, as what button numbers? FSUIPC3 uses the basic windows joystick API (like FS98 and FS2000 used to), and it may just be that the device isn't compatible with that. FSUIPC4 uses the same methods as FSX. There's a utility program called "HidScanner" available in the Download Links subforum (in the "Latest Lua" thread). If you run that it will show details about all the HID joystick devices on your system. find that card and show me the extract from the Log it produces. If you are using FS9 or before, and the device isn't compatible with the basic joystick interface, then the only way to access the buttons in FSUIPC would be via a Lua plug-in using the Hid functions in the COM library. Regards Pete

So, is it a this visibility layer, or a cloud, or is the actual layer's visibility being changed back and forth? What do AS say? Have you used FSUIPC's weather logging to see what is happening? You could also use the little demo application "WeatherSet" to check (see download Links subforum). I'm afraid i can't really say whether FSUIPC's facilities will defeat whatever it is AS is doing. Unless AS know what is going on all you can do is experiment and see. I've not used FS9 for years now but i don't remember anything like that with AS6.5 and FSUIPC. Pete

Sounds like a little haze layer added by your weather program, to make the ground look hazy from above. Not specifically if you are already in the surface layer. You can set the minimum surface visibility, differently for different cloud conditions, but all the other visibility options concern the area above the surface layer. Have you enabled FSUIPC's visibility smoothing? If so check its parameters too. Are you sure it's a visibility thing and not a thin cloud layer? Check the haze option(s) in AS. You might want to ask this over in the AS support forum as they have more idea of what the assorted AS options do over there. Regards Pete

Okay. checking today ... It sounds like you've not moved the min-max enough, then ... Filtering will slow the changes considerably, and allow a calibrated 0 to be seen, but evidently your calibrated "idle" zone is not large enough to guarantee a stable enough idle. I think that might be because of the specific sound device configuration. Try 5.1 surround or similar. I use it here and get sound positioned well. [LATER] I just re-tested the sound with 4.729, and it certainly positions correctly here. The speakers used depend on the sound device configuration. For example with "Stereo" selected it'll be using front speakers only -- left-centre-right, with 5.1 it will use rear speakers too, to get 360 positioning. Regards Pete

I notice from these: Throttle1=-16383,0,0,16383/40 Throttle2=-16383,0,0,16383/40 Mixture1=-16192,0,0,16192/40 Mixture2=-16192,0,0,16192/40 PropPitch1=-16192,0,0,16192/40 PropPitch2=-16192,0,0,16192/40 that you have FSUIPC's Filtering checked. Why is this? Are you joysticks very jittery? By some coincidence you might see from another thread near here (here)that some problems have been discovered with filtering, and I'm now wondering if this double event is another side effect of this. So, could you try with the filtering off on all those 6 axes, please (I say all because there's a good chance of them cross-interfering as I discovered today). Please let me know. If that helps you might want to try 4.729 which I supplied today in that other thread, because that should have the filtering bug fixed: http://fsuipc.simfli.../FSUIPC4729.zip The other odd thing about those "calibrations" is that they seem too 'perfect' to be true calibrations! Surely you should allow some dead zone at either extremes, otherwise you cannot guarantee to reach a stable idle nor max thrust! In fact with min and max set at -16383 and +16383 the calibration is doing nothing at all, there's little point in using it! Meanwhile, tomorrow I'll see if I can reproduce this double event -- but I shall be using 4.729. Regards Pete

I think that's the number of separate applications allowed to connect with this connection. I've no idea how shared cockpit works -- I've never used it and was not even aware it had anything to do with SimConnect. I thought it was a multiplayer type interface as in previous FS versions. The usual default MaxClients is 64 I think, so you could try bumping it up. Sorry, I don't know what "Nagles" are! Those only load local applications or DLLs, which may then become SimConnect clients or may not. They won't use up any of the "max clients" in your XML file -- there are two other connections, local and pipe, both of which have another 64 limit (default) each. Not in anything like this. I'm an extensive user of SimConnect as a normal client, that's all. On Windows 7 or Vista don't even think about messing with WinSxS folders. I ended up having to reformat the disks and reinstalling Windows in order to get SimConnect working again, just because I was trying to work out a way for folks to do repairs themselves, or even writing a program to do it! I gave up. It is far too convoluted. You could enable SimConnect logging and see if there's any sign in there about what is going wrong. Regards Pete

So, it isn't a bug, just something in your program "not working correctly!" ;-) Why post the code if you know it is perfectly good? FS and FSUIPC aren't going to behave differently just because you started a new project! Check with FSInterrogate, or just monitor the offset in the FSUIPC logging page -- you can see it in real time in an FS window then. Pete

Sorry, it isn't my programming language. Maybe someone else will jump in, but you may need to put the language details in the title. Why not try tracing through what you are doing with a debugger? Pete