Jump to content
The simFlight Network Forums

Pete Dowson

Moderators
  • Posts

    38,265
  • Joined

  • Days Won

    170

Everything posted by Pete Dowson

  1. A successful registration enables many facilities for your use in FSUIPC, but it doesn't change the way it interacts with FS at all, nor with applications -- UNLESS there is something wrong with the Registration. Er, sorry, what "failed registration"? You mean when you attempted it with the wrong email address? If that's what you mean, then of course it would say so in the Install Log. Run the installer again and take the "check registration" offer, see what it says then ... Are you sure there's nowhere to click on that notification to obtain more details? From the wording it certainly seems as if has loaded, else it couldn't stop. There are different sets of reasons for Windows reporting that it cannot run a program, usually related to missing components preventing its run-time linking. No. Is there an FSUIPC log file in the Modules folder? If so show it to me please. Do you have any applications (add-ons) which use FSUIPC? In other words, what was FSUIPC doing there when it wasn't registered? Without more information from Windows and that error message I'm not sure how we can proceed. The only type of FS crash which normally supplies no error information are those so-called "Crashes to Desktop" (CTDs), when FS literally just vanishes without a trace. Getting an error message is usually good because it tels you things. Regards Pete
  2. I'm still not understanding the problem I'm afraid. Do the Flaps physically move to #4 immediately, then go back to 2 then 3 then 4? It seems very unlikely to me. Are you sure this is not simply down to the fact that you are reading back the value you wrote to 0BDC first, before FS has received the command, reacted to it and starts changing the lever position itself? If you want to read the actual flaps position, not its control, you need to look at 0BE0 and 0BE4, not your control input at 0BDC. Regards Pete
  3. You have made an "FSUIPC" folder in the FSX modules folder? Strange. Normally you'd put the Installer EXE somewhere temporary, like the desktop. You have to actually run the Installer to install FSUIPC4. Anmyway, the interim releases in the Updates Announcement don't come in an installer. Just the DLL. You have to copy the FSUIPC4.DLL into the FSX Modules folder, NOT into any "FSUIPC" folder you might have made. It won't work from there. No there aren't -- there cannot be more than one file with the same name in the same folder. There will only ever be one FSUIPC4.INI file in the FSX Modules folder. And there cannot be any INI file from any update UNTIL you run FSX -- FSUIPC cannot make an INI file if it isn't run! Don't ditch anything. You appear to be very confused and I don't know why. ALL you needed to do was copy the new DLL into the FSX Modules folder. It overwrites the other one. There is no new INI file and nothing replaces your INI file. Just run FSX and enjoy it! Pete
  4. Of course, that is the email address bound irrevocably with that Key and your name. No. Why should it? Why ask that question? You need more information on what it is saying. There must be more details available in the error report. When did it "stop working" in any case? If it "stopped working" it must have loaded, else it could not stop. Regards Pete
  5. Yes, I understood that question. But what has the Network got to do with it? But if you are not already connecting another PC, why would WideServer's log be any use? So you need to ask Mr. Dyer a different question I think! ;-) Regards Pete
  6. Are you using a Network then? I didn't see any reference to a Network with WideFS. If you are using wideFS there weill be a WideServer log in the FS Modules folder, where the FSUIPC log also can be found. You only need WideFs if you want to run some FSUIPC application on a Networked PC, one not running FS. Are you sure this is what you want to do? It seems a long way from your original questions! I'm sorry but I have no idea what you are doing. Maybe you need to explain yourself. This thread has taken a strange turn all of a sudden. Tell me what you want to do and what you have done. Regards Pete
  7. Sorry, I've no idea -- it would depend on the device in any case. It it imitated a genuine joystick device it would be a type of joystick driver in any case and seen in FS and FSUIPC as a collection of buttons and so on. You need to follow the pointer I gave you. Pete
  8. Yes. There are plenty of controller cards which allow switches, buttons, axes and even indicator circuits to be added. They may come with a driver to make them look like USB joystick devices, or a driver to interface to FSUIPC directly, which can be more efficient sometimes. Visit the Forums over on http://www.mycockpit.org/forums and you will get plenty of pointers and advice. Regards Pete
  9. Didn't you save copies of the broken ones? I'd like to have seen what happened to them, and maybe identify the culprit that way! Yes, but that really cannot possibly happen merely by copying in the new DLL. There's no way, honestly. There's really never any need to do that. And you didn't want to show them to me as I asked? Now I cannot identify the cause. The same problem can occur again. The previous user did the same, so we are none the wiser yet again. :-( Regards Pete
  10. The version is the same, registration merely makes the User facilities available. The Updates announcement, you mean? And did you simply copy the DLL in, no other changes? Because that's al that is needed. Okay .. so you changed something else as well. Merely copying in the DLL won't introduce any new serious errors. What "files", exactly? Surely only the one you copied -- FSUIPC4.DLL. I hope you haven't deleted anything else. Why "tried"? The log showed you succeeded. Is there still a problem? I'm lost now. If you currently have a problem with 4.53 installed, and you didn't before, with 4.53 installed, then you've changed something else in FSX - another add-on installed or reinstalled, perhaps? Did you check that other thread I pointed you to? In that case exactly your error occurred because of a corrupted FSX file, either or both of the EXE.XML or DLL.XML files. Fixing those fixed the problem. Regards Pete
  11. I don't know about "engine heat", I don't think there's a control by that name. But engine anti-ice is most certainly hot bleed air used to prevent ice accumulation. not sure exactly where such accumulation occurs, sorry, but if "nacelles" is the place then that must be it. It's just a term I don't know. Pitot heat is of course the dynamic air pressure probe heat, to stop the pitot tubes blocking up with ice and causing the ASI to malfunction. On the 737 overhead, at least, it's called probe heat. Regards Pete
  12. Ouch. Not a good idea, and never needed for any FSUIPC update. Rightit won't start without that -- "FSUI" is "Flight sim User Interface"! Regards Pete
  13. You might have better luck getting an answer from the PM forums over on MyCockpit: http://www.mycockpit.org/forums/forumdi27981&f=99 Regards Pete
  14. Sorry, I don't know anything about "Phidgets". Isn't there any documentation supplied or support offered with the product? If they imitate genuine joystick buttons, switches and axes, then Windows should see them and so should FS and FSUIPC. However, they probably have a driver which you'd need to install. [LATER] I was rather curious about this so I did a search on "Phidgets" and came up with this, probably the most useful reference: http://www.fscockpit.com/specialinterfacesolutions.html Scroll down to the Phidgets section. It seems to recommend an easy-to-use interface program called "FS2Phidget" by Alan Dyer. I suspect that's what you need? Also, I think you may get help on the Mycockpit forums. I have seen Alan Dyer's name there on occasion. Regards Pete
  15. That is not 4.558, but 4.53. "Back"? But it says it is 4.53!? Sorry, but everything in this report is related to 4.53. Is that what you mean, that you cannot run 4.53? The log shows it running okay. The install shows it installing okay. Why would you want to install it 3 times when once is enough? Please explain what the problem is and what version it is you really mean. Everything, apart from the message above, shows 4.53 is working correctly. The Log shows 4.53 is working even if the message doesn't. Which is correct? You second message is even more confusing: What "other thread"? If this is a continuation of something you already started, why not keep it in the same thread so that there is some continuity. It is not easy to follow what you are talking about otherwise. So please could you answer these quite simple questions? 1. Have you ever used FSUIPC4 before? 2. Which version and was it working okay for you? 3. If it was okay and has stopped working, what have you changed in the mean time? [LATER] It occurs to me that you might have a problem in your SimConnect files, just like the one eventually found and fixed in this thread: viewtopic.php?f=54&t=78579 Perhaps you could show me your DLL.XML and EXE.XML files? I expect there's a problem in one of those. They can be found in the same folder as FSX.CFG, i.e. C:\Users\Skylar\AppData\Roaming\Microsoft\FSX Regards Pete
  16. Sorry, Ive never heard of wing/stabiliser heat. do you mean wing de-ice? See offset 337D. There's also a prop de-ice at 337C. But I've no idea if either work in FS9 or before -- it probably depends on the maircraft modelling. 337D is okay in FSX and ESP, not sure about 337C. Why not look it up? 3BE3 is just as documented, one of that batch of 18 FAILURE modes 3BD6. Please do refer to the documentation provided -- it clearly isn't a switch like the other! No idea. What is "engine nacelle heat"? Obviously not since one sets a failure and would make the other inoperative. Regards Pete
  17. 3.82 is not valid and is long unsupported in any case. What "new one" are you trying? I'm sorry, but it really isn't any use at all making reports without version numbers. I could also do with an explanation of exactly what you mean by "FS9 dont't start up". Regards Pete
  18. The full list of panel IDs in the FSX Panels & Gauges SDK code header file is // Panel identifiers #define IDENT_MAIN_PANEL 0 #define IDENT_MAIN_PANEL_ALT1 1 #define IDENT_MAIN_PANEL_ALT2 2 #define IDENT_MAIN_PANEL_ALT3 3 #define IDENT_MAIN_PANEL_ALT4 4 #define IDENT_MAIN_PANEL_ALT5 5 #define IDENT_MAIN_PANEL_ALT6 6 #define IDENT_MAIN_PANEL_ALT7 7 #define IDENT_MAIN_PANEL_ALT8 8 #define IDENT_MAIN_PANEL_ALT9 9 #define IDENT_THROTTLE_PANEL 10 #define IDENT_RADIO_STACK_PANEL 50 #define IDENT_COMPASS_PANEL 75 #define IDENT_MINI_CONTROLS_PANEL 100 #define IDENT_ANNUNCIATOR_PANEL 125 #define IDENT_ANNUNCIATOR2_PANEL 150 #define IDENT_IFR_MAIN_PANEL 175 #define IDENT_COLLECTIVE_PANEL 200 #define IDENT_GPS_PANEL 225 #define IDENT_OVERHEAD_PANEL 250 #define IDENT_PARKING_BRAKE_PANEL 251 #define IDENT_FLAPS_TRIM_PANEL 252 #define IDENT_FUEL_PANEL 253 #define IDENT_ELECTRICAL_PANEL 254 #define IDENT_TRIM_PANEL 255 #define IDENT_LANDING_GEAR_PANEL 256 #define IDENT_MISC_POPUP_1 260 #define IDENT_MISC_POPUP_2 261 #define IDENT_MISC_POPUP_3 262 #define IDENT_MISC_POPUP_4 263 #define IDENT_MISC_POPUP_5 264 #define IDENT_MISC_POPUP_6 265 #define IDENT_MISC_POPUP_7 266 #define IDENT_MISC_POPUP_8 267 #define IDENT_MISC_POPUP_9 268 #define IDENT_MISC_POPUP_10 269 #define IDENT_USER 10000 #define IDENT_USER_MAX 19999 #define MIN_HUD_IDENT 20000 #define IDENT_AIRCRAFT_HUD_3D_PANEL 20000 #define IDENT_HELICOPTER_HUD_3D_PANEL 20001 #define IDENT_CONTROLS_HUD_3D_PANEL 20002 #define IDENT_TEXT_HUD_3D_PANEL 20003 #define IDENT_DAMAGE_HUD_3D_PANEL 20004 #define IDENT_SCORE_HUD_3D_PANEL 20005 #define MAX_HUD_IDENT 20006 #define IDENT_LSO_WINDOW 22000 #define IDENT_POI_WINDOW 22001 #define IDENT_TIMER_WINDOW 22002 #define IDENT_DROPPABLE_OBJ_WINDOW 22003 #define IDENT_INVALID 4294967295 But that file does not define the string names, only the names to be used in gauge and panel code. The ESP SDK includes this list of names: MAIN_PANEL MAIN_PANEL_ALTn (where n is 1 to 9) THROTTLE_PANEL RADIO_STACK_PANEL COMPASS_PANEL MINI_CONTROLS_PANEL ANNUNCIATOR_PANEL ANNUNCIATOR2_PANEL IFR_MAIN_PANEL COLLECTIVE_PANEL GPS_PANEL OVERHEAD_PANEL PARKING_BRAKE_PANEL FLAPS_TRIM_PANEL FUEL_PANEL ELECTRICAL_PANEL TRIM_PANEL LANDING_GEAR_PANEL MISC_POPUP_n (where n is 1 to 10) MINIPANEL but how these equate to numbers isn't stated. Note, however, that there is a "MINPANEL" as well as a "MINI_CONTROLS_PANEL". The listing order of these follows the numeric assignment order in the include file, so my first guess for MINIPANEL would be 270, though of course it could be anything between 269 and 10000. [but see below!] Of course. The parameter must be numerical. How does it know how to translate "MINIPANEL"? [LATER] Found it in the "PANELS.DLL" of FSX. It's 20000, the same as the number assigned to "AIRCRAFT_HUD_3D_PANEL" Regards Pete
  19. What version number is this "latest"? That is a pretty meaningless way of identifying it I'm afraid. Are you sure it isn't corrupted? Does its signature check out correctly -- right-click, Properties, Signature (there are instructions in the documentation). Sounds like you've told windows or FS that you don't trust software from simFlight. The older versions, signed "Peter L. Dowson" have an expired signature so they shouldn't work in any case. Regards Pete
  20. If there is only one FSUIPC.INI file there, then that one MUST be the one it is reading. If it "didn't pick it up" it would have created one. It cannot run without there being an active INI file, and there can only be one of those called "FSUIPC.INI"! There is no point whatsoever going back to an old unsupported version of FSUIPC. If you persist then don't please ask for any help. What is most likely is that your joystick numbers have changed, that is all. The USB connections are mapped onto joystick numbers by windows, and a re-installation (or re-connection to different sockets) will change them. If you look in the INI file you will find a section implanted there by any recent version of FSUIPC which gives you the joystick numbers corresponding to each connected device. There are facilities in FSUIPC for automatically re-mapping those when they change, but you do have to USE those facilities to get any benefit. Since you evidently haven't done so, the answer now is to edit the joystick numbers in each [buttons], {Axes] and [JoystickCalibration] section to match the devices correctly. If you apply the named (lettered) joystick facility first you can avoid such problems in the future. These facilities are provided to deal with this type of problem exactly. Regards Pete
  21. ErACTUAL altitude changes are like Latitude/Longitude changes. Neither are anything to do with weather stuff like air pressure. If you are saying the aircraft is literally jumping up and down (at an effective infinite speed and acceleration) then something is very wrong with the whole simulation engine, not with the weather. You can change the characteristics via several parameters. The default values were arrived at over many weeks testing with the real 747 pilot who was assisting in the development of PMDG's 747X add-on, and ended up being satisfactory to all -- FSX's default being considered quite unrealistic. But you can please yourself by adjusting the parameters as you like. Regards Pete
  22. Sorry, but PMDG keep these things secret and, though I don't much like that, to maintain good relationships with such suppliers I cannot allow their proprietary information to be published openly here. If you need help hacking into other producers program data you need to look elsewhere. Good luck! Regards Pete
  23. Sorry, there's not enough information in the question for me to even hazard an answer. What is this "GA panel"? Hardware or software? What drivers? Any support for it/them? Networking difficulties are unlikely if the WideServer and WideClient logs show no errors, timeouts or reconnections. Have you checked? Regards Pete
  24. If it doesn't come with any instructions or software, and you don't know how it works, then I would think it is a difficult project as you'd first need to determine those things. If it comes with information about how to program it, then I'm sure you could write a program to interface to FSX either via FSUIPC or via SimConnect. Your choice. Regards Pete
  25. WideClient just needs an IP address which will link it to WideServer, in FS. If you can implement such a link then yes, of course, though I've no idea what sort of frame rates you'll get. There's nothing in either end which checks whether the link is to a local PC or not -- in fact I wouldn't know how to implement such a check.You can change the Port number at both ends if necessary. Regards Pete
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.