Pete Dowson

For #1 you just set the mousewheel move, as documented on page 18/19 of the User Guide. It isn't a "zoom", it's a eyepoint move. Mouse wheel zooming is part of the Mouse look facility, page 19 in the user guide. #2 is not something FSUIPC can do (unless you program it as a Lua plug-in). FSUIPC provides no assignment facilities for the mouse. Use buttons or joystick axes or keypresses. Pete

You really need someone who can help you with VB6. It is obviously a prgramming problem. You do realise, I hope, that, if my memory serves me correctly, VB6 treats all numbers as 32-bit signed numbers. So your &HB000 may become &HFFFFB000 because of sign extension when used in the FSUIPC interface calls? I've seen this problem many times, but not for a long long while (back to FS98 or FS2000 days, the time VBn was much used). I think, but you'll need to check, that you append another & at the end to stop the sign extension. Check though. I don't have any VB6 references. That would apply to both reads and writes of course. The complete structure is used when using the binary structured data. If you are writing and reading METAR strings then of course you do not use any of that EXCEPT to set the Weather station ID, like "GLOB", before wrting the METAR, or (in a separate command) to clear weather, or whatever command you want to execute. Here I can only really repeat what it says in the ReadMe document. Signatures are only used to deal with the problems of different programs trying to read different weather stations at the same time. If you don't expect anyone else to be using the NWI then you can just set it to zero and keep it zero. You can in any case check the ICAO against the one you requests when you see the timestamp changed and so can read the new entries. This is wrong: The NW_CLEAR is a command to clear the weather. You send that on its own. Writing GLOB sets the ICAO for whatever you want to do next. It does nothing by itself. You need to read or write something. What are you trying to do? Clear the weather and read the clear weather later? The procedures are written step by step in the ReadMe text file in more detail that I can go into here. What do you want me to do, just reproduce it all here? Pete

I am not familiar with SPAD. Does it detect button 7, or did you just program it with numbers? The virtual button system is used a lot -- I use around 80 of them for my multi-page WideFS "ButtonScreen"s, for small touch screens in the cockpit. There's really no way a bit can get set in the virtual button offsets without it being detected in FSUIPC, so I really think you need to check the detection into SPAD. For more data you could use FSUIPC's IPC write logging to see what gets written to FSUIPC offsets when you turn the knob. Button 64,7 would be the top bit (0x80) in offset byte 0x3340. Pete

There are many add-on aircraft which waste computer time continuously sending controls to FS. Why do you think it is anything to do with FSUIPC? Events occurring inside FS does NOT mean they originated from button presses or key presses. They can be raised internally, by add-on aircraft, or even by other add-ons, internal or external. To see if you have buttons or keys pressed and repeating you'd need those logged. Is this activity doing any harm? If it still happens with default settings in FSUIPC (you tested with the INI file removed), then it obviously is nothing to do with FSUIPC or your assignments or profiles. If you want me to look at your settings I would need to see the INI file (and profile if you are using separate Profiles in the Profiles folder). And next time you post an FSUIPC log file please do NOT remove the first few lines. I cannot even see what version you are using because you did that, nor what logging options you set. For instance, did you enable button logging to see if it was buttons repeating? Or keys pressed? Why are you logging events in any case? Pete

Please don't put your replies inside quotes from me. It makes it very hard to answer back properly! In FSX assignments do you see it actually recognised as button 1? Have you actually used FSX to assign to any of the butons or just left all to default? Are you sure there's no Saitek program running which is sending stuff to FSX. It does sound like something else is reading the buttons first and interpreting them. Otherwise it is very strange. Maybe it's the Win8 problem attacking!? Some special logging might help. Please edit the FSUIPC4.INI file (in the FS Modules folder, adding these lines to the [General] section: Debug=Please LogExtras=x200008 Then run FSX, Enable Axis and Button logging in FSUIPC's logging tab, then go and press some of those buttons. Close FSX. Then I need to see the FSUIPC4.INI and FSUIPC4.LOG files, please. You can paaste ther contents into a message here.Use the <> button above the edit area here to enclose the texts. Pete

Well FSX wasn't sufficiently uninstalled to make it look like it wasn't there, and your SE installation is the same as it would have been if FSX was still installed (for instance it uses an FSX_SE.CFG file instead of FSX.CFG, and stores its flights in the Steam section of your Documents folder). Look, it is obvious from the log: Looking in registry for FSX install path: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\10.0 Parameter"SetupPath" ... >>> OK! FOUND FSX! <<< ... SetupPath=C:\Program Files (x86)\Steam\steamapps\common\FSX Looking in registry for FSX-SE install path: HKEY_CURRENT_USER\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator - Steam Edition\10.0 Parameter"AppPath" ... >>> OK! FOUND FSX-SE! <<< ... AppPath=C:\Program Files (x86)\Steam\steamapps\common\FSX\ See? The Registry has entries for both FSX and FSX-SE, but they now both point to SE! Further down you will see that FSUIPC installed for FSX first, then FSX-SE. The FSX install failed because it couldn't locate FSX.CFG file -- that is where your error comes from. The FSX-SE install was perfectly successful and would have certainly been reported as such. So why not believe it? Why do you doubt? If you don't want the spurious error and extra installation for FSX, you'd need to delete the Registry entry saying FSX is installed. i.e.the keys here: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\10.0 In the next version of the Installer I'll try to suppress the error when it sees both paths point to the same place. Pete

You can't calibrate buttons. FSUIPC's calibration is for axis controls and works on the actual controls, not the inputs. No, I don't want an image. What button numbers are they in FSX? FSUIPC only supports buttons 0-31 (numbered 1-32 in FSX). I know people SAY that. I've never said it and every time folks say it here I tell them there is no reason I know of which would make it better in FSUIPC than in FSX itself, as both use the same methods. The only advantage FSUIPC has is that it does see disconnections and reconnections of USB devices -- with FSX you normally have to restart it to see a newly added device. FSUIPC sees them when it scans on entry to the relevant option tabs. Pete

If you programmed it in FSUIPC then obviously FSUIPC does read and recognise you knob, turned both ways from what you say! So you really mean you don't know how to program it for the NGX. How are you programming it? The PMDG aircraft have autopilots which don't use any of the standard FS controls. Pete

You'll need to show me the FSUIPC4 Install log, placed in your FSX-SE Modules folder. One thing I don't understand. you say " I am running FSX SE alone (no FSX)." but then shortly after " I went back and ran FSX". FSX? Or FSX-SE? I suspect, but I can't confirm without seeing the Install log, that you have a Registry entry for FSX and for FSX-SE. Did you first install FSX-SE before uninstalling FSX? If the registry entries say both are installed but one isn't really there, you'll get this spurious error because the Installer is trying to set both of them up. It won't do any harm (at least to FSUIPC), but can then only be corrected by removing the incorrect Registry entries. I could tell you a lot more with the Log (which is why the log is produced, incidentally!) Pete

What happens when you press your buttons, then? Sorry, you'll need to describe what you see. Do you have some Saitek software interfering, maybe? Does FS see your buttons? Does Windows, for that matter? FSUIPC doesn't do anything special for Saitek. It just reads buttons and axes off any normal joystick or hgame controller type device, using standard Windows facilities. Same as FSX in fact. If FSX "loses" joysticks I expect FSUIPC will too, as they are both trying to use the same Windows interface. Pete Pete

Just go to SimMarket and open your account. All the keys for all your SimMarket purchases are always obtainable that way. Pete

WideFS registration is independent of FSUIPC registration. Neither, either or both. Pete

That is a techincal problem as I deal with FSUIPC registration problems. Every single time anyone has been unable to register it has been because of either of these two reasons: 1. They are making mistake. ALL THREE PARTS must be absolutely identical to those as originally issued. This is not variable. it does not change just because you reinstall Windows. I'm frequently amazed at how many ways folks want to spell their names, for instance. Additionally you do NOT use a new changed email address, you use the one you purchased it for. No other. 2. They try to use a key purchased for FSUIPC3 with FSUIPC4, or vice versa. They are different products with different keys. Same for WideFS6 and WideFS7. The registration system for FSUIPC and WideFS has not changed in the 11 years it has been operating. In fact it was made more flexible some years back by allowing different email addresses for FSUIPC and WideFS registrations. If you are really convinced you are doing things correctly, send me the details -- order number and what you are entering, to petedowson@btconnect.com. But thoroughly check what you are doing first. There have been no exceptions to the above in all this time, so I'm very sure of my ground here. Pete

Yes, that is the Windows game controllers applet, and it is often replaced for specific devices by the version specific to your hardware. If you go into Windows Control Panel - DEvices and Printers, you should see your device. Right click on it and you'll see "Gamer controller settings". which brings up a list of installed game controllers. That shows how Windows is classifying your device. Maybe on the disk which comes with the device there's an installable "inf" file, or setup, which provides a mpre appropriate driver and / or classification. Evidently Windows thinks your device is different to what it is. You need to see if there's a better driver, or maybe select a more matching default selection. However, you should be able to do it. It normally only moves on if you press a button . Maybe you are accidentally pressing one, possibly at the ends of the axis travel? I do see that this is not because of FSUIPC. For now after removing the B377 portion in FSUIPC.ini and enabling controllers in FSX the throttle behaves weird. Can go from -16000 to around zero for just nudgong the lever when at idle detention. I don't use any of these commercial devices so I can only advise on what others say. I use PFC serial port devices. with my own drivers. Pete

Oh dear. You first added this to another, presumably irrelevant thread, which is where I first saw it and answeredit, and now your own thread. Please do behave sensibly. Here is my reply from the other thread: SimMarket provide sales support for registered customers by them raising a problem ticket. It is not at all "terrible", it is just a different method. If you want technical support with a product you ask via the appropriate support forum for the product. SimMarket do not provide technical support, you need to go to the correct place! Pete

SimMarket provide sales support for registered customers by them raising a problem ticket. It is not at all "terrible", it is just a different method. If you want technical support with a product you ask via the appropriate support forum for the product. SimMarket do not provide technical support, you need to go to the correct place! Pete

Not that much out, then? Max difference I see there is 5/128ths of the travel. Typical variation between hardware. Pete

FSUIPC is not really designed to send commands to anything other than the User Aircraft. However, for AI aircraft you can use the offsets at 0x2900 once you get the ID from the TCAS tables. Note that the ID FSUIPC uses is not the same one you see in Traffic Explorer. I think it's the negative of it, or maybe the complement (NOT). The most flexible way of handling traffic and objects in FSX and P3D is by using SimConnect. FSUIPC is all about cross-platform compatibility, since FS98, so newer things which are better handled in SimConnect (only new in FSX) are left to that interface. Pete

Oh dear. You are pointing it to Prepar3D when it it trying to find FSX. Look: Looking in registry for FSX install path: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\10.0 Parameter"SetupPath" ... >>> OK! FOUND FSX! <<< ... SetupPath=D:\Flight Simulator\ According to your Registry you have FSX installed in D:\Flight Simulator. It needs to check the FSX.EXE, not the Prepar3D.EXE! The Regstry also says you have Prepar3D v2: Looking in registry for Prepar3D v2 install path: HKEY_LOCAL_MACHINE\SOFTWARE\Lockheed Martin\Prepar3D v2 Parameter"SetupPath" ... >>> OK! FOUND Prepar3D v2! <<< ... SetupPath=D:\Prepar3D\ s if you cancel out of trying to install for FSX (which I assume you deleted without removing the Registry entries saying it is there!?) it should carry on and handle Prepar3D. Why are you aborting? If you deleted FSX you should remove the Registry entries at HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\10.0 Pete

When it "fails to launch", is there any error logged by FSUIPC? If so the error number will tell you what the problem is -- it will be a standard Windows system error code, as listed here: https://msdn.microsoft.com/en-us/library/windows/desktop/ms681381%28v=vs.85%29.aspx UAC shouldn't be anything to do with it. The Program Files folders might be protected, but it's against being written, not read or executed. Pete

You've forgotten already? Didn't you even try it back then? See my answer to the same question back in post #13 on the 2nd of this month! Pete

Sorry, I cannot help any further. FSUIPC simply reads what FS provides. FS9 weather system is not very clever in any case. It may be that the layers from one weather station interact with another, and the indications FS provides get mixed up. Did you even ever bother to see what WeatherSet was reading at all? You simply want me to solve apparently insoluble problems in a program long since unsupportable? I strongly suggest you abandon such an old product and move to FSX if you want more reliable indications. Pete

FSX does not offer any sort of calibration facility. you must be talking about the Windows calibration. And that works fine. If the device looks like a yoke it is either because it identifies itself incorrectly, or you are choosing the wrong sort of device. Which version of Windows are you using? Either way, it makes no difference. Place it anywhere except either end for the middle. It's only your end points, min and max, which matter at this time. You also seem to need some help. Go to the CH-Hangar website where you will certainly get help with any CH device. http://www.ch-hangar.com What did you assign it to? The RAW is never sleected and greyed out except for special axes like POV devices (hats), axes P and Q. Delete the relevant profile sections from the FSUIPC4.INI file, found in the FS Modules folder. If you set "UseProfiles=Files" you also need to delete the named profile .INI file in the Profiles subfolder. Pete

If you OK out then next time you try to set more Sync Positions you are asked if you want to start again or just add to the ones you've set. The prompt is actually Sync settings already exist: should these be replaced? and to add more just say No. But if you simply move both levers, and hit Sync Pos for each position, there is no way you'll get that prompt. That is just a facility to enable you to start agai, if you want to (reply "Yes") or add to the existing list (reply "No"). It isn't hard! Also, it looks as if you haven't even calibrated properly yet: Throttle1=-16380,-512,512,16380/32 Throttle2=-16380,-512,512,16380/32 apart from the /32, indicating "no reverse zone", the rest are default values, set by FSUIPC as a starting point only. Pete

You evidently misunderstand. Clear air turbulence can occur with no cloud. That shows up in the wind layer you are in, as is clear from the log. Use Weatherset2 to read the actual weather FSUIPC is not incompatible with any weather program. It reads the weather direct from FS no matter how it is set. Weather options cannot change weather already set, only weather which is set subsequently, and only weather set through FSUIPC. I don't remember. Are you using FS9 or FSX? If FS9 then most programs will be setting weather through FSUIPC. In FSX most set it directly sing SimConnect, so then the options don't apply. If you want to suppress turbulence I suggest you do that before you even start ActiveSky, or perhaps do it IN ActiveSky. Pete