Pete Dowson

All that sounds insane. I'm afraid I'm unable to test here because I do not have FS9 any more. I never reinstalled after my last PC died late last year. I'm really getting to the position where I can no longer support a version of FS which is over 11 years old. However, you can run tests and show me the results quite easily. You can see the state of those three offsets the program uses by logging them in the FSUIPC Monitor. Go to the Logging tab, then, on the right hand side, use three of the 4 entries: enter 0E88 with type U16, 0E98 type U16 and 0366 type U16, then select options below -- Advdisplay to show them on the FS screen (for you to see and correlate with the sounds), but check normal log too so we get a log with times. Edit the Lua plug-in to log when the sound starts and stops: i.e. after the line sndflg=1 insert ipc.log("Starting turbulence sound") and after sndflg=0 insert ipc.log("stopping turbulence sound") Run it, get the problem, show me the FSUIPC.LOG. Pete

Only once for FSUIPC3 or once for FSUIPC4. Why do you think you have to pay more times? No, they are included in the Accelerator pack. Why are you asking me? What? No, of course not. Thousands of users are happy with Saitek devices and FSUIPC. Where are you getting all this nonsense? Pete

Both instances look perfect as far as FSUIPC is concerned. The performance (30 fps or close) was maintained well in both cases and there are no stops. I think the Airbus has the problem. Maybe there's something it doesn't like about the options or assignments you have in FSUIPC? Sorry, I think you need to do to the Airbus support forum. Pete

WeatherSet is a program to read FSUIPC weather offsets and display them neatly. It is part of the FSUIPC SDK, but also available separately in the Download Links subforum. WeatherSet2 is the better version for FS9 and FSX. Weatherset in for the older FS versions, but both will work. You need an event programmed so that the change in the ground flag calls the function -- in your script it is only called when the turbulence values change! Add this to the end: event.offset(0x0366,"UW","turbulence") Pete

Use WeatherSet to see if the turbulence indication is still there. I don't know what you are using to detect it. If you want sounds to stop early on certain other conditions you'd need to program for that. Whilst "ground" is checked before starting the sound, there's no event programmed for the ground flag changing to stop the sound. Just add it if that's what you want. Pete

You have Windows set to hide the real filenames from you!! There are instructions in the FSUIPC document about that. The log file IS called FSUIPC.LOG but Windows treats it as a text doument, as of course it is. But best change that stupid Windows option else you'll often have trouble finding the correct files. Just as well as I don't support old versions! Anyway, there's no clue in the log so you'll need to send me you order number or other details as I suggested. Do NOT post your Keys here though. I you want details to remain confidential (I see you aren't using your real name, for instance), send to petedowson@btconnect.com. Pete

No no no. The method Paul is talking about is in no way related to the FSUIPC pre-defined Hotkeys tab. It is a facility for an application to register an interest in keypresses by filling in details in a table in FSUIPC Offsets -- i.e. places you WRITE using the FSUIPC application interface. Please refer to the FSUIPC Programmers guide. It is all described under the heading "Hot Keys for Applications". Pete

Why do you understand this. Does it say so somewhere? I don't recall it being published, but FS9 was a long long time ago and I haven't dealt with it for years, so I may have forgotten. However, I just found it on my disk and reproduce it below. Just same it into the Modules folder as 737 OHD.mcro: [Macros] Module="PMDG_737NG_Overhead.gau" 1=Batt=RX3170*X8b90 2=CabUtil=RX3210*X8b90 3=IFE/PassSt=RX3260*X8b90 4=Gen1off=RX32b0*X8b90 5=Gen1on=RX32f0*X8b90 6=APUGen1off=RX33b0*X8b90 7=APUGen1on=RX33f0*X8b90 8=APUGen2off=RX3430*X8b90 9=APUGen2on=RX3470*X8b90 10=Gen2off=RX3330*X8b90 11=Gen2on=RX3370*X8b90 12=PanelLights=RX18f0*Xb990 13=LogoLts=RX1ce0*Xb990 14=PosnLts=RX1d30*Xb990 15=Strobe=RX1d80*Xb990 16=Anti-Coll=RX1dd0*Xb990 17=WingLts=RX1e20*Xb990 18=Drive1=RX3580*X8b90 19=Drive2=RX35d0*X8b90 20=BattAuto=RX31c0*X8b90 21=GrndPwrOff=RX3500*X8b90 22=GrndPwrOn=RX3540*X8b90 999=Show/Hide=C66506,24 Module1="PMDG_737NG_OHD_APU.GAU" 40=APU=R1:1 41=Start1+=R1:6 42=Start1-=R1:5 43=WiperL<=R1:2 44=WiperL>=R1:3 45=WiperR<=R1:6 46=WiperR>=R1:7 Module2="PMDG_737NG_OHD_PAX_SIGNS.GAU" 60=SmokeDn=R2:3 61=SmokeUp=R2:10 62=ECoolSupply=R2:1 63=ECoolExhaust=R2:2 64=EmergLtng=R2:5 65=StBeltDn=R2:4 66=StBeltUp=R2:11 67=Attend=R2:9 68=Call=R2:8 Module3="PMDG_737NG_OHD_VOICE_REC.GAU" Module4="PMDG_737NG_OHD_Pressurization.GAU" 100=FltAltDn=R4:2 101=FltAltUp=R4:1 102=LndAltDn=R4:3 103=LndAltUp=R4:4 104=PressManDn=R4:8 105=PressManUp=R4:7 106=PressAltnDn=R4:6 107=PressAltnUp=R4:5 Module5="PMDG_737NG_OHD_PROBE_HEAT.GAU" 120=ProbeHeatA=R5:1 121=ProbeHeatB=R5:2 122=ProbeHeatTest=R5:3 Module6="PMDG_737NG_OHD_LIGHTS_LEFT.GAU" 140=LandLts=R6:1 141=TurnOffL=R6:2 142=TurnOffR=R6:7 143=TaxiLts=R6:4 Module7="PMDG_737NG_OHD_LIGHTS_RIGHT.GAU" Module8="PMDG_737NG_OHD_Flight_Controls.GAU" 161=SbyRdrA=R8:1 162=SbyRdrB=R8:2 163=AltFlpArm=R8:3 164=AltFlpUp=R8:8 165=AltFlpDn=R8:7 166=SplrA=R8:4 167=SplrB=R8:5 168=YD=R8:6 Module9="PMDG_737NG_OHD_PNEUMATIC_800.GAU" 180=AirSpply< 180.1=R9:13 180.2=R10:13 181=AirSpply> 181.1=R9:20 181.2=R10:13 183=AirConCab<=R9:10 184=AirConCab>=R9:8 185=AirFwdCab<=R9:18 186=AirFwdCab>=R9:19 187=AirAftCab<=R9:11 188=AirAftCab>=R9:9 189=AirRecircL 189.1=R9:22 189.2=R10:7 190=AirRecircR 190.1=R9:7 190.2=R10:7 192=AirOvhtTest=R9:12 193=LPackOff 193.1=R9:15 193.2=R10:15 194=LPackOn 194.1=R9:4 194.2=R10:4 195=RPackOff 195.1=R9:16 195.2=R10:16 196=RPackOn 196.1=R9:6 196.2=R10:6 197=IsolValveOff 197.1=R9:17 197.2=R10:17 198=IsolValveOn 198.1=R9:5 198.2=R10:5 199=AirTripReset 199.1=R9:14 199.2=R10:14 200=BleedEng1 200.1=R9:1 200.2=R10:1 201=BleedAPU 201.1=R9:2 201.2=R10:2 202=BleedEng2 202.1=R9:3 202.2=R10:3 Module10="PMDG_737NG_OHD_PNEUMATIC.GAU" 182=AirSpply/Pass=R10:13 191=AirRecirc=R10:7 Module11="PMDG_737NG_OHD_ELECTRICAL.GAU" Module12="PMDG_737NG_OHD_FUEL.GAU" 240=FuelXfeed=R12:7 241=FuelLCtr=R12:5 242=FuelRCtr=R12:6 243=FuelAft1=R12:1 244=FuelFwd1=R12:2 245=FuelFwd2=R12:3 246=FuelAft2=R12:4 400=FuelAll 400.1=R12:1 400.2=R12:2 400.3=R12:3 400.4=R12:4 400.5=R12:5 400.6=R12:6 Module13="PMDG_737NG_OHD_WS_HEAT.GAU" 260=WinHtLSide=R13:1 261=WinHtLFwd=R13:2 262=WinHtRFwd=R13:3 263=WinHtRSide=R13:4 264=WinOvht=R13:5 265=WinOvhtTest=R13:6 Module14="PMDG_737NG_OHD_HYDRAULIC.GAU" 280=HydEng1=R14:1 281=HydEng2=R14:3 282=HydElec1=R14:2 283=HydElec2=R14:4 Module15="PMDG_737NG_OHD_ENG_AI.GAU" 300=AntiIceWing=R15:1 301=AntiIceEng1=R15:2 302=AntiIceEng2=R15:3 Module16="PMDG_737NG_OHD_ELECTRICAL_DISP.GAU" 320=ElecLeftSel<=R16:2 321=ElecLeftSel>=R16:1 322=ElecRghtSel<=R16:4 323=ElecRghtSel>=R16:3 Module17="PMDG_737NG_OHD_NAV_SOURCE.GAU" 340=VHFsrc<=R17:6 341=VHFsrc>=R17:1 342=IRSsrc<=R17:5 343=IRSsrc>=R17:2 344=DsplySrc<=R17:7 345=DsplySrc>=R17:3 346=PanelSrc<=R17:8 347=PanelSrc>=R17:4 Module18="PMDG_737NG_OHD_ENGINE_STARTERS.GAU" 360=Start2+=R18:2 361=Start2-=R18:1 362=Ignition<=R18:3 363=Ignition>=R18:4 30=Lights 30.1=RX18f0*Xb990 30.2=RX1ce0*Xb990 30.3=RX1d30*Xb990 30.4=RX1d80*Xb990 30.5=RX1dd0*Xb990 30.6=RX1e20*Xb990 Pete

PMDG have their own cockpit controls, and especially their autopilots are always different to the FS ones. The documentation that comes with it should tell you these things. Have you asked on the PMDG forums? Pete

That system is for a program which wants to register keypresses in FSUIPC which can be detected by programming inside that program which monitors the flag bits which tell it when the key is pressed. There is a similar facility for detecting button presses. And of course that works for clients or local programs because it is all a matter of offset manipulation. Maybe he asked you for such advice earlier, but the question I was answering was "On my main PC I want to press a key combination such as Ctrl-1 and pass that through FSUIPC such that on my remote PC my app can detect it. Then my app can act accordingly with that key combination." which seemed to be asking more for something like KeySend. Maybe I misunderstood him too? Maybe we are both wrong in our interpretations? Pete

There are lots of logging facilities in WideClient, documented in the documentation for WideFS. You should also use FSInterrogate and/or one of the FS utilities supplied, like WeatherSet or TrafficLook, to make sure they are getting data okay. The business of facilities in WideFS which you can use actually being documented has come up twice in a short time now. Do you actually have the documents to hand. They are supplied in the downloadable ZIP for WideFS. Pete

There's no facility that does exactly that, but there is one which is much more flexible and can be programmed to do that if you wish. This is "KeySend", which is actually documented in the WideFS documentation. Briefly you assign whatever you like, keystroke or button, it doesn't matter, to the "Keysend" control in FSUIPC, giving it a parameter, a number from 1-255. Then in WideClient.INI you place a parameter which tells WideClient what to do when it receives than specific KeySend. As well as sending keystrokes to a program it can start or stop a program and a few other things. Pete

Well, that is one I've seen mentioned before, so it might be worth looking at, but I can't promise anything. It depends on what the code looks like, whether there's an easy way to bypass the crash area without just moving it elsewhere. I won't be able to look at it for a week or so, too many other commitments, but it is on my list. Pete

Please run FS9, at least until you are ready to fly, and then close it. Go to the FS9 Modules folder and find the log ("FSUIPC.LOG"). Open it in a text editor, and copy and paste the whole content into a message here. You can use the <> button above the edit area to enclose it neatly. Pete

It depends entirely on the aircraft model. Are you using the new Prosim738 model? If so the cabin lights need other lights setting too. No idea why. If you are using that model let me know and I'll give you the 0D0C settings I use. Took a lot of experimentation to work it all out! Pete

Well there's no Simconnect reconnects, so FSUIPC itslef isn't stuttering nor even seeing one. The actual flying time started after where it says "Advanced weather interface enabled". Are the Stops due to you going into menus or similar? If not are they about the right times for the stutters? (the numbers on the left are elapsed milliseconds, so the "stops" occurred at 8.4, 78 and 109 seconds into the flight. FSUIPC logs those when Simconnect tells it the Sim is stopped. It looks like you didn't close FS before getting the log, so something's I might be able to see are missing. However, at present it all points to something the aircraft is doing. Pete

I said "do check the FSUIPC4 log file"! You don't need to do anything. Just run, get the stutter, close down, find the FSUIPC4.LOG file in the FS Modules folder, and paste it into a message here. Pete

Reinstalling FSUIPC never makes any difference. What happens if you just say "Yes" to this prompt? Usually this is just a SimConnect DLL timing bug, and it recovers. After that it doesn't happen again. Pete

Which G3D.DLL error? There are lots of different ones. Pete

For keyboard key presses, FSUIPC assignments will override FS assignments, so, yes, you can do what you want without de-assigning the FS assignments. Just assign the keypresses in FSUIPC which you want to be different But you cannot do this with buttons and axes (levers, yokes, rudders, joysticks). Either assign in FS and not have them different in profiles, or disable controllers in FS and assign all in FSUIPC. Then you can have different ones for different profiles. Pete

Thanks Dougal. :oops: :oops: :oops: Pete

What happens if you register WideFS first? Why not register both in the same install attempt? There has been no change in the registration system for years The last change was to allow separate email addresses from FSUIPC and WideFS. If you tell me both SimMarket order numbers I will try and see what your problem is. Pete

But earlier you implied (though your detail was very mised up) tht the IP address was 192.168.2.1. See here: Pinging 192.168.2.1 with 32 bytes of data: Reply from 192.168.2.1: bytes=32 time<1ms TTL=64 Reply from 192.168.2.1: bytes=32 time<1ms TTL=64 Reply from 192.168.2.1: bytes=32 time<1ms TTL=64 Reply from 192.168.2.1: bytes=32 time<1ms TTL=64 Ping statistics for 192.168.2.1: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 0ms, Average = 0ms However, I cannot ping my #1 PC by its name fresh1011-MSI The fact that "ping" also gets the wrong IP address shows something is wrong on your Network, or maybe the router set up. Pinging fresh1011-MSI.Belkin [198.105.254.228] Er, what's the difference? TCP operates with ports. The ports WideFs uses are defined in the INI files, and they only need to match. "Connect to FSX" surely just means "connect to WideServer which is part of FSUIPC which is running inside FSX". I really don't know what you are on about here. So earlier when youpnged it on 192.168.2.1 you were mistaken? When WideServer is enabled in FSUIPC options, it opens the port. It only does this when FS is ready to fly, not when in the preliminary setup screens. The title bar of FSX will sohw that it is waiting for clients. If it does not show this then it is not enabled. You've never showed me your WideServer.log file from the Server, so I can't tell whether you've got it enabled and licensed or not. Pete

Yes, I'm pretty sure Accelerator does both. I think it might be better to just try installing the two missing Simconnect's first. You'll find them in the SDK section of the disk, in the LegacyIUnterfaces subfolder of SimConnect. Pete

Well, I said it was okay, but you shouldn't get these if your FSX is up to date. If the SP2 and SP1 versions of SimConnect aren't installed you will find many add-on applications won't run. Pete