Pete Dowson

Good. I am pleased it is coming in so useful! Pete

That means little more than they are getting power. I have never heard of that. There used to be a driver called "TRClink". Is that not used these days? Well not the programming of anything in FSUIPC. I'm afraid I cannot speak for hardware changes. When you say "All the OH switches function o.k.", are they operating through this "USBFSUIPC" driver too, on the same USB link, or are those "BU0836X" boards from a different supplier? If the USBFSUIPC link is working for those but not for your other connected hardware then it must certainly be either the hardware or the driver configuration. Not really, as I cannot support hardware no other folks' drivers. It does sound like a hardware problem. If you want me to check whether FSUIPC is okay, when FS is closed grab the FSUIPC Log file and paste it in here for me to check. Regards Pete

Good! But I would like to know what the problem was if you can figure it out! Regards Pete

Actually it was so easy to fix (just changing a number in two places) that i've fixed it now. Please download WideClient 6.774 from either of the Downloads announcements. Let me know when you have an example you are happy with. It needn't be the "final" one (there's no such thing in this hobby, in any case -- we always tinker ). And please let me know if you mind being credited (by what name?). After all if it wasn't for you none of these new facilities would exist in any case. ;-) Regards Pete

Sorry, but I don't know. I've never tried it. I do not deliberately filter out the IP addresses to match any particular masking, so if anexplicitly supplied IP address (in the WideClient.INI file) refers to an internet-connected PC I don't see why it should not work. Let me know. Regards Pete

This is 277: 277=7G360"N" but where is line 360= to which it refers? The last line appears to be: 348=4G240"G1000\rMFD" It is probably defaulting to "Unused" because the place it is supposed to go doesn't exist. BTW if you post INI examples here could you (a) just post the relevant section (i.e. the ButtonScreen section here), and (b) "code" it (i.e. enclose it as a "code" example, using the button above the editing area). This will do two things 1. Make your message much much more readable, and shorter, 2. Make it much, much easier to extract your parameters for testing. [LATER] I've tried your example after changing line 277 to refer to an existing line (300 or 301), and you are right. It still isn't working. Looks like I've got an inappropriate "288 buttons" check in there. I'll fix it and post an update tomorrow (Thursday). Regards Pete

Yes, I am intending to come (depending upon a lift from a friend). Busy time -- I'm off to the FSWeekend at Lelystad this Saturday. Your stand is Alpine Computers I assume? Regards Pete

Don't you scan the Announcements? Check the FSX Downloads one. That's where it was always destined to go, as it is where all the FSUIPC4 interim updates go! I did actually tell you to look there, and you said you would! Pete

Well that's a sure indication all in not well in the Server PC. WideFS should have no measurable impact on your FS performance. My cockpit runs with at least 8 and often 10 PCs linked via WideFS, all pretty busy with several FSUIPC-interfacing applications on each, and there is no noticeable difference in the frame rates with it enabled or disabled. It sounds as if all the time is being spent deep in the Windows TCP/IP stacks try to recover from some problem or other, and not succeeding. In view of this I would doubt that changing ports will accomplish anything. Something else is wrong. I would really recommend first trying to uninstall and re-install all of the Network components of the system, to try to recover from any corruption. [LATER] I just saw your subsequent message. You went even further than I recommended then! Sowhat's blocking it now? Firewalls again? Regards Pete

Really? Ouch. You've got something really weird going on there. What sort of frame rates are you getting them? Must be down near zero! (Shift+Z twice for frame rates). Are you using fixed IP addresses, or letting a router assign them? Possibly the router has some settings restricting access. If you are using fixed IP addresses and have the Gateway IP address entered correctly in both PCs you sohuld be able to see the Internet on both. It could well be related. When you say "I have full read/write access on both machines from both machines", what exactly do you mean? Just that Windows Explorer can see the folders on the other PC and can read and write to them? Surely only on those you've shared, not on them all? Anyway, we know the broadcast from the Server to the client works. That's on port 9002. I wonder if somehow you have port 8002 closed, either in Vista's settings or in the router. Maybe you could change it to, say, 9003, in both WideServer.INI and WideClient.INI and see if that works around it? I'm grasping at straws here I'm afraid. Whenever I've had Network problems I've had to seek help from folks who know Networks -- Katy Pluta is pretty good. She occasionally visits the FSX Forum here, maybe the FS2004 Forum too. In the worst cases of problems I've had I've uninstalled the complete netwrok, reset the modem/router, and started again -- with success, I might add. I've also had two NIC (Network) cards go down on me. These days all motherboards have Ethernet ports and they do seem more reliable. Regards Pete

No. What do you mean by "refreshes"? There should be no noticeable effect of having WideFS running. I'm sorry, but there is most certainly something blocking your Network. I'm afraid I have no idea what it is, but neither end is seeing anything from the other on Port 8002. In the 12 years of WideFS this has always meant either a broken network or a firewall problem. Pete

If there aren't any functions to assign to, you cannot assign them. It is really that simple. For some add-on panels you may be able to add functions yourself using the Mouse Macro facilities. For other add-on programs which use keystrokes you can assign keystrokes. If they are not susceptible to either but you can operate them with the mouse you may need to purchase Luciano Napolitano's "Key2Mouse" and then program keys to operate the mouse. Have you looked very hard? I don't think so! There are most certainly controls in the lists for all three of those standard FS functions. If you have difficulty searching the lists, just enable FSUIPC's "event" logging (on the Logging tab), operate the controls with the mouse, then look in the FSUIPC Log file to see what control it used, if any. Regards Pete

It isn't anything to do with any application. Your Network isn't working, or at least it isn't only the standard ports WideFS uses. There's no point in doing that -- as you can see from the log you posted, the client is getting those details okay from the Broadcast! Of course not. You've not done anything to change whatever it is that is stopping it. The WideServer log might help. It is never any good withholding half of the information. But it still looks most likely to be a firewall problem. Regards Pete

At least now it is receiving the Broadcasts. Did you make the Workgroups the same? Continual time-outs every 20 seconds or so mean it isn't receiving anything from the Server on its normal (non-broadcast) port. The normal reason for that is a firewall, or else something else is using the same port (8002). You only provide half of the story. Where's the WideServer log from the FS PC? Regards Pete

FSUIPC will be useful in any case. Read the user guide -- I think you should find it well worthwhile. As for "doing something about it" I'm afraid you are probably on a hiding to nothing there. By all means ask SimMarket -- they are the traders, not I. I provide technical support and do all the development work, I have nothing to do with sales. Regards Pete

Compatible? Yes, and FS2000, and even FS98, CFS1 and CFS2 at a push. But I'm afraid I do not re-test each new version on anything earlier than FS2004, so, whilst the intention has been all along to maintain backward compatibility, if it has in some places gone wrong I'm afraid I'm unlikely to be able to fix it now. However, if you do find a problem, let me know. Don't expect many, if any, of the newer offsets and facilities to work, though. The subset which always worked on FS2002 should certainly still work. Oh, one more thing. If you do want to report anything, please always first try the latest increment from the "Other Downloads" Announcement above. That would be the version I would need to test with. Currently it is version 3.847. Regards Pete

Seems so. Really it is best to actually read a little of a program description before buying it. WideFS is nothing to do with screens or visuals in any case. First off, it is for linking programs running on a Networked PC to a copy of Flight Sim running in a server PC -- i.e. it is for Networks. Second, it is not for extending FS visuals like panels or scenery, but for other, external programs, running on their own, outside FS, using the FSUIPC interface. There is a program called WidevieW, by a different author (Luciano Napolitano), which is also for Networks, which links multiple copies of Flight Sim so that different visuals from the same user aircraft can be obtained. That is usually used for extraordinarily wide scenery views. For multiple views on a single PC, using two ports of a single video card, or multiple video cards, or a Matrox TripleHead2Go device, the facilities for undocking panels and windows in FS itself suffice. You need no add-on programs at all for that. However, note that having more that one 3D (scenery) window will cut frame rates dramatically. Dragging undocked panel windows to other screens works quite well, though, especially in FS9 and before (it seems it is a little more difficult in FSX to get them to stay put). Regards Pete

So, what is the question? You've not posed one. If you are simply putting forward an idea, then I think it probably belongs in the cockpit builders forum. If, on the other hand, you want to know if it is supported in FSUIPC, the answer is yes, of course, look at the right-hand side of the Axis Assignments tab, and read the example in the dox of a gear axis driving the Gear Up and Gear Down controls. In your case you'd need several zones of "Incs" going one way and "Decs" going the other, but the principle is the same. it isn't like rotary encoders because the latter have no predefined positions and. more importantly, no limits, so they can keep incrementing one way and decrementing the other. With an axis you have to determine the number of discrete steps you need to support and calibrate it for those. Regards Pete

The broadcasts from the Server aren't reaching the Client. Maybe a firewall? Or you are not using XP or Vista on both PCs? Or they aren't in the same WorkGroup. You may need to provide the ServerName and Protocol explicitly in the WideClient.INI file if you cannot solve these problems. Please do refer to the documentation. No, the failure of IPX/SPX only matters if you wanted to use IPX/SPX. You can use TCP (default) or UDP without installing IPX/SPX. Pete

Er, slow down a bit. Why is this "driver" for the throtle trying to set flaps 0? Please expplain why that should be so. Axes are intercepted in any case unless they are assigned directly in FSUIPC's axis assignments for "direct to FSUIPC calibration". then the axis intercepts from FS are generally not wanted, and can cause problems for some add-ons (like the Level D 767). There's no point because FSUIPC3 always intercepts all axes. It was different on FSX because of the way intercepts have to work through SimConnect. It's a very technical difference, not a difference in user facility. I think you are seeking the wrong solution to a problem which isn't fully explained. If you can go into some more detail, p[erhaps I can see a better solution. Having a driver enforcing flaps 0 does not make any sense to me at all. Regards Pete

You have something wrong there, then. WideFS 6.7 is for FSUIPC3 and FS9 or before, not FSX. You have not enabled the WideServer facility in FSUIPC4. Maybe you've not even registered it via the installer? There is no WideServer.DLL nor WideServer.INI file for FSX. You are failing to read the simple instructions! Not with WideServer.DLL and FSX, they would NEVER have worked together. For FSX WideServer is built into FSUIPC4. Please read the instructions. Regards Pete

Download 6.773, now available via the Downloads announcements. I've added a facility for a page title, with its own colour number (8) and facilities to set two more colours (8 and 9). I've not managed to change the font, though. That involves a *lot* more code which I'm really not willing to get involved in. I'd be very interested in looking at your eventual results. Perhaps I could use than as an example, if you are using all these facilities constructively? What do you think? Regards Pete

Just assign to the Flaps Inc and Flaps Dec controls, instead of Flaps Down and Flaps Up. Then the same rocker can handle any number of steps (like the 4 in the Cessna, the 7 in the 747 and the 9 in the 737). Pete

It sounds like you are using an integer variable. Obviously the end value is going to be small, with many fractional parts, which your integer cannot hold. It would be okay (without the overflow) if you divided by the 65536*65536 before multiplying by 360, but then you'd always get zero (of course)! For anything like this ALWAYS copy the value you are reading into a floating point variable first. Only with floating point will you retain all the accuracy of the original in a useful form. Do the conversion after you have it safe in floating point. Pete

The former -- the "Unused" status is identical to the black reserved spot for the default PREV button on the first page, and the NEXT button on the last (though obviously there wouldn't be any further button numbers to displace in the latter case. The only uses intended for "Unused" were (a) for the old default layout to work the same WITHOUT displacing button numbers, as I now do not have 2 reserved positions on each screen for PREV / NEXT, and (b) possibly to act as layout fillers where you didn't want to waste real buttons but also didn't want to mix functions on the one screen. Don't use them to 'reserve' buttons for later allocation. Best to simply assign those blank labels (a space only -- omittted labels with give you the default, the button number). You can colour them black if you want, as long as you are clear that when clicked they will send the button number to FSUIPC.