Pete Dowson

Well, only just. The font is rather small, isn't it? I've made it bigger in my response ... I'm really not sure what the question you have might be, because the explanation here seems quite clear: Which part are you asking questions about? I don't think I can expand on that in any helpful way. Regards Pete

You should make all the macros for that cockpit between "create macro" and "end macro making". Even so, Windows should not be creating the file the way you showed it. I don't know how it does that. (FSUIPC doesn't handle the file itself, it is handled by standard Windows "profile" facilities, the same as the INI file and all of FS's own CFG files). Anyway, for now just edit the file the way I showed above and you'll be okay with that one. But the macro name is preceded by the Macro filename in any case. doesn't that make it easy to find? Regards Pete

If all those are in one .mcro file I'm not surpised. In such a file you are only allowed one of each parameter. Each successive "Module=" parameter overrides the previous one, and the same for each successive "1=" line. Please tell me exactly how you managed to create that file. Are you enabling macro creation, creating one macro, then closining macro creation and starting over? If so then each time you do that you are overriding the last one. You should start macro file creation, create ALL of the macros for the one cockpit, then close it and finish. The file would then contain: Module="BlackBox-AirbusPro.DLL" 1=bbslanding=RX4def0*X33cc 2=bbsrwyto=RX4ded0*X33cc 3=bbsbeacon=RX4de30*Xa1cc 4=bbsstrobe=RX4de00*Xa1cc 5=bbssmokeon=RX4db10*Xa1cc 6=bbsseaton=RX4daa0*X83cc 7=bbsseatoff=RX4da80*X83cc 8=bbstaxi=RX4df10*Xa1cc 9=bbsbeacon=RX4de30*Xa1cc I'd like to know exactly what you did to create the file still, please, because something looks like it is going wrong with the Windows Profile system, as it should automatically replace each Module= and 1= line with the new one when you made the next one. Then your file would contain just: Module="BlackBox-AirbusPro.DLL" 1=bbsbeacon=RX4de30*Xa1cc with the same result as you see now but no way of recouping the earlier made macros. BTW, why pre-pend all of the macro names with "bbs", so making all of them longer than they need to be? Why not make BBS part of (or all of) the .mcro file name instead? Pete

Sorry, but there was no attachment. Maybe you can cut and pate the relevant part? I really have no idea how to change a Windows display mode. Regards Pete

Do you think they are related at all to FSUIPC? Why? What was your previous version? What sort of crashes? Please get the crash data from Windows logs. You need to get the Module name and Offset, plus Crash Code. FSUIPC makes a log in any case. It's in your FS Modules folder. Pete

It seems you definitely have either a hardware fault or a corrupted or mismatched Network driver system. There's no way WideServer itself can cause a BSOD, those things always indicate low level problems, hardware or hardware drivers. I can only suggest you try uninstalling the network hardware and re-installing it so that Windows will reload fresh drivers. Regards Pete

Oh dear. Try reading the files in an editor, eg Notepad. Cut the complete text from Notepad and paste into a message. Don't you know how to cut-and-paste? They are just text files. Have you never looked at or edited a text file, like a INI or CFG or TXT? The MCRO files are the same. Pete

I've come to the conclusion that it really is easier and better (more consistent) for you to manually move the mouse pointer to top left when you've finished using the mouse on a gauge, rather than let go of the mouse and press a button to make it move. So I'll leave the cursor off/on toggle option as it is, though it really doesn't have its originally intended purpose. Regards Pete

I need to see the files. They are text files. Paste their contents into a message, along with the filenames, so i can see why they "disappear"! Te;; me the full names of the ones which "disappear". Pete

If the .mcro file you saved them in is still there, they cannot just "disappear". Please paste the contents of the affected macro files, with their filenames, and tell me which you don't see in the drop-down list. Pete

The EXE is just a file, like any other. If something is deleting it then it is because you have something running which is deleting it. Maybe you have a virus checker which thinks it has got a virus? Certainly none of my programs can possibly delete themselves, and especially not without actually being run! That would be magic! Pete

Okay. Done. Please get MakeRunways 4.62 now available in the Download Links subforum. Pete

"Latest version" doesn't help. Do you mean 3.999z or 4.863 or some other "latest version". Please ALWAYS give version numbers! I can't even tell which version of FS you are using! After creating the macro file did you tell FSUIPC to reload? (The "reload" button on the Buttons and Switches tab). That tells FSUIPC to rescan the files in the Modules folder so that newly created ones will be discovered. Don't forget macros are listed with the macro filename first, then : and the macro name withing the file. A macro file can contain many macros. Pete

All FSUIPC access to devices is by standard Windows interfaces. It receives data from active devices, and not from others. There's no actions taking place inside FSUIPC to disconnect things. If something stops responding it is because FSUIPC is receiving nothing from them. I wonder if that problem was not related to this other one you have. Seems there's a general problem with USB on your system. So you don't really know if the POV still works in FSUIPC, nor if the other controls don't in FSX? . Sorry, but there really is nothing else FSUIPC can do to help here. It isn't overly complex code, just standard DirectInput. Regards Pete

Probably isn't modelled with a turning nose wheel. I wouldn't even notice that because I can't see the nose wheel from the cockpit! Pete

Hmm. I'm afraid I would be as perplexed as you. Whenever I've had any sort of networking problem I've only ever solved it by a system of trial and error -- in other words trying things till it works, with frequent reference to stuff o the internet, reading others networking prtobmes and seeing what other folks have tried. Normally data access okay one way but not the other implies some sort of permission or other access blockage, like firewall or Windows securities. But if you can read and write files on the Vista PC from the other, as you imply, I would have thought that showed that this area was fine. What would the Ping be accessing which makes it more intrusive than Explorer's file access? Pete

That is certainly the problem you need to address. Maybe a bad connection someplace. Please check the section in the FSUIPC user guidle about Joy Letters. If you change to using the Letters for joystick identifiers rather than numbers then FSUIPC will take care of matching the assignments for you. Just do it before experimenting. If FSUIPC were to keep rescanning and remaking assignments all the time your controls would be really really jerky. It isn't a short process. it has to scan the registry and do all sorts of Windows direct input calls to get the list of devices. It simp;y is not feasible, and most certainly sohlud not ever be needed. It is already able to do a lot more in this than FSX. I cannot explain your success with FSX assignment -- are you sure it copes with all axces and buttons? Try pulling the plug and pushing it in a gain. Here FSX has to be completely restarted to recover! Only the POV? Are you sure the POV wouldn't continue to work in FSUIPC? Why are you not assigning it in FSUIPC in any case? Pete

No. It was possible in FS2002 and FS2004, but not in FSX or P3D. The point of the FSUIPC Offsets Status document is to show the status of the offsets in FSX compared to previous versions. That's why it says "No" in both the read and write columns against that offset. Regards Pete

FSUIPC doesn't know or care about what thrust mode your AutoThrottle is in. Perhaps you need to disconnect FSUIPC's assignments to throttle when A/T is active -- there are FSUIPC-added controls to for "throttles off" and "throttles on" (even "throttles toggle"). But note also that FSUIPC does NOT send throttle commands unless the throttle axes are moving. Maybe you have too much jitter in the axes, in which case you need to park them in a stable position, like full or idle. Otherwise I think you'll need assistance form PMDG support. I'm afraid I do not use their aircraft at all. You could use FSUIPC's logging to see what it is doing. There are plenty of ways of investigating, but I'm afraid not being a PMDG user I cannot really help. If you do find more information and you need it explained, by all means show me and I'll do my best. Pete

Are you sure the G5 nose wheel is animated in such a way? Doesn't rudder steer that aircraft on the ground? You don't mention which version of FS you are using, but if it is FSX or P3D then there is a steering axis supported. In FSUIPC you can assign a single control lever/axis to up to 4 controls, so i would be no problem to set the aileron movement on your yoke to also operate the steering. Pete

Don't use "Filter" unless you have a really poor power supply. It's only there to cope with really bad controls. You have a conflicting assignment then -- some other axis (even one no longer connected) assigned to spoiler. Check FS as well as FSUIPC. Pete

I'll experiment and get back to you. Pete

Ugh! Must not only slow loading down, doing all that copying, but also cause all that scenery to take up loads more disk space. Is Aussie123's VOZ scenery being used on CD or a separate PC, I wonder? Anyway, the important thing for MakeRunways is this: So I'll only look ar "Remote=" if the "Local=" is blank. Note that before running MakeRunways you'll need to make sure the CD or Networked PC is online. Thanks & Regards Pete

Okay, thanks. Really it will be an easy change to make the program use the Remote line instead of the Local if the latter is blank. It just never occurred before. The only thing I need to know is which it takes if both are given. But I can experiment here on that -- Monday. I don't remember seeing a way of selecting 'remote' there, so I'd guess the entries were made automatically by the Installer. Weirder, if it is truly local to the FS9 folder. But if it is simply an alternative way of doing the same thing, I can fix MakeRunways to handle it easy enough. But Monday, as I said. Regards Pete

"Remote"? Is that ever used? I've never seen any use for it. I have my sceneries placed on several separate drives to FS and they are all identified by the Local parameter. Even the ones withing the FS folder itself have full path names so I can use the same SCENERY.CFG file with both FSX and P3D. Did you deliberately add them in as "remote" by editing the file or were they generated like that in some other way? This is new to me. What is it supposed to mean? i thought it might mean "elsewhere, not on the system, maybe on the Internet"? If all it means is "another place just like Local, treat the same" then I don't understand why it's there. And what if both Local and Remote have paths in? What would that mean? If you understand all this, as a user of this option, perhaps you'd explain it and I'll see what I can do to make MakeRunways cope with it properly. It is most odd that it has never cropped up in the 12 years or more that MakeRunways has been in use! I'm afraid I'm away now till next Monday, 11th March, but i'll certainly sort it out then, so please see if you can come up with a definitive explanation. I might catch it in the morning before I depart, but not solve it till next week. Regards Pete