Graham Pollitt

No but then I had never tried it until today just before I replied to this thread to see if I could see the issue that Adam was referring to. It doesn't affect me anyway as I don't assign using that method so is irrelevant to me whether it's an issue with FS, FSUIPC, Windows, Razer driver etc. The way I assign to the Razer works and that's all I'm bothered with,

Adam, You need to assign a key on the main keyboard to a function either within FS or FSUIPC and then assign that same key to a button on the keypad via the Razer software. I use mine in both FSX and P3D and have never had any problems setting up this way. I understand what you mean by FSUIPC not detecting the button press but if you setup as above then that is not an issue.

Hi Pete, Any plans to implement the new SDK items to offsets within the recent update for the PMDG NGX? thanks

Run makerwys.exe, copy the r5.csv file to your project folder or path directly to the file in the FS directory. Code a parser reader to find the two airports that you want from the r5.csv file and to obtain the lat/lon co-ordinates of those two airports Read here for the formulae you'll need for the distance between two lat/lon points. You'll have to decide which point you want to use for each airport http://williams.best.vwh.net/avform.htm

No you wouldn't set the interval nor enable the timer within the 'tick' routine as it would never start Set the interval in the form load section or at design time if the interval does not need to be changed and start the timer when the app is started

Did you have FSUIPIC reinstalled again when V/S stopped working? Above you don't mention reinstalling it. If you didn't its not a problem with FSUIPC If you did have you checked buttons and axis assignments in case there has been a control assigned that shouldn't be and is overriding the AP?

Did you look in the log file as Pete suggested above? The answer could lie within!

I don't have a use for it but thanks for sharing your work anyway, maybe somebody will find it useful and give you some positive feedback :cool:

Quick search found this http://forum.simflight.com/topic/74981-assign-left-mouse-button-to-joystick-button-how/

You mean remove the dll from the modules folder? Soumds to me like a possible axis conflict but it can't be if you are using an unregistered copy as you wouldn't be able to assign and calibrate etc

If anything it should be on to prevent the airspeed misreads depending upon icing etc. Not saying it may be the cause of your problems but off is bad compared to it being on.

No you just copy the data below the header eg in my ini file I have the below [buttons] ButtonRepeat=20,10 1=RB,0,C65607,0 2=RB,1,C65615,0 3=PA,4,C66079,0 4=PA,5,C66080,0 7=PA,10,K97,8 8=PA,11,K123,8 9=PA,7,C65752,0 [buttons.PMDG 737] 0=PA,9,K88,9 1=PB,4,K86,10 2=PB,5,K86,11 3=PB,6,K66,10 4=PB,7,K66,11 5=PA,0,K88,10 6=PA,8,K90,10 8=RB,11,C65602,0 9=UB,11,C65604,0 11=PA,1,K67,10 so to make the 737 buttons apply as generic I copy that section into the generic buttons section like this. [buttons] 0=PA,9,K88,9 1=PB,4,K86,10 2=PB,5,K86,11 3=PB,6,K66,10 4=PB,7,K66,11 5=PA,0,K88,10 6=PA,8,K90,10 8=RB,11,C65602,0 9=UB,11,C65604,0 11=PA,1,K67,10 To make the 737 buttons apply to another specific aircraft only you could copy that same section into the header for the new aircraft like this [buttons.PMDG Jetstream 41] 0=PA,9,K88,9 1=PB,4,K86,10 2=PB,5,K86,11 3=PB,6,K66,10 4=PB,7,K66,11 5=PA,0,K88,10 6=PA,8,K90,10 8=RB,11,C65602,0 9=UB,11,C65604,0 11=PA,1,K67,10 There may be an easier way to do this but I am happy editing files etc so thats the way I would do it. Only takes a few seconds anyway.

I think one way would be to edit your ini flle and copy the sections eg I have a section like [buttons.PMDG 737] for the NGX and like this [buttons] for generic aircraft. Just find the section for the aircraft you have programmed and copy it into the [buttons] section

Thanks Pete, I've used the 333C offset and works fine. Code below for anyone interested (vb.net) though you'll need to modify for own use Private Shared fsWideFSRunning As Offset(Of UShort) = New FSUIPC.Offset(Of UShort)("widefs", &H333C) Public Shared WideFSRunning As Boolean Public Shared Sub getfsWideFSRunning() FSUIPCConnection.Process("widefs") WideFSRunning = fsWideFSRunning.Value End Sub then check like this - I have this code at the start of my timer section SimulatorEvents.getfsWideFSRunning() If SimulatorEvents.WideFSRunning = False Then Me.Timer_Seconds.Enabled = False 'pause polling' Dim msg = MessageBox.Show("The connection to Flight Sim has been lost, retry connection?", "WideFS connection lost", MessageBoxButtons.YesNo, MessageBoxIcon.Question) If msg = DialogResult.Yes Then Me.Timer_Seconds.Enabled = True Exit Sub 'exit sub and retry on next poll count' Else Dim msg2 = MessageBox.Show("Abandon retry?", "Restart Application?", MessageBoxButtons.YesNo, MessageBoxIcon.Question) If msg2 = DialogResult.Yes Then 'stop main timer and reset app' Me.Timer_Seconds.Enabled = False frmMain.ClearData() Exit Sub Else 'no' Me.Timer_Seconds.Enabled = True Exit Sub 'exit sub and retry on next poll count' End If End If End If

Hi, I am unable to detect a crash and my app continues to run normally on the client pc when the fsx server disconnects and I am connecting via WideClient. Obviously I don't get any new data just the same data from the last read each time my timer ticks. Even when WideClient eventually times out and gives the 'waiting for a connection' message my app still continues to read the offsets as though the connection is still there. Any ideas how to trap this please? I've had a quick read of the WideClient manual but can't seem to locate a relevent parameter. thanks Graham