Pete Dowson

It sounds plausible, but if so it seems to be rather a serious error in the design of that part of PM. What does Enrico say? He will surely know that there are folks with individual throttle controls. Please keep me posted. Pete

It sounds plausible, but if so it seems to be rather a serious error in the design of that part of PM. What does Enrico say? He will surely know that there are folks with individual throttle controls. Please keep me posted. Pete

Yes, of course you do! The Server is the one "serving" the clients. No client knows about any other clients! Furthermore, the shutdown facility is done merely by setting an offset in FSUIPC which is read by all clients. If FS isn't running, then neither can FSUIPC or WideServer, so there is nothing going on between any of them! This is why the shutdonw facility in WideServer is delayed by a number of seconds, to ensure all Clients read the message. Pete

Yes, of course you do! The Server is the one "serving" the clients. No client knows about any other clients! Furthermore, the shutdown facility is done merely by setting an offset in FSUIPC which is read by all clients. If FS isn't running, then neither can FSUIPC or WideServer, so there is nothing going on between any of them! This is why the shutdonw facility in WideServer is delayed by a number of seconds, to ensure all Clients read the message. Pete

I'm sorry, but I've not heard of this "Safeline" console. It sounds like a piece of hardware from what you say. Does it have a driver running in the PC? If so is it an EXE talking to FSUIPC, or a module or gauge for FS? Does it even use FSUIPC? >> I have contacted the manufactur for the last three month and tried different things including replacing the CPU on the console. << Ah, so it definitely is hardware! >> The console uses the COM port. It seems that the computer does not recognize the console anymore. << Right. So there is some driver which you must be loading in the FS PC. Is this an EXE? OR have you installed something into FS? It is this which is most suspect I think -- either that or your COM port has become inoperable for some reason. Maybe you've changed your PC configuration and the COM port IRQ is being shared? That might not be good. >> I tried to revert back to the older version of FSUIPC, it did not help either. << Well that most certainly eliminates FSUIPC in any case -- FSUIPC does no permanent changes. If you revert, you revert. >> I have read the posts on this forum and documents came with the update and could not find an answer. << I think you need to look at what the console driver is doing, and whether that has been corrupted or whether something is amiss with the COM port side of things. Pete

I'm sorry, but I've not heard of this "Safeline" console. It sounds like a piece of hardware from what you say. Does it have a driver running in the PC? If so is it an EXE talking to FSUIPC, or a module or gauge for FS? Does it even use FSUIPC? >> I have contacted the manufactur for the last three month and tried different things including replacing the CPU on the console. << Ah, so it definitely is hardware! >> The console uses the COM port. It seems that the computer does not recognize the console anymore. << Right. So there is some driver which you must be loading in the FS PC. Is this an EXE? OR have you installed something into FS? It is this which is most suspect I think -- either that or your COM port has become inoperable for some reason. Maybe you've changed your PC configuration and the COM port IRQ is being shared? That might not be good. >> I tried to revert back to the older version of FSUIPC, it did not help either. << Well that most certainly eliminates FSUIPC in any case -- FSUIPC does no permanent changes. If you revert, you revert. >> I have read the posts on this forum and documents came with the update and could not find an answer. << I think you need to look at what the console driver is doing, and whether that has been corrupted or whether something is amiss with the COM port side of things. Pete

Page 1 is the "all engine" throttle with no reverse section. Page 3 are the individual throttles for each of up to 4 engines. Those have reverse sections. They are different FS axis controls. Please see the FSUIPC documentation where the controls are listed in the tables. >> I am assuming that the problem is related to the "Axis_throttle_set" and "Axis_throttle1_set", "Axis_throttle2_set" etc in the FS joystick setup linking to different values in FSUIPC and that the PM software is reading from a differing value. << Sorry, I've really no idea what you are talking about here. Before even attempting to use FSUIPC's joystick facilities you do need to get things working normally. Apart from the special mapping facilities in FSUIPC, the calibration is only a final "tweaking" of the values just before they get to the FS simulation engine, for more precise null and centre settings. If PM's Airbus processing is at all realistic (i.e. fly by wire) your joystick inputs, including throttles, would actually be disconnected from FS in any case and manipulated by the flight management system, even without auto-throttle or A/P engaged. There are facilities in FSUIPC to allow this to be done -- but you will have to ask PM support what is actually going on I'm afraid. Meanwhile, either delete the joystick section from your FSUIPC.INI file, or press the "reset" button in FSUIPC options for each axis, and get everything reasonably working without FSUIPC calibration first. Only use it to "sweeten" the results afterwards. Pete

Page 1 is the "all engine" throttle with no reverse section. Page 3 are the individual throttles for each of up to 4 engines. Those have reverse sections. They are different FS axis controls. Please see the FSUIPC documentation where the controls are listed in the tables. >> I am assuming that the problem is related to the "Axis_throttle_set" and "Axis_throttle1_set", "Axis_throttle2_set" etc in the FS joystick setup linking to different values in FSUIPC and that the PM software is reading from a differing value. << Sorry, I've really no idea what you are talking about here. Before even attempting to use FSUIPC's joystick facilities you do need to get things working normally. Apart from the special mapping facilities in FSUIPC, the calibration is only a final "tweaking" of the values just before they get to the FS simulation engine, for more precise null and centre settings. If PM's Airbus processing is at all realistic (i.e. fly by wire) your joystick inputs, including throttles, would actually be disconnected from FS in any case and manipulated by the flight management system, even without auto-throttle or A/P engaged. There are facilities in FSUIPC to allow this to be done -- but you will have to ask PM support what is actually going on I'm afraid. Meanwhile, either delete the joystick section from your FSUIPC.INI file, or press the "reset" button in FSUIPC options for each axis, and get everything reasonably working without FSUIPC calibration first. Only use it to "sweeten" the results afterwards. Pete

You need the AllowShutDown in each Wideclient.ini and, if you want FS also to shut down, in WideServer.ini too. The Server maintains the command in the ShutDown offset for 10 seconds, or something like that, to give time to each of the others to see it, before it too closes. This works consistently here -- mixture of XP and 98SE PCs, TCP/IP. Pete

You need the AllowShutDown in each Wideclient.ini and, if you want FS also to shut down, in WideServer.ini too. The Server maintains the command in the ShutDown offset for 10 seconds, or something like that, to give time to each of the others to see it, before it too closes. This works consistently here -- mixture of XP and 98SE PCs, TCP/IP. Pete

Yeah. The control names are none too good in many cases. All FSUIPC does is read the FS assigned names from the CONTROLS.DLL, so it gets what MS called them internally. It's the only was FSUIPC can get the correct list for each version of FS without me building in losts of extra data. Regards, Pete

Yeah. The control names are none too good in many cases. All FSUIPC does is read the FS assigned names from the CONTROLS.DLL, so it gets what MS called them internally. It's the only was FSUIPC can get the correct list for each version of FS without me building in losts of extra data. Regards, Pete

Of course, they can program it how they like. Maybe they didn't like the way the FS A/P controlled vertical modes, but were happy with the horizontal control. You'd have to ask the authors. Regards, Pete

Of course, they can program it how they like. Maybe they didn't like the way the FS A/P controlled vertical modes, but were happy with the horizontal control. You'd have to ask the authors. Regards, Pete

Please use the FSUIPC weather logging (see Technical page) to help figure out what is happening. Maybe also enable IPC write logging. If you need me to check it, zip the appropriate log and send it as an attachment. Try to keep it short, please. Pete

Please use the FSUIPC weather logging (see Technical page) to help figure out what is happening. Maybe also enable IPC write logging. If you need me to check it, zip the appropriate log and send it as an attachment. Try to keep it short, please. Pete

All FS controls and then some can be assigned to buttons or keystrokes in FSUIPC's Buttons and Keys pages. The Taxi light switch is "Toggle Taxi Lights". Pete

All FS controls and then some can be assigned to buttons or keystrokes in FSUIPC's Buttons and Keys pages. The Taxi light switch is "Toggle Taxi Lights". Pete

Probably just not reading the documentation well enough? . Sorry, but I couldn't resistyou'll see it explains that this cannot work, in fact never did work, if you have Windows options set to show windows whilst moving them. I think XP defaults this on, for example. Regards, Pete

Probably just not reading the documentation well enough? . Sorry, but I couldn't resistyou'll see it explains that this cannot work, in fact never did work, if you have Windows options set to show windows whilst moving them. I think XP defaults this on, for example. Regards, Pete

If they do not use the Microsoft Autopilot for these things then there will be no "offset". The A/P variables will likely be maintained internally to their A/P gauge. Regards, Pete

If they do not use the Microsoft Autopilot for these things then there will be no "offset". The A/P variables will likely be maintained internally to their A/P gauge. Regards, Pete

FSMeteo and Radar Contact V3 -- yes. FSNavigator, and panel components -- no. The latter are not separate programs but only modules of FS and cannot run except inside FS. There are separate instrument sets, such as Project Magenta (payware) and FreeFD (freeware) which you could investigate. There are links on the Schiratti site. Regards, Pete

FSMeteo and Radar Contact V3 -- yes. FSNavigator, and panel components -- no. The latter are not separate programs but only modules of FS and cannot run except inside FS. There are separate instrument sets, such as Project Magenta (payware) and FreeFD (freeware) which you could investigate. There are links on the Schiratti site. Regards, Pete

Sorry, I really know nothing about Squawkbox or VATSIM. Possibly SB is assuming it is talking to FS2000 or even FS98? The Multiplayer protocol changed between some FS versions. If no one else here can help I would suggest you might get better help with the Squawkbox folks. Do they have a forum or support site? Regards. Pete