Pete Dowson

What does the PMDG aircraft need t get "idle reverse"? What actually IS "idle reverse"? How much thrust if not 0? With FS default all you set is the thrust value, represented by a throttle setting of -4096 (but, depending on Aircraft.CFG max reverse setting, -4096 represents 25%) to 16384. 0 is idle. Any non-zero value represents some thrust. If the PMDG aircraft needs some special value to set set "idle reverse", then I suppose you might be able to set it by using ThrottleN set, with the parameter = the value needed. (where N is the engine number). Pete

Lost all your keys to other FS add-ons too? You do really need to make backup of these things, on paper, CD or another PC. You can retrieve your Registration details from your SimMarket account. You'll need to use your original Registration email, both to access the details and when registering. BTW, there is a thread in the FAQ subforum ("Frequently Asked Questions") which tells you what to do if you lose your key. Pete

Okay, the facilty is in version 4.942, which I needed to release for other reasons in any case. Here's the description of the change, from the Changes document: Enjoy! Pete

What about 0C6F? If you are viewing the documents with a PDF viewer I'm sure you'll find there's a search facility. All I did was search for "NAV2 GS". 0C5C is already used for NAV2 relative bearing. Do you not see that listed either? What are you looking at? Pete

Please always post support questions in the Support Forum. the Announcements subforum is for .... anhnouncements (oddly enough)! And no, FSUIPC3 is for FS2004 and before, FSUIPC4 is for FSX, FSX-SE and P3D. They are different products with different names and separate purchase places in SimMarket, which do clearly state which is for which version of FS. Incidentally, 3.93 is very old (from August 2009 in fact), and has not been supported for years. You should be keeping up to date. The current FSUIPC3 is 3.999z8 or z9. Pete

Can you please show me the Lua file which gives this error? The event.cancel function is most certainly not a "nil" value, so it must be the function it is referring to. event.cancel is working perfectly well here. And how does P3D itself crash as you stated? A Lua error merely causes that Lua plug-in to be terminated. Pete

Does it do the same when running FS9 in Windowed mode? If not, then it's a problem with your video driver. You might need to find a later version, or a different version. Pete

There's been no change in Lua in 4.939n. What was your previous version? Have you tested with the current version at all (4.941)? I can't support old versions. Can you find a better translation than "that seems no longer consideration (nil value)" as I don't understand what that means in English. If you still have a problem with the current version, please show me the Lua file which gives you a problem. I would also need to Windows crash report details, please. Pete

Must be something strange about that aircraft. Is it the Aerosoft one? I thought with those you couldn't use FSUIPC calibration in any case as they need to hook the controls at a higher level? (Or is that only with PMDG aircraft?) However, why are you engaging smoothing? It's only really meant for VERY seriously unstable devices, usually caused by fluctuating power supplies. It was added main to help folks in remote parts of third world countries! Even on default aircraft it would introduce some latency in the control responses. Pete

Hmm. something wrong with the Windows 10 caching system them. Try saving using the ; key or menu; entering the name. It will do exactly the same thing. There is no way anything in FSUIPC can change how FS saves flights. As I said, all it does is call the routine to save the flight in the same way the normal FS facilities do. There's nothing else is can do. Did you at least check that Windows is not set to always write immediately rather than use caching? Pete

Yes, the instructions in the section in the WideFS User Guide about configuring the network (the part with the red warning to read at least part of it) is explicit that you need BOTH lines, not just the one. No, that's not true. If you don't give the Protocol it needs the Server to tell it through its broadcasts. It's one or the other -- specify details in the client parameters, or leave to to the Server broadcasts. No, parameters are never deleted. There is no Protocol parameter there by default so that you can choose it for all clients at the server end. You only supply a Protocol parameter to override the one set at the Server end. Pete

Normally no parameters need to be added to the client INI file, because the broadcasts from the server end provide both the server details and the protocol to be used. The documentation is clear that if you add explicit Server details to the client parameters, you need the protocol to be explicit too. I see no harm in that, and it has been that way now since day one of WideFS, back in FS98-2000 days. Of course, back then the protocol of preference would have been IPX/SPX, being lean and mean and efficient. Only the lack of support for it from Microsoft (it being a Novell invention, not MS) makes the choice now either TCP or UDP, and if there were to be an assumed default, UDP might often fit the bill better, being, again, more efficient, especially combined with using a broadcast setup at the Server ("BroadcastMode=Yes", whereby the same data is sent once, to all clients, instead of each client getting its own tailored data). My setup, with 7 clients, uses UDP and broadcasting on all clients except one, the one used for Radar Contact, where it is very important for all the commands being set TO the server to be in the correct order, something that UDP cannot guarantee. Pete

It is always useful to see the Log files -- that is what they are for. There's a WideServer log file on the Server and a WideClient log file next to the INI file you've shown. Note that your INI file is missing an essential parameter. If you specify the Server IP address you MUST also set the protocol, i.e. Protocol=TCP or Protocol=UDP Pete

All FSUIPC's autosave does is call the FS save routine at intervals, exactly as if you'd gone to the menu to save, or used the ; keypress. Any delay will be caused by one or other of: 1. Bad hard disk organisation, maybe needing defragging 2. Windows set to not cache files, so it tries to do the disk operation immediately 3. Add-on aircraft saving their own data and freezing the sim whilst they collect it (PMDG are famous for this). Pete

Well, I could just say "ask Microsoft", as all these facilities are doing is calling the relevant facilities in SimConnect. However, my guess is that the location change is simply that, like Slew in FS. Such facilities are needed to synchronise likned PCs following the same flight. The "initial position" facility is more like going to the main selection menu dialogue in FS and selecting a new position. Obviously it assumes nothing about where it was before. Well, I looked it up and it says that it is "... the elapsed real time, in seconds, at the last time any of the aircraft situation variables (LLAPBH, Lat Lon alt Pitch Bank Heading) in offsets 0560-0580 were updated by FS", so its most obvious application is to time the change in a linked PC running FS using the facilities just mentioned, to set position etc, to avoid them stuttering or jerking in relation to the FS view. It's a facility requested by folks making sophisticated multi-PC systems. You don't actually NEED to use facilities you don't understand, surely? Pete

Looks to be a reasonable idea. I'll take a look. Won't be till next week though. Pete

Luckily, for most folks, hardly any of this action is needed. I don't know why it is in your case. Generally it is just a load-and-go process, possibly just answering a question from the Firewall stuff as to whether to allow it through. In my case I do run without the firewall but I know lots of folks who don't disable anything, but just allow those programs which need to communicate to do so. I didn't need to do anything to my anti-virus software (I use Avast). Regards Pete

How odd -- a computer problem their end I suppose? I'm glad it was sorted out, on the same day as the order too. It isn't bad service. Regards Pete

Please don't flood this forum with messages! I cannot sit in front of my PC just waiting for messages to answer. I do have other things to do, you know, and a life to lead! I've just gone to your order and it is exactly as all others, the registration key is plain to see. You must be looking in the wrong place. I have nothing to do with sales in any case, all I can do is check. If you have a problem finding the right place you must raise a problem ticket with SimMarket. I must say I have never had anyone before with such a strange problem. Since the process in SimMarket is all automated I really don't see that your order can be treated differently to any other. Regards Pete

Can you start it using the facilities FS or iFly provide -- ie without worrying about buttons and switches on your hardware? If so, please re-read this part of my last message: Since it is an add-on aircraft then it might be completely different and not use any FS controls in any case. You'll need to refer to the iFly documentation. Do they provide keyboard short cuts which you can assign, for instance? Pete

All registration information is held in your account. Just log on to SimMarket, open your account, and retrieve it there. It is not sent by email. Pete

And what does it do instead? I don't know the 747 very well, being a 737 guy, but mostly Boeing's speedbrake/spoiler lever has just 4 positions. Intermediate positions might be sort-of settable but aren't really used. There's 'down' (stowed), 'armed', 'flight detente' and the fully deflected ground setting which only happens on landing -- you can't raise them right up when flying, only to the flight detente. Where there is some continuous adjustment is between the armed position and the flight detente, but, at least on the 737, you are really supposed to either have them down altogether whilst flying, or in the flight detente position. The supports aren't strong enough to guarantee no damage in intermediate positions. Why are you using a "range' with spoiler inc and dec controls when there's a perfectly good spoilers axis you can assign to on the left, with a calibration facility which understands things like Armed position? Er, "both parameters" for what? INC and DEC commands don't use a parameter, they have fixed increment/decrement values. If you mean the axis input value, how does a "range" become defined by one number? How many of the 10 ranges supported are you using. Sorry, but what you are describing makes little sense. Try assigning to axis spoiler set, or even spoilers set, on the left hand side. There's no point in using the right hand side for axis controls. Its main use it to use axis controls to do non-axis type things, such as gear up/down using a lever. Pete

Aha! You are right! I hadn't looked far enough! (In a rush for a dentist appointment). Sorry Krishna. Yes, as the summary shows, you got connected okay: 158606 ****** End of session performance summary ****** 158622 Total time connected = 69 seconds 158622 Reception maximum: 20 frames/sec, 582 bytes/sec 158622 Reception average whilst connected: 18 frames/sec, 491 bytes/sec 158622 Transmission maximum: 0 frames/sec, 19 bytes/sec 158622 Transmission average whilst connected: 0 frames/sec, 24 bytes/sec 158622 Max receive buffer = 548, Max send depth = 1, Send frames lost = 0 ;-) Pete

Sorry, the "ProtocolPreferred" parameter is a Server parameter. don't know why that's in the WideClinet.INI? You need Protocol=TCP Pete

Did you change it at both ends -- [WideServer] section in the FSUIPC4.INI file and in the Wideclient.INI. If not there's no chance! Sorry, I don't know. I'm sure there's a utility which can tell you, but we'd need to search. Can you use Google? Pete