JPL19

Great! Have downloaded, will try to get it tested tonight - it may be tomorrow though. Thanks! Joe

Any enhancement will work great, the one you describe I would think would work very well. I normally leave the DISCON ELEVTRIM AXIS checked. Adding a line to the aircraft specific setting (over riding to "unchecked") would be very appropriate in my case. The feelthere Airbus also requires other AC specific joystick entries (and it requires "unchecked" for for the DISCON also). So there is an aircraft specific entry for it in my fsuipc.ini already. I would see it possible that Center elevator on AP Alt Change, Enable V/S sign correction and Reverse the elevator trim sense might also be AC specific. Can't say I need those at this moment but it would be foreseeable that it could be beneficial. So, hopefully that's what you want me to be more explicit on? Thank you again, Joe

Don't know if this is do-able / feasible etc, but, here goes. Would it be possible to make the "DISCON ELEVTRIM AXIS FOR AP" selection under miscellaneous aircraft specific? There are a few other choices in miscellaneous that might be "specific" also. Asking because selection of this enhancement varies between add ons, and quite frankly sometimes I forget to change it when flying a different AC. (Flying FS9 still) At least one developer (feelthere) recommends one setting (checked) for their 737 series, and then recommends unchecked for their Airbus. Thank you for any consideration. Joe Lorenc

Well I do sincerely apologize. It just seemed as if my original post which stated I was using the latest versions, and that the fact I stated the problem is occuring now was being ignored. :oops: The issue iwith FDC is secondary though. I do believe the IPC Request Contains Bad Data issue is not caused by FDC. Maybe I need to discuss it with the Active Sky folks as it occurs when it is processing a route in AS2004.5. A lot of times it is hard to know where to begin, I figured they would refer me here since the error shows in WideFS. The effect causes a problem in FDC, but I do not see FDC as the source since it is idle when I get the BAD DATA message. Again Pete, please accept my apology. Joe

Just for the record I am using version 1.6 (as clearly stated in my initial thread), and if I do not start in the proper sequnce (RADAR CONTACT then FDC then AS2004) I do get the error. I am not some folk using an old version. My ini and log files for Wide FS: Wide server ini: ; PLEASE SEE the documentation for parameter details ; ================================================== [Config] AutoRestart=0 AutoUpdateTime=13 MaximumBlock=4096 NoStoppedRestarts=Yes Port=8002 RestartTime=10 SendTimeout=15 TCPcoalesce=No ; ----------------------------------------------- [user] Log=Errors+ ; =============================================== [ClientNames] 1=BIG_KAHUNA WideServer LOG: ********* WideServer.DLL Log [version 6.47] ********* Blocksize guide = 4096 (double allowed) Date (dmy): 06/03/05, Time 19:55:42.593: Server name is BIG-DADDY 107453 Initialising TCP/IP server 107532 Initialising IPX/SPX server 107563 ServerNode=256.31029.0.0.256 107563 *** WARNING! *** This ServerNode is probably incorrect! Running IPXROUTE to get list ... 107563 IPXROUTE config >"D:\Program Files\Microsoft Games\Flight Simulator 9\MODULES\WideServer.ipx" 109625The correct value is probably one of these: 109625 ServerNode=0.0.16384.50275.50948 ("Local Area Connection") 109625 ServerNode=0.0.29366.21024.21313 ("NDISWANIPX") 155188 Restarting service due to total lack of use 220110 Incoming connection Accepted ok (skt=2300) 220141 Connected to computer "BIG_KAHUNA" running WideClient version 6.470 (skt=2300) 411047 Error 10053: client socket disconnected at Client: removing (skt=2300) 438860 Closing down now ... Memory managed: Offset records: 134 alloc, 134 free Throughput maximum achieved: 12 frames/sec, 505 bytes/sec Throughput average achieved for complete session: 1 frames/sec, 35 bytes/sec Average receive rate from "BIG_KAHUNA": 1 frames/sec, 338 bytes/sec ********* Log file closed ********* WideClient Ini: ; PLEASE SEE WideFS documentation for parameter details ;===================================================== [Config] UseTCPIP=Yes ServerName=BIG-DADDY Window=3,3,464,237 ButtonScanInterval=20 ClassInstance=0 NetworkTiming=5,1 PollInterval=2000 Port=8002 ResponseTime=18 TCPcoalesce=No WaitForNewData=500 ApplicationDelay=0 MaxSendQ=100 Priority=3,1,2 OnMaxSendQ=Log NewSendScanTime=50 ; ----------------------------------------------- [user] Log=Errors+ ;=============================================== WIdeClient Log: ********* WideClient Log [version 6.47] Class=FS98MAIN ********* Date (dmy): 06/03/05, Time 20:01:45.397: Client name is BIG_KAHUNA 550 Attempting to connect now 711 Trying TCP/IP host "BIG-DADDY" port 8002 ... 711Okay, IP Address = 192.168.0.11 711 Connection made okay! 3985 New Client Application: "ShowText" (Id=3540) 15782 New Client Application: "rcv31" (Id=3612) 20770 New Client Application: "Flightdeck_Companion" (Id=3188) 30744 New Client Application: "AS2004" (Id=2016) 191455 ****** End of session performance summary ****** 191465 Total time connected = 189 seconds 191465 Reception maximum: 11 frames/sec, 467 bytes/sec 191465 Reception average whilst connected: 5 frames/sec, 163 bytes/sec 191465 Transmission maximum: 12 frames/sec, 3794 bytes/sec 191465 Transmission average whilst connected: 2 frames/sec, 393 bytes/sec 191465 Max receive buffer = 368, Max send depth = 20, Send frames lost = 0 191465 **************** Individual client application activity **************** 191465 Client 3540 requests: 220 (Ave 1/sec), Data: 31500 bytes (166/sec), Average 143 bytes/Process 191465 Client 3612 requests: 2845 (Ave 15/sec), Data: 98937 bytes (523/sec), Average 34 bytes/Process 191465 Client 3188 requests: 25804 (Ave 136/sec), Data: 6452995 bytes (34142/sec), Average 250 bytes/Process 191465 Client 2016 requests: 394 (Ave 2/sec), Data: 52596 bytes (278/sec), Average 133 bytes/Process 191465 ********* Log file closed (Buffers: MaxUsed 20, Alloc 30374 Freed 30374 Refused 0) *********

Show AdvDisplay is what the window heading reads using ShowText - should have just said "ShowText". Well it seems to have a lot to do with it. In the FDC forums there have been reports about the "start sequence" when using multiple add ons on the client. Not Enough Hot Key Slots is very commmon if not starting in a proper sequence with FDC. I can not restart FDC once the IPC REQUEST error occurs, same as if FDC is started out of order. Sorry - should have clarified - two different aircraft add ons - Level-D 767 and PMDG 737NG, and the default Cessna 172 as well. Other than the starting sequence issue above I have been running both on the client PC without issue (I purchased FDC over two years ago and have been running in this fashion for almost that entire time). Will check log files - no changes to ini files - just dropped latest DLLs and executables in their respective positions. Thx, Joe

I am getting the message "IPC Request Contains Bad Data" inside ShowADV Display. I am using WideFS 6.47 and FSUIPC 3.47 (full version). On my client I am running RADAR Contact 3.1, FDC 1.60, AS2004.5 and Flight Tracker 8.0.1. The message seems to occur when Route Processing in AS2004, before starting Flight Tracker. I will get the message for what seems like 1-2 minutes, then a reconnect. However, FDC remains disconnected, and will not reconnect because it is out of sequence (not enough hot key slots). My normal procedure that has always worked until now is start FS on the host, then WideClient / ShowADV / RADAR Contact / FDC / AS2004 / and finally Flight Tracker. This has happened with two different flights and two different add ons. Any help or suggestions appreciated. Joe Lorenc

Will comply - as always, thanks for the very prompt service! Joe

I am having a problem with the Traffic Density Toggle. I have not been able to fly much, and just noticed this for the first time tonight. If I have my traffic set at 100% and press the button (joystick2 btn1) I get dumped to the desktop. The traffic clears, there is a very brief pause, then CTD. If I start with traffic at zero% (or change it via the FS menu) and press, it proceeds as normal and sets traffic to 100% with no issues. I have three or four other button presses assigned and they still work fine. I also made sure I do not have anything assigned to that button within FS. Using latest version. This happens with default AC, default start up (KSEA), and everywhere else. It happens even if I am at an airfield with no AI. Windowed or full screen, day or night. Any help would be appreciated. Joe

Greetings, It may be by design, but when using version 3.135 and selecting "Minimum Weather Defaults" several "non-weather" choices under the technical tab become "unchecked". This includes at least "Stop Cockpit Sizing and Moving", "Fix Control Accel", "Extend Battery Life" and "Keep FS Clock Sync'd". Easily enough rechecked once you know it happens, but seems odd none-the-less. ***EDIT - also know realize it wipes out all my HOT KEYs too. Registered version of course. *** Thanks - happy Holidays to you and yours. Joe Lorenc

I changed the default choices for 1 & 2 in RADAR Contact for now to "q" and "w" (after reassigning those key functions in FS9). I didn't realize the effect RC would have especially running across WideFS - but that seems to have been it. So far, that seems to have solved the problem. I now have exit-2, pushback-L and pushback-R each assigned as their own single buttons in my X-Keys control pad. So far today it has worked without any problems. I had previously given up on any turning pushbacks in FS9 (I used a LAGO add on in FS2k2). Thanks for pointing out the parameter function - I will keep that in mind. Thanks for your help. Joe

Hello Pete, Several of the default aircraft have second exits now, including the 737, 747, and 777 (cargo doors in each case). You are correct in that it is a sequence of keys - the exit key plus the number of the exit for anything other than the first (actually labeled .0 in the aircraft.cfg file). There is an "exit rate" in the cfg file that controls the rate of opening or closing but has no effect on this issue. (The rate makes for some realistic movement effects, for some add ons it controls stairways instead of doors etc.) The problem persists even with the default panels. But now that I think about it, it does seem to happen for sure once I start RADAR Contact, which does use the normal keyboard number keys for "response selections" (even across WideFS). I can not really say it doesn't happen without RADAR Contact, but maybe I'll try some flights with default ATC to see. However, even when I had the "select item 2" assigned to a joystick button (as in button-6 rather than a macro) the problem occurs. Also once it occurs even closing all add ons and WideFS doesn't solve it. I'm sorry, but I don't follow the suggestion "Have you tried setting the parameter for that control to the door number, instead of leaving it default to 0? " There is only one option that I see for selecting an exit, rather than a series of choices for each exit number (but perhaps I misunderstand). You definitely are on the right path, as once this happens the ability for me to choose pushback direction fails also. If I can find some unused keys I may be able to reassign the RADAR Contact keys also to see if that helps. They would have to be unused single keys for simplicity - I'll look into that. Thanks for the prompt response! Joe

Well, I'm wondering if you have anything in your bag of magic tricks that could help solve a problem with exits in FS9. This problem has plagued me in FS2k2, FS9, and on two different computers. A lot of add on AC now have multiple exits, which is great. But I have a repeatable, so far unsolvable problem. The selection of any exit other than the default one works intermittently, at best. It normally works at start up, and at some point after I have gone through pre-starts and am ready to close everything up the ability to select the second exit fails. I then am either forced to fly with the cargo doors open (ha ha), or, go into the main menu and reselect the aircraft which puts all exits in the closed position. It is a regular occurrence, and seems to happen once I start running add ons through WideFS (ActiveSky or FS Meteo, RADAR Contact and FDC). Once it starts happening closing the add ons and WideFS does not solve the problem. I have tried several different things. First, I have the exit key selected to a "non" shifted, alt or ctl key. "u" in this case for me. I had better luck, but still not reliable then assigning a joystick button to "select item 2", and then pressing the exit key immediately followed by the joystick button. I also tried assigning key presses in my CH throttle for a button press. Some luck, but not complete using a macro of "press-u, press-2, release-2, release-u", other combinations were less successful. Using the keyboard "default method" of press "exit key" press "2" rarely works in any press/ release sequence. So there you have it. Not sure if there is anything you can recommend or do, but thought I'd throw it out for consideration. Thanks. Joe Lorenc Registered user FSUIPC and WideFS

Hello, It is acceptable, and is there any problem having a registered copy of both FSUIPC and WideFS in both sims on the same system? I don't expect to fully migrate for some time, but would like the programs on my second system to have a common interface. Thanks, Joe Lorenc