Jump to content
The simFlight Network Forums

Pete Dowson

Moderators
  • Posts

    38,265
  • Joined

  • Days Won

    170

Everything posted by Pete Dowson

  1. You are READing the command word, not WRITING it? Where's the Write for the Dynamics offset value? You'd need to read the whole weather structure, all parts, change the bit you want, then write it back. Using that interface there's no way to change just one part, you have to change it all -- the weather is written as one entity. Note that setting.Global weather only sets the default weather for those stations which have none set yet. FS2004 uses localised weather and cannot be switched to global weather mode like FSX. Not unless you use the Pending version of the commands, in which case you'd need to activate them all. Regards Pete
  2. Try using commas, as documented, instead of points (.) which make things like 3.0 look like number 3.0 and 66079.0 similarly. Parameters are separated by commas. 14=W0366=0 P3,0,C66079,0 Regards Pete
  3. I'd need to see your INI file. It may be that you have short aircraft names matching some already assigned to profiles for the [Axes....] sections. Please just paste your INI file here and I'll see what is going on. No, FSUIPC doesn't try anything clever. It is all user-controlled, by names and assignments. The INI file will show. Regards Pete
  4. There's no DDL.XML file which is relevant. Perhaps you mean the DLL.XML file? That's in this folder on your PC: C:\Users\WayneF\AppData\Roaming\Microsoft\FSX However, that fact that you get a run time LOG file means the DLL.XML file must be okay. Best to paste them into the question, as you have done, and then enclose them in "code" parentheses, using the <> button above the edit area. Your install and run-time logs show everything is fine. AND that FSUIPC4 did, indeed, get its Menu entry added: Maybe you are looking in the wrong place? The AddOns menu is in the FSX Menu Bar, during normal flight modes, at the end, to the right of "Help". Regards Pete
  5. GPSout functions are built into FSUIPC4 and are enabled in the Options. They need a Registered install of FSUIPC. FSUIPC3 never output any sentences -- I assume you mean GPSout.DLL? Was that ever reported? I can only fix problems I know about. Which version were you using? Regards Pete
  6. Correct. You have to change an INI file option. Pete
  7. Out of range for what? FSUIPC deals with joystick assignments up to 255 locally, and much higher for buttons on WideFS client PCs. (1000 added for each PC). Regards Pete
  8. But why? 088C will be updated by FS to reflect the internal throttle value, and changing it will mess thins up. But the 3110 write merely sends the AXIS control, whichi s just exactly what your DirecTX throttle would do. There's no point in writing to 088C as well, surely? I am now completely lost -- you are speaking as if your throttles are motor controlled, in which case for sure they should be using a different method. If they are not motor controlled I've on idea what you are actually talking about. From what you say I don't think the throttles are of any use at all! ;-) What other methods do you think exist which FSUIPC cannot accomplish? Pete
  9. Yes. You'd need to detect that change in the FSUIPC offset using the event.offset Lua library function, and when it changes send an appropriate "KeySend" control. The WideClient parameters for that KeySend would by "RunKeyN" (where N is 1 to 8), and a line "RunKeyN=...." would provide the full path and filename of the program or .CMD file to be executed. Regards Pete
  10. What FSUIPC Speed Hold? Pete
  11. I moved this from out of one of the information sub-forums where otherwise it would have gone unnoticed. Please use the Support forum for Support. First off, is there an FSUIPC4.LOG and FSUIPC4.INI file in the FSX Modules folder? Paste in the Install FSUIPC4 log and the FSUIPC4 log please. Don't run anything as "Admin". Your posting of the DLL.XML file is indecipherable. Could you paste it again and enclose it in "code" parantheeses (see <> button above the edit area). Pete
  12. I wouldn't be able to check them as my French is long forgotten (through disuse), but if you think they'll be useful you can send them as attachments to an email, to petedowson@btconnect.com (ZIP them please) and I can make them available in the Download Links subforum, credited to you of course. Or else you can host them as you say and I can provide a link instead -- let me know what that link should be. Thank You & Best Regards Pete
  13. Always test things on a default aircraft first. If it's only a problem with the PMDG one then you'll probably need to go to their Forum. And have you first actually CALIBRATED the axis (not set detentes) so that you can move the lever back and forth and the flaps lever follows suit? You MUST do that first, to establish the correct minimum and maximum values! Additionally, as far as I'm aware the GoFlight devices have no detentes, have they? If the hardware has none then there's really no point in setting axis ranges for them, is there? Just assign and calibrate. forget detentes. They're for cockpit builders with realistic flaps levers. Regards Pete P.S. I'm away now till March 14th.
  14. No, not so strange. did you not look to see what your program is doing? Look 1290078 WRITE0 3104, 4 bytes: 00 00 00 00 1290078 *** EVENT: Cntrl= 66242 (0x000102c2), Param= 0 (0x00000000) TOGGLE_MASTER_ALTERNATOR 1290078 *** EVENT: Cntrl= 65955 (0x000101a3), Param= 0 (0x00000000) FUEL_SELECTOR_OFF 1290078 *** EVENT: Cntrl= 65595 (0x0001003b), Param= 0 (0x00000000) FLAPS_UP and 1334625 WRITE0 3101, 4 bytes: 01 00 00 00 1334625 *** EVENT: Cntrl= 66339 (0x00010323), Param= 0 (0x00000000) TOGGLE_ELECT_FUEL_PUMP 1334625 *** EVENT: Cntrl= 66241 (0x000102c1), Param= 0 (0x00000000) TOGGLE_MASTER_BATTERY 1334625 *** EVENT: Cntrl= 66242 (0x000102c2), Param= 0 (0x00000000) TOGGLE_MASTER_ALTERNATOR 1334703 *** EVENT: Cntrl= 66242 (0x000102c2), Param= 0 (0x00000000) TOGGLE_MASTER_ALTERNATOR Did you not norice that 3101 and 3104 are a one byte values? You are writing 00 to 3102, 3103 and 4104 as well when you write 3101, and similarly also to 3105, 3106 and 3107 when you write to 3104. No wonder things are goping off which should be on. I'm surprised worse doesn't happen! I wonder how many other things you have set the wrong size write? You can easily crash FS this way! This is why I asked you about the size (length) of the writes you are making. I don't know your type of code, I only know C/C++ and ASM. That's why I asked. Just because the source value is 32-bits doesn't mean (shouldn't meant) you only ever write 4 bytes. You should stick to the documented variable size! Also I'd like to know more about what these lines are for: 1286250 WRITE0 3210, 2 bytes: FF FF ... 1296609 WRITE0 3210, 2 bytes: FF FF .. 1306984 WRITE0 3210, 2 bytes: FF FF ... 1317328 WRITE0 3210, 2 bytes: FF FF .. 1327703 WRITE0 3210, 2 bytes: FF FF ... 1338062 WRITE0 3210, 2 bytes: FF FF Seems that every 10 seconds you set all virtual buttons 64,0 to 64,15 to "pressed". What are these buttons assigned t od? Do you intend this? Regards Pete
  15. Did you make sure the workgroup name was the same in both? Win7 uses a different name by default to XP. Did you read the part of the WideFS document which says, in RED, that you should be sure to read it? Did you try setting the ServerName and Protocol in the INI file? I don't know the Windows error numbers off by heart. What were the words? Did the log say it had the IP address or name of the Server? It would really be quicker to paste the log rather than quote one number from it. From tomorrow i am away until March 14th, so apologies for any delays in further responses. Regards Pete
  16. What is the version number of this "latest" version of FSUIPC, please? It is no use simply saying "latest" -- folks have said that and been using a very old one. By "latest" they meant the last one they'd bothered to go find or seen on some website somewhere. I need always to know version numbers. They are no so hard to find. On screen in the options, in the Log, in the properties of the DLL. Something is clobbering your SimConnect responses. What about internal SimConnect users, like FSUIPC? PMDG aircraft, for example, and lots of others. You will need to carry out a process of elimination, stopping one at a time. Did you try making the time longer like I suggested? What were the results? I'm afraid I am away from tomorrow until March 14th. A little holiday. Apologies therefore for any delays in further responses. regards Pete
  17. Light switches in the default 737? Take a look through the controls list. You don't have to just scroll through the drop-downs, you can refer to the controls list document installed for you in the FSUIPC Documents folder in the FS Modules folder, alongside the rest of the documentation. Pete
  18. Oh dear. :-( When you load the offsets list for viewing, aren't you using a program which provides a search facility? I don't remember all of the offsets. There are many hundreds. Any time someone asks me such a question i have to load up the document and search for the answer. Why can't you do this? Search on the word "Ground". You'll find Ground Altitude, Ground Speed and "aircraft on ground" all in the first three or four attempts! It really isn't hard, and it's a darn sight faster than asking me each time. :-( Pete
  19. Not a problem for me, but you only just caught me. I'm off from tomorrow on holiday until March 14th. Er ... this macro file. Is it one you've made yourself, for the Posky aircraft? I'm afraid I still don't understand your wording. By "offsets" are you still meaning "assignable controls"? Why are you using the term "offsets" all of the time? It makes no sense. If you are talking about the 737 OHD.mcro file supplied with FSUIPC as an example of programming mouse macros, then that is only for a specific version of the PMDG 737. There is no way any mouse macro will transfer between different aircraft's gauge files because they are designed to call routines directly inside the code of those gauges, and each is different. You have to make your own macros for your own aircraft. Pretty much nothing in any of the Microsoft default aircraft is susceptible to the mouse macro methods in any case. Ah! So by "offsets" you DO mean "controls"? Can you please use the term "controls" because "offsets" are are completely different subject. You are being inconsistent in any case. Why would you use a 737 Overhead macro for strobe lights and not for landing lights? Both are actually, for a 737, in the overhead. Anyway, the answer, in any case, is NO! Unless you are using the specific 737 for which the supplied Macro file is an example. To switch the strobe lights on and off use the Strobes on and Strobes off controls! That's what they are for. Regards Pete
  20. Sorry, can you re-phrase that please? I don't understand it. Regards Pete
  21. Really? I think you must be misreading something? FSUIPC3 keys don't work with FSUIPC4 or vice versa -- they are two separate programs. But else any valid keys work with currently supported versions (3.98 is the earliest supported version for FS9 -- version 3.989y is available here in the Download Links subforum). Regards Pete
  22. Yes, of course, it is the "aircraft on ground" flag at 0366. Regards Pete
  23. I need more information. You need to enable Event logging and IPC Write logging -- see the Logging Tab in FSUIPC options. Then repeat the whole sequence. Check that what you THINK you are writing is actually being written. Also check whether it applies to all aircraft or only some -- the Master Alternator might be tied to the Battery switch so that you have to operate one before the other. What sort of code is that? Where is the size of the write defined? Is the "keyswitch" value supplied in the FSUIPC_Write call a pointer to where the 0 or 1 is stored, as it should be? Does the variable pointed to have the correct size? BTW I am away from tomorrow (Friday) until Sunday 13th March. So apologies if you get no more replies from me till then. Regards Pete
  24. I just, luckily, noticed your post in the FAQ subforum (which is for documented solutions to Frequently Asked Quesdtions) and moved it here, the Support Forum. You relaly alsways need to post questions to the Support Forum else they might not get noticed! You are entering something incorrectly, then. All three parts -- name, email, key -- must be EXACTLY as originally registered. If you don't remember how you spelled your name, please open your account at SimMarket and retrieve the details again. BTW, reinstalling FSX rarely means having to re-register FSUIPC. As noted in the documentation, you should keep a copy of the FSUIPC4.KEY file as well as other things in your FSX Modules folder (your settings and macro files, for instance), and restoring those re-enables the registration. You only really need to re-register if you reinstall Windows, or move to another PC, or roll-back your Registry to a point before you first registered. Regards Pete
  25. FSUIPC doesn't current offer anything for wheel rotation, but I notice that SimConnect does. It offers these values: [b]WHEEL RPM:[i]index[/i][/b] Wheel rpm. Index is 0 = center 1 = left 2 = right 3 = aux Rpm [b]CENTER WHEEL RPM[/b] Center landing gear rpm Rpm [b]LEFT WHEEL RPM[/b] Left landing gear rpm Rpm [b]RIGHT WHEEL RPM[/b] Right landing gear rpm Rpm [b]AUX WHEEL RPM[/b] Rpm of fourth set of gear wheels. Rpm [b]WHEEL ROTATION ANGLE:[i]index[/i][/b] Wheel rotation angle. Index is 0 = center 1 = left 2 = right 3 = aux Radians [b]CENTER WHEEL ROTATION ANGLE[/b] Center wheel rotation angle Radians [b]LEFT WHEEL ROTATION ANGLE[/b] Left wheel rotation angle Radians [b]RIGHT WHEEL ROTATION ANGLE[/b] Right wheel rotation angle Radians N - [b]AUX WHEEL ROTATION ANGLE[/b]Aux wheel rotation angle Radians I could add offsets for these, but at present I've no idea if they work or whether they'll tell you what you need to know. What do you think? Unfortunately, I am going away from a short holiday tomorrow, not back till the 14th, so I wouldn't be able to provide anything for nearly two weeks. Wouldn't the ground speed and the "on ground" flag be sufficient? Don't forget that the wheels can still be rotating off the ground, until the pilot taps the brakes before raising the gear. 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.