cjibbotson Posted December 11, 2011 Report Posted December 11, 2011 Hi Pete, I hope you dont mind me cross posting a thread I started a couple of days ago on AVSIM regarding the above. I've been having issues using PMDG's 737NGX and its becoming apparent it only exists when FSUIPC is installed. The following URL will explain my initial issues which is a slightly edited copy of a post another user made in August who was having the same problems. The only way he could resolve it was to remove FSUIPC (which I can concur stopped my problems regarding the autothrottle) which I do not want to do as I like it and the work you have done to help G3D.DLL crashes means I must keep it as I was plaqued with them. I'm hoping you can look through this and comment, there's only a few posts to read. I'm using the latest installer with update 'e' installed http://forum.avsim.net/topic/355826-using-separate-throttles-with-the-737ngx/page__fromsearch__1 Thanks Chris Ibbotson
Pete Dowson Posted December 11, 2011 Report Posted December 11, 2011 I've been having issues using PMDG's 737NGX and its becoming apparent it only exists when FSUIPC is installed. The following URL will explain my initial issues which is a slightly edited copy of a post another user made in August who was having the same problems. The only way he could resolve it was to remove FSUIPC (which I can concur stopped my problems regarding the autothrottle) I would rather have seen a description of what was actually going wrong. Having read through the referenced thread the only detail of what you thought was wrong was this: I'm using a Saitek Pro Flight Yoke with additional throttle quadrant with the 737NGX, and I'm having a bit of trouble setting the 737NGX up to work correctly with separate throttles (i.e. "throttle 1" and "throttle 2"). It works manually, but not under A/T but the "cyan arc" feature does not work correctly, and sometimes moving the throttle causes the autothrottle to disconnect The only other useful tidbit was this: It does it if 2 axis are configured in FSUIPC for throttle 1 and throttle 2, it also does it if I remove these axis and assign them within FSX axis control. I have tried a few options in FSUIPC...i.e. assigning the axis to use FSUIPC Calibration or as a direct FSX control but both change thrust and disconnect the AT when it shouldnt all of which implies that the throttles are calibrated in FSUIPC. The place of assignment would then make no difference -- the FSUIPC calibration will normally make the AXIS_THROTTLE controls change to THROTTLE controls, and that probably bypasses the check in the NGX code. You either need to turn off the FSUIPC throttle calibration (press the Reset button), or set it for NRZ (no reverse zone) operation and with the "UseAxiscontrolsForNRZ=Yes" option in the appropriate [JoystickCalibration] section of the INI file. The same sort of need applies to the Wilco airbus. You can of course make this Profile or Aircraft specific. Regards Pete
cjibbotson Posted December 11, 2011 Author Report Posted December 11, 2011 Hi Pete and thanks for your reply. Basically the issue appears to be that if 2 separate throttles are assigned either through FSX (and axis removed from FSUIPC) or vice versa any movement of the Saitek throttle lever when flying with the Autothrottle engaged resulted in the engines spooling up/down to match the controllers position then after a second or two would return to its correct postion, moving it a larger distance would result in the AT disconnecting and returning to manual speed control, PMDG have options for this throttle override to have it ALWAYS, NEVER or the realistic option in HOLD/ARM mode which would allow the pilot to pull back the thottles say to abort a takeoff thus disconnecting the AT. PMDG have implimented a new feature of a 'blue arc' on the N1 thrust display, it shows the physical position of your hardware controls compared to the sims position allowing you to adjust if you are planning to manually disconnect AT soon so theres no sudden shift in thrust. I think I tried it with the throttles reset in the calibration page, but will try your again when I return home. As it still gave issues only assigned via FSX controls it may not work but hope it does along with your suggestion about the *.ini file. A quick test on Friday with my whole Modules folder removed from the root directory made the throttles perform correctly but obviously I dont wish for this option. Frogot to say the Throttle Set 1 and 2 (sorry forgotten the exact name) are both calibrated with no reverse zone as I have thrust reverse assigned to two buttons which are triggered when the throttles are detended below idle. Thanks for any input in helping Pete
Pete Dowson Posted December 11, 2011 Report Posted December 11, 2011 I think I tried it with the throttles reset in the calibration page, but will try your again when I return home. As it still gave issues only assigned via FSX controls it may not work Where and how you assign things does not affect FSUIPC calibration -- if you've enabled calibration then it works on the controls no matter where or how you assign. FSUIPC assignment facilities were added a long time after calibration. The latter has been possible for FS axes since FS2000 times I think. If you aren't assigning in FSUIPC, or are assigning to FS controls not direct to calibration, and you are not calibrating in FSUIPC, then FSUIPC doesn't touch the controls at all. It only intercepts them if it needs to. ,,, but hope it does along with your suggestion about the *.ini file. If you switch off the calibration then the INI option is irrelevant. You only need to try that if you actually want to use FSUIPC calibration. Pete
cjibbotson Posted December 15, 2011 Author Report Posted December 15, 2011 Hi Pete, Just updating you on the above issues and no matter what I do or if throttle axis are assigned in FSX or FSUIPC they will now work correctly with the Autothrottle on the NGX providing I do NOT calibrate them using FSUIPC. Once I do that moving the levers results in the engines spooling up or down and eventual disconnection. It's a bit frustrating as I like the option to sync the axis so they are both calibrated the same. Chris Ibbotson
Pete Dowson Posted December 15, 2011 Report Posted December 15, 2011 Just updating you on the above issues and no matter what I do or if throttle axis are assigned in FSX or FSUIPC they will now work correctly with the Autothrottle on the NGX providing I do NOT calibrate them using FSUIPC. I assume you tried the NRZ option with the INI file change I mentioned (UseAxiscontrolsForNRZ) ? Odd that if this is a general problem no one else has mentioned it. However, there really isn't anything i can do about it if PMDG have programmed it in such a way that they only take account of throttle controls arriving from SimConnect at the top priority, which sounds like may be the case. You see, in order for FSUIPC to receive the values, calibrate or sync them, and send them back, it has to receive them from SimConnect at one priority level then send the changed ones back at a lower level. It cannot send at the same or higher level because you'd then get a never-ending loop and no one would ever see the throttle values. Regards Pete
cjibbotson Posted December 15, 2011 Author Report Posted December 15, 2011 I assume you tried the NRZ option with the INI file change I mentioned (UseAxiscontrolsForNRZ) ? Odd that if this is a general problem no one else has mentioned it. However, there really isn't anything i can do about it if PMDG have programmed it in such a way that they only take account of throttle controls arriving from SimConnect at the top priority, which sounds like may be the case. You see, in order for FSUIPC to receive the values, calibrate or sync them, and send them back, it has to receive them from SimConnect at one priority level then send the changed ones back at a lower level. It cannot send at the same or higher level because you'd then get a never-ending loop and no one would ever see the throttle values. Regards Pete PMDG do warn in their Introduction Manual against calibrating using FSUIPC for some reason, perhaps this is one. Yes I tried both pressing the NRZ tickbox, as I use a button to reverse and also tried manually changing the INI to YES but on manual control those made thorottle 2 behave strangely, when pulling them both back the throttle one would go to idle but throttle 2 would stop around 50% and display the calibration going from +16300 down to approx +4000, it wouldnt go to -16300. Its not that big a deal I'm just glad I've got 2 throttles working, just thought I'd say incase there was a conflict with the Autothrottle on PMDG. On my original post the guy Martin had the exact same issue and he simply removed FSUIPC which will of course resolve it as it's not doing any calibration. Chris Ibbotson
Pete Dowson Posted December 15, 2011 Report Posted December 15, 2011 Yes I tried both pressing the NRZ tickbox, as I use a button to reverse and also tried manually changing the INI to YES You'd need both together, not one or the other. but on manual control those made thorottle 2 behave strangely, when pulling them both back the throttle one would go to idle but throttle 2 would stop around 50% and display the calibration going from +16300 down to approx +4000, it wouldnt go to -16300. They are both treated identically, so it sounds as if you didn't recalibrate throttle 2 after changing the options. You would need to do that. Regards Pete
cjibbotson Posted December 15, 2011 Author Report Posted December 15, 2011 Pete thats the problem, I did recalibrate both axis, I've Treble checked the assignments which are correct too, when NRZ is ticked, throttle 2 doesnt go into the minus figures like throttle 1, resetting it and even unplugging the controls and trying again still failed, it seemed to stop around +4000. I've a separate throttle quadrant and even tried two axis on that after removing from other quadrant but same results. BTW I only see one tickbox for NRZ and only one entry for it in the ini file, is this correct? I've also removed FSUIPC and reinstalled and started afresh with my assignments but no luck
Pete Dowson Posted December 16, 2011 Report Posted December 16, 2011 Pete thats the problem, I did recalibrate both axis, I've Treble checked the assignments which are correct too, when NRZ is ticked, throttle 2 doesnt go into the minus figures like throttle 1, resetting it and even unplugging the controls and trying again still failed, it seemed to stop around +4000. It sounds like something else it contributing something there. Perhaps you could show me your INI file for this, and tell me which version of FSUIPC you are using. Actually, first, if it isn't 3.998m or 4.751, could you update and check with the latest first, please, so when I check it i know I'm using the same. BTW I only see one tickbox for NRZ and only one entry for it in the ini file, is this correct? There's a different NRZ checkbox option for each group of controls -- i.e. 4 throttles, 4 mixtures, 4 prop pitches. They can be separately selected, but It wouldn't make sense to have one engine with a completely different method of control to another. In the INI file the NRZ settings are part of the encoding in the calibration, in the number at the end after the /. The only INI file option with "NRZ" in the name is the one stating "UseAxisControlsForNRZ" hich should be in the same JoystickCalibrations section as the calibrated axes it relates to. Regards Pete
cjibbotson Posted December 16, 2011 Author Report Posted December 16, 2011 This is my ini file at present, without the throttle axis set in the calibration tab. I'll calibrate them and post separately [General] UpdatedByVersion=4749e History=1TRAZUNSYVA2O2B1460LD MouseWheelTrim=No MouseWheelTrimSpeed=1 JoystickTimeout=20 PollGFTQ6=Yes BlankDisplays=No FixControlAccel=Yes FixMachSpeedBug=No VisibilityOptions=No OneCloudLayer=No CloudTurbulence=No CloudIcing=Yes 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=Yes WindSmoothness=2 WindSmoothAirborneOnly=Yes PressureSmoothness=0 TemperatureSmoothness=0 DisconnTrimForAP=No ZeroElevForAPAlt=No ThrottleSyncAll=No WhiteMessages=No ShowPMcontrols=No SpoilerIncrement=512 MagicBattery=No RudderSpikeRemoval=No ElevatorSpikeRemoval=No AileronSpikeRemoval=No ReversedElevatorTrim=No ClockSync=Yes ClockSyncMins=5 ClearWeatherDynamics=No OwnWeatherChanges=No TimeForSelect=4 LoadFlightMenu=No LoadPlanMenu=No PauseAfterCrash=No BrakeReleaseThreshold=75 SaveDataWithFlights=No ZapSound=firework ShortAircraftNameOk=No UseProfiles=Yes EnableMouseLook=No AxesWrongRange=No TCASid=Flight TCASrange=40 AxisCalibration=No DirectAxesToCalibs=No ShowMultilineWindow=Yes SuppressSingleline=No SuppressMultilineFS=No AxisIntercepts=No DontResetAxes=No InitDelay=0 GetNearestAirports=No WeatherReadFactor=2 WeatherRewriteSeconds=1 CustomWeatherModify=No SimConnectStallTime=1 LuaRerunDelay=66 Console=No FSVersionUsed="Microsoft Flight Simulator X",10.0.61472.0 SimConnectUsed=10.0.61259.0 [JoyNames] AutoAssignLetters=No 0=Logitech Formula Force EX USB 0.GUID={F421FC40-1933-11E1-8002-444553540000} 1=Saitek Pro Flight Throttle Quadrant 1.GUID={EE3A0880-1934-11E1-8001-444553540000} 2=Saitek Pro Flight Yoke 2.GUID={EFE8C9F0-1934-11E1-8002-444553540000} [buttons] ButtonRepeat=20,10 2=P1,3,K50,10 3=P1,2,K49,10 4=P1,4,K51,10 5=P1,5,K52,10 6=R2,14,K53,10 7=R2,15,K54,10 8=R2,16,K55,10 9=R2,17,K56,10 10=R2,18,K57,10 11=R2,19,K48,10 12=R1,7,C65966,0 13=R1,8,C65971,0 14=R2,0,K190,8 15=R2,2,C65607,0 17=P1,0,K190,10 18=R2,3,C65615,0 19=R2,32,C65734,0 20=R2,36,C65735,0 21=R2,38,C65671,0 22=R2,34,C65672,0 23=R2,39,C65854,0 24=R2,33,C65856,0 25=R2,35,C65857,0 26=R2,37,C65855,0 27=P2,5,C65860,0 28=P1,1,C65861,0 29=P2,6,C65564,0 [AutoSave] Next=4 Interval=120 Files=5 SaveOnGround=No AutoSaveEnabled=Yes 1=Mon 190917 2=Thu 224421 3=Thu 224620 4=Mon 190517 5=Mon 190717 6=Tue 225357 7=Tue 225457 8=Tue 225556 9=Tue 233149 10=Tue 224501 [GPSout] GPSoutEnabled=No Port=COM0 Speed=4800 Interval=2000 PosTo6Decimal=No Sentences= [GPSout2] GPSoutEnabled=No Port=<none set> Speed=4800 Interval=2000 PosTo6Decimal=No Sentences= [WideServer] WideFSenabled=Yes [sounds] Path=D:\Microsoft Flight Simulator X\Sound\ Device1=Primary Sound Driver Device2=Speakers (SoundMAX Integrated Digital HD Audio) Device3=Digital Output (SoundMAX Integrated Digital HD Audio) Device4=Speakers (Apowersoft_AudioDevice) Device5=SPDIF Interface (SoundMAX Integrated Digital HD Audio) [JoystickCalibration] AllowSuppressForPFCquad=Yes ExcludeThrottleSet=Yes ExcludeMixtureSet=Yes ExcludePropPitchSet=Yes SepRevsJetsOnly=No ApplyHeloTrim=No UseAxisControlsForNRZ=No FlapsSetControl=0 FlapDetents=No 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=-16380,-512,512,16380 Elevator=-16380,-512,512,16380 Rudder=-16249,-512,512,16383/16 Flaps=-16384,16256/16 Spoilers=-16384,16128/16 [Axes] 0=0S,256,D,3,0,0,0 1=1X,256,D,22,0,0,0 2=1Y,256,F,65820,65821,0,0 3=1Z,256,F,65821,0,0,0 4=2X,256,D,1,0,0,0 5=2Y,256,D,2,0,0,0 6=2U,256,D,23,0,0,0 7=2V,256 8=2V,D,-16384,-3381,66080,0 9=2V,U,9728,16383,66079,0 10=2V,B,1536,6528,65700,0 [Axes.] 0=0S,256,D,3,0,0,0 1=1X,256,D,22,0,0,0 2=1Y,256,D,9,0,0,0 3=1Z,256,D,10,0,0,0 4=2X,256,F,65695,0,0,0 5=2Y,256,F,65694,0,0,0 6=2U,256,D,23,0,0,0 7=2V,256 8=2V,D,-16384,-3381,66080,0 9=2V,U,9728,16383,66079,0 10=2V,B,1536,6528,65700,0 [Profile.] 1=
cjibbotson Posted December 16, 2011 Author Report Posted December 16, 2011 Here's the ini with the 2 throttes calibrated. This is a fresh FSX install and both throttles seem to work corectly now intune with each other compared to throttle 2 previously only going down to about 40-50% after syncing the axis, I've created about 5 sync points. They now work fine manually in the NGX but still issues when using the autothrottle. A white arc appears beside N1 thrust rating whilst the engines spool up/down, when autothrottle is engaged and cruising at the requested speed moving the saitek levers shows a blue arc so you can match the physical lever position to the N1% in the sim so that when you disconnect its the same and no sudden shift in power, just noticed with throttles calibrated in FSUIPC this blue arc is missing...its white so the engines change thrust until you let go of the throttles, they then go back to the correct value. Removing the throttles from your calibration page results in the NGX working correctly. Heres my calibrated ini [General] UpdatedByVersion=4749e History=UNK6TOHLUP6FIW5VY0UFL MouseWheelTrim=No MouseWheelTrimSpeed=1 JoystickTimeout=20 PollGFTQ6=Yes BlankDisplays=No FixControlAccel=Yes FixMachSpeedBug=No VisibilityOptions=No OneCloudLayer=No CloudTurbulence=No CloudIcing=Yes 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=Yes WindSmoothness=2 WindSmoothAirborneOnly=Yes PressureSmoothness=0 TemperatureSmoothness=0 DisconnTrimForAP=No ZeroElevForAPAlt=No ThrottleSyncAll=No WhiteMessages=No ShowPMcontrols=No SpoilerIncrement=512 MagicBattery=No RudderSpikeRemoval=No ElevatorSpikeRemoval=No AileronSpikeRemoval=No ReversedElevatorTrim=No ClockSync=Yes ClockSyncMins=5 ClearWeatherDynamics=No OwnWeatherChanges=No TimeForSelect=4 LoadFlightMenu=No LoadPlanMenu=No PauseAfterCrash=No BrakeReleaseThreshold=75 SaveDataWithFlights=No ZapSound=firework ShortAircraftNameOk=No UseProfiles=Yes EnableMouseLook=No AxesWrongRange=No TCASid=Flight TCASrange=40 AxisCalibration=No DirectAxesToCalibs=No ShowMultilineWindow=Yes SuppressSingleline=No SuppressMultilineFS=No AxisIntercepts=No DontResetAxes=No InitDelay=0 GetNearestAirports=No WeatherReadFactor=2 WeatherRewriteSeconds=1 CustomWeatherModify=No SimConnectStallTime=1 LuaRerunDelay=66 Console=No FSVersionUsed="Microsoft Flight Simulator X",10.0.61472.0 SimConnectUsed=10.0.61259.0 [JoyNames] AutoAssignLetters=No 0=Logitech Formula Force EX USB 0.GUID={F421FC40-1933-11E1-8002-444553540000} 1=Saitek Pro Flight Throttle Quadrant 1.GUID={EE3A0880-1934-11E1-8001-444553540000} 2=Saitek Pro Flight Yoke 2.GUID={EFE8C9F0-1934-11E1-8002-444553540000} [buttons] ButtonRepeat=20,10 2=P1,3,K50,10 3=P1,2,K49,10 4=P1,4,K51,10 5=P1,5,K52,10 6=R2,14,K53,10 7=R2,15,K54,10 8=R2,16,K55,10 9=R2,17,K56,10 10=R2,18,K57,10 11=R2,19,K48,10 12=R1,7,C65966,0 13=R1,8,C65971,0 14=R2,0,K190,8 15=R2,2,C65607,0 17=P1,0,K190,10 18=R2,3,C65615,0 19=R2,32,C65734,0 20=R2,36,C65735,0 21=R2,38,C65671,0 22=R2,34,C65672,0 23=R2,39,C65854,0 24=R2,33,C65856,0 25=R2,35,C65857,0 26=R2,37,C65855,0 27=P2,5,C65860,0 28=P1,1,C65861,0 29=P2,6,C65564,0 [AutoSave] Next=2 Interval=120 Files=5 SaveOnGround=No AutoSaveEnabled=Yes 1=Fri 082535 2=Thu 224421 3=Thu 224620 4=Fri 082136 5=Fri 082335 6=Tue 225357 7=Tue 225457 8=Tue 225556 9=Tue 233149 10=Tue 224501 [GPSout] GPSoutEnabled=No Port=COM0 Speed=4800 Interval=2000 PosTo6Decimal=No Sentences= [GPSout2] GPSoutEnabled=No Port=<none set> Speed=4800 Interval=2000 PosTo6Decimal=No Sentences= [WideServer] WideFSenabled=Yes [sounds] Path=D:\Microsoft Flight Simulator X\Sound\ Device1=Primary Sound Driver Device2=Speakers (SoundMAX Integrated Digital HD Audio) Device3=Digital Output (SoundMAX Integrated Digital HD Audio) Device4=Speakers (Apowersoft_AudioDevice) Device5=SPDIF Interface (SoundMAX Integrated Digital HD Audio) [JoystickCalibration] AllowSuppressForPFCquad=Yes ExcludeThrottleSet=Yes ExcludeMixtureSet=Yes ExcludePropPitchSet=Yes SepRevsJetsOnly=No ApplyHeloTrim=No UseAxisControlsForNRZ=No FlapsSetControl=0 FlapDetents=No 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=-16380,-512,512,16380 Elevator=-16380,-512,512,16380 Rudder=-16249,-512,512,16383/16 Flaps=-16384,16256/16 Spoilers=-16384,16128/16 Throttle1=-16380,-512,512,16383/32 Throttle2=-16384,-512,512,16128/32 SyncSlopeThrottle2=26/26,48/49,76/77,104/105,127/128 [Axes] 0=0S,256,D,3,0,0,0 1=1X,256,D,22,0,0,0 2=1Y,256,F,65820,65821,0,0 3=1Z,256,F,65821,0,0,0 4=2X,256,D,1,0,0,0 5=2Y,256,D,2,0,0,0 6=2U,256,D,23,0,0,0 7=2V,256 8=2V,D,-16384,-3381,66080,0 9=2V,U,9728,16383,66079,0 10=2V,B,1536,6528,65700,0 [Axes.] 0=0S,256,D,3,0,0,0 1=1X,256,D,22,0,0,0 2=1Y,256,D,9,0,0,0 3=1Z,256,D,10,0,0,0 4=2X,256,F,65695,0,0,0 5=2Y,256,F,65694,0,0,0 6=2U,256,D,23,0,0,0 7=2V,256 8=2V,D,-16384,-3381,66080,0 9=2V,U,9728,16383,66079,0 10=2V,B,1536,6528,65700,0 [Profile.] 1=
Pete Dowson Posted December 16, 2011 Report Posted December 16, 2011 Here's the ini with the 2 throttes calibrated. This is a fresh FSX install and both throttles seem to work corectly now intune with each other compared to throttle 2 previously only going down to about 40-50% after syncing the axis, I've created about 5 sync points. They now work fine manually in the NGX but still issues when using the autothrottle. As I said earlier, I really can't do anything about the latter. It must be due to the way they've programmed the NGX. BTW version 4.749e is a few versions out of date. We got as far as 4.749i in that range, but the current version is 4.751. Now the the odd calibration issue has disappeared (?), I cannot really diagnose that 00 the INI data looks fine, except that there's an error. At some time it looks like you went to create a Profile but pressed "enter" instead of providing a name or using ESCape to cancel. In recent FSUIPC versions I detect that and don't create a null profile, but you must have created one some time ago, as witnessed by these sections of the INI which you should certainly delete (notice the '.' in the header which should be followed by the profile name): [Axes.] 0=0S,256,D,3,0,0,0 1=1X,256,D,22,0,0,0 2=1Y,256,D,9,0,0,0 3=1Z,256,D,10,0,0,0 4=2X,256,F,65695,0,0,0 5=2Y,256,F,65694,0,0,0 6=2U,256,D,23,0,0,0 7=2V,256 8=2V,D,-16384,-3381,66080,0 9=2V,U,9728,16383,66079,0 10=2V,B,1536,6528,65700,0 [Profile.] 1= Regards Pete
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now