Pete Dowson

I still need to edit it to read it. Why keep all those lines you don't use? [Devices] 1=Primary Sound Driver 2=SB Audigy 2 ZS Audio [DF00] [Polling] Epic=10 Var=5 [Sounds] Path=ESounds 2=nappminimums 4=nminimums 12=nv1 13=nrotate [Triggers.ERJPANEL1] 2=ALTITUDE_ABOVE_GROUND<=410, 2,0 4=ALTITUDE_ABOVE_GROUND<=210, 4,0 12=AIRSPEED>= 138, 12,0 13=AIRSPEED>= 148, 13,0 [SwitchedTriggers] 1=OnGround 2=InAir [Triggers.InAir] 2=ALTITUDE_ABOVE_GROUND<=410, 2,0 4=ALTITUDE_ABOVE_GROUND<=210, 4,0 [Triggers.OnGround] 12=AIRSPEED>= 138, 12,0 13=AIRSPEED>= 148, 13,0 Not sure why you have the line numbers matching the waves in each section. the Trigger line numbers are irrelevant apart from controlling order of execution. Is the [Triggers.ERJPANEL1] section correctly named for your aircraft? It seems an unlikely aircraft name -- you can see the aircraft title in FSUIPC's Flaps calibration section. I don't remember too much, but I don't think the switched sections will actually do anything unless you have some triggers which operate the switches. Well there's no point in using the Path= statement to give the path, then adding the same path to all the entries. The whole point of specifying a path for all the Wave files is to save you entering it in each line. I suppose it should work, it just seems very strange. You'd normally only specifiy an individual path when the WAVE file is elsewhere. I suppose the wave files ARE there? If you don't specify one it uses the default one in Windows. That's all I know. Sorry. Regards Pete

Well, the only changes have been improvments in the reliability of the reads and writes. Sounds like there was some misunderstanding in the original protocol. Right. stop there. Do you write this as one FSUIPC_Write of 8 bytes? If not you must write the signature second, not first, as this acts as the trigger. No IPC read logging works identically to the write logging. It has never not worked. It is essential for program development and i use it all the time. Regards, Pete

There's a set of 64 bytes from 66C0-66FF for general use -- they are used in the examples for the GFdisplay program I provide. They shouldn't clash with any registered application. Regards, Pete

It doesn't. There is no Internet stuff in WideFS at all. What else are you running? Pete

Sounds like the pot has shifted off-centre -- assuming you've not moved a trim lever on the device somewhere. (If you have, recentr it with that). Yes, FSUIPC canfix the centre, but you may have less sensitivity on one side than the other with the pot so mispositioned. As your yoke is well out of warranty it may be worth opening it and looking to see if you can re-adjust it. Pete

I shouldn't think so because the firmware only provides one code for each switch -- PFC.DLL cannot distinguish between identical codes. In fact I've no idea how you managed to connect two. I would assume they'd use the same driver circuits on the digital controller board and maybe even damage them. I'd re-check with PFC if I were you. Regards, Pete

That message from WideServer normally means WideFS is not registered. Check the WideServer.LOG file and the About/Register option in FSUIPC. Pete

Show me the FSUIPC Log please. Which FS2004 are you using -- it may need the FS9.1 upgrade. Pete

I'll look, but I haven't used Esound for many many years and probably will struggle to help. There's so much commented out there that I've edited it to read it: [Devices] 1=Primary Sound Driver 2=SB Audigy 2 ZS Audio [DF00] [Polling] Epic=10 Var=5 [Sounds] Path=ESounds 2=ESounds\nappminimums 4=ESounds\nminimums 12=ESounds\nv1 13=ESounds\nrotate [Triggers] 2=ALTITUDE_ABOVE_GROUND<=410, 9,1 4=ALTITUDE_ABOVE_GROUND<=210, 7,1 12=AIRSPEED>= 138, 11,1 13=AIRSPEED>= 148, 12,1 Now there are several things I think need checking: 1. Where is the Esounds path? If the path is set to Esounds, why is the "Esounds/" part also in most of the pathnames? 2. There's also only one sound actually referred to -- 12. Sound numbers 7, 9 and 11 were commented out, so those trigger lines are no use. You must relate triggers to the sounds else how does it know? 3. Where is the [settings] section and line defining the device, sound position and volume level for setting 1 which is all you are using? If you want to omit [settings] and just default it you need to either leave off the ",1" or use ",0". [Now I know this is explained in the doc]. Regards, Pete

What version of my PFC.DLL? If not the latest interim, please try that (above). Sounds very much like Windows power management. Go into the properties for the USB port and switch it off. Also, try putting your two USB devices on separate USB hubs -- the motherboard USB ports are in pairs. Try moving one of the devices to a different pair. Doesn't it say? 3000 milliseconds in 3 seconds. Regards Pete

How did it tell you? Was it in a line at the top of the outside view in FS? I don't know the FSRealTime option for that. If it is in the message window, maybe you've got the options set incorrectly? Check those on the "About/Register" page in FSUIPC -- check the early pages in the documentation too. Let me know. The new options work with all the programs I tried them with, but I don't know the FSRealTime one. Regards, Pete

On the rotaries I have each "click" sends eith a button down or button up, so I program both. If yours sends a complete pulse (down and up) for each click, then simply don't assign a control to the release. Pete

Yes, it should do. Pete

No idea, but I would presume that after a snowfall the ground is supposed to stay white. Maybe you could raise the temperature to try to melt it? I really don't know anything about the graphics in FS. Sorry. Regards, Pete

Yes. Where did you get the key from, and when did you buy it? Have you read the announcement at the top about needing FSUIPC 3.53 or later? Regards, Pete

Yes. Where did you get the key from, and when did you buy it? Have you read the announcement at the top about needing FSUIPC 3.53 or later? Regards, Pete

I would need more information to help. There is no A/T Arm facility built into FSUIPC. What are you using? Does whatever it is work with a default aircraft? Pete

The graduated visibility option in FSUIPC graduates the visibility from the top of the normal FS layer to a specified higher altiude, with an upper maximum there -- so it varies as you might wish. There's no upper altitude limit to the visibility restriction as in default FS -- though even in the latter you can set the upper level very high. Unfortunately though this produces the same visibility value all the way up. Regards, Pete

No idea, but FSUIPC casn only deal with axes which are dealt with using the original windows joystick interface - XYZRUV. There are only six. FS now uses DirectInput and I believe that can support more. Regards, Pete

Oh, that. No idea really. It isn't anything to do with FSUIPC, it relates to how the problem of passing pointers to data in managed (i.e. interpreted) languages which MS seems keen on these days. was solved. Maybe someone who understands how the managed languages work can explain -- I never get that far away from the machine. Regards, Pete

Sounds like the axis is using a Log pot, not a Linear one. Regards, Pete

Because WX and FLT files are saved by FS, not by an external program. The problem with the external program arises because it gets notified of the second save and gets its name before managing to react fully to the first one. Really, if you are keen on saving files manually it may be better to simply uninstall AutoSave. Use one or the other, not both. Regards, Pete

Actually the current version, the one supported, is 3.60, though there's also now3 a 3.601 available above with a small fix. Not really. FSUIPC doesn't use any keypresses at all unless you program them, either in the Hot Key or Keys sections. Maybe something else is trapping that key? The sort of crash you are seeing is generally related to video drivers and their settings. If you are using full screen, try Windowed mode, or vice versa, to see if it make a difference. ALT + ENTER toggles these modes. You may also find that changing the "render to texture" FS hardware display option may help, or small adjustments to the anti-aliassing and other settings in your video driver. Finally, you don't say, but if you have not updated your FS installation to FS9.1 do that -- there were many crashes of this type in the early version. Regards, Pete

Take a look at the documentation you already have for FSUIPC. You don't pay for a particular 3.xxx version, but all 3.xxx versions. In fact you are expected to upgrade otherwise you don't get support -- as it says above, in the assorted announcments, I only support the latest versions. The same applies to unregistered users too, by the way. I don't expect anyone to stick with old versions. Regards, Pete

No, as it clearly tells you in the first few paragraphs of the WideFS documentation (see Important Notes). Exactly. Not only that, but it doesn't even use FSUIPC to interface to FS, so how would it use WideFS which is merely an extension of FSUIPC onto other PCs? Regards, Pete