Pete Dowson

So, what would you suggest? And is this new? What about on P3D4 (I did ask!)? Pete

You server or browser must have cached the file from before, as it is defintely updated. Try clearing the cache. How that's done varies according to brower. Pete

You'd think a problem like that would affect P3D4 as well. Does it? I used to have lots of problems with cheaper end USB-Serial adapters. My PFC equipment (and my GS28R VFR cockpit) depends on good RS232 comms. I found Brainboxes to be the best make for sheer reliability and not hanging during transfers. Some others seem to hang as soon as you let their FIFO buffer fill. Brainboxes do PCI and PCI-E cards, avoiding USB altogether, and also, more recently, two different USB adapters -- one high capacilty one with a really big FIFO buffer. Expensive though, compared to the dirt cheap ones. Pete

Thanks for letting us know. Pete

And do the two computers belong to the same Workgroup? Both running Win10? You were supposed to read the "must read" sectin of the User Guide first. Did you? Ifnot look for this, about page 4 I think: Configure your Network IT IS IMPORTANT FOR ALL USERS TO READ AT LEAST PART OF THIS! Pete

More likely the fact that with a Cylinder setting the aircraft actually deleted might not be the one in front of you. With 5000 feet altitude it could be above, below, to the side or behind you. It should be the nearest, but that might not be the one you can see! Really the cylinder option is rather, er, esoteric. It was added by request, but personally I don't see much use for it. Without that set the Zapper operates on the nearest aircraft in front of you within range (and within quite a narrow angle). The other thing really odd with the user settings is that range of 25 nm. AI aircraft aren't even visible (not visualised) at that range, so why would you want to ZAP an aircraft so far away? The default values were arived at through a lot of experience with trying to acoid problems with things like landing and taxiing blockages. Best to start with those defaults, and certainly to test with those values if you are in doubt that it works. BTW the "firework" sound (or whatever is assigned) means success in detecting and deleting a suitable aircraft. It isn't sounded if there's no such aircraft to be deleted. Pete

Where are you looking? The package is PFChid.zip, not explicitly PFChid64.dll nor does it bear the version number. When you download the ZIP it contains both the 32-bit and 64-bit versions plus documentation. Whether you download from FSUIPC.com or from the Download Links subforum above, you get the same file and it most definitely contains PFChid64.dll version 5.1.3. Pete

Ah. That log is clearer and actually shows that FSUIPC is not terminating at all. The Log shows it is hanging "Closing devices". So, try without the Arduino and the VRI devices. Some software driver associated which one or the other is not terminating. (The other devices look pretty innocuous). Pete

Just to add to this, in case it helps. When this sort of thing occurs, with possibly only one of FSUIPC's many threads not terminating, it is nearly always down to some driver or other which has been used by a plug-in and has hung, simply not returning. Since FSUIPC thinks it has successfuly closed everything such eventualities are not only difficult to diagnose, but impossible (as far as i can see) to program against. Lua threads which are created by FSUIPC are forcibly terminated if they don't go quietly (in the same manneras terminating a hung process via Task Manager) but there's nothing to stop Lua-started DLLs creating subthreads which FSUIPC isn't aware of. I can only think that a process of elimination amongst the many parts of LINDA (which I've never been able to fathom) might get to the cause. Pete

I don't know how you've managed it, but you appear to be trying to use the DLL.XML method to load up both FSUIPC5 and FSUIPC6 into the one (unnamed!) simulator. I think you nneed to supply more details, like what you started with (P3D4 and FSUIPC5 installed perhaps), then what you actually did to get here. I think you need to provide your FSUIPC5 Install log and your FSUIPC6 log files too. Pete

Do you realise you have added to a thread which has been dead for nearly 4 (FOUR) years? Furthermore, after a quick look at your LOG, no it is NOT the same problem. If you want some expert attention to a problem here you should please construct your own thread with a suitable title. The title to this one in no way matches your problem, which simply shows that you have no proper SimConnect modules installed. Pete

Where are you looking -- how are you trying to get them? Does this involve FSUIPC at all? I'm afraid you have to give more details. Pete

There is no way to access most Menu options without visiting the menus. I can only do the same as you and look through the current list of controls provided. If there's nothing likely in the list of assignable controls in P3D itself, then FSUIPC produces a more complete up-to-date list, extracted from your copy of P3D, as a text file for your reference. Check the FSUIPC documents folder. Pete

Have you tried the latest version (see the Updated Modules thread in the Download Links subforum above)? Pete

Right. DLLStop is the procedure in FSUIPC (in all added SimConnect DLLs) which is called by the simulator when it is closing. without that notification FSUIPC cannot do any tidying up. No, it isn't even getting the notification. I think your P3D5 is not closing but crashing out. Check the Windows Event Viewer to see if there are any errors listed mentioning Prepar3D.exe. They'll be in the Windows Logs/Application section. Pete

So this Global Weather program uses FSUIPC, does it? Not SimConnect? Oh, so you are simply saying you cannot get WideFs working? Have you looked at the WideFs User Guide. There's a section which is essentia reading. It even highlights this in read. After that I need to see more information: * FSUIPC4.LOG from the P3D Modules folder * WideServer.LOG from the P3D Modules folder * WideClient.LOG from the folder on your client PC where you have WideClient. Pete

You need to download the update driver for P3Dv5. See http://FSUIPC.com Pete

Where's the log, please, showing this.as requested. I'm taking a little time off now, so it'll be later -- enought time for you to find the log, for sure! 😉 Pete

You've posted on a thread which has been dead for well over THREE years! You are lucky I saw it! And if you want help with something, then please do state what your problem is. You say "how do i find that out". What exactly do you want to find out? What is the actual problem? Pete

Okay, the new log you provided shows you registered okay. It also shows that you have your controllers enabled in P3D. If you intend to use FSUIPC for assignments you need to disable controllers in P3D. The INI file shows that, so far, you have assigned an axis to Flaps but have default calibration, with no detentes set. you've assigned the flaps to one of the levers on your Saitek Quadrant and you might find that conflicts with assignments in P3D. There's still no involvement of FSUIPC in yor reversers. in fact you've assigned nothing else at all, only the Flaps. Pete

Ah, so I need to chase Nat to get his version of the software updated, pronto! Yes, same here. Though I got so used to using a centre compromise over the last few years that now, using a captain or first officer view, depending where I'm sitting, I'm actually off a little without realising it! (I'll get used to it ...). Pete

I'm using them both here quite happily with FSUIPC6 on both P3D4 and P3D5. Are you sure it's not just a matter of different privilege levels? Check that you are running both P3D4 and P3D5 with the same "compatibility" settings (right click on the EXE or shortcut and choose properties - compatibilty. I forgot to set mine correctly originally and got simlar problems. If this isn't the problem i need to see your FSUIPC6.LOG file from the P3d5 run. Pete

Strange. No problem here with V4. Pete

I'm using TruView, which is NatVis's tailored version of Immersive Display Pro. the installation and screen was all done by Nat Crea. Currently Truview doesn't want to play with P3Dv5, so i can't move over yet. I thought it was to do with DX11 v DX12, but that should theoretically affect you too, with Immersive Pro. Are your views using P3D ViewGroups? Maybe it's to do with the changes of method (we used to use nVidia Surround instead, but since P3D4.5 ViewGroups has been better). Of course, with 3 flat screens Immersive Pro has not got a lot to do. The warping is mostly the compensation for the curvature on a curved screen. What exactly does Immersive Pro do for three flat screen projections? Pete

I'm not sure OneDrive has anything to do with it? I have that installed and running in the background too, and don't have problems. You don't point to any Addons folder. The installer finds the only correct Addons folder in any case. You point it to where you want FSUIPC installed. Mine is E:\FSUIPC, a folder i created specially as a common place for it for both P3D4 and P3D5. The needed XML file is created separately to the actual program installation folder and goes automatically to the P3D Add-Ons folder in your Documents. This is the way prescribed by L-M and being followed now by most add-on software providers. Pete