Pete Dowson

Yes. I probably forgot to ask Enrico to change that. Or maybe I did ask him and he forgot. Unfortunately I don't have access to it myself. The links on their mostly point to the files downloadable from the Download Links subforum here, which is always the best place to check. Pete

Yes, the threads dealing with setting the values in only activated by detectng a change in the input from the device. Not easy the way the architecture is, and I would have though hardly worth it. Surely there's really never a need to change the sync mode "on the fly"? If there is, why? I would reduce to idle on all axes before changing anything. Pete

It is as very bad idea indeed to have controllers enabled in P3D and assigned in FSUIPC. Choose one or the other! Assign axes in P3D not in FSUIPC if that's where you want buttons assigned. Otherwise DISABLE controllers altogether in P3D and use FSUIPC exclusively. Currently you have no buttons assigned in FSUIPC at all, so I can't help you with why they may not function. BTW, whilst your PFC devices look exactly the same as mine they are completely different. Yours are standard joystick devices, which must be supported by PFC or their retailers. They were wrong referring you to me! I've never had any such devices to test with and they do not use any driver software I provided specifically for PFC devices. Pete

The limiter is NOT enabled by default in any case. As the documentation tells you, you enable it by setting a non-zero limit, which you can do in the Sim on the Miscellaneous tab in FSUIPC Options, and disable it by setting 0 there. It is not necessary to edit the INI file at all Pete

Yes, of course. Pete

As far as the FSUIPC processing of requests is concerned it is MUCH more efficient to do all your requests in one Process call each cycle, and just match your cycle time to your typical frame rate, but no higher than needed by your application. 20 or 30 times per second should be easy with no performance impact for quite a huge number of variables. The time taken at both ends is in the changing of process and the queueing of messages in FS. You can see this if you use FSInterrogate to request are large area of the offsets. Try larger and larger with a higher and lower frequency. You'll see it takes a lot more variables than you think to impinges upon performance at all. Pete

No. They are different on different PCs, and are probably different if you reformat and reinstall Windows. I expect they can also change if you completely uninstall the device, so it removes all details from the registry and maybe INF files too. But otherwise they are the only sure way of keeping assignments the same if you disconnect and reconnect. Product GUIDs are not so useful because folks often have multiples of the same product. Yes, of course. Only back in FSUIPC3 times and before was it using the "joy" interface, which is much simpler. But that's where the use of Joystick IDs comes from. The DirectX methods also need to instance GUIDs to connect. So for compatibility I equate the one to the other. this was actually always done by Windows automatically (placing the Joystick ID alongside the GUID in the Registry) but it seems erratic with Win8 and Win10, especially it seems with Saitek devices. Pete Pete

Always test with a default aircraft. Many add-ons do their own thing. If there's no input from the device then FSUIPC can't do anything with it. What is this "reverse axis" in any case?. Where do you have that on the device? My PFC throttle quadrant just has the 6 levers. Are you using two of those? All the levers on mine were the same, just 6 axes you could assign to anything. I fly 737 so I have two throttles, two reversers, a speedbrake and a flaps assigned on mine (not in that order). It's controlled through my PFCFSX.DLL driver. From the fact that you've not mentioned PFCFSX I assume your device is some new USB connecting device which doesn't need my PFCFSX.DLL driver. Is that right? I know PFC were moving away from the old serial port based system to standard USB joystick control. Otherwise, if you are using PFCFSX, then it is just a matter of selecting the correct configuration in its own menu, and calibrating there. If it is a standard Windows-recognised Game Controller with 7 axes and the flaps INC/DEC lever, then I assume FS can see all of the levers and the switches?Can you see them all in Windows Game Controllers? Do they operate correctly there? I can help with FSUIPC and PFCFSX, but not with generic joystick devices I've never seen. I do software support (my my software), not hardware. So maybe you should explain in a lot more detail what you have, what you have tried, and what you are doing. Unfortunately I'm now away till Monday, so there will be a delay before any more replies. Pete

That's why I use them to tie up your assignments to the actual devices. The ID numbers themselves can change. Pete

Please update to 4.964 now. Why not try assigning them in the axis assignments? The FSUIPC User Guide might help! Pete

"Used to"? What did you change? The numbers is how FSUIPC identifies the devices in the Registry in order to get the GUID it needs to handle them. The letters are there so that if you move the devices around (unplug them and plug them in differently) it can keep track of them and not mess up all your assignments. The facility is called "JoyLetters", and you evidently enabled this facility else you'd have no letters! It is described in the User Guide. Pete

That all looks a lot better! ;-) Pete

Apart from the /16 (REV) those are just the defaults. You haven't actually calibrated the brakes. I have found you ALWAYS need more space at the released postion to ensure that the brakes are off even when using the rudder. There are numbered steps to good calibration given in the FSUIPC user guide. I suggest you follow them. Also your Rudder calibration is really wrong: That says one side you have full movement from -16384 to 0. But then the central area, which does nothing, goes from 0 all the way to 16253, which is your calibrated maximum deflection as well! So you only have rudder operation on one side, not the other! If you are actually managing to use a rudder set this strange way then it simply must mean you also have it assigned in the Sim, which could also easily explain your problem with the toe brakes. Go and actually cvheck that controllers are DISABLED in the sim! Then re-calibrate all your assigned axes properly, following the guidelines. Pete

What "rescan". I don't think reloading assignments necessarily does the whole works. To force a USB joystick rescan you'd normally need to pull one of then out of the PC or hub and plug it back in again. I'm not so sure about "messed up", but it still lists the same joysticks and their assignments, with GUIDs, so they are still in the Registry and will still be subject to FSUIPC's normal DirectInput requests. Does FSX still recognise them when FSUIPC doesn't? You are using probably the worst version of Windows ever for DirectInput devices. It has a predilection for losing them. I would strongly suggest you either return to Windows 7, which IMHO is still the best version ever, or update to Windows 10 which now seems to be a lot better behaved with devices. Also, I see you are two full versions of FSUIPC out of date. Please install 4.964 before coming back. Pete

Ah, I don't have any of those, but I see the problem you have. It's going to run out not only of memory very quickly, but probably also of available object handles. Overload your Sim in any way and you'll get a crash. it isn't specifically the number of AI. Well, I have both UK2000 and Aerosoft EGLL, and I currently use the Aerosoft one because it's quite significantly faster. Both are okay here with 100% traffic (in the sense they don't crash). I don't recall ever having a crash with AI except maybe long ago with some bad AI aircraft models -- with 100% you are more likely to pick up obscure ones which yo may not otherwise get. I'd check your AI aircraft files if I were you. Pete

Which Sim is this? I've never had such a crash and have tested the limiter all the time up to release with 100% on the FS/P3D slider. What sort of crash is it, in which module? I only reduced mine now, but to a level which still gives me most airlines, because I wanted to balance the mix better with what I have UT2 also doing. At Aerosoft Heathrow, before I started limiting, I was getting up to 600 total aircraft (not all on the airfield itself of course) within a short time of starting up. You can set different FS slider levels using FSUIPC controls. I'm pretty sure those work in P3D too. Pete

There should be virtually no performance impact as the deletions happen immediately as each aircraft is added, whether it is that one deleted or another (according to the settings etc). The only possible impact I know of depends on whether the memory used by the initial loading of the aircraft is regained immediately, later, or not at all. I cannot tell you that, but it is probably one of the first two. So far I've not noticed an increase in VAT usage just from raising the slider value, but that's something you'll need to see for yourself. Some folks say that traffic being injected into the Sim by UT2 or similar will cause a problem after deletions by re-injecting them, but I've not found that -- it seems to behave well. I have my FS/P3D slider set at about 60% with MT6 and the UT2 ones at 40% and 30% Pete

Why are you asking it to check anything? To check registrations you'd need to enter all your details first. If you are already registered you just click "Not Now" in the Registration options. Have you never run the Installer on an already registered installation before? It is ony saying it cannot check your registration because you've not pprovided the details to check against. The installer has not changed in this area since it was first provided, way back in early FS9 days -- the exception just being the change from the "Cancel" button to "Not now" which was less misleading. with "cancel" folks thought it meant cancelling te installation, not just the registration. Pete

Of course. You don't think CTDs are progrsammed in, on purpose, just to annoy people do you? There are so many variiations and possiiblities of systems and combinations of add-ons out there that no one, and I mean NO ONE, can guarantee that any program they supply will be free from problems. No, in fact most of those were NOT caused by FSUIPC at all. It is just that FSUIPC being so universally used is the first to get blame. You evidently fail to get to the end of the stories you read to get the proper solution. The ones you mentioned turned out to be out of date or corrupted COUATL or BGLMANX addons and were corrected by re-running Virtuali Add-on Manager. That is already the case. The Schiratti forum and the full Install here are the latest tested. The interim updates are listed separately and are just the DLLs with no installer. I am really cheesed off with folks first blaming FSUIPC then very often not bothering to go back to all the threads they spread this stuff onto to correct the issue. I don't thank you for joining in. I suggest you do rather more research because you come down on me with such heavy handed and incorrect accusations. Enough. Pete

Most toe brake levers are reversed. In other words, unless you REVErse them back before calibrating, they will be fully on until depressed and fully off only when pressed fully. Just check the REV button when calibrating. You must re-calibrate AFTER doing this. Well, as you didn't show the calibration lines from your INI file, only the axis assignments, I can't check. But if you've calibrated them correctly with REV checked and they are still operating in reverse, then maybe you have unusual toe brakes which actually operate the right way, so then you'd need to uncheck REV and calibrate again. Alternatively you may also have axes assigned in FS/P3D -- you should diasable controllers there is assigning in FSUIPC. Pete

You can add it if you like. I'll make it appear more magically in 4.964, releeased later today. There are some minor bugs in 4.963 in any case. Pete On the latter you can assign a key or button to the traffic contols implemented in FSUIPC long ago. For the FSUIPC limiter values you'd need to use an Offset control (Offset Word for the limit, Offset Byte for the other values) to change the values, or have a Lua plug-in to change the offsets for you. Pete

4.963 was not prone to CTDs either. You are in a thread talking about an interim test release, which you should ignore in any case if you are involved and not interested in trying what it offered. The modification in this interim version which had problems was fully tested and working perfectly on Windows 7. It was a bug in Windows 10. If you are saying freeze FSUIPC and not accede to any more requests from anyone, then I'm sorry, it isn't in my nature. If I did that I'd also not be able to correct any bugs folks find, like the Throttle Sync one found by Bob Scott which has been there since it was first added as a facility. By all means stay with whatever version suits you, but then just don't ask for support. I won't be offended, honest. I suppose you also refuse updates to FS/P3D, Windows and other programs you use in order to stay exactly with what you've got? Do you also never add anything new -- aircraft, sceneries, the like? They are all a big risk to your preserved stability. Just peruse the AVSIM forums. Pete

Did you delete the previous additions? You never need to do that! You can put them in manually, but download 4.964 instead and use that. It will be uploaded to the usual places within the hour. There are several bugs fixed. Pete

Don't use anything later than 4.963 on Win10 at all, until I release 4.964. I've had to revert back to the older joystick scanning. The new one, which looks so good on Win7, is simply using broken facilities on Win10. Maybe I'll try again in 6 months or a year in the hope that MS will fix it. 4.964 will be 4.963 with a couple of other fixes, not relevant here. Pete

Okay, I saw that you'd posted your settings just after I answered here. I've already looked and answered. Basically, there's no Win10 or other similar problem to anything here. You are simply doing everything wrong in FSUIPC. I've explained what in the other thread. Pete