Pete Dowson

Sorry, then. It works perfectly here. I don't know where to start working out what is different there. I'm tired and exhausted. i've been trying to do too much today. It's no good at my age. If anything occurs to me tomorrow i might have nother have a look, but my first guess is that you are still running the old version, as nothing has changed it at all. That makes no sense. You need to replace it and restart WideClient. Pete

Taking that last one first, your assignments do not show conflicting actions between press and release, so of course they work. Obviously, from your log, the SPOILERS SET parameter control is being sent. This is because you are calibrating. I know that for most axes, the PMDG aircraft in particular don't work with any FSUIPC calibration. They seem to be intercepting the FS controls at the higher level and not using the ones FSUIPC supplies. However, are you seeing the spoilers operate with your lever so set? As for arming, none of the values you "SPOILERS SET" axis setting sent would set Arm. There's a limited range for ARM down a lot lower than the lowest you sent which was, apart from the initial and final 0, 5620. It seems you haven't calibrated very well. Have you calibrated the Arm setting at all (the centre two numbers in calibration)? It doesn't look like it. Pete

Okay. This should work okay, it does here: Replace all of this: if len > x then --need to split mycopy2 = string.sub(mycopy, x+1) len = string.len(mycopy2) if len > x then --need to split again! mycopy2 = string.sub(mycopy2,1,x) .. "\r" .. string.sub(mycopy2, x+1) end mycopy = string.sub(mycopy,1,x) .. "\r" .. mycopy2) end by all of this: if len > x then --need to split n = x + 1 mycopy2 = mycopy while len >= n do mycopy = string.sub(mycopy2, n) mycopy2 = string.sub(mycopy2,1,n-1) .. "\n" .. mycopy len = string.len(mycopy2) n = n + x + 1 end mycopy = mycopy2 end This isn't limited. It will split into as many lines as needed. Better would be to find the nearest space character before your limit, and split there each time. But that's more complicated again and I don't have time at present. I may look at it again some time. Pete

Hmm. I must still have an error there somewhere. I'll have a look when I get time. Sorry, I have much bigger problems to sort out first. Pete

This log is insufficient. I doesn't tell me the version of FSUIPC you are using or the version of FS you are using, or even confirm the aircraft you are using. Please do NOT press the log tab button button to start a new log, and always show the complete log, at least from the start (essential information) to the point of interest. Please also test with a default aircraft. Some add-on aircraft do their own thing. Pete

I think that line should be mycopy = string.sub(mycopy,1,x) .. "\r" .. mycopy2) Please test again. I still won't guarantee it. Written in haste -- extremely busy at the moment. The idea of adding Lua to FSUIPC was to allow users to help themselves in making new facilities, so i didn't really expect to have to do it myself still, As a consequence so I don't give it as much time as the program itself. Sorry. Pete

They are always slightly different, as they are in the real aircraft once it isn't new from the factory. But there are facilities for making the calibrations line up at a number of points along the travel. It's all in the User guide. Pete

Well, the numbers came from some time it was there when you closed FS. I wouldn't worry about it. Delete it ccmpletely if you like -- when the sim isn't running though. Pete

15, not 16. 16 is 0x10, more that 4 bits! ;-) Pete

I've had to move this into the support forum, which is where support is provided. Please do not post support questions into the reference subforums. As you found by setting normal defaults, FSUIPC itself does not interfere with anything your aircraft is doing. So something you are setting is the problem. That button changes some of the the settings (mostly those on the Miscellaneous tab) which are saved and used thereafter all the time until you change them again. Just press OK to exit the options when you've pressed it, and it is saved. The settings go into your FSUIPC4.INI file which is loaded each time you run FS. I don't use any PMDG aircraft and I don't know what option(s) you selected which your addons didn't like. However, I have to say that there really is nothing FSUIPC can do to prevent LNAV, VNAV, AT and LVL CHG operations. The worse you might have done is set reversed trim and zero elevator options on the miscellaneous page. Why not just be careful what you select and only use the settings you need and understand? Pete

No. C is 12, the max in 4 bits is 15 which is F so bright yellow would be 0x0FF0 . In 24 bits your 255,255,0 would be 0xFFFF00. If you don't understand hexadecimal please review the FAQ subforum thread "About bits, numbers and hexadecimal". Pete

It is RGB, but the colour is encoded as 12 bits per pixel, not 24, so only 4 bits each, not 8 which your 255 would need. So 6C0 = 6 of Red, 12 of Green, no Blue. Pete

Version 4.959 itself (not the later interim updates) did have an error in one of the Version fields still saying it was 4.958. However, that was corrected in all of the subsequent interim updates (the DLLs only, no installer). Pete

Hi Bob, Any success with that q version of FSUIPC 4.959? I'd like to know before releasing 4.96, hopefully later tomorrow. Thanks, Pete

Not according to the crash report -- or is your system date set incorrectly?: Look: Source: Application Error Date: 23/01/2017 09:09:10 Event ID: 1000 Task Category: (100) Level: Error Keywords: Classic User: N/A Computer: CathalsPC Description: Faulting application name: Prepar3D.exe, version: 3.4.18.19475, time stamp: 0x5851bfd2 Faulting module name: FSUIPC4.dll_unloaded, version: 4.9.5.8, time stamp: 0x5857240f I cannot support LINDA myself. Crashes in LINDA.exe have to be dealt with by their support. This might be the DX problem already reported in the L-M forums. I suspect LINDA crashing left some device or other in a strange state. Loading with the n version can still fail if the previous session crashed. Precisely how and why this happens is still unknown, but by all reports if the crashes at the end of session which were occurring with 4.959 + LINDA are fixed, then it is okay ever after. Sometimes crashes on exit go unnoticed. The crash you reported in your first post was actually before FSUIPC was loaded ("FSUIPC_unloaded"), not the crash on exit. To find those you'd need to look further back still in the logs list, and those would certainly be before the n release because even this morning's was, as shown above! Pete

You are not actually testing with FSUIPC 4.959n according to the crash report which is dated 3 days later than the n release -- by then the incorrect version 4,9,5,8 shown in such reports was corrected to show 4,9,5,914, the 14 signifying n. Please replace the DLL with the later version before testing! Pete

Thanks for the feedback. There are definitely others with similar problems. Pete

Oh, I use ProATC/X too. What messages are too long? If it's the clearance or taxi instructions, which obviously vary in length, then this isn't part of the menu but its it the normal test window , w2 = wnd.open("FSX Text", WND_FIXED, 0,0,1024,100) wnd.backcol(w2, 0xfff) wnd.textcol(w2, 0x000) wnd.font(w2, WND_ARIAL, 10, WND_BOLD) I see you already have the font much smaller than that for the other two windows (10 rather than 17), so i suppose you don't have scope to reduce it further? Why not try changing this parameter, so it splits the line earlier? x = 80 --my example of how many characters you want, max After all, this was only my 'example'. If you want to split it further you need rather more complex code, maybe, for three lines, replace this: mycopy = msgs[1] --make a copy for me to use len = string.len(mycopy) if len > x then --need to split mycopy = string.sub(mycopy,1,x) .. "\r" .. string.sub(mycopy, x+1) end by this: mycopy = msgs[1] --make a copy for me to use len = string.len(mycopy) if len > x then --need to split mycopy2 = string.sub(mycopy, x+1) len = string.len(mycopy2) if len > x then --need to split again! mycopy2 = string.sub(mycopy2,1,x) .. "\r" .. string.sub(mycopy2, x+1) end mycopy = string.sub(mycopy,1,x) .. "\r" .. string.sub(mycopy2, x+1) end I haven't been able to test this (my cockpit is not up at present), but it looks okay. If not you should be able to see what it is trying to do and fix it yourself. Scrolling is possible, using code which keeps displaying from one later in the string, via another timer in another function. but that's even more complicated. If you fancy that, why not have a go? Pete

Your FSUIPC is way out of date! Download and install the latest version. Please always check you are using a current version before asking for support! Pete

The messages are just as they are. If they don't fit, they don't fit. What GSX messages are the problem? I have never had a problem reading them. Is your window very small. BTW you seem to have quoted something from me completely disconnected from your question, and there is no "code above". Pete

It's there on my system. FSUIPC gets the list from FS or P3D. What version of FS/P3D are you using and, more importantly, what version of FSUIPC? Pete

Surely it doesn't look "obscure", it is pretty well self-expnatory, and similar to the similar window entries you get in FSX.CFG and Prepar3D.CFg. It saves the position of the last Lua plug-in display window you had showing. At some stage you had some plug-in creating such a window -- LINDA maybe? Or something else you used? And if you want to change them you'd need to do it before starting P3D, and even then they'll probably be overridden by the display plug-in, especially if they are invalid like all 0's. Pete

Assuming the flight you are loading actually was saved with a more 'usual' view, it sounds like you have some incorrect assignment somewhere. Mate you using CH's control program, or are the CH devices only acting directly into FS/FSUIPC? Try enabling event both button and event logging on FSUIPC's Logging tab. You'll need to do that then restart FS so that the log starts off with those set. Show me the log after, and also your settings (the INI file). Both are in the Modules folder. Pete

I found one little suspicious bit of code which I've "fixed", or so I think (the code is old and so am I!). Can you try this test version please? FSUIPC4959q_TEST.zip Pete

You'd need to re-create the file every time, doing the open, write and close all together. Pete