Pete Dowson

There is a stall warning horn implemented in most (all?) of the FS aircraft. No. VASI and PAPI, etc, are purely visual. If you can't see them properly you should be doing an instrument approach, not a visual one, or seeking an alternate airport if you are not Instrument Rated. Depends on what the failures are I should think -- and anyway not many things are repairable in flight. Emergency procedures usually involve using alternative methods or instruments, and so on, not performing actual running repairs. There's not normally enough time to repair anything even if the diagnosis was easy. The priority is to fly the plane. There is a flight recorder (black box) application. "FltRec" I think it is called. You can probably get it on several FS download sites. I don't know exactly what it records I'm afraid. Pete

Hmmm. Very strange. Everything else looks right now. so now I've really no idea what Windows can mean by "Socket type not supported". Windows documentation says "The support for the specified socket type does not exist in this address family. For example, the optional type SOCK_RAW might be selected in a socket call, and the implementation does not support SOCK_RAW sockets at all. " The "socket type" I am asking for in WideFS is SOCK_SEQPACKET. Now this was new to Winsock Version 2, but Winsock 2 was most definitely introduced with Windows 98 (and possibly 95 SR2, but I cannot remember -- it wasn't part of the original Windows 95, I know). So the only conclusion I can draw is that your Win98SE installation is in error, possibly corrupted or changed by something else that's been installed. Try running the System File Checker (SFC, accessible through System Information I think). Maybe re-installing Win98SE over the top will recover it. But first of all, in case it is down to your NIC driver, try re-installing the NIC itself -- delete it from the Windows System-Device Manager list, then re-booting and re-installing its driver(s). I really can't think of anything else. sorry. Pete

Well I suppose a program interfacing to multiplayer could do that. It isn't an area I know anything about I'm afraid. Perhaps someone who has actually used, and, better, programmed, MP could jump in here. [Jose, are you here?] Regards, Pete

FSUIPC has options to prevent turbulence, in clouds or in clear air (winds section), or to induce random turbulence. Be warned that with either form of turbulence enabled you will get poor frame rates in areas of denser AI traffic, so you may want to turn them down. All this stuff is covered in the FSUIPC User Guide, and it should be easy enough for you to find the options in FSUIPC's options (look for the word "turbulence" in the Wind and Cloud pages). I expect FSMeteo has options for some things too. Have you looked? Pete

You say you are using WideFS 5.50, but the WideClient LOG shows otherwise: You should use the matching WideClient which was inlcuded in the WideFS 5.50 package. The above error message most certainly shows that WideClient is trying to use a protocol you've not installed. You do not show your WideClient.ini file, but the default protocol bfore version 5.50 was IPX/SPX, so that could be the reason. For TCP/IP you will also need to provide the ServerName in the Client INI files, of course. Pete

Yes, there's no use for the parameters in those two controls. If you wanted a button to set, say 50% spoiler deployment then you'd use the Spoilers Set control with a parameter like 8192 (maybe -- I can't remember off-hand whether the spoiler runs from 0 to 16383 or to 32767, or neither). Mostly, when using a control with parameters, it's a matter of experimentation. Pete

All of the "AXIS ..." and "... SET" controls for FS use a parameter too -- for Axis controls it would be the value of the joystick input, and so on. the example given in the FSUIPC documentation for the KOHLSMAN_SET control shows the parameter being used to set the value for an Altimer setting of 1013.2 mb (29.92"). For FLAPS SET you'd work out what parameter values you need to enter for specific flap settings (this would vary according to the number of detentes). And so on. If you are not using any of the controls which accept a parameter then it is irrelevant. Do not worry about it. Pete

Hmm. I don't know it, maybe Chris will chip in here, but you'll need to check its "cycle" time and what your code is doing to find out where those extra seconds are coming from. Certainly WideFS will be easily capable of sending updated values at rates similar to FS frame rates -- in fact you can get the WideClient frame rate displayed in its title bar -- there's an option for that in the INI. Check the dox. Project Magenta would be out of business if its instrumentation was several seconds out rather than pretty well instantaneous, and its Autopilot, running on a separate PC, would lose control in no time! Regards, Pete

That's exactly what Lago's "FSAssist" did for you, automatically, in FS2000 -- it had different settings you could adjust for different modes of flight -- taxi, takeoff, climb, cruise, descent, landing. That sort of thing. For some reason in the FS2002 version they only monitor these settings and allow manual adjustment by hotkey. I don't know why the automatic adjustment was removed. Possibly because FS stops and reloads textures et cetera when some of the settings are changed? I really don't have a clue where in FS they get these parameters nor how they adjust them. Maybe one day I will have time to do some research and find out, but if FSAssist is also provided for FS2004 I would not want to undermine their product in any case. This is precisely what the Graduated Visibility option in FSUIPC is for. You don't need to reduce the "maximum" only the actual setting, which is what FSUIPC does. Regards, Pete

What are you using to get such a delay? If this is with WideFS, there's something strange going on in your code -- there are many folks using cockpits powered by Project Magenta, using WideFS with multiple clients, and the PFD/AI/ND et cetera run at the same frame rate as FS. In fact since version 5 that's exactly what WideFS is designed to do -- send every Client updates at the FS frame rate. The latency is just a few milliseconds. Pete

Yeah, I downloaded it to check and it is definitely faulty on the Schiratti site. I did this immediately after replying to you and then immediately wrote to Enrico to tell him, but I assume he's out for the day/weekend with his family. Did you write? All my modules also go to Avsim, the PFC site itself (flypfc), and a load of others -- about 50 places altogether, all by request. Now some of those are software developers or magazines, not web-sites hosting files, but I don't know which are which without asking them. And I think many of the sites now either only post up selected modules (possibly only FSUIPC) or simply link back to Enrico's. I can email it to you direct if you have no joy soon -- I did try attaching it here, but there seems to be a limit of 125kb on attachments so it wasn't accepted. Sorry. Pete

Not when it left here to over 50 sites, via my normal distribution method. The ZIP is 1.2 Mb or so. If you have problems downloading from any site you need to check with them. It may well be your caching not the site at all. I can't do anything myself, I have no web site. Pete

Not that I know of. Only one of the PCs can actually be simulating the flight, so all the control inputs (rudder/elevator/aileron/throttle etc) have to be input to that PC. I did do a facility to link multiple ISA Epic Cards across a LAN, and you could have duplicate inputs that way. But it isn't terribly good because of the Network latency - ok for airliners perhaps, certainly not for aerobats and fighters. If your pilots are both actually in the same room, sitting next to each other as in a real aircraft, then all you are really talking about is dual controls. that can most certainly be done -- FSUIPC provides multiple axis input facilites (see the Advanced Users guide). But you are then talking about one FS simulating PC again --- if you want a nice wide view then consider projection or use a Parhelia with three large screens configured as one wide one. You could use WidevieW and separate PCs, but your control inputs still all need to be directed to the serving PC, the one actually simulating the flight. Hope this helps. Pete

It's the "/2" at the end of the Reverser= line in the [JoystickCalibration] section. Just delete the "/"2". Good catch by the way -- the inability to remove it in the Options page is a definite bug. It'll be fixed in the next version of FSUIPC. No one else has mentioned it! Regards, Pete

Ahsorry. I forgot completely about that special facility. Yes, you are right. It doesn't work now because, since about version 5 of WideFS I had to make WideServer's main message processing 'window' (an invisible one) a "top level" window rather than one within FS's enclave. I clean forgot that PFC sends messages to the Window and now it can't find it. I'm releasing an Interim version of PFC.DLL (1.53) with this fixed. The DLL now tries to find WideSever wherever it may be hiding! I've checked this here with RW on a Client and it works fine. Please take a look on the Schiratti site in a few hours or so. Thanks for the good "catch"! Pete

How are you configuring it? Are you assigning KeySends in the FSUIPC Buttons options pages, as described in the FSUIPC documentation, or doing it the older way, assigning the KeySends in the WideServer.ini? What settings have you got and do they match those you allocated in the WideClient.ini for "RWon" and "RWoff". Please cross-refer to the documentation which should be clear about all these, right down to the examples I added. WideServer does NOT send any button presses to clients. The KeySend mechanism is a way of sending allocated signals within the normal data distributed to clients. If your Client is receiving stuff for your applications it will receive KeySend parameters too as they are merely parts of the same data. It sounds like you simply have not defined matching KeySend numbers to operate RW. Pete

Sorry, you need to be more specific. What "client boxes" are these? Are you talking about WideFS and reading weather at the clients? The weather data distributed to clients by WideServer is the same as in FS, as you can see by running WeatherSet on the clients. How are you clearing the weather? There's a hot key assignable in FSUIPC's options which may be easier than going into the FS options, but they eventually amount to the same thing. If you are instead talking about mutliple FS installations linked by WidevieW, then this is a question for Luciano Napolitano, author of WidevieW. He has a website I think. Regards, Pete Dowson

Yes, I think I'm going to have to. Two answers to that: 1) I can provide free keys for true freeware. The rest of FSUIPC doesn't have to work to allow applications to interface to it. The user doesn't get any options if he doesn't pay, and other programs won't work unless they are keyed in or subscribed. 2) If someone else did a replacement for FSUIPC then that would also be good. I could get on with something else, something that did earn money. It's just that for several years it has been a FULL TIME job, which doesn't look like lessening, and I cannot afford it now I've only got a pension to look forward to. You should not worry. I am thinking through all the angles and devising ways of doing everything needed. I am going to be as fair as I can be. Regards Pete

I don't use C# but in C/C++ these are what they say -- type "float". You just read them into a variable defined as "float". This is why I defined them like this, to save you any conversion problems! It was different in the FS98 offsets areas, those units were feined by MS long before I started this stuff. Pete

I tested this today and it works fine here. I cannot think what is wrong there. Make sure you have a line AFTER the ControlName line, just in case. Maybe Windows doesn't read parameters which don't end in a new line control. Pete

Yes. FSUIPC consists only of a DLL. One module. When you place it into the FS Modules folder it replaces any previous one. It has to -- you can only have one file with that name. The file system does not allow multiple files with the same name in the same place. Just never RENAME FSUIPC to anything else. Flight Sim loads any modules it finds in the Modules folder, it doesn't care about the name, so you can easily get duplicates then -- but only by renaming. Don't do that and you won't get into trouble. Pete

If you mean via the FSUIPC interface, there is none. The interface provides access to FS's internal settings for each engine. However, there is a facility for "throttle sync" -- if you set bit 2^4 (i.e. value 16) in the byte at offset 310A (=12554 decimal) then your throttle 1 values will be applied to the other three. You can access this facility also through a Hot Key, programmed in the FSUIPC Hot Keys page. That's a question for Andrew at http://www.747mcp.com I think. Pete

The error numbers don't go up that high. Maybe 10040 or 10044? The numbers and their messages are just those returned by Winsock (or, in your case, presumably an emulation of WinSock?). Here's a full list for you (in name order, not number. sorry). Looks like yours was 10044? If so then the Linux implementation of WinSock does not support the facilities needed by WideFS. In case it helps, these are the calls used by WideFS to obtain a socket: For IPX/SPX (uses SPX, sequential packets) socket(AF_NS, SOCK_SEQPACKET, NSPROTO_SPX) : For TCP/IP (uses IP streaming, not UDP) socket(AF_INET, SOCK_STREAM, 0); ======================================= The following is a list of possible error codes returned by the WSAGetLastError call, along with their extended explanations. Errors are listed in alphabetical order by error macro. Some error codes defined in Winsock2.h are not returned from any function—these are not included in this topic. WSAEACCES (10013) Permission denied. An attempt was made to access a socket in a way forbidden by its access permissions. An example is using a broadcast address for sendto without broadcast permission being set using setsockopt(SO_BROADCAST). Another possible reason for the WSAEACCES error is that when the bind function is called (on Windows NT 4 SP4 or later), another application, service, or kernel mode driver is bound to the same address with exclusive access. Such exclusive access is a new feature of Windows NT 4 SP4 and later, and is implemented by using the SO_EXCLUSIVEADDRUSE option. WSAEADDRINUSE (10048) Address already in use. Typically, only one usage of each socket address (protocol/IP address/port) is permitted. This error occurs if an application attempts to bind a socket to an IP address/port that has already been used for an existing socket, or a socket that wasn't closed properly, or one that is still in the process of closing. For server applications that need to bind multiple sockets to the same port number, consider using setsockopt(SO_REUSEADDR). Client applications usually need not call bind at all—connect chooses an unused port automatically. When bind is called with a wildcard address (involving ADDR_ANY), a WSAEADDRINUSE error could be delayed until the specific address is committed. This could happen with a call to another function later, including connect, listen, WSAConnect, or WSAJoinLeaf. WSAEADDRNOTAVAIL (10049) Cannot assign requested address. The requested address is not valid in its context. This normally results from an attempt to bind to an address that is not valid for the local machine. This can also result from connect, sendto, WSAConnect, WSAJoinLeaf, or WSASendTo when the remote address or port is not valid for a remote machine (for example, address or port 0). WSAEAFNOSUPPORT (10047) Address family not supported by protocol family. An address incompatible with the requested protocol was used. All sockets are created with an associated address family (that is, AF_INET for Internet Protocols) and a generic protocol type (that is, SOCK_STREAM). This error is returned if an incorrect protocol is explicitly requested in the socket call, or if an address of the wrong family is used for a socket, for example, in sendto. WSAEALREADY (10037) Operation already in progress. An operation was attempted on a nonblocking socket with an operation already in progress—that is, calling connect a second time on a nonblocking socket that is already connecting, or canceling an asynchronous request (WSAAsyncGetXbyY) that has already been canceled or completed. WSAECONNABORTED (10053) Software caused connection abort. An established connection was aborted by the software in your host machine, possibly due to a data transmission time-out or protocol error. WSAECONNREFUSED (10061) Connection refused. No connection could be made because the target machine actively refused it. This usually results from trying to connect to a service that is inactive on the foreign host—that is, one with no server application running. WSAECONNRESET (10054) Connection reset by peer. An existing connection was forcibly closed by the remote host. This normally results if the peer application on the remote host is suddenly stopped, the host is rebooted, or the remote host uses a hard close (see setsockopt for more information on the SO_LINGER option on the remote socket.) This error may also result if a connection was broken due to keep-alive activity detecting a failure while one or more operations are in progress. Operations that were in progress fail with WSAENETRESET. Subsequent operations fail with WSAECONNRESET. WSAEDESTADDRREQ (10039) Destination address required. A required address was omitted from an operation on a socket. For example, this error is returned if sendto is called with the remote address of ADDR_ANY. WSAEFAULT (10014) Bad address. The system detected an invalid pointer address in attempting to use a pointer argument of a call. This error occurs if an application passes an invalid pointer value, or if the length of the buffer is too small. For instance, if the length of an argument, which is a SOCKADDR structure, is smaller than the sizeof(SOCKADDR). WSAEHOSTDOWN (10064) Host is down. A socket operation failed because the destination host is down. A socket operation encountered a dead host. Networking activity on the local host has not been initiated. These conditions are more likely to be indicated by the error WSAETIMEDOUT. WSAEHOSTUNREACH (10065) No route to host. A socket operation was attempted to an unreachable host. See WSAENETUNREACH. WSAEINPROGRESS (10036) Operation now in progress. A blocking operation is currently executing. Windows Sockets only allows a single blocking operation—per- task or thread—to be outstanding, and if any other function call is made (whether or not it references that or any other socket) the function fails with the WSAEINPROGRESS error. WSAEINTR (10004) Interrupted function call. A blocking operation was interrupted by a call to WSACancelBlockingCall. WSAEINVAL (10022) Invalid argument. Some invalid argument was supplied (for example, specifying an invalid level to the setsockopt function). In some instances, it also refers to the current state of the socket—for instance, calling accept on a socket that is not listening. WSAEISCONN (10056) Socket is already connected. A connect request was made on an already-connected socket. Some implementations also return this error if sendto is called on a connected SOCK_DGRAM socket (for SOCK_STREAM sockets, the to parameter in sendto is ignored) although other implementations treat this as a legal occurrence. WSAEMFILE (10024) Too many open files. Too many open sockets. Each implementation may have a maximum number of socket handles available, either globally, per process, or per thread. WSAEMSGSIZE (10040) Message too long. A message sent on a datagram socket was larger than the internal message buffer or some other network limit, or the buffer used to receive a datagram was smaller than the datagram itself. WSAENETDOWN (10050) Network is down. A socket operation encountered a dead network. This could indicate a serious failure of the network system (that is, the protocol stack that the Windows Sockets DLL runs over), the network interface, or the local network itself. WSAENETRESET (10052) Network dropped connection on reset. The connection has been broken due to keep-alive activity detecting a failure while the operation was in progress. It can also be returned by setsockopt if an attempt is made to set SO_KEEPALIVE on a connection that has already failed. WSAENETUNREACH (10051) Network is unreachable. A socket operation was attempted to an unreachable network. This usually means the local software knows no route to reach the remote host. WSAENOBUFS (10055) No buffer space available. An operation on a socket could not be performed because the system lacked sufficient buffer space or because a queue was full. WSAENOPROTOOPT (10042) Bad protocol option. An unknown, invalid or unsupported option or level was specified in a getsockopt or setsockopt call. WSAENOTCONN (10057) Socket is not connected. A request to send or receive data was disallowed because the socket is not connected and (when sending on a datagram socket using sendto) no address was supplied. Any other type of operation might also return this error—for example, setsockopt setting SO_KEEPALIVE if the connection has been reset. WSAENOTSOCK (10038) Socket operation on nonsocket. An operation was attempted on something that is not a socket. Either the socket handle parameter did not reference a valid socket, or for select, a member of an fd_set was not valid. WSAEOPNOTSUPP (10045) Operation not supported. The attempted operation is not supported for the type of object referenced. Usually this occurs when a socket descriptor to a socket that cannot support this operation is trying to accept a connection on a datagram socket. WSAEPFNOSUPPORT (10046) Protocol family not supported. The protocol family has not been configured into the system or no implementation for it exists. This message has a slightly different meaning from WSAEAFNOSUPPORT. However, it is interchangeable in most cases, and all Windows Sockets functions that return one of these messages also specify WSAEAFNOSUPPORT. WSAEPROCLIM (10067) Too many processes. A Windows Sockets implementation may have a limit on the number of applications that can use it simultaneously. WSAStartup may fail with this error if the limit has been reached. WSAEPROTONOSUPPORT (10043) Protocol not supported. The requested protocol has not been configured into the system, or no implementation for it exists. For example, a socket call requests a SOCK_DGRAM socket, but specifies a stream protocol. WSAEPROTOTYPE (10041) Protocol wrong type for socket. A protocol was specified in the socket function call that does not support the semantics of the socket type requested. For example, the ARPA Internet UDP protocol cannot be specified with a socket type of SOCK_STREAM. WSAESHUTDOWN (10058) Cannot send after socket shutdown. A request to send or receive data was disallowed because the socket had already been shut down in that direction with a previous shutdown call. By calling shutdown a partial close of a socket is requested, which is a signal that sending or receiving, or both have been discontinued. WSAESOCKTNOSUPPORT (10044) Socket type not supported. The support for the specified socket type does not exist in this address family. For example, the optional type SOCK_RAW might be selected in a socket call, and the implementation does not support SOCK_RAW sockets at all. WSAETIMEDOUT (10060) Connection timed out. A connection attempt failed because the connected party did not properly respond after a period of time, or the established connection failed because the connected host has failed to respond. WSATYPE_NOT_FOUND (10109) Class type not found. The specified class was not found. WSAEWOULDBLOCK (10035) Resource temporarily unavailable. This error is returned from operations on nonblocking sockets that cannot be completed immediately, for example recv when no data is queued to be read from the socket. It is a nonfatal error, and the operation should be retried later. It is normal for WSAEWOULDBLOCK to be reported as the result from calling connect on a nonblocking SOCK_STREAM socket, since some time must elapse for the connection to be established. WSAHOST_NOT_FOUND (11001) Host not found. No such host is known. The name is not an official host name or alias, or it cannot be found in the database(s) being queried. This error may also be returned for protocol and service queries, and means that the specified name could not be found in the relevant database. WSA_INVALID_HANDLE (OS dependent) Specified event object handle is invalid. An application attempts to use an event object, but the specified handle is not valid. WSA_INVALID_PARAMETER (OS dependent) One or more parameters are invalid. An application used a Windows Sockets function which directly maps to a Win32 function. The Win32 function is indicating a problem with one or more parameters. WSAINVALIDPROCTABLE (OS dependent) Invalid procedure table from service provider. A service provider returned a bogus procedure table to Ws2_32.dll. (Usually caused by one or more of the function pointers being null.) WSAINVALIDPROVIDER (OS dependent) Invalid service provider version number. A service provider returned a version number other than 2.0. WSA_IO_INCOMPLETE (OS dependent) Overlapped I/O event object not in signaled state. The application has tried to determine the status of an overlapped operation which is not yet completed. Applications that use WSAGetOverlappedResult (with the fWait flag set to FALSE) in a polling mode to determine when an overlapped operation has completed, get this error code until the operation is complete. WSA_IO_PENDING (OS dependent) Overlapped operations will complete later. The application has initiated an overlapped operation that cannot be completed immediately. A completion indication will be given later when the operation has been completed. WSA_NOT_ENOUGH_MEMORY (OS dependent) Insufficient memory available. An application used a Windows Sockets function that directly maps to a Win32 function. The Win32 function is indicating a lack of required memory resources. WSANOTINITIALISED (10093) Successful WSAStartup not yet performed. Either the application hasn't called WSAStartup or WSAStartup failed. The application may be accessing a socket that the current active task does not own (that is, trying to share a socket between tasks), or WSACleanup has been called too many times. WSANO_DATA (11004) Valid name, no data record of requested type. The requested name is valid and was found in the database, but it does not have the correct associated data being resolved for. The usual example for this is a host name-to-address translation attempt (using gethostbyname or WSAAsyncGetHostByName) which uses the DNS (Domain Name Server). An MX record is returned but no A record—indicating the host itself exists, but is not directly reachable. WSANO_RECOVERY (11003) This is a nonrecoverable error. This indicates some sort of nonrecoverable error occurred during a database lookup. This may be because the database files (for example, BSD-compatible HOSTS, SERVICES, or PROTOCOLS files) could not be found, or a DNS request was returned by the server with a severe error. WSAPROVIDERFAILEDINIT (OS dependent) Unable to initialize a service provider. Either a service provider's DLL could not be loaded (LoadLibrary failed) or the provider's WSPStartup/NSPStartup function failed. WSASYSCALLFAILURE (OS dependent) System call failure. Returned when a system call that should never fail does. For example, if a call to WaitForMultipleObjects fails or one of the registry functions fails trying to manipulate the protocol/name space catalogs. WSASYSNOTREADY (10091) Network subsystem is unavailable. This error is returned by WSAStartup if the Windows Sockets implementation cannot function at this time because the underlying system it uses to provide network services is currently unavailable. Users should check: That the appropriate Windows Sockets DLL file is in the current path. That they are not trying to use more than one Windows Sockets implementation simultaneously. If there is more than one Winsock DLL on your system, be sure the first one in the path is appropriate for the network subsystem currently loaded. The Windows Sockets implementation documentation to be sure all necessary components are currently installed and configured correctly. WSATRY_AGAIN (11002) Nonauthoritative host not found. This is usually a temporary error during host name resolution and means that the local server did not receive a response from an authoritative server. A retry at some time later may be successful. WSAVERNOTSUPPORTED (10092) Winsock.dll version out of range. The current Windows Sockets implementation does not support the Windows Sockets specification version requested by the application. Check that no old Windows Sockets DLL files are being accessed. WSAEDISCON (10101) Graceful shutdown in progress. Returned by WSARecv and WSARecvFrom to indicate that the remote party has initiated a graceful shutdown sequence. WSA_OPERATION_ABORTED (OS dependent) Overlapped operation aborted. An overlapped operation was canceled due to the closure of the socket, or the execution of the SIO_FLUSH command in WSAIoctl. ================================== Hope this helps, Pete

I'd prefer you call me "Pete", please. Version 2.85 is very old and not supported. If your program is only checking for that one version then it is wrong. You need to write to the author please and get him to fix it. Pete

Steering is by rudder input, differential thrust, differential braking, or combinations of all three. If you simply want a tiller control to steer like the rudder does then connect it as a rudder axis. I'm pretty sure that's what most cockpit builders will be doing. You'd calibrate it differently of course. Pete