Pete Dowson

Ouch. Just two weeks ago I purchased a new system, much faster than my now 3 year old one, and it too came with Win10-64. I had no end of trouble. Three of my own hardware drivers (not using Lua) kept crashing -- one right at the start, during initialisation. On top of that Prepar3D behaved really bad, sometimes taking 20 seconds to fill in textures even though it was a view seen only a few seconds before. Oddly FSX-SE was fine. Several of my non-FS related programs crashed periodically, ones which I'd been using reliably for years. I would have ordered it with Win7 installed, but it wasn't an option from that supplier. I tried to start again, installing Win7 Pro from scratch, but turned out to be impossible without some obscure BIOS changes. The supplier tried to help me in this, but failed, and in any case they said they didn't advise Win7 on that PC and couldn't support me if I changed. So I returned that one and got my money back and purchased one with an almost identical specification, from a different supplier who did offer it with Win7 or Win10, buyer's choice. That PC is now all set up and performing excellently with no problems at all! So, with all or any events? With no events outstanding the lua thread would terminate, so any outstanding event will keep it running. FSUIPC tries to terminate it tidily, but that depends a lot on what the lua program has set up in the way of connections. After it has flagged te closure to the lua interpreter, if the thread hasn't terminated itself within a certain time, it is closed forcibly, in the same manner as Task Manager does when you use it to end a process. One thing I always need in any support request is missing in your report: the version number of FSUIPC. Why remove the startup lines in the Logs? They are important for version numbers, environment and set up. What sort of hardware? What sort of interface to it? Do you only mean regular USB joystick type devices, or somnething more complex? Depending on what version of FSUIPC you are using (make sure you are up to date) you can try the following: 1. Increase the TimeForLuaClosing value in the FSUIPC4.INI file. It defaults to 1 (second). 2. Try to detect closing using the event.terminate function, and use that to tidy up and do an ipc.exit(). 3. Add these lines to the INI file [General] section to get extra logging of the termination sequencing in FSUIPC: Debug=Please LogExtras=x4 That might give a clearer indication of the stage things are crashing, but since the crash is in ntdll I don't hold out a lot of help. Even with a debugger, whenever I've had any crash in that it is so far nested down in heaps of calls from things I don't even use and am completely unfamiliar with that it's impossible to get anywhere. Quite honestly, I think Windows 10 is simply incompatible with too many useful programs. I'm sticking to Windows 7, the best platform MS ever did. Pete

Hmm. It sounds like SimConnect is using the normal user ID for the MP aircraft and not sending me an update with the new local ID. (I wish IDs would stay the same for the one local user ID). I don't think that'll make any difference. The data is obtained by FSUIPC from the sim it is running in. I'd check into it, but I can't with P3D 3.2. That's too much out of date. Any reason you've not moved on to 3.4? 3.4.14 is the current one. It might be a bug which is fixed. Meanwhile, try this test version of FSUIPC, FSUIPC4958f.zip This one logs the User ID it receives, and does actually use it now. Previously (at least since version 4.10) it seemed better to default the user ID. Check the log. See if you get a different User ID logged anywhere. The first one, when you start up, will be 1 I think, always, logged like this: User Aircraft ID 1 supplied, now being used If it still doesn't work, try forcing FSUIPC to re-connect to SimConnect after you switch to MP. Youcan do that with a keypress or button assigned to the control in the drop-down assignments list called "Re-simconnect". Pete

Changes to FSX or P3D do not affect anything WidFS does. The logs show that broadcasts are not getting through. Check that your Windows workgroup name is the same on both PCs. Broadcasts stay in one workgroup. Alternatively, if you prefer to have two different workgroups, you need to add the ServerName or ServerIPaddr and the protocol parameters to the WideClient.INI, as instructed in the user guide (in the section with the red text heading asking everyone to read it!) Pete

Sorry, I only meant you to run it to see if it found a valid AFD BGL file. You need to point the program to your SCENERY.CFG file so it can scan the actual scenery folders! There is nothing to do wrong running MakeRunways. If it finds valid airport files it will include the data. If it doesn't, it cannot. It is that simple! It cannot invent data out of thin air. If it isn't including airports you think you've added then those BGL files do not include usable airport data files. Pete

Sorry, I'm lost. The displayed values are the values for the aircraft, right? So what is wrong? FSUIPC simply reads the values it gets direct from SimConnect, using the user aircraft ID. Are you saying it is providing the values for someone else's aircraft? Pete

So this GPS panel uses the FSUIPC interface, it isn't another FS gauge like most? I'd check that again if I were you. I thought Reality XP made their own interfaces into FS. Pete

In that case there are no BGL files in that folder being recognised as AFD (Airport Facilities Data) files, or at least having some AFD content. Maybe the airports you think you've added are simply enhancements to the default ones, not changing runways, taxiways, gates and so on. In such cases they may not need an AFD BGL. Run something else to double-check if you doubt this. Something like "Simple Airport Scanner" from www.scruffyduckscenery.co.uk . Pete

No offsets in FSUIPC are subject to any sort of locked access! The only offsets assigned to Lekseecon were 9000 to 93FF. Nico Kaan also has 8B00-8BFF for FSCONV, which I think is also something to do with the Level D. Pete

I don't know without information. There are log files produced to help. They are always needed! WideServer.log at the Server end (in the Modules folder) and Wideclient.log at the client end, in the same folder as WideClient. Pete

MakeRunways will only include scenery which is listed in the SCENERY.CFG file. If that "Physics P3D" program adds things there, or uses somewhere like the Addon Scenery folder to put generated BGLs into, then they'll be included. Whether you want to keep re-generating the database each time you change the SCENERY.CFG file is up to you. There's probably nothing wrong with just having everything in to make the database, because if you don't use and entry it doesn't really matter if it is there or not. Pete

They are command line parameters. So you need to make a short cut to start Makeunways with, then, in Properties of that short cut (right click for those), in the Shortcut tab, add a space after the Target pathname (not in the quotes) then />0 /Water. Put a space between the two parameters too. Then OK. When you then start it with the shortcut, the parameters will be seen. Pete

I don't think any Reality XP product uses FSUIPC, so not WideFS. Whether it would be okay with WidevieW I've no idea. Maybe you should ask Reality XP or the WidevieW support. There's no demo version, free or otherwise, for WideFS. An unregistered FSUIPC still provides the full interface for applications. That's the original part of FSUIPC and it has always been free for end users (since FS98). The registration enables the user facilities. WideFS is a different registration code. There's never a "need" for WideFS. It us a user's choice. But it is only any use with FSUIPC applications such as Radar Contact, Project Magenta, and older versions of Active Sky before it chnaged ot SimConnect. If you don't know if you can use it you probably can't. It tends to be used by cockpit builders. My own cockpit uses 7 networked PCs, all linked by WideFS to make all the displays and lights and switches work. Pete

No, WideFS is an network extension to the FSUIPC application interface. So PCs running WideFS (WideClient locally) will run applications which need FSUIPC will run just as if FS is running on the same PC. for bits of FS over a network you need WidevieW by Luciano Napolitano. Whether it does gauges or not these days I don't know. Mostly it is used for wide, er, views -- i.e the scenery spread out all round you. There's no "free" version of WideFS. I think your other questions are made redundant by the first two answers. Pete

Sorry, I don't know what L-M has planned. All I can do for each release of P3D is to track down the tables and allow the Lua functions to write to them. I've never had a use from the friction stuff myself and really I don't think I'd be able to tell whether changing them made a difference or not. I think you misunderstand. The friction tables are defined inside P3D code. All FSUIPC does is provide the address of them to the Lua functions. I didn't develop this friction modification business. Someone else was offering a patched version of the relevant FSX module (SIM1.DLL) with fixed changed friction tables. It is not good to distribute modified pieces of FS (and probably illegal anyway) so I offered to do it dynamically, at run time. I don't know anything else about the facility than you see. Pete

Check offset 3110 in the offsets list. There you write a parameter (first) in 3114 then the control number in 3110, and FSUIPC sends the control for you. This works with ANY control numbers. Pete

Okay. Looks like the latest P3D doesn't use these friction tables then. You could ask the question over in the L-M forum. Pete

You need to state the actual version number. Folks frequently say "latest version" when in fact they mean the latest one they noticed or downloaded. Look in the FSUIPC4.LOG file, in the Modules folder. Not far from the beginning you should see this group of lines, referring to interface hooks and links into P3D: ------------------------------------------------------------------- ------ Setting the hooks and direct calls into the simulator ------ --- CONTROLS timer memory location obtained ok --- SIM1 Frictions access gained --- FS Controls Table located ok --- Installed Mouse Macro hooks ok. --- Wind smoothing fix is installed --- SimConnect intercept for texts and menus installed ok --- All links okay (except older global weather setting method) ------------------------------------------------------------------- The important one for the frictions is that third line. Is it there, exactly like that? If so then the problem is in P3D, if not then the problem is that you have the wrong version of FSUIPC, not one specifically updated for P3D 3.4.14. Pete

FSUIPC doesn't create the files. It writes nothing itself at all. All it does is call the exact same facility in FS/P3D that your manual saving does, just supplying the filename and description. It's a SimConnect facility. I think you should report your problem to both PMDG and L-M, because it sounds like an issue that needs resolving between them. Pete

The download and licence are not connected. Just download the latest version and install it. You are expected to d this anyway to keep up to date. The licence data is the same as before. If you've lost it you can get it in your SimMarket account. Pete

There is no such message in WideClient. Why did you look in the ZIP file for a LOG file? You have installed WideClient into a folder of your choice, have you not? If not then it can't run in any case. If you have, did you edit the INI to address your Server, or have you made sure both PCs are in the same Workgroup? Pete

ProATC/X has its own excellent support forum. If you have problems with that program it would really be best to ask there. Pete

The log is produced when you run WideClient.exe and is placed it the same folder. It isn't in the ZIP file. The ZIP file is how WideClient in supplied. A log is not supplied because it reflects what happens when you run the program! The Server logs just indicate that the server is working and waiting for the Client to respond. If you cannot show me the run time log then it sounds like you have not run WideClient, as it always makes a log. You'll need to explain exactly what you mean by this: Pete

The client part of WideFS is WideClient.exe. The logs to diagnose problems are WideServer.Log and WideClient.log. It's no use giving me stuff relating to FSUIPC. Please read the WideFS user guide. Pete

The 4.958a version which had a specific change for a specific request was supplied only to the person who requested it. 4.958 IS the current version and the one yuou should use. I've no idea where you got the idea of 4.958a -- how did you get such a reference and link? The current interim version which again has only gone to specific persons for testing and feedback is actually 4.958d. There may be more before 4.959. Please only use the currently supported version, as stated, unless you have a specific prroblem I need to fix for you and for you to test the solution. FSX-SE has not changed for months and no changes have been necessary in FSUIPC to support an unchanging sim. Most of the changes since the last release of FSX-SE have been for trhe many Prepar3D updates, and also to add some features asked for by users. The "Changes" and "History" documents you have with 4.958 will tell you of all the changes. Please do believe the statements where it tells yo clearly whch versions of FS and P3D are supported. I don't understand why you are doubting so much! :-( Pete

FSUIPC and its registration don't care about the machine or the operating system. The key never changes. It belongs to you and you can use it on any PC you own and with any operating system. If it says it isn't valid it is because you have something wrong. ALL THREE PARTS, name, email and key, must be exactly as originally registered. Pete