Pete Dowson

Nothing I now of. Here both "mouse look" and the Pan View assignment operate pretty much the same as they do using the FS facilities. In fact they were specifically adjusted to be similar. It's entirely your choice. Note that FS's mouse look facility only works if controllers are enabled in FS. That is why I implemented the same facility in FSUIPC. As described in the Advanced User's guide, you set "PollInterval" in the main [Axes] section of the INI file to a smaller number -- the value is the number of milliseconds between polls. In the [buttons] section it controls button polling, in the [Axes] section it controls axis polling. So a value of 10 gives 100 checks per second. Also you need to make sure the Delta value in the axis assignment page is set to 1 for the assigned axis -- it should be that by default for a POV Hat. The "Direct to FSUIPC" option only gives you access to those axes which FSUIPC can calibrate. The Pan View control is an FS control, so only available in the FS assignments list. Pete

You probably need to go someplace where folks understand OpenCockpits software. Don't they have a support forum? Else you could try MCockpits forums: http://www.mycockpit.org/forums/ Pete

You can increase the joystick scanning speed, but that has other effects too. I don't understand why you see any difference, it is pretty much identical here. FS actually scans joysticks slower than FSUIPC, but FSUIPC has higher overheads (it has to send stuff via SimConnect). Pete

Just Google error 740 (see below). Seems you aren't running everything at the same privilege level! Best to run everything normally. If you must use "Run as Administrator" you must run everything "as administrator"! Pete

JoyNames is nothing to do with Profiles, it is part of the way FSUIPC keeps track of devices, that's all. The Profiles facility is simply one way of keeping different assignments and/or calibrations for different aircraft, so only sections appertaining to those things will get separated once you opt to use the separate folder. Pete

There's something wrong, then, because there's nothing in any version with any SIM which can stop the menu opening if it it present. 4.936 was released ealier today. Pete

Of course not. They are aimed differently. Always were -- PS/2 and Aerowinx. I ran PS/2 alongside FS in the old days. There's a lot of difference when things go abnormal. This is why I don't use PMDG but a combination of Project Magenta and TSR and my own systems software to make my cockpit as realistic as possible in pretty much all circumstances. And projects like ProSim were actually built from the system flow side of things upwards, not from the top down. All I'm saying is that there is the wherewithall to do it as good now AND have the graphics and scenery and weather and other lovely add-ons. I have no objection whatsoever to someone taking on such a development. It just won't be me. I don't want more work at my age (71 next week), but less. It's time i actually used my simulator and finished my model railway .... and go on more overseas steam train trips, of course! ;-) Regards Pete

Hi Reinhard, I think you missed the entire point of my message. You didn't follow the thread at all? I was explaining to the OP what HE would see! I don't even have FA installed on this, my test PC! I was merely showing him that the line he is using would never actually try to load FSX, but simply give an error message in the Log instead! Pete

"Install controls"? Do you mean assign buttons? If you cannot "install controls" how do you test the controls which are not "installed"? Have you referred to the user guide? If you have installed FSUIPC4 okay (your first message appeared as if you couldn't even install the program!), then, every time you run FSX, a Log file, called FSUIPC4.LOG, will be created in your FSX Modules folder. Please find that, and the FSUIPC4.INI file, and paste the text from both into a message here -- use the <> button above the edit area to contain them. And please actuaslly explain what you are doing. I don't even know what you mean by "install controls". Pete

Sorry, no way can I take on more work. It's bad enough still having to develop FSUIPC for Prepar3D after all these years! I'm sure there are others out there who'll take it on if that sim is popular. I remember when I had it (or was it PS/2 back then?), someone did an interface to it for FS, so you could combine its faithful cockpit programming with FS's external graphics. Now with the likes of really sophisticated and accurate cockpit renditions that PMDG produce, and of course the cockpit builder's software such as ProSim, SimAvionics and Project Magenta, I thing Aerowinx and PS/2 resurrections will really not be so much needed. Maybe you should ask the chap who did the FSUIPC type interface for X-Plane? Anyway, all of PFC's new hardware is standard USB stuff, so new/revised sims that support actual joysticks should be okay this it. Regards Pete

All the conditions work only with unsigned integers. All the >0 test would do is check if it is not zero. If that is not what you want, then your only alternative is to use a Lua plug-in to do what you want. The plug-in system was added precisely for this reason, to allow folks to do things I hadn't thought of without me constantly adding more and more facilities into FSUIPC itself. Regards Pete

No, I see that. But I have just put your exact line into my INI file (just changing C:\ into E:\ because my FSX is in E:\FSX) and ran FSX, and all I get is this error logged in the FSUIPC Log file: 3869 FSUIPC couldn't run: "E:\FSX\FSX Fiber Accelerator\FSX Fiber Accelerator.exe" [Error=267] Error 267 is something like path or file not found. If your quotes were the real ones, then either your version of Windows is way different from mine (Win7 64-bit, fully updated), or there's something else rather spooky going on. Maybe some program had replaced the Fiber Accelerator.exe in that folder with a renamed FSX.EXE, though that seems very unlikely. Too late to do any checking like that now, in any case. Thanks. It seems there's nothing that can be done. If I were over with you at the time, maybe we could have gotten to the bottom of the matter. Thanks again, Pete

I've seen folks say this, but I've also seen folks say the opposite. I nkow of no reason why FSUIPC assignment would fix any Win8 problem, though. Have you calibrated in Windows first? Did you calibrate in FSUIPC? This action is almost always a result of the device being categorised in the Registry as a "digital" control rather than "analogue". You might need to go to a Thrustmaster support website for an answer -- it will likely be a Registry patch. Pete

Why are you running FSX in Windowed mode in any case? I don't see a difference where the mouse cursor is in full screen mode, and the latter has always been faster for me as well. Anyway, to answer your question, there is already an FSUIPC control to hide the mouse pointer: "mouse pointer toggle". Having the mouse moved automatically is generally not a good idea because it is used for virtual cockpit viewing and that operates relative to the last position as known by FS -- if something else moves it there could be confusion. If you do want to experiment doing your own thing with the mouse, the Lua plug-in system does offer full facilities in its Mouse library. Pete

But unless it's a bug in Windows, there is really no way the line Run1=CLOSE,"C:\FSX\FSX Fiber Accelerator\FSX Fiber Accelerator.exe" could start an entirely different EXE in a different folder, unless the "" were missing. With missing "" the line would read as running "C:\FSX\FSX", with parameter "Fiber Accelerator\FSX Fiber Accelerator.exe", which would indeed try to start FSX. Are you sure the " character you used is the standard ASCII ", the one above the 2 on a standard keyboard? If you were using WordPad or a Word processor, rather than a plain text editor like Notepad, it is possible that the quotes were those used in pairs by word processors. Here's my [Programs] section: RunIF1=READY,"E:\FSX\Modules\SismoAft.exe" RunIF2=CLOSE,HIDE,"E:\FSPS Fiber Accelerator\FSX Fiber Accelerator.exe" RunIF3="E:\FSX\pmSounds\pmsounds.exe" RunIF4=KILL,"E:\mcp\mcp.exe" RunIF5=KILL,"E:\mcp\pfcmcp.exe" RunIF6=KILL,"C:\Program Files (x86)\HiFi\ASNext_FSX\ASNext.exe" RunIF7=CLOSE,"D:\OpusFSX\FSXSERVER.EXE" Now if Windows was stopping at the first space, as it would have had to in your examples, then my Fiber Accelerator would not start -- it would try to run "E:\FSPS.exe" instead, and similarly my ASN would not start, as it would try "C:\Program.Exe" instead. This would certainly happen if the "" used were not recognised as such. Regards Pete

No, nothing noticeable at all. Pete

If you were using the joystick lettering already, then the same INI file from the FSX Modules folder should still work okay. But then, if you weren't using your original INI file I don't understand how things got crossed because you would have had no existing assignments to get crossed! Obviously I am misunderstanding your original report! Pete

Sorry, I don't understand. Are you saying you are using a PFC quadrant WITHOUT installing and configuring PFCFSX.DLL? If so it must be some new version of their quadrant, because the only one i know about is a serial device, possibly with a USB adaption (but looking like a COMn device in Windows) which needs PFCFSX.DLL as its FSX/PFC driver If it is a pure USB device and looks like that in Windows then your problem certainly isn't anything to do with my software, so please ignore what I said before. Pete

Okay. It's an access violation in the PMDG module identified. You need to report this problem to PMDG because the crash is actually in their DLL. Maybe you could try uninstalling and re-installing the 737NGX first, because it could be a corruption, but if it is a bug then only they can track it because they have the source code and can pin-point the position of the error in their DLL from the information above. I suspect the fact that it only crashes when FSUIPC is setup just so is to do with memory patterns or timing. This is often the way with some bugs, especially those involving unintentionally using uninitialised variables. But without something actually wrong with PMDG_737NGX.DLL (maybe only your copy, through corruption), there's no way anything in FSUIPC can cause that DLL to crash. Pete

An unregistered FSUIPC is not reading the joystick buttons nor axes, but a registered one, whilst reading them IF assigned, will not do anything with buttons if not pressed, and will not produce keyboard characters unless programmed to. So it sounds like you have something assigned badly in your FSUIPC INI file! Pete

If FSUIPC's log reaching the exact same point? Have you any information about the crash. If it's a normal WQindows reported crash there will be module name and offset details, and an error code. Try looking at the Windows event viewer, application logs. There will be a record, with details, of each crash. Also, it does sound rather like some other corruption in that Flight file. Try creating a new one. Pete

Okay. This points to a corrupted weather file, probably associated with flight KTNT.FLT. There are two crucial weather files which are used by SimConnect as soon as FSUIPC starts asking for weather data -- the WX file associated with the flight being loaded, and WXStationList.BIN. The WX files are stored next to your FLT files, usually in your FSX documents folder, and the WXStationList.BIN file is in the same folder as your FSX.CFG file. I suggest you delete both. The BIN file will be rebuilt by FSX, and the WX file won't matter if you are using a weather program or some other weather source and don't need the weather saved with the flight. You might also delete the WX file associated with the default flight (D:\FSX\FLIGHTS\OTHER\FLTSIM.WX), although I doubt that this is at fault. Pete

Since this is a subject which may well interest others, I've split the solution part of this thread and placed it into the User Contributions subforum, here: http://forum.simflight.com/topic/77525-updating-radio-frequencies-for-wideview-network/ Pete

Actually 59999 is +12.4 not -12.4, meaning it was on the bounce up off the runway at the time it was recorded. You must read that offset as a SIGNED value. 4294967036 is actually hexadecimal FFFFFEFC which is the 32-bit representation of decimal -260. Using that will give you the -199.92 value. Pete

I'm afraid I cannot make head nor tail of your message. If you have an install problem it is likely that your Registry is not correctly pointing to the FSX or P3D location. I need to see the Install log produced by the FSUIPC installer. Paste in into a message here -- use the <> button above the edit area to eclose the text from the file. In case you cannot find the log file, just save the log from the screen copy of the log by using the entry in its File menu. Pete