Pete Dowson

Can SIOC read the yoke values and write them to offsets? If so, no problem. Pete

Surely this was perfectly clear in the main AVSIM thread which started all this? And it is clear from the comment by the author near the beginning of the "Dynamic" one where it says: -- Modded by Bob Scott to restrict wheel and brake reduced rolling friction effects to taxi speeds Doesn't matter much. If you run both the one run second will initially override the one run first as each resets the values to start with. However, then the dynamic one will take over as it runs continuously whilst the other one runs once and terminates. Well, if you want to activate it manually. Otherwise use the [Auto] facility to run it automatically. If you wish. Parameters are only relevant to those which use them. If you want to control it manually as you seem to, from the above. You'd really be better off checking the thread about all this in AVSIM's FSX forum. Regards Pete

FSUIPC Lua libraries are internal to FSUIPC and the FS process. You cannot access them from a completely separate process in a completely separate virtual machine! Pete

By "reinstalled", could you explain, please, exactly what you did? What version did you reinstall? Did you delete any files first -- for instance, the INI file? I really cannot understand how a working feature can simply stop working with no other change anywhere in the system, but i need more information so I can investigate. For example, is this always only with Win 8? Does it happen during an actual session, or only on a restart? Regards Pete

What's the "infamous DLL error" please? When does this happen, what are the symptoms? Is it a crash reported by Windows, and if so what is the error number and offset? does a log get generated and if so please show it? Regards Pete

You seem to have reversed it twice -- the REV check box and the option below. Try only once and ALWAYS calibrate after selecting such options. Regards Pete

I think SimFlight had some server glitch a week or so ago and this might have affected their key generation program -- probably a date error on their server -- but they said it was fixed. I've no idea how much damage that did, but if you can't get it resolved via a problem ticket to SimMarket, please ZIP up your FSUIPC.KEY or FSUIPC4.KEY file and send it to me at petedowson@btconnect.com. I can check it easily here and refer to SimMarket for you. [EDIT] Okay. Not SimMarket after all, but yours truly. Seems I never expected FSUIPC3 still be be selling after over 8 years, and it ran afoul of a check at the end of 2012. I've extended the registration date limit now. Please download 3.999y5 from Download Links subforum and put it into your FS Modules folder. I'll make a full new release with Installer later this month. Regards Pete

Seems that the FSUIPC4.KEY file, containing your registration, didn't get installed to the correct Prepar3D Modules folder. The most relevane file to show me is not the FSUIPC log but the Installer's log instead, please. One or two folks have reported that re-running the installer and re-registering fixed siimilar issues, so I would guess it's to do with some timimg problems in Windows enabling access permissions. Try searching from FSUIPC4.KEY. I'd like to know where it got to. Win8 isn't officially supported yet. I've really no way of developing for it at present. Maybe later in the year. There seems to be quite a few problems with it as yet, like hardware controllers being forgotten. Regards Pete

Do you have the "Log LVars.lua" plug-in installed in the FS Modules folder? FSUIPC can only list and assign to installed plug-ins. Regards Pete

I need more information I'm afraid. Are you using the FSUIPC_Loader at all? You say "latest version" but what is the actual version number please? "Latest version" doesn't really mean too much. A glance at your FSUIPC4.INI file might help too. Pete

Apologies for the delay in replying. As announced, I have been away on holidays. However, for almost all switches, knobs, etc, the update for the NGX which included the SDK documented all of the control numbers needed, and these can be assigned directly, by number, in recent versions of FSUIPC4. The list is in the .h file provided by PMDG in the SDK subfolder. You don't really need any Lua or L:Var implementatin. Regards Pete

Apologies for the delay in replying. As announced, I have been away on holidays. And the answer is the same. I'd need to see the LOG and INI files. I cannot help without actual information. Pete

Apologies for the delay in replying. As announced, I have been away on holidays. All of FSUIPC settings are saved in its INI file. Uness you delete that they won't be lost. More likely is a change in device number when you reconnect, especially if you use a different USB port or have make other USB connections in the mean time. To get around this sort of problem, use Joy Letters, as if you have multiple devices. See the chapter on this in the User Guide. Pete

Apologies for the delay in replying. As announced, I have been away on holidays. It processes data in exactly the same way as FS does -- i.e. in order of the layers in the SCENERY.CFG file, and obeying any DELETE commands included to remove earlier values. That would only happen if you placed the new layer lower than whatever else is providing it. Check the Runways.txt file generated by MakeRunways -- it is a huge file but it contains the complete analysis of what it sees. Search on the airport ICAO code and see what is going on. Also, always make sure you are using an up-to-date version. The program has been regularly updated. See Download Links subforum. Pete

Apologies for the delay in replying. As announced, I have been away on holidays. The date being incorrect is the most common reason. There aren't really many others, so I'd need to check here. Please find your FSUIPC.LOG and FSUIPC.KEY files (in the FS Modules folder), ZIP them up and send to me at petedowson@btconnect.com. Pete

Apologies for the delay in replying. As announced, I have been away on holidays. Sorry, I'm afraid I don't really know what you are talking about here. Who is everybody? What are you 'serving'? If this is related to Multiplayer facilities, I think you may need to go elsewhere for help. Pete

Apologies for the delay in replying. As announced, I have been away on holidays. Events are messages/controls initiating an action. They have no "states" to be read! 83645 is outside the range of controls for FS. Are you talking about an added PMDG or other add-on control? If the PMDG 737NGX have you checked to see if the state you need is not available mapped to offsets in FSUIPC? Check the documentation provided for the 737NGX offsets in your FSUIPC Documents folder. Sorry, I don't understand that message. Pete

Apologies for the delay in replying. As announced, I have been away on holidays. Try sending the axis event with the specific parameter values required, or use the FSUIPC Offset inc/dec commands to directly increase of decrease the internal FS values directly by a more suitable value. There's an example in the user manual for this, in that case for trim adjustment. You'd need the FSUIPC SDK to get the offset list. Otherwise, to do literally what you asked (i.e. make repreats to a specific number and stopped by another action) you'd need to program it in a Lua plug in and assign that. Regards Pete

Apologies for the delay in replying. As announced, I have been away on holidays. Min and Max refer to numerical values from the lever, NOT the position of the control surface. The numbers must increase left to right. Pete

Apologies for the delay in replying. As announced, I have been away on holidays. You can't actually save a flight without a WX file. In my experiance, consistent crashes in WEATHER.DLL are due to corrupted weather files. The only reason FSUIPC gets implicated is because the crashes occur when the corrupt data is processed by Simconnect by request of FSUIPC, and FSUIPC always reads the weather data. The corrupted file could be the WX file associated with the default flight, not necessarily the flight loaded later -- corrupted data can result is other corruption which has a later effect. to test this simply remove (save to another folder if you like) all .WX files from your Flight Simulator X Files folder in your Documents. Another file which can be corrupted, especially on an interrupted weather download from the MS site, is "wxstationlist.bin", in the same folder as your FSX.CFG file. If the above test doesn't fix the proble, try deleting that file. FSX will make a new default. Regards Pete

Apologies for the delay in replying. As announced, I have been away on holidays. Check the "InitialButton" parameter described in the Advanced User's guide. You can then have a macro instigated by that button which sends your keystrokes. If you want to do timed events like that you'll need to have a Lua plug-in (ipcReady.lua is run when FSUIPC is ready to fly). Pete

Apologies for the delay in replying. As announced, I have been away on holidays. Sounds like something is changing the time -- that's the usual reason for scenery/texture reloads. Maybe those functions don't exist in the aircraft you are using? Without details i'm afraid I cannot advise. FSUIPC does not control the aircraft. All your auto-pilot controls are doing is sending the same instructions to FS and clicking the A/P functions on the screen with the mouse. Seems like you've got some assignments wrong. All the assignable FS controls arel isted in the List of Controls provided for you in your FSUIPC Documents subfolder. You'd need to find them there or in the drop-down assignments lists. If you have difficulty simply enable FSUIPC's "event" logging, use the on-screen switch, and check the log for the name of the relevant control. This can only be caused by a few things: conflicting assignments, connection problems (eg loose wiring), or, possibly more commonly, devces going to sleep because of lack of power. For the latter make sure you turn off Windows USB power management -- it defaults to 'on'. Check all the USB hub devices in the System - Device manager. Best to assign it as a hat in the Axis assignments. Check FSUIPC documentation. Check the rudder trim and make sure it is zeroed. Depending on the aircraft you may also be experiencing torgue or propwash effects. Until you get pedals you'll need to turn down some of the aircraft realism settings. Try the VRi support forum. The are different AP alt hold setting controls. You are using the one which enables climbing or descending to a preset altitude. Try the other one. All FSUIPC settings are in the INI file, in the FS Modules folder, next to FSUIPC, as documented. Pete

To what and where did you assign the two levers? In FSUIPC? To Throttle1 and Throttle 2 respectively? If you have the assignments correct, I would suspect that you have dual assignments somewhere. Check assignments in FS and, if used, the GoFlight software. Pete

Apologies for the delay in replying. As announced, I have been away on holidays. Are you using digital PFC controls connected via a serial port, or some USB version? Which PFC driver are you using, and wihch version (number please) or FSUIPC? Where are you assigning and calibrating? Pete

Apologies for the delay in replying. As announced, I have been away on holidays. Either simply assign each variant to the same named profile when you load it (this will be remembered from then on), or, if you fancy editing the FSUIPC4 INI file, just make sure that the "ShortAircraftNameOk" parameter is set to ShortAircraftNameOk=Substring and the find the [Profile.<name>] with the named profile and edit the 1= line below to give a part of the name of the aircraft which applies to all variants. Eg possibly "737NGX" or "PMDG" or "737". Find one which applies to all the ones you want and none you don't want. Regards Pete