Pete Dowson

Toe brakes? Try calibrating. Regards Pete

Excellent. And I see you posted it in User Contributions. Thanks! best Regards Pete

Wherever you put it, it will play on the client not on the main FS PC. I don't recall offhand what the default sound folder is for WideClient -- I think it is a Sound subfolder in the same folder as Wideclient -- but if you've already run that WideClient, just look in its INI file. The current default sound path is there, in the [sounds] section. Pete

I don't think so because it has already been shown that hiding the cursor isn't enough to stop the fps drop on those cockpits which have a lot of mouse spots. You can only stop the drop by placing the mouse off screen or letting FS itself hde the cursor. Pete

I don't really know VB, but aren't VB strings in wide character format, with two bytes per character? FS only uses plain ASCII, one byte per character. And also I thought whilst FS needs a zero terminator on strings, VB puts a length at the start instead? Mind you, I'm not sure about that either. Hopefully someone will contribute who knows VB. One other thing, again I don't know VB, but in C/C++, the '\' character is an escape character, so that controls like '\n' for newline can be included. To get a true '\' you have to use '\\'. Maybe the same applies in VB? Pete

Have you tested it? Counting "end"s, isn't there one too many? One for each "if then" makes 2 and one to end the function makes 3 in total, yet there are 4. Pete

Okay, please download and try FSUIPC 4.864, now in the Download Links subforum. I actually had most of the code needed in place already, for the HID device facilities in the Lua COM library, so I just made it call the same device re=scanning as used when you enter FSUIPC options. It only does this when notified, by Windows, of a HID device disconnection or reconnection. There will therefore be two such scans if a device momentarily disconnects. This will certainly cause a glitch in the control actions. but will at least recover without having to visit the FSUIPC options. Let me know how you get on with this, please. Testing here by pulling out a USB device and plugging it in again does produce a definite pause in flight (two -- one for out, one for in), but the control does then contiune operating. I may try differentiating between connection and disconnection -- ignoring the latter probably as something it can't really do much about. That should reduce the pausing slightly. Regards Pete

They must have been assigned in FSX, not in FSUIPC, if FSX needed restarting, as FSUIPC will re-detect them by simply visiting the options. I'm surprised "most games/software" don't notice disconnections, because they are fatal when DirectInput is used. However, I may do some research to see if I can spot a way which doesn't involve continuous scanning, as when the options menu is entered. I think I can get automatic notifications of disconnection, but I don't know how much more efficient I can make the reconnections. Regards Pete

Could easily be something else. Changing one module causes memory allocations to change. A bug which corrupts innocuous memory before corrupts vital memory now. Happens a lot. To suspect 4.86, which is in daily use on very many systems which don't crash, is not really as logical as you suppose. And you didn't say what the previous version of FSUIPC ("for a couple of years"?) was. Maybe another add-on which uses FSUIPC is using it in a way which was wrong but which has now been changed. There are all sorts of possibilities. I would help you if I had any information other than your accusations, but starting off by making strong assumptions helps no one. I'm away on holiday from Friday for two weeks, so if you want further help please try to make it snappy. Regards Pete

Okay. At a quick perusal, not checking everything for you, why create a directory called D:\esounds\sounds when you have the instruction pointing to a different drive altogether? See: Incidentally, why not just put whatever sounds you want into FS's "sounds" folder, which is the default path for the Lua sound library, and so save yourself all this directory hassle in the first place? Then you simply need ref=sound.playloop("turb.wav") And what was wrong with your original posted earlier? Do you also want all that other stuff? Programming in any sort of language, whether an easy scripting one like Lua or a complex one like C++ is an activity demanding a level of care and attention not often needed in normal pursuits. This isn't just a matter of expertise or experience but patience ans examnation. Inspecting each line of code is an important part of checking and debugging. Ask youself, at each step, whether it makes sense, is it going to do what you actually want. Regards Pete

Er, pre-defining is not a "technical term" to be looked up, it is basic English. It simply means "defining beforehand". In the context it was used, obviously simply before the function. I did actually say this, you did the same for sndlg and I said "As well as "sndflg" ... " if you look back! Pete

Just assign the aileron axis to both aileron and rudder, as I suggested. Pete

Sorry, it is really a question for scenery developers. Try the scenery design forum over in AVSIM: http://forum.avsim.net/forum/123-msfs-scenery-design-forum/ Pete

If you delete the INI file altogether (make a copy first, just in case you want to check back on anything), then the new one made by FSUIPC will have Profiles already enabled. Try to use profiles, assigning all similar aircraft (i.e. those with only livery or engine or winglet variations) to the same profile -- eg "737NG", I'm away from this friday until April 1st, so I'm afraid I won't be able to help during this period. Hopefully others can, though, whilst I'm away. Pete

Yes, and I told you the problem. you already have 127 macro files listed in the INI. FSUIPC cannot cope with more!!! Please READ my last reply! It would be "EZY320:extpwr", but none of the macros in that file will be listed for assignment because, as I said (and you seem to have ignored) there is no more room in the MacroFiles list! Why? Please please PLEASE read my previous reply more carefully. If any of the Macro files listed in your INI no longer exist, or can be deleted, do so. But as far as I can see your setup is in a complete mess. According to your assignments already made you have assignments to many of these Macro files, but not all. You could delete those not needed and delete the corresponding line in the [MacroFiles] section of the INI. for example, these don't appear to be used: (by number -- see the earlier list for names) 1-5, 20-23, 25-32, 35-41, 47, 57-62. There may be more, but I just haven't the patience to go through every one of your assignments to check. If you are really loathe to start again (which I still thoroughly recommend) then delete those macro files and those entries so that FSUIPC can pick up your latest macro file. I see you also have separate assignments for simple livery variations of the 737NGX aircraft. Why aren't they all assigned to the same 737NGX profile? It would make your whole set up MUCH more compact and simpler to manage! You seem to be wasting FSUIPC facilities by ignorting them! Why no Profile use at all? Pete

You edit the INI file and add the text provided!!! What else? You don't insert ANYTHING into FSX.EXE -- FSX.EXE is the FSX program! You use an editor, possibly Notepad, to edit FSUIPC4. INI and insert the text shown, simply replacing the "E:\FSX" part with the path to your FSX.EXE on your PC! It is assuming that you saved the Batch file called FSX.BAT to the FSX.EXE folder, that's all. As far as I can see the original text is in plain English. It isn't computer technical talk. I assume your first language is not English but maybe Spanish? I can try to explain in a lot more words, in English still though. Sorry, I don't speak / write any other. Regards Pete

And what about my other questions? This is taking a LONG time because you do not answer them. i.e. what is the name of the macro file you are trying to assign into? Is it in the Modules folder? Show me your FSUIPC INI file -- it lists all the macro files it finds.. what exact name are you looking for in the drop-down list? According to the INI file you have 127 macro files!!! That's the absolute limit! Look, here is the list of files (see below), each presumably with many macros inside? Which of these are you not able to find in the drop-down list? Which of these files is NOT actually in your Modules folder? It looks as if, for every aircraft you have created a separate file for each and every action -- presumably just one macro per file!!! That is incredibly wasteful! Each file can contain hundreds of macros. You should have just one file for each aircraft. Why on Earth did you not follow the instructions in the User Guide? I've never seen anyone get into such a mess before! You simply need to load the aircraft, start creating macros, make ALL of the macros for that aircraft, then end macro making. You'd name the macro file for the aircraft NOT for one of the macro functions in the file! I can really see no alternative for you but to start again. To merge all those macro files and to edit all of your assignments is just going to take longer and will be very very error prone. I recommend that you delete all the .mcro files in your Modules folder, and delete your INI file, and start again, aircraft by aircraft. Whilst I could probably increase the limit beyond the current 127, it isn't really the answer and would involve quite some work for me in FSUIPC3 and FSUIPC4. It really should never be needed. For someone to have more than 127 cockpits just isn't realistic. FSUIPC can cope very well with many more actual macros, but it does so in an efficient way, not by having loads of little files each with just one line to be read! Pete List of macro files:

I'll answer here this time, but please use the Support forum next time. This subforum is the Download Links subforum, providing links to my files for download. On that point, how come you are in "download Links" and didn't even see the PFC stuff listed in the Update Modules thread? Also the PFC drivers are prominently listed in the very same website where you must have obtained FSUIPC in the first place. However, if your PFC equipment was in use with the Elite simulator, it may not be compatible with FS. You'd need to check with PFC. Elite uses a completely different protocol which is proprietary to them and which I've never been privy to. Regards Pete

What "macro you just created"? I thought you'd made a macro file as you showed me. Have you gone back to making single macros then assigning? Why not use the file you showed me? And what is the name of the macro file you are trying to assign into? Is it in the Modules folder? Show me your FSUIPC INI file -- it lists all the macro files it finds.. And what exact name are you looking for in the drop-down list? Pete

Testing is needed as well as inspection, but at a short read my only comments would be: 1. As well as "sndflg", ref needs pre-defining before the function, because the way you have it it is local to the function and therefore created and destroyed on each call because of the event. 2. All '\' characters in the path string need to be \\, not just the first, because \ is an escape character used also to define other control characters, like \n for new line 3. You don't really need the sleep call unless you want the sound to play for 1 second minimum Regards Pete

Well every time this has been reported it has been fixed by the Registry change which is documented somewhere on their support site and which I'm certain was originally posted by one of their support staff -- probably before Saitek were taken over by MadCatz. I expect no one there knows how to support the things these days. I think it's simply to do with the way the axis is defined in the Registry. Regards Pete

Try Saitek support. It is obviously a Saitek problem. Pete

Go to FSUIPC buttons & switches tab, press a button, select FS Control, and in the drop down select the macro you want on that button. It IS that simple. The macro will be identified by the macro filename followed by the individual macro name. It is really easy. Why are you so puzzled? Pete

All virus programs I've ever used have ways of overriding false positives. Is there no Help or documentation? It's a false positive. Wideclient is compressed and the compression creates binary patterns which are not code at all, but may contain fragments which virus checkers without more extensive checks think are viruses. You either need to overide it or report the false identification to AVAST so they can improve the checking for that specific virus, whatever it thinks it is. Pete

I don't really know much about WidevieW these days. i've not even looked at it since FS2000 days, but it is a system for linking multiple copies of FS. I guess you could have the GPS running on one copy of FS, the 'master', with the actual cockpit, with the visuals only on the other. You'd be better off asking such things on the WidevieW support forum though. Note that you wouldn't use my WideFS on the same client PC as a WidevieW client because that client would be running FS as well. Pete