Pete Dowson

That is exactly why I suggest using cut-and-paste. Really? I've always used my real name on every forum I've ever joined, for many years. What problems do you expect me to get as a result? Regards Pete

Okay. There's either an installer download corruption (check as I stated), or one of the other problems exists. Have you checked the other points I mentioned in my last reply? Pete

No, there is no text. It looks like the timer event isn't operating. Check the last line in the Lua file you saved. Is it: event.timer(1000, "mytimer") If not then that's the reason. The dialogue is created, but never updated. In case you have difficulty copying the file from my post, I attach a Zipped up one here, called FayreDisplay.lua, for you to install instead. Regards Pete FayreDissplay.zip

Can you please tell me the actual version number of FSUIPC4? If you aren't using the 4.70 version installer, then please update and try again. Then, in the FSX Modules folder, find the Install log and paste its contents into a reply here. There are only a few possible reasons for a failed signature check:. First, if you look in the FAQ subforum you will find two separate threads which deal with this problem. You may well find the answer there. Generally, these are the possible reasons: 1. The DLL is in fact corrupted. If it came from an installer with a good signature, this is impossible. So check the signature on the Installer EXE file. Right click, select Properties, then Digital Signature, then select the one shown and then "Details". It should say that the signature is okay. If not, then either that file is corrupted (so download another) or one of the next two reasons applies. 2. The signatory is listed as an "untrusted publisher". The signatory is simFlight GmbH these days (my own signature expired and these days individuals are not allowed them, you have to be a registered company). You can check trusted and untrusted publishers in Internet Explorer. 3. You have some services in Windows missing. Most likely the cryptographic one, which is needed to decode and check signatures. Some folks stop assorted services in the belief this makes FS run faster, but some are still essential although not looking so. If you've not stopped any and the correct services are running it may be that they are corrupted in some way, in which case a Windows repair or re-install may be needed. 4. Some times a registry setting gets changed by one installer which seems somehow to change your protection features to such a high level that no new signatures are accepted. I've not been able to reproduce anything like this, but there is help in one of the threads in the aforementioned FAQ subforum. Regards Pete

The title of the thread, which seems to date back to 2006, is FSUIPC error = 7 with a registered copy of FSUIPC in FS2002 How does FS2002 and that error number relate to whatever it is your talking about? Why have you appended your query to a 5 year old thread? Is is relevant? Without any useful information, like the actual version number of FSUIPC, the version of FS, and ideally the Install log, I can't really help, but I can point out that if a signature fails you either have a corrupt copy of FSUIPC or a corrupted installation of Windows -- one with the needed services not running. I strongly suggest you post in a new thread with a more appropriate title, and include some information. Then I may be able to help. However, first of all check that you are in fact trying to install a supported version of FSUIPC -- certainly no earlier than 3.99 for FS2002 or FS2004, or 4.70 for FSX and later. Regards Pete

If it isn't accepted it will because you are either getting it wrong, or because you aren't entering your name or email address correctly either. There's no point in sending me anything. I have them all here in any case. They are generated automatically in any case using the same algorithm as FSUIPC's installer uses to check them. Maybe you purchased a key for FSUIPC3 instead of FSUIPC4? [LATER] I can only guess because you don't use your real name here for some reason (I never understand why), but if you are Markus Wilhelm, the key is fine. You are making a mistake. Regards Pete

the units used in FS aren't often what you want to see. They are chosen for internal efficiency. If you want to know more, to add your own values, for instance, you'll need the list of offsets -- the documents describe the offset values and units used. The lists are in the FSUIPC SDK download. Regards Pete

Okay. All done. I've done it a different way -- not as a separate free-standing program, but as a Lua plug-in for WideClient. I think this is much more flexible, for all sorts of uses, and easier for adapting as the source is readily changeable. You'll need to update to version 6.895, from the Download Links subforum. I've added a new library to the WideClient lua package, featuring these functions: You don't need the last two for your application. Also, not that you'll need it, but you can have multiple displays in different places with different titles and different entries. Here's the Lua plug-in code to match what you requested. I've included enough comments for you to make any changes you like. -- Create the display window for 8 values, position x=800, y=400 h = display.create("Jason Fayre Display", 8, 800, 400) -- Update the display at 1000 msec intervals (see event at end) function mytimer(time) -- display 1 = airspeed airspeed = math.floor((ipc.readSD(0x02BC) / 128) + 0.5) display.show(h, 1, "Airspeed " .. airspeed .. " knots") -- display 2 = altitude altitude = math.floor(((ipc.readDD(0x0570) * 3.28084) / (65536 * 65536)) + 0.5) display.show(h, 2, "Altitude " .. altitude .. " feet") -- display 3 = heading heading = math.floor(((ipc.readUD(0x0580) * 360) / (65536 * 65536)) + 0.5) display.show(h, 3, string.format("Headng %03d degrees", heading)) -- display 4 = vertical speed vertspeed = math.floor(((ipc.readSD(0x02C8) * 60 * 3.28084) / 256) + 0.5) display.show(h, 4, "Vertical speed " .. vertspeed .. " knots") -- display 5 = mach mach = math.floor((ipc.readUW(0x11c6) / 204.80) + 0.5) display.show(h, 5, string.format("Mach %1.2f", mach/100)) -- display 6 = Altimeter qnh = ipc.readUW(0x0330) / 16 hPa = math.floor(qnh + 0.5) inches = math.floor(((100 * qnh * 29.92) / 1013.2) + 0.5) display.show(h, 6, string.format("Altimeter %d hPa, %2.2f inches", hPa, inches/100)) -- display 7 = Radar Contact line 1 decode (waypoint) display.show(h, 7, RC1) -- display 8 = Radar Contact line 2 decode (runway) display.show(h, 8, RC2) end -- Adjust timing to taste: 1000 = 1 second event.timer(1000, "mytimer") Just save this as a type Lua file (e.g. FayreDisplay.lua) into the same folder as your wideclient.exe, and it will start automatically when FS is "ready to fly". This pic shows what it does, with rather fictitious values, though -- actually a result of extreme slewing! Oh, I've just noticed I've inserted "QNH" when I'm actually displaying the altimeter setting, not the actual QNH. I've changed the Lua code above, but the picture still shows QNH instead of Altimeter. Pete P.S. TABS do work okay.

I don't know what you mean by "key for the download". The download doesn't need a key. The keys for FSUIPC and WideFS registration are NOT 9 digits, but 12 characters! Also, all three parts must be entered EXACTLY as stated, name, email and key. Use cut and paste to avoid mistakes. As well as this, make sure you are installing a current version (4.70 or later), and that the date is set correctly on your PC. Pete

I'll add a link, thank you! You could ask the developers, though I think they have stopped development years ago. Also, if you mean to run on a separate PC, I think you can do that with both products already. No idea, sorry. I doubt very much that I'll get involved. I am getting too old now to start again, and I don't think it will be compatible in any way. Regards Pete

You posted this support query into the "User Contributions" subforum, where it is lucky i noticed it. I've moved it to the Support forum for you. Local variables, or L:Vars, can be written to using Macros, which can in turn be assigned to keys or buttons in the normal assignments dialogues. Please refer to the Advanced User's guide. You'll find the topic listed in the contents, under "Macro controls". Pete

Unfortunately the originally planned sequence of updates for SimConnect never happened. Aces was closed and that was that. Maybe Lockheed-Martin will develop SimConnect further in Prepar3D, but that doesn't really do normal FS users much good I'm afraid. Pete

I've added a Mouse Look facility in FSUIPC version 4.712. Please see the notes in the Download Links subforum. Regards Pete

Sorry, I think you have come to the wrong forum. I've never heard of any of the software you are talking about and nothing in any of my software will ever give any Assertion messages. They don't occur in the languages I use. I think you need to find the correct Support Forum for the software you are using. [LATER] Googling "Caiset" found answers in various places, mainly the Aerosoft support forum for the software you are using. It looks like the error you are talking about has been in that software since 2008 but there is a work-around. Regards Pete

Sorry, that is not a message which exists in FSUIPC. I think it must be referring to Error #6 in the interface software you are using, whatever that is. If it's the C code I wrote for the FSUIPC LIB you might be using, it's "FSUIPC_ERR_MAP", here: // create the file-mapping object m_hMap = CreateFileMapping( (HANDLE)0xFFFFFFFF, // use system paging file NULL, // security PAGE_READWRITE, // protection 0, MAX_SIZE+256, // size szName); // name if ((m_hMap == 0) || (GetLastError() == ERROR_ALREADY_EXISTS)) { *pdwResult = FSUIPC_ERR_MAP; FSUIPC_Close(); return FALSE; } But none of the code I wrote actually reports the error with that message, it simply returns the error code -- it must be your code doing it, or the library code of someone else that you are using. The source and all documentation for this is included in the FSUIPC SDK. You should be able to debug your program with the debugger included with your compiler. Regards Pete

There's no such thing as "local Zulu time". There's local time -- the time at your location -- and Zulu time (also known as GMT or UTC), which is the time at the Greenwich Meridian. There are offsets for both listed in the FSUIPC offsets lists. All the offsets for FS9 and before are listed in the Programmers Guide, and those for FSX and later in the FSUIPC4 Offsets Status document. Both documents are supplied as part of the FSUIPC SDK download. Regards Pete

Good. I'm glad you got it all sorted out! Pete

Yes, indeed. I find XML quite annoying. It looks to be a very flexible form of data definition, but the slightest error in its syntax causes things to go wrong. Seems to defeat the object to me. And it is very cumbersome compared to the simple INI / CFG file format. Glad you got it sorted so easily. Regards Pete

You should really do that in your weather program. Seems that the DLL.XML file has been destroyed or corrupted by something you installed. Not UT2 which is loaded via the EXE.XML file. It is more complex, but i don't think "finicky". The problems tend to arise from bad installers which mess crucial files up. Pasting is the best way anyway. It certainly sounds like that was the last time FSUIPC4 was actually loaded and run, then, because it will create a new log file each time. Either that or the date and time of your PC are set incorrectly. Of these: There's no such thing as "FSUIPC4.CFG". Don't you mean "FSUIPC4.INI"? That contains all your FSUIPC4 settings. Anyway, the log file shows everything was okay. All that is hapening now is that FSUIPC4 (and probably that LVLD.DLL) aren't being loaded, because the DLL.XML file is either deleted or corrupted. If you know where to find your FSX.CFG file, look in the same folder. You will see the EXE.XML file, which must be there as it loads UT2, and maybe a DLL.XML file. Rename or move the latter, so you don't lose it, and then re-run the FSUIPC4 Installer. It will make a new DLL.XML file. Run FSX and FSUIPC4 will run okay. But now any other DLL's you may have installed will not. So, paste the DLL.XML file you renamed or saved here so I can see what is wrong and help you fix it. Despite the filetype of XML it is an ordinary text file. If you don't know where to look for these files, paste the FSUIPC4 Install log here and I will tell you, as it will be logged therein. Regards Pete

Okay. I'll check when I get to do something about this. If it does, I'll maybe just use normal edit fields and simply ensure you can't accidentally change anything! ;-) Pete

It wouldn't fail, just produce an empty edit field -- or I could hide it if it was empty, if that makes your Braille converter easier to use. One thing, from what you said earlier: I've not checked this yet, but doesn't the default Windows dialogue method have TAB skip read-only fields? Pete

That's only the Client log. What about the Server? All connections have two ends. Information about what both are seeing is needed. So, at least Windows on the client knows the Server -- i assume that is the correct IP Address? Er, 7 seconds isn't long enough for the initial exchanges to occur. Why terminating it so abruptly? Pete

Not the waypoint data from RC then? I can't get the transition level from anywhere.-- FS only uses 18,000. I can provide two entries, one for airspeed the other for mach, or else have one and let you switch them with some keystroke. Maybe, but it would take me much longer in that case, to tart it up, as I'm generally pretty shy about showing my bad coding techniques and completely commentless obscure algorithms.. Bad habits -- comes of doing it for 47 years! I don't know when I'll be able to get to this. I'm pretty tied up for most of this coming week. Maybe the week after. I should certainly have time this month, at least. Regards Pete

If they are in the same workgroup, and both are running windows versions at least not before XP SP1, then you shouldn't need to add those parameters as the broadcast message from the server will tell the client where it is. There are log files produced by both Server and Client. Please check those. Show me them if you don't understand them. If it's a normal Cat5 Ethernet cable, it won't work. You'd need a crossover cable, for linking two PCs instead of PCs to a switch or router. And of course the IP addresses of the wired connection won't be the same as the wireless one -- you'd select the IP address in Wideclient.INI instead of the Server name, which would be ambiguous. That simply means there's no Initial.Lua file. Did you want some Lua plug-in loaded initially? If not, ignore the message. More important in the log is to see what link errors or reports there might be, not fuss over Lua plug-ins you may noyt even want. Regards Pete

you don't provide enough information. Are the computers in the same Workgroup? If not then broadcasting won't work, so, how have you configured WideFS? Please do first refer to the WideFS user guide, in particular the early part of the section on configuring your network. Most folks who've tried wireless give up and use wires in the end. It isn't really suited to such real-time applications unless it works really really well. Pete