Pete Dowson

No, you have it wrong. There were certain crashes in G3D.DLL which were common in FSX (and earlier versions of P3D too!) which I found a way to prevent. But just that. When FSX-SE came out, the same problem occurred in the same place, and I handled that too. There was a common TERRAIN.DLL crash which I tried to handle, but failed. A few weeks ago DoveTail released a Public Beta version of FSX-SE (build 62610) which actaully fixed pretty much all of the well known G3D and TERRAIN crashes. That Beta was withdrawn recently, and since then there have been other internal Betas. The end result, very soon I expect, will be an excellent FSX-SE release with all these fixed. Patience is key here. They need to make sure they are not introducing more and potentially worse bugs! No, I cannot determine things like that. I do not have any sources of FSX, and i am not part of Microsoft nor Dovetail. I've never heard of a crash in UTIL.DLL before. I suggest you most urgently report this to DoveTail through the proper reporting channels (their forum in Steam, I suppose), so it gets looked at! Pete

Shame. Most PC suppliers are still offering Windows 7 as an option rather than Win 8 -- after all, it is still a valid O/S and can be purchased everywhere.. I'm using Win7 and WinXP, the two best operating systems MS every produced. Folks are hoping Win10 will fix things, and that's a free update from either Win7 or Win8 as far as I understand. Pete

Really? That's awful. something is very wrong there! I can't really say. It certainly won't just by purchasing it. You'd probably have to at least assign the axes in FSUIPC, disabling controllers in FS. But without knowing why you get this odd thing happening, I couldn't say if it would help or not. Have you asked CH? One thing that may possibly help when assigning in FSUIPC rather than FS is that it will tend to pick up re-connected joystick devices, maybe automatically, but definitely when visiting it's axis assignments pages -- it re-scans them then. Maybe that would save you having to reload FS, but i don't know if it could help further. Pete

Sorry, I don't know how you are logging it there? That's the FS message window, I think? Doesn't it get defined in the FS/P3D CFG file someplace? Easiest would be via a little Lua plug-in with its own display. They are sizeable and positionable. Or best on a separate PC via WideFS. Here's the one I use, which runs under WideClient and shows frame rate and VAS free. You'll need to set the window position and size in the wn.opn function (the four numbers are x,y,cx,cy): w = wnd.open("VAS Monitor", WND_FIXED, 2455,1075,425,100) wnd.backcol(w, 0x000) wnd.textcol(w, 0x6c0) wnd.font(w, WND_ARIAL,-2) -- Update the display at 500 msec intervals (see event at end) function mytimer(time) wnd.clear(w) fr = ipc.readUW(0x0274) if fr ~= 0 then fr = 32768/fr end fr = math.floor((fr * 10) + 0.5)/10 mem = ipc.readUD(0x024C) memmb = math.floor((mem/1024) + 0.5) wnd.text(w, "Frame Rate " .. fr .. " fps\nVAS free " .. memmb .. " Mb") end -- Adjust timing to taste: 500 = 1/2 second event.timer(500, "mytimer") Regards Pete

Problem? Or simply measuring different things? FSUIPC simply keeps that value updated from the identical value (02C8), fed continuously frame-by-frame from FS, except when FS indicates that the aircraft is "on-ground". Maybe it is the Wilco one which is wrong, or maybe, because it is their aircraft, they know more precisely when the rubber on the tyres skim the surface (and thus start spinning) more accurately than FS does in deciding it is "on the ground". Maybe the FS one needs the actual gear compression to start. Or maybe it's vice versa? Who knows which point is the most precise, and is there really just one answer? If there's a bounce sufficient to make FS decide it isn't on the ground again then the offset might be updated further, but I do have a delay inbuilt (at least in FSUIPC4, not sure about FSUIPC3) which should prevent that, except possibly for giant leaps! ;-) Pete

It was because new posters have their first thread held for Approval by a moderator. Okay. But for future reference please note that MakeRunways is not part of FSX or P3D and cannot influence what those programs show in their menus. If you ever have a discrepancy in the Aircraft or Airport selection menus in FS or P3D you need to look at the add-on you installed and are expecting to see! MakeRunways is just a utility to extract information about correctly installed scenery, for use elsewhere, NOT within FS itself! Pete

This seems to be pretty much identical to another thread with a different title! Please note that this is the Support Forum for FSUIPC, WideFS and my other programs, yes, including MakeRunways. But it is not the support forum for Aerosoft scenery! So, sorry, seems there are two threads posted in the wrong place? Pete

If it isn't in the P3D selection menu, and not in the MakeRunways lists, then it is not defined correctly in the Scenery. So you need to go to the support forum for that product, right? Not sure why you'd report it here? Pete

Are you using FSUIPC's application interface with something you've programmed and which is now being marketed? If so please email me (petedowson@btconnect.com) and we will discuss it. I shall need some details. If you mean the use of FSUIPC as any user might use it, with a normal paid-up licence from SimMarket, there is no other requirement. Pete

I don't know of an NMEA program for FSX. The GPSout facility built into FSUIPC does provide NMEA output, to a serial port. Is that what you are thinking of? Pete

There's no "default profile" -- I assume you mean default settings, which of course are outside any Profile. Default settings apply to aspects of an aircraft's assignments which aren't overridden by Profile entries --axes and calibrations are overridden if there are relevant applicable profile settings, KeyPresses and Buttons are only overridden where the same keypresses and buttons are assigned in the profile. This latter allows common switches and operations to e programmed for all aircraft with certain keypresses and buttons specific to Profile aircraft. Pete

Did you look at the log? See: 88281 *** LUA Error: ...X\steamapps\common\FSX\Modules\linda/system/init.lua:29: module 'linda/libs/._lib-fallback' not found: no field package.preload['linda/libs/._lib-fallback']linda/libs/._lib-fallback no file 'C:\FSX\steamapps\common\FSX\modules\linda/libs/\_lib-fallback.lua' no file 'C:\FSX\steamapps\common\FSX\modules\linda/libs/\_lib-fallback\init.lua' no file 'C:\FSX\steamapps\common\FSX\modules\lua\linda/libs/\_lib-fallback.lua' no file 'C:\FSX\steamapps\common\FSX\modules\lua\linda/libs/\_lib-fallback\init.lua' no file 'C:\FSX\steamapps\common\FSX\modules\lua\linda/libs/\_lib-fallback.dll' no file 'C:\FSX\steamapps\common\FSX\modules\lua\loadall.dll' no file 'C:\FSX\steamapps\common\FSX\modules\lua\linda/libs/.dll' no file 'C:\FSX\steamapps\common\FSX\modules\lua\loadall.dll' I don't know Linda at all, never used it and cannot support it, but it looks to be like you are missing most of it! Isn't there support for Linda somewhere? Pete

Assignments, you mean? Have you tried simply deleting them? Joystick axis assignments and calibrations made for a Profile replace all those made outside the Profile, so there is no problem there. So I assume you mean button assignments? There again, if you assign them to something else in a Profile, the non-Profile assignment for the same buttons will be ignored. The only buttons and keys which will be active in your profile are those assigned IN your profile, plus those assigned outside the profile but not in it. In other words, there's never any clash or problem with using a profile and leaving old assignments alone. However, if you really must delete default (non-profile) button assignments, you need to: 1. Go to the FSUIPC Options, Buttons & Switches tab, 2. Make sure the 'Profile-specific' tick is clear -- click on the option if not to remove the tick and let the dialogue show non-profile assignments, 3. Press the button you want to un-assign 4. Click on the Clear button below the assignment(s) 5. OK, done. Pete

What's being multithreaded? Serial ports are serial devices. The output to them is serialised. There's no way it can "get mingled up". But in any case, surely you aren't using three separate Lua plug-ins, one for each light? You only need the one, with three events. Events can't interrupt the flow, pendng ones will queue till your processing is done. This sort of thing is actually quicker to try than worry about questioning. Haven't you tried? Pete

It's a bit pointless posting pictures. The INI file tells the correct story. But as you can see, NONE of those axes are processed, not even for Engine 1, so why bother checking the "map 1->234" option? So, how are you assigning your throttle (where, and to what?), because it isn't to any of the Axis throttleN set, ThrottleN or ThrottleN set controls. You haven't even bothered pressing a SET button in order to calibrate either. "Normal defaults" are for all the other options. There's no such thing as "normal defaults" for assignments and calibrations. If you don't want FSUIPC to do any of that it is easiest simply to delete the FSUIPC4.INI file before running FS. Pete

If you know the <name> of the profile, just find and delete the complete sections with the titles [Profile.<name>] [Axes.<name>] [buttons.<name>] [JoystickCalibration.<name>] [Keys.<name>] [Auto.<name>] Or, if you are using Profiles=Files, delete just [Profile.<name>] in the INI and the <name>.ini file in the Profiles subfolder. To merely remove a specific aircraft from a profile, just delete its entry in the [Profile.<name>] section. Pete Pete

Sorry, I don't understand -- you want to delete assignments in FSUIPC? Have you tried? Pete

This is nothing to do with FSUIPC. The module "xuipc.dll" is a regular part of FSX and is not in any way I know related to anything FSUIPC does. I've never even heard of a crash in that module, but you might want to go and search in the AVSIM FSX CTD forum to see if anyone else has experienced this. Pete

That's one trouble with using more realistic simulations -- you need to understand more about what is going on! I get similarly misled myself too sometimes! Pete

Are you using some sort of Migration tool? Please try FSUIPC 4.939g, the current version, as I made some changes to the installer to try ot deal with some of the messes they seem to make. Pete

You can try using logging, there are lots of options -- see the Logging tab in FSUIPC's options. There's no need to mess in FSUIPC INI. But you need to know what you are looking for. I'm afraid I don't know SPAD and cannot support it myself. Isn't there a support place for it, or any documentation? Pete

The name of the Server, DON-PC is supplied by WideServer (inside FSUIPC) by a broadcast message. Then WideClient gets the IP address belonging to that name from Windows. So it is Windows, or more likely your DHCP server (likely your router) which is giving that incorrect IP address. There is a thread in the FAQ subforum about this sort of problem (look for the title "WideFS Server names translating into incorrect IP addresses". As one of suggestions thee says, try setting the correct address as the "ServerIPaddr" parameter in the Wideclient.INI file. Please also refer to the WideFS User Guide. There's a section in that which explains configuring your network and the options available. Pete

That's a bad migration tool! It should at least clean up its mess when it has finished. It makes the Registry point to your P3D installation for FSX, and also seems to put an FSX.EXE there (or renamed Prepar3D.exe), which makes the confusion even worse! The end result is: There is really no way a decent installer can untangle the sort of mess this is in! Your so-called "migration tool" should only do its fiddle temporarily, whilst you are using stupid installers which can't work things out correctly. Then the "migration tool" should put things back correctly so that normal well-written installers can find the right things in the right place! Okay. I think you should only "activate" the tool when installing things which don't understand what they are doing, then deactivate it afterwards for normal use. Pete

And what was your previous install version? I need to see the Install log to determine why that occurs. What version of FSX do you have installed? Sorry, what are you trying to install, then? I'm now confused. Do you ONLY have P3D, no FSX? Because the error you mention says that your registry points to an FSX installation. So, what is the problem? Please explain! don't you believe it? Oh, no! Not one of those horrible migration programs which renames the progeam so that FSUIPC and other programs can't even tell what is going on? When you say "it doesn't work" can you expand on that. What "doesn't work" about it? If FSUIPC running? Just paste contents of text files into your messages. Use the <> button above the edit area to enclose them. And the main file, for installation problems, is the install FSUIPC log file. I also suspect FDC can't work with a renamed P3D installation. You need to undo whatever your horrible migration tool is doing to mess everything up! Pete

It's ready earlier than I originally planned, version 4.939g will be released today (Sunday 22nd March). Pete