CBB

Hi John, you kindly passed me the 7.3.17B beta to solve the WASM not initiating I wonder if this is caused simply when I close down MSFS Thx, I'll try this beta

Hi Pete, well I tried it again but still no detection (see my last post on prosim forum), it seems to me that prosim is not detecting the switch for some reason, which is odd as other users have this working

Just received a reponse on the prosim forum, it seems the Gate should be set to an 8 bit unsigned, rather than 32 that I had. I will try that tomorow

Thanks, Pete, yes I have posted this on the prosim forum. I got this idea from another Prosim post in the following link, where he managed to do the same thing, albeit with the R/T switch and not the I/C switch but it is the same principle - see Step 3 https://prosim-ar.com/forum/viewtopic.php?f=12&t=16468&p=116361&hilit=Configure+CPFlight+ASP+R%2FT+switches#p116361 Charles

P3D 4.5, Prosim 2.30, CPflight h/w connected via the MCP, FSUIPC 5 I am trying to get FSUIPC to recognize as a button the movement of the I/C switch on my CPflight ASP (Audio Sound panel) But I cannot get FSUIPC (version 5) to recognize a virtual button. I went into prosim/configuration/Gates and selected the I/C on the captain side to FSUIPC 32 bit U with the offset 0x3340.0 (see attached pic) but when I go into FSUIPC buttons tab (with everything running including P3D, prosim system, prosim MCP), it does not sense the moving of the I/C switch as a button. I tried other offsets (3344.0, 3352.0) but still no joy. I checked that the I/C switch hardware is working, it is recognized by the CPflight hardware test all ok. I would be very grateful if you can shed light on this! Charles

Great to have you back, Pete! Now seems to be resolved after I installed 4948c. But I don't know if it was that or the fact that this time, before installing 4948 (from 4939v) I cleared out the old registry entries for FSX (which I do not have) which were causing an issue on install of FSUIPC as detailed in the prosim forum. I suspect these were messing something up on install. Also, someone else on the prosim forum reported that the wxr radar worked for him after uninstalling the p3d fsx migration tool so maybe having FSX "left behind" is the culprit Anyway, thanks again Best Charles

Hi Pete, when you return from your hols, pls have a look at this, confirmed there is a problem with 4,948 of fsuipc causing radar.bin to be null. Version 4,939n of fsuipc is confirmed to be last version that worked with prosim radar. Here is link to prosim threads http://prosim-ar.com/forum/viewtopic.php?f=13&t=8971&p=65769#p65769

Hi, I am using P3D 2.5, Prosim 1.46b5, ASN and wxr radar has been working fine for months. Just upgraded fsuipc from 4.939v to 4.948 and no longer have any wxr visuals on my ND, even in heavy cb area. I checked the fsuipc ini and I still have the entry ASNwxRadarPath=c:\ProSim737\radar.bin and my latest prosim log has: 11/14/2015 5:50:26 PM * System:Active Sky Next integration enabled 11/14/2015 5:50:26 PM * System:Active Sky Next radar.bin loaded successfully, using prerendered ASN cloud data Anyone else had this problem with fsuipc 4.948? Looking in my simconnect log for today (14th nov) there is a simconnect error message, but I think this is something else as I had the same message yesterday (13th nov) and previously, when the wxr radar was working fine. FSUIPC had an install error because it was looking for an old path to a dummy fsx folder which I no longer have, but the install to P3d seems ok The logs are all attached here on the prosim forum (I couldn't attached them here) http://prosim-ar.com/forum/viewtopic.php?f=13&t=8971&p=65571#p65571 Best Charles

OK, apologies, here is the log and the ini used to produce it: ********* WideClient Log [version 6.999n] Class=FS98MAIN ********* Date (dmy): 07/07/14, Time 09:47:14.445: Client name is CHARLES-4 Monitoring 330F,17 250 KeyHook added: 259=0,0,, 250 KeyHook added: 260=0,0,, 250 LUA: "C:\Wideclient\Initial.LUA": not found 265 Attempting to connect now 281 Trying TCP/IP host "Newserver" port 8002 ... 281 ... Okay, IP Address = 192.168.0.115 281 Connection made okay! 515 Using "C:\Wideclient\GFDEV.DLL", version 2.2.1.0 31559 Monitored LAN data received: Offset 0330F: 01 03 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00 . 31559 c:\fast\fast 31559 c:\fast\fast\fastflightsim.exe 31559 Checked KeySend[0]=3 31856 New Client Application: "FASTFlightsim" (Id=3272) 43056 Monitored LAN data received: Offset 0330F: 02 03 03 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00 . 43056 Program 18, Window = 90222 43056 Checked KeySend[1]=3 45209 Monitored LAN data received: Offset 0330F: 03 03 03 03 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00 . 45209 Program 18, Window = 90222 45209 Checked KeySend[2]=3 60404 ****** End of session performance summary ****** 60404 Total time connected = 60 seconds 60404 Reception maximum: 22 frames/sec, 668 bytes/sec 60404 Reception average whilst connected: 14 frames/sec, 432 bytes/sec 60404 Transmission maximum: 0 frames/sec, 177 bytes/sec 60404 Transmission average whilst connected: 0 frames/sec, 25 bytes/sec 60404 Max receive buffer = 638, Max send depth = 1, Send frames lost = 0 60404 **************** Individual client application activity **************** 60404 Client 3272 requests: 15 (Ave 0/sec), Data: 322 bytes (5/sec), Average 21 bytes/Process 60404 ********* Log file closed (Buffers: MaxUsed 2, Alloc 931 Freed 931 Refused 0) ********* any my ini: [user] Log=Keysend Monitor=330F,17 KeySend3=RunKey1 RunKey1=c:\fast\fast\fastflightsim.exe UseSendInput=Yes

I updated to 6999n and deleted the assignment in FSUIPC on release of the button, so the assignment in FSUIPC is just Kesend and parameter=3. In the wideclient.ini I have the following, I ran the test with Log=Keys but no extra log was produced, so I ran again with Log=Keysend and got the following 2 logs Result was the same, it opens the program the first time I do it, but not the 2nd and after. I have to close and re-open wideclient for it to work Wideclient ini: [user] Log=Errors+ Log=Keysend KeySend3=RunKey1 RunKey1=c:\fast\fast\fastflightsim.exe UseSendInput=Yes Logs: ********* WideClient Log [version 6.999n] Class=FS98MAIN ********* Date (dmy): 08/07/14, Time 11:02:29.306: Client name is CHARLES-4 234 LUA: "C:\Wideclient\Initial.LUA": not found 250 Attempting to connect now 266 Trying TCP/IP host "Newserver" port 8002 ... 266 ... Okay, IP Address = 192.168.0.115 266 Connection made okay! 500 Using "C:\Wideclient\GFDEV.DLL", version 2.2.1.0 15803 c:\fast\fast 15803 c:\fast\fast\fastflightsim.exe 16037 New Client Application: "FASTFlightsim" (Id=1764) ********* WideClient Log [version 6.999n] Class=FS98MAIN ********* Date (dmy): 07/07/14, Time 10:48:09.369: Client name is CHARLES-0 265 Attempting to connect now 265 LUA: "\\CHARLES-4\Wideclient\Initial.LUA": not found 2824 Trying TCP/IP host "Newserver" port 8002 ... 2824 Error on client gethostbyname() [Error=11004] Valid name, no data record of requested type 35194 ****** End of session performance summary ****** 35194 Total time connected = 0 seconds 35194 Reception maximum: 0 frames/sec, 0 bytes/sec 35210 Transmission maximum: 0 frames/sec, 0 bytes/sec 35210 Max receive buffer = 0, Max send depth = 0, Send frames lost = 0 35210 ********* Log file closed (Buffers: MaxUsed 0, Alloc 0 Freed 0 Refused 0) *********

The button is a goflight button, I have checked it is working fine on the buttons page of FSUIPC. I have it programmed as Kesend3 (key press not to be held) and then for release Keysend4, which I have not yet assigned....ah, ha maybe that is the issue? (I will delete this keysend4 and see) I put in the Log=Keysend when I did the last test....I thought the log files above were the result or is the log filed somewhere else? What I found odd was the line 63165, why it only picked part of the address first or is this normal? 63165 c:\fast\fast 63165 c:\fast\fast\fastflightsim.exe

Thanks, I just tried again and same problem. My log files look like this: ********* WideClient Log [version 6.999b] Class=FS98MAIN ********* Date (dmy): 07/07/14, Time 22:04:13.191: Client name is CHARLES-4 234 LUA: "C:\Wideclient\Initial.LUA": not found 250 Attempting to connect now 250 Trying TCP/IP host "Newserver" port 8002 ... 250 ... Okay, IP Address = 192.168.0.115 21294 Error on client pre-Connection Select() [Error=10060] Connection timed out 21294 Ready to try connection again 22324 Attempting to connect now 53384 Connection made okay! 53571 Using "C:\Wideclient\GFDEV.DLL", version 2.2.1.0 63165 c:\fast\fast 63165 c:\fast\fast\fastflightsim.exe 63804 New Client Application: "FASTFlightsim" (Id=2112) ********* WideClient Log [version 6.999b] Class=FS98MAIN ********* Date (dmy): 07/07/14, Time 22:02:46.664: Client name is CHARLES-4 281 LUA: "C:\Wideclient\Initial.LUA": not found 281 Attempting to connect now 1045 Trying TCP/IP host "Newserver" port 8002 ... 1045 ... Okay, IP Address = 192.168.0.115 22074 Error on client pre-Connection Select() [Error=10060] Connection timed out 22074 Ready to try connection again 23104 Attempting to connect now 66613 ****** End of session performance summary ****** 66613 Total time connected = 0 seconds 66613 Reception maximum: 0 frames/sec, 0 bytes/sec 66613 Transmission maximum: 0 frames/sec, 0 bytes/sec 66613 Max receive buffer = 0, Max send depth = 0, Send frames lost = 0 66613 ********* Log file closed (Buffers: MaxUsed 0, Alloc 0 Freed 0 Refused 0) *********

Hi Pete I have the following in my wideclient .ini: [user] Log=Errors+ KeySend3=RunKey1 RunKey1=c:\fast\fast\fastflightsim.exe and on my FSX PC I assigned Keysend 3 to a button. It works fine after I first run wideclient and press the button on the FSX PC, the program loads fine. Then I manually close the program and try the button again, but nothing, it won't load the program again, only if I close and retart wideclient. I also tried pinning this program on the windows taskbar, from where I can activate it with the windows start button, ie it is the 2nd program on the taskbar so Winkey+2 will open it. I tried putting in the wideclient ini the following but nothing happened: KeySend3=50,40 (I understand 40 is the winkey) Best Charles

Sorry, Pete, apologies I didn't see it. I read the FAQ....good news re your point about persistence because I have not had the message for some time now, so it may just have been due to my reinstall of FSUIPC, but now it has got thru all will hopefully be ok. If not I will try some of the ideas on the FAQ

Any thoughts on this?

I loved the video and cockpit, Pete, these always make you feel motivated again! Btw, re your lack of space, why don't you try 2 LCDs on either side?.I have 2 projectors for the front view connected via Matrox DualHead2Go and my video card handles the extension to 2 LCDs on either side. If this is too much for your video card/CPU you can do this with Wideview too, but I tried that and I found it more fiddly, better to invest in a good CPU and GPU than 2 extra PCs...around Gatwick with UK2000 scenery I am still pumping fps of 40. This 220 deg view gives you so much more immersion and you don't have to use that hat switch anymore, which was the only bit of the video that was not so good Other thing re the plane, have you tried the Project Opensky 737?....its flight dynamics and feel are very close to the real thing I am told and they have an awesome sound package to go with it. I use it with PM software, there is no difficulty making it work with PM like PMDG and ifly and the models are very well painted (file here http://www.flightsim.com/vbfs/fslib.php?searchid=10491781) Now I have praised you can you help with my dll issue on loading FSX!? Best Charles

Could it be because it is in my fsx.cfg twice, see below? [Trusted] C:\FSX\fsdreamteam\couatl\couatl.exe.ctotreaniuiriteutecwuozhkueateqletqchtai=1 C:\GoFlight\GFDevFSX.exe.neatcoaehunierqttlrrotranenurbnretoacicw=1 C:\FSX\bglmanx.dll.lqohnbcrhiqnbhbohrzqtrrqhhketcrhnbrhnkbe=1 C:\FSX\FsPassengers\bin\fspassengersx.dll.llbokehaiurallquankeoroqonuctkwbkqrzqrkl=1 C:\FSX\VistaMare\ViMaCoreX.dll.ciuczebwbuubbnlewbzlabiaqbhnioqclbuwrche=1 C:\FSX\Modules\FSUIPC4.dll.qbcoubowoobuhroqcitkwearnzbnntcczewobzrt=1 C:\FSX\Modules\FSCopilot.dll.weclqqqhnlenttaucuewewznikhqinoknooqwwel=1 C:\Program Files (x86)\IVAO\IvAp v2\ivap_fsx_bootstrap.dll.kzkbcihbutkkzrrthrceqkcozokbcczrtowwlnei=1 C:\FSX\GAUGES\XGauge.DLL.lwnrrnarwnqbbnlaqqzeoeuenrztaatzuubikeut=2 C:\FSX\GAUGES\737-400.DLL.eknnwqqzblklolhzucthwtbrwbrktbrclqhrwque=2 C:\FSX\GAUGES\Mooney_Bravo.DLL.luaqewwezbuecuwczqhatlrctitchunlcohcakhl=2 C:\FSX\GAUGES\Bendix_King_Radio.DLL.nwwwbeawcrqeltukqnacthzcquotcotitwnbocto=2 C:\FSX\FsPassengers\bin\FsPassengersMini.DLL.rozrrlcqlackeaurzbhenukhziihkzikznhwrlwe=2 C:\FSX\fsdreamteam\couatl\couatl.exe.aiqkuaiqruatorlaniznhtabcheubnohozwihhcz=1 C:\FSX\bglmanx.dll.znncqinokqliquwacqoqtbbwkaekabutabirhkqh=1 C:\FSX\Modules\FSUIPC4.dll.bacnrhtoewrnlqituhkzztcnalkinwzcirwuwuuh=1 C:\GoFlight\GFDevFSX.exe.kwehiekcqhothanzbhcazcbhwbetuqlohiqqcork=1 C:\FSX\Modules\FSUIPC4.dll.telrawnqqiqeieqqhoqcuaebaaetiubawwkqucot=1 C:\FSX\fsdreamteam\couatl\couatl.exe.rabenwkqnrakuntqrnbnqeztoiwkbbzhchineaqw=1 C:\FSX\bglmanx.dll.uellencobbrzwirheuaqqhwaeokizinarnknizwb=1 C:\FSX\GAUGES\BoeingGeneric.DLL.khelcneezrhaozitruhqqqitlhuebewnthkknriq=2 C:\FSX\GAUGES\Magnetic_Compass.DLL.obblrqwzckkneeqwzwnoztuhorcoctzwclbzrnbi=2

Hi Peter, since I did the reinstall after the certificate issue, I too am unable to load FSX and I have never had this problem before, my FSX has been going strong without problem for 2 years now and I have not loaded anything else. When I boot FSX the following error message appears (this does not happen always, only on occasion): Flight Simulator has detected a problem with a third-party software program (add-on): Name: FSUIPC4DLL: FS new universal IPC interface Version: 4,90 Company: Pete Dowson File: Modules\FSUIPC4.dll Do you want to run the software (not recommended): To avoid seeing the message in the future, uninstall the program or disable its ability to start when running flight simulator. For more information about third-party programs, contact the publisher.... Could it be because I have multiple mentions of fsuipc dll in my fsx cfg, have a look below. Can I just delete all mention of these and let FSX request them to be trusted again or how fix this? [Trusted] C:\FSX\fsdreamteam\couatl\couatl.exe.ctotreaniuiriteutecwuozhkueateqletqchtai=1 C:\GoFlight\GFDevFSX.exe.neatcoaehunierqttlrrotranenurbnretoacicw=1 C:\FSX\bglmanx.dll.lqohnbcrhiqnbhbohrzqtrrqhhketcrhnbrhnkbe=1 C:\FSX\FsPassengers\bin\fspassengersx.dll.llbokehaiurallquankeoroqonuctkwbkqrzqrkl=1 C:\FSX\VistaMare\ViMaCoreX.dll.ciuczebwbuubbnlewbzlabiaqbhnioqclbuwrche=1 C:\FSX\Modules\FSUIPC4.dll.qbcoubowoobuhroqcitkwearnzbnntcczewobzrt=1 C:\FSX\Modules\FSCopilot.dll.weclqqqhnlenttaucuewewznikhqinoknooqwwel=1 C:\Program Files (x86)\IVAO\IvAp v2\ivap_fsx_bootstrap.dll.kzkbcihbutkkzrrthrceqkcozokbcczrtowwlnei=1 C:\FSX\GAUGES\XGauge.DLL.lwnrrnarwnqbbnlaqqzeoeuenrztaatzuubikeut=2 C:\FSX\GAUGES\737-400.DLL.eknnwqqzblklolhzucthwtbrwbrktbrclqhrwque=2 C:\FSX\GAUGES\Mooney_Bravo.DLL.luaqewwezbuecuwczqhatlrctitchunlcohcakhl=2 C:\FSX\GAUGES\Bendix_King_Radio.DLL.nwwwbeawcrqeltukqnacthzcquotcotitwnbocto=2 C:\FSX\FsPassengers\bin\FsPassengersMini.DLL.rozrrlcqlackeaurzbhenukhziihkzikznhwrlwe=2 C:\FSX\fsdreamteam\couatl\couatl.exe.aiqkuaiqruatorlaniznhtabcheubnohozwihhcz=1 C:\FSX\bglmanx.dll.znncqinokqliquwacqoqtbbwkaekabutabirhkqh=1 C:\FSX\Modules\FSUIPC4.dll.bacnrhtoewrnlqituhkzztcnalkinwzcirwuwuuh=1 C:\GoFlight\GFDevFSX.exe.kwehiekcqhothanzbhcazcbhwbetuqlohiqqcork=1 C:\FSX\Modules\FSUIPC4.dll.telrawnqqiqeieqqhoqcuaebaaetiubawwkqucot=1 C:\FSX\fsdreamteam\couatl\couatl.exe.rabenwkqnrakuntqrnbnqeztoiwkbbzhchineaqw=1 C:\FSX\bglmanx.dll.uellencobbrzwirheuaqqhwaeokizinarnknizwb=1 C:\FSX\GAUGES\BoeingGeneric.DLL.khelcneezrhaozitruhqqqitlhuebewnthkknriq=2 C:\FSX\GAUGES\Magnetic_Compass.DLL.obblrqwzckkneeqwzwnoztuhorcoctzwclbzrnbi=2

Hi Christof I am thinking of doing the same, using a touchscreen to operate the buttons on the FSINN client, rather than a mouse. Have you tried it yet and does it work? As soon as you know pls advise. You can assign buttons/keys to FSINN but that only works if you use FSINN on your main FS pc. If, like me, you use FSINN on a networked client this assignment does not work and I don't think FSUIPC can help here either. That was why I think my only solution is the touchscreen. I was thinking of putting it on the lower EICAS in my 737 cockpit Best Charles

I have now completed the 2nd test, which was a Vatsim flight in the Posky Thomsonfly 737-800 from the Posky site and totally flawless. The 1st test was a Vatsim flight in the Posky KLM 737-900 from the Posky site and totally flawless as well. I have now freshly downloaded Thomson VA Bluesky (the pirep software) again and installed it and next test will be this with the a Vatsim flight in the Posky Thomsonfly 737-800 from the Posky site again (not from the T VA site). If this works I will not download the Posky Thomsonfly 737-800 from the Thomson VA site, but close this issue. Btw, after I downloaded the Thomson VA Bluesky sw this time, it came up with a similar message as before that "Your version of Macromedia Flash ActiveX Control is not compatible with this version of windows". It then redirects me to Adobe for resolution and download of v 11.3.300.257 (I have W7 and had Flash v 10 installed). Before when I installed this (when I had the subsequent problems) I uninstalled V10 and installed this new version and I have a slight suspicion (but not 100%) that something unwanted may have entered at this point. But this time I simply downloaded and installed the new version and it seemed to replace V10 automatically. I'll let you know how the test goes.

OK, thanks, I'll update after the next test. The other odd thing re the above (reading it again) is that things went wrong at time of landing...up until then the flight was flawless, I could taxi on departure and take-off was ok....ie something kicked in on the arrival phase which is what is weird. If I had double assignments, etc you would expect the problem to occur from the start.

I just completed a Vatsim flight with my PC restored to before installing the Thomson VA B737 and their Bluesky software, as before there were no issues at all (ie using my Posky KLM B737) I have updated to FSUIPC 4,839 now. My next test will be to do a flight with my KLM 737 and the Thomson Bluesky software. Sorry, was unclear. I am talking about IN and OUT, when I pressed on the left pedal both would go positive in the Axis Assignment page, when I pressed on the right pedal both would go negative. But when I did the same in the Joystick Calibration page immediately after, press left would go positive and then jump to negative and press right would be negative (on both IN and OUT). I checked at the time that the rudder was assigned to direct to FSUIPC. Normally I would press "rescan" or clear and then the values next to "Press" would blank out, but in this case neither would do anything. The rudder values were extremely jittery because I tried pressing filter to see if it would calm down but there was little effect. I mean the Max Set field in the Joystick calibration page for the Aileron. When I moved the pedal on one of the tests only that field changed which is when I started to think of virus. I have FS axis controls completely disabled and all my axis movements assigned through FSUIPC direct. I did all axes assignments like this, simple MIN and MAX with dead zone in the middle for some (aileron, rudder and elevator) and detentes for flaps and spoilers, nothing more complex. Attached is my ini file although this is after restoring my PC back...and as mentioned above it is working fine. If I get the same problem on one of the future tests I will send you the ini before restoring [General] UpdatedByVersion=4839 History=W6S1U6R0PZK9037A1QJ4S MouseWheelTrim=No MouseWheelTrimSpeed=1 JoystickTimeout=20 PollGFTQ6=Yes BlankDisplays=No FixControlAccel=No FixMachSpeedBug=No VisibilityOptions=No OneCloudLayer=No CloudTurbulence=No CloudIcing=No GenerateCirrus=No SuppressCloudTurbulence=No MaxIce=-4 MinIce=-4 UpperWindGusts=No SuppressWindTurbulence=No SuppressWindVariance=No WindTurbulence=No TurbulenceRate=1.0,5.0 TurbulenceDivisor=20,20,40,40 SuppressAllGusts=No MaxSurfaceWind=0 WindLimitLevel=200 WindDiscardLevel=400 WindAjustAltitude=No WindAjustAltitudeBy=2000 SmoothBySimTime=No WindSmoothing=No WindSmoothness=2 WindSmoothAirborneOnly=Yes PressureSmoothness=0 TemperatureSmoothness=0 DisconnTrimForAP=No ZeroElevForAPAlt=No ThrottleSyncAll=No WhiteMessages=No ShowPMcontrols=Yes SpoilerIncrement=512 MagicBattery=No RudderSpikeRemoval=No ElevatorSpikeRemoval=No AileronSpikeRemoval=No ReversedElevatorTrim=No ClockSync=No ClockSyncMins=5 ClearWeatherDynamics=No OwnWeatherChanges=No TimeForSelect=4 LoadFlightMenu=No LoadPlanMenu=No PauseAfterCrash=No BrakeReleaseThreshold=75 SaveDataWithFlights=No ZapSound=firework ShortAircraftNameOk=No UseProfiles=No TCASid=Flight TCASrange=40 AxisCalibration=No DirectAxesToCalibs=No ShowMultilineWindow=Yes SuppressSingleline=Yes SuppressMultilineFS=No AxisIntercepts=No DontResetAxes=No GetNearestAirports=Yes WeatherReadFactor=2 WeatherRewriteSeconds=1 CustomWeatherModify=No SimConnectStallTime=1 LuaRerunDelay=66 Console=No DeleteVehiclesForAES=Yes EnableMouseLook=No AxesWrongRange=No InitDelay=0 MouseWheelMove=No AutoScanDevices=Yes OOMcheck=Yes FSVersionUsed="Microsoft Flight Simulator X",10.0.61637.0 SimConnectUsed=10.0.61259.0 [JoyNames] AutoAssignLetters=No 1=PFC USB Pedals 2 1.GUID={6CE4EAD0-6492-11E1-8002-444553540000} 2=GoFlight GF-TQ6 Throttle System 2.GUID={6CE67170-6492-11E1-800E-444553540000} 0=PFC USB Yoke 0.GUID={6CE4EAD0-6492-11E1-8001-444553540000} [buttons] ButtonRepeat=20,10 4=P101,14,C2999,36 5=P101,15,C2999,37 6=P109,15,K53,9 7=R0,0,C65588,0 9=P0,6,K83,8 10=P109,0,K65,8 14=P167,0,C66079,0 15=P167,1,C66080,0 16=P167,3,C65752,0 17=P167,2,C65752,0 18=P109,7,C66531,0 19=P174,8,C1007,0 20=P174,9,C1007,1 21=P174,10,C1007,4 22=P174,11,C1007,5 25=R101,0,C65671,0 26=R101,1,C65672,31 33=P175,0,K66,8 39=R169,2,K113,8 40=U169,2,K112,8 41=R0,2,C65615,0 42=R0,3,C65607,0 43=U167,3,C65752,0 44=U167,2,C65752,0 45=R101,6,C65734,0 46=R101,7,C65735,0 47=P101,8,C2999,30 48=P101,9,C2999,31 49=P101,10,C2999,32 50=P101,11,C2999,33 51=P101,12,C2999,34 52=P101,13,C2999,35 53=P174,0,C2999,38 54=P174,1,C2999,39 55=P109,8,K13,24 56=U109,8,K13,24 59=P0,7,C66654,0 60=R0,1,C1001,0 61=P109,14,C2999,60 66=U109,0,K65,8 68=U109,14,C2999,61 69=U109,15,K53,9 70=P109,3,Cx0900561A,x01 71=U109,3,Cx0500561A,x01 72=P109,4,Cx0900561A,x02 73=U109,4,Cx0500561A,x02 74=P109,13,K51,9 75=U109,13,K51,9 76=U0,1,C1002,0 78=P101,3,C1120,0 79=P101,4,C1122,0 80=P141,1,C1119,0 81=P141,2,C1120,0 82=P141,0,C1122,0 83=P142,1,C66463,0 84=P142,2,C66464,0 85=P141,17,C66447,0 86=P141,18,C66451,0 [AutoSave] AutoSaveEnabled=No Next=1 Interval=60 Files=10 SaveOnGround=No [GPSout] GPSoutEnabled=No [GPSout2] GPSoutEnabled=No [WideServer] WideFSenabled=Yes AdvertiseService=1 Port=8002 Port2=9002 [sounds] Path=C:\FSX\Sound\ Device1=Primary Sound Driver Device2=Speakers (Realtek High Definition Audio) Device3=Realtek Digital Output (Realtek High Definition Audio) Device4=Realtek Digital Output(Optical) (Realtek High Definition Audio) [ClientNames] 1=PHILIPSPC 2=CHARLES-1 3=CHARLES-2 [Window.Radar Contact] Docked=1536, 75776, 28672, 77824 [Axes] 0=0X,256,D,1,0,0,0 1=0Y,256,D,2,0,0,0 2=1R,256,D,3,0,0,0 3=2X,256,D,22,0,0,0 4=2Z,256,D,9,0,0,0 5=2R,256,D,23,0,0,0 6=2U,256,D,10,0,0,0 [JoystickCalibration.Project Opensky Continental Boeing 737-900] AllowSuppressForPFCquad=Yes ExcludeThrottleSet=Yes ExcludeMixtureSet=Yes ExcludePropPitchSet=Yes SepRevsJetsOnly=No ApplyHeloTrim=No UseAxisControlsForNRZ=No FlapsSetControl=0 FlapDetents=Yes FlapStarts=-16384,-11392,-10368,-9472,-6528,-2176,3381,8192,11703 FlapEnds=-11520,-10624,-10112,-8448,-3584,1170,6891,10662,16384 ReverserControl=66292 Reverser1Control=66422 Reverser2Control=66425 Reverser3Control=66428 Reverser4Control=66431 MaxThrottleForReverser=256 AileronTrimControl=66731 RudderTrimControl=66732 CowlFlaps1Control=66162 CowlFlaps2Control=66163 CowlFlaps3Control=66164 CowlFlaps4Control=66165 SteeringTillerControl=0 MaxSteerSpeed=60 Aileron=-15898,-1666,1946,15630 Elevator=-15453,-6950,-3072,15490 Rudder=-15439,-5998,553,14834 Throttle1=-11963,-512,512,9472/32 Throttle2=-11572,-512,512,10240/32 Spoilers=-11264,-9984,-6016,11312/16 Flaps=0,16380/16 [JoystickCalibration.POSKY KLM NC B737-900] AllowSuppressForPFCquad=Yes ExcludeThrottleSet=Yes ExcludeMixtureSet=Yes ExcludePropPitchSet=Yes SepRevsJetsOnly=No ApplyHeloTrim=No UseAxisControlsForNRZ=No FlapsSetControl=0 FlapDetents=Yes FlapStarts=-16384,-10880,-10368,-9472,-7040,-1920,3771,8192,11963 FlapEnds=-11520,-10624,-9984,-8064,-3456,2080,6631,10922,16384 ReverserControl=66292 Reverser1Control=66422 Reverser2Control=66425 Reverser3Control=66428 Reverser4Control=66431 MaxThrottleForReverser=256 AileronTrimControl=66731 RudderTrimControl=66732 CowlFlaps1Control=66162 CowlFlaps2Control=66163 CowlFlaps3Control=66164 CowlFlaps4Control=66165 SteeringTillerControl=0 MaxSteerSpeed=60 Aileron=-16036,-3263,2825,15567 Elevator=-15422,-5802,-1303,14417 Rudder=-15106,-3332,1993,15830 Throttle1=-11963,-512,512,10112/32 Throttle2=-11703,-512,512,10112/32 Spoilers=-11648,-8960,-6144,11572/16 Flaps=0,16380/16 [Profile.Project Opensky Continental Boeing 737-900] 1=Project Opensky Continental Boeing 737-900 [Profile.POSKY KLM NC B737-900] 1=POSKY KLM NC B737-900 [Axes.POSKY KLM NC B737-900] 0=0X,256,D,1,0,0,0 1=0Y,256,D,2,0,0,0 2=1R,256,D,3,0,0,0 3=2X,256,D,22,0,0,0 4=2Z,256,D,9,0,0,0 5=2R,256,D,23,0,0,0 6=2U,256,D,10,0,0,0 [JoystickCalibration] AllowSuppressForPFCquad=Yes ExcludeThrottleSet=Yes ExcludeMixtureSet=Yes ExcludePropPitchSet=Yes SepRevsJetsOnly=No ApplyHeloTrim=No UseAxisControlsForNRZ=No FlapsSetControl=0 FlapDetents=Yes FlapStarts=-16384,-11264,-10368,-9344,-7040,-2048,3381,8062,11442 FlapEnds=-11392,-10624,-9728,-7936,-3840,1820,6761,10922,16384 ReverserControl=66292 Reverser1Control=66422 Reverser2Control=66425 Reverser3Control=66428 Reverser4Control=66431 MaxThrottleForReverser=256 AileronTrimControl=66731 RudderTrimControl=66732 CowlFlaps1Control=66162 CowlFlaps2Control=66163 CowlFlaps3Control=66164 CowlFlaps4Control=66165 SteeringTillerControl=0 MaxSteerSpeed=60 Aileron=-15889,-2119,4204,15642 Elevator=-15505,-4183,-316,14974 Rudder=-15717,-5387,6587,15110 Throttle1=-11963,-512,512,9600/32 Throttle2=-11703,-512,512,10240/32 Spoilers=-11264,-9088,-5632,11312/16 Flaps=0,16380/16

Hi Pete I fly at least once a day on Vatsim and have had a very stable-running setup for the last 4 months flying the Posky 737-900 KLM on FSX with Project Magenta and FSUIPC 4.80 in a home-built cockpit. No crashes, no issues. I recently thought of moving to the next stage which was logically to a virtual airline, my prime concern being that I would have to use a new aircraft of the VA's fleet and the consequent risk to the stability I had worked hard to get to. I made the plunge and recently joined Thomson VA and was pleased with how everything was going and saw that there was a Posky 737-8K5 available as part of the fleet which I downloaded (apparently just the Thomson 737-800 from the Posky site with textural chnages). I also downloaded Blue Sky which is their Pirep software, which apparently has no input to my flight sim other than send a message to my screen, they use the bridge fsuipc to communicate between blue sky and FSX. I then did a test flight of everything and all was absolutely fine until on final approach I made a poor landing and ran off to one side of the runway and could not get back (fortunately not very usual!). I discovered that my rudder was not working properly (it had worked fine on taxxing to the dep runway), so much so that I could not taxi to gate, it was all over the place (I have used flypfc pedals for some years now with no problem). I thought maybe the pedals themselves were not working, but I did a test in the windows device settings and it was fine, I even recalibrated them to be sure. Looking into this further, I found out that within FSUIPC´s axis assignment all was well, so that when I pressed the left pedal the numbers increased and when I pressed the right they decreased and went negative. But when I went into the Joystick assignment and pressed the left pedal sometimes the numbers would go negative rather than positive and when I pressed the right pedal they would be negative again! (this is not the “reverse” button because that was off). Then I went back into axis assignment and selected to “rescan” or “clear” and nothing would happen (the assignment would not clear), I had to exit FSUIPC and go in again. Then in the axis assignment page the numbers move absolutely fine still, ie positive (when push left) and negative (when push right). I noticed too that on one of my tests, when I moved the pedals on the FSUIPC joystick calibration page the values for the Aileron Max field were changing! Then again I could not clear/rescan on the axis assignment page and had to close and re-enter FSUIPC. I put my pedals in a different USB slot but no change. These tests were occurring without Bluesky running. I double-checked that I have no other conflicting assignments (eg within FSX) but these were all as I had before with my KLM, ie all deactivated. I have never experienced any problem with FSUIPC before and I have used it for the last 3 years extensively. So luckily I made a restore point before all this, I loaded up my old KLM and the Thomson 737 from the Posky site (not the Thomson site) and sure enough the pedals are absolutely fine, although this may mean nothing as they were fine when I departed with the Thomson site's Posky 737. I have raised this with Thomson VA and we agreed I´ll try flying my KLM without Bluesky, then I´ll try my KLM with Bluesky, then (the Posky Thomson Fly 737 from the Posky site with and without Bluesky and then © the Posky Thomson Fly 737 from the Thomson site with and without Bluesky. Hopefully that may give more information for us! In the meantime, can you shed any light on possible causes? I thought of static but never had this before and would be very coincidental for this to occur when I change aircraft and load Bluesky.

Thanks for the input, I have found the culprit, my GF modules were plugged into USB 3 rather than USB 2 slots, I plugged them back into the USB 2 and now all fine. I am not sure if this is a GF v USB 3 problem or the other issue may be that USB 3 goes to sleep as GF suggested in their response (copied below), I have put this back to John Krieg at GF. Sorry to use up space on a non-FSUIPC issue: "Disable power management on the USB To preserve power, Microsoft Window's tries to disable USB when a device is not used. Under certain circumstances this function does not work and may cause USB devices to fail to respond when called. To resolve this issue, disable power management. a..Open your Control panel. b..Click on Change Power plan. c..Click on Change Advanced Power setting. d..Now in Advanced setting's expand the USB. e..Under USB Selective Suspend Settings. f..Set to Disable Apply and exit."

Hi Pete I have had the GF airliner module for about 2 yrs now and not had any problem. Recently I have upgraded to W7 and from FSX Deluxe to Gold. I check in the Goflight Software and all my modules are showing, I then launch GFDEV.fsx and then fsx (Gold with Acceleration). When FSX is loading all the modules light up and then go out as per normal. But then when FSX is loaded, engines running and battery/avionics on, there is no display on the radios nor on the ATC module. If I turn the radio knobs they do not change the radios in FSX. However the movement of their knobs does show up in FSUIPC. I uninstalled and reinstalled the latest version of GF (203) and I upgraded FSUIPC to the latest (4,80) but still no joy. I did the same procedure, but deleting GFDEV.dll in the modules folder first, but still no joy. I have raised this with GF too, but knowing that you use GF and I saw you commented on similar problems in the past (but I could not see a resolution), I thought I would ask you too Best Charles