Jump to content
The simFlight Network Forums

Bman.

Members
  • Content Count

    12
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Bman.

  • Rank
    Member
  1. ...we are stumped. The [Auto] load of LUAs is not functioning. It use to but something has gone wrong and now no scripts will autoload. We have tried a new .ini all together, used another known good ini file, checked spelling and syntax and all appears correct. The LUAs will load with assigned buttons but nothing via [Auto]. I am not sure what broke. Any one with suggestions? [Auto] 1=Lua ThrottleManager 2=Lua FuelManager 3=Lua BrakeManager 4=Lua PayloadManager 5=Lua ReadWeather [Auto.Jetstream] 1=Lua JS41SaitekMP 1=Lua JS41ColdDark [LuaFiles] 1=ThrottleManager 2=NOT USED 3=JS41SaitekMP 4=JS41ColdDark 5=TurbineSwitches 6=NOT USED 7=RandomWeather 8=FuelManager 9=PayloadManager 10=ReadWeather 11=BrakeManager The Log & Console are showing the same information. Console Started ... ********* FSUIPC4, Version 4.85 by Pete Dowson ********* Running inside FSX on Windows 7 Module base=14450000 User Name="Benjamin Van Eps" User Addr="fly-bman2006@hotmail.com" User WideFS Addr="fly-bman2006@hotmail.com" FSUIPC4 Key is provided WideFS7 Key is provided 1388 System time = 14/08/2012 23:09:53 1388 FLT UNC path = "\\BMAN-FSX\Users\Bman\Documents\Flight Simulator X Files\" 1419 Trying to connect to SimConnect Acc/SP2 Oct07 ... 1435 FS UNC path = "\\BMAN-FSX\Bman - OS Drive\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\" 1685 LogOptions=00000000 00000001 1685 Wind smoothing fix is fully installed 1685 G3D.DLL fix attempt installed ok 1685 SimConnect_Open succeeded: waiting to check version okay 1685 Trying to use SimConnect Acc/SP2 Oct07 2699 Running in "Microsoft Flight Simulator X", Version: 10.0.61637.0 (SimConnect: 10.0.61259.0) 2699 Initialising SimConnect data requests now 2699 FSUIPC Menu entry added 2714 \\BMAN-FSX\Users\bman\documents\flight simulator x files\Default Cold & Dark.FLT 2714 \\BMAN-FSX\Bman - OS Drive\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\SimObjects\Airplanes\Aircreati on_582SL\Aircreation_582SL.AIR
  2. Making headway. The Alpha naming is working out pretty good. A few interesting things about the GUID numbers - if you disconnect the controller and hook up a different one in it's place, the GUID goes away for the Alpha labled controller. Plug it back it and it's still gone when you restart FSX / FSUIPC but.... but... the controll axis still work just fine. It must call up the control and use the GUID for the same joystick with the same name. See below. This is my current .ini. See how A and B have no GUIDS (but the same control name with the numeric label does). This is with those quadrants plugged back into the mix. No GUID for the Alpha named controllers. PS - where in this list is joystick Q being called up? Buttons & Keypresses? [JoyNames] AutoAssignLetters=No Y=Saitek Pro Flight Yoke Y.GUID={A3EFA000-DC20-11E1-8001-444553540000} T=Saitek Pro Flight Cessna Trim Wheel B=Saitek Pro Flight Throttle Quadrant A=Saitek Pro Flight Throttle Quadrant R=Saitek Pro Flight Rudder Pedals R.GUID={3A735F20-D90C-11E1-8002-444553540000} C=Saitek Pro Flight TPM System << MISSING JOYSTICK >> 0=Saitek Pro Flight Rudder Pedals 0.GUID={3A735F20-D90C-11E1-8002-444553540000} 1=Saitek Pro Flight Yoke 1.GUID={A3EFA000-DC20-11E1-8001-444553540000} 2=Saitek Pro Flight Cessna Trim Wheel 2.GUID={B468D960-DC20-11E1-8002-444553540000} Q=<< MISSING JOYSTICK >> 3=Saitek Pro Flight Throttle Quadrant 3.GUID={E5D4FAB0-DC20-11E1-8003-444553540000} 4=Saitek Pro Flight Throttle Quadrant 4.GUID={E5D4FAB0-DC20-11E1-8004-444553540000} [WideServer] WideFSenabled=Yes AdvertiseService=1 Port=8002 Port2=9002 [buttons] ButtonRepeat=20,10 1=RT,20,C66634,0 5=PQ,21,CL1:T,2 6=PQ,20,CL1:T,1 7=PY,5,CL7:R,1 53=B3125&1=x0 P65,0,C66340,0 54=B3125&1 U65,0,C66340,0 55=B3125&2=x0 P65,0,C66341,0 56=B3125&2 U65,0,C66341,0 9=B3125&4=x0 P65,0,C66342,0 10=B3125&4 U65,0,C66342,0 11=B3125&8=x0 P65,0,C66343,0 12=B3125&8 U65,0,C66343,0 13=P65,3,C66162,0 14=U65,3,C66162,16383 15=P65,3,C66163,0 16=U65,3,C66163,16383 17=P65,3,C66164,0 18=U65,3,C66164,16383 19=P65,3,C66165,0 20=U65,3,C66165,16383 21=P65,2,C66072,0 22=U65,2,C66073,0 23=D281C=0 P66,0,C66241,0 24=D281C U66,0,C66241,0 25=D3B78=0 P66,1,C66363,0 26=D3B78 U66,1,C66363,0 27=D3AB8=0 P66,1,C66364,0 28=D3AB8 U66,1,C66364,0 29=D39F8=0 P66,1,C66365,0 30=D39F8 U66,1,C66365,0 31=D3938=0 P66,1,C66366,0 32=D3938 U66,1,C66366,0 33=P65,1,C66488,1 34=U65,1,C66488,0 35=P65,1,C66489,1 36=U65,1,C66489,0 37=P65,1,C66490,1 38=U65,1,C66490,0 39=P65,1,C66491,1 40=U65,1,C66491,0 41=D2440=0 P65,1,C66338,1 42=D2440 U65,1,C66338,0 43=B0609=0 P64,0,C66023,0 44=B0609=0 P64,1,C66024,0 45=B0609=0 P64,2,C66025,0 46=B0609=0 P64,3,C66026,0 47=B0609=0 P64,4,C66027,0 48=B0609 P64,0,CL5:R,5 49=B0609 P64,1,CL5:R,6 50=B0609 P64,2,CL5:R,6 51=B0609 P64,3,CL5:R,10 52=B0609 P64,4,CL5:R,9 57=PR,7,CL1:T,2 58=PR,6,CL1:T,1 59=RY,6,K187,8 60=RY,7,K189,8 63=PB,6,CL1:T,1 64=PB,7,CL1:T,2 65=PC,0,K49,9 66=PC,1,K50,9 67=PC,2,K113,10 68=UC,2,K113,10 69=UC,0,K49,9 70=UC,1,K50,9 71=PC,6,K68,9 72=UC,6,K68,9 [AutoSave] AutoSaveEnabled=No Interval=60 Files=10 SaveOnGround=No Next=9 1=Fri 002055 2=Fri 002155 3=Fri 002254 4=Fri 002354 5=Fri 002453 6=Fri 002553 7=Sun 225415 8=Sun 225813 9=Fri 001856 10=Fri 001956 [GPSout] GPSoutEnabled=No Port=COM1 Speed=4800 Interval=2000 PosTo6Decimal=No Sentences= [GPSout2] GPSoutEnabled=No Port=<none set> Speed=4800 Interval=2000 PosTo6Decimal=No Sentences= [sounds] Path=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\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=BENJAMIN-ASUS [MacroFiles] 1=4X_DA20-100 [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=-16350,0,512,16383/8 Elevator=-16384,0,512,16320/8 Throttle1=-16384,-512,512,16383/40 Throttle2=-16384,-512,512,16383/40 PropPitch=-16380,16380 PropPitch1=-16384,0,512,16383/40 Mixture1=-16384,8192,8192,16383/32 Mixture2=-16384,-16384,-16384,16383/32 PropPitch2=-16384,0,512,16128/40 Rudder=-16383,0,512,16383 LeftBrake=-16384,24576/24 RightBrake=-16384,24576/24 Mixture=-16384,16383 [Axes] 21=CX,256,D,4,0,0,0 22=CY,256,D,5,0,0,0 23=CR,256,D,6,0,0,0 0=RX,256,D,7,0,0,0 1=RY,256,D,8,0,0,0 2=RZ,256,D,17,0,0,0 3=RR,256,D,3,0,0,0 4=YX,256,D,1,0,0,0 5=YY,256,D,2,0,0,0 6=YZ,256,D,14,0,0,0 7=TX,256,D,7,0,0,0 8=TY,256,D,8,0,0,0 9=TR,256,D,3,0,0,0 10=AX,256,D,18,0,0,0 11=AY,256,D,13,0,0,0 12=AZ,256,D,14,0,0,0 13=BX,256,D,9,0,0,0 14=BY,256,D,10,0,0,0 15=BZ,256,D,17,0,0,0 [auto] 1=Lua ThrottleManager 2=Lua FuelManager 3=Lua BrakeManager 4=Lua PayloadManager 5=Lua ReadWeather [Auto.Jetstream] 1=Lua JS41SaitekMP [LuaFiles] 1=ThrottleManager 2=NOT USED 3=JS41SaitekMP 4=JS41ColdDark 5=TurbineSwitches 6=NOT USED 7=RandomWeather 8=FuelManager 9=PayloadManager 10=ReadWeather 11=BrakeManager [Window.LUA display] Docked=7347, 2835, 3541, 2457 Undocked=2286, 183, 1108, 212 [Keys] 9=49,10,L7:R,1 11=50,10,L10:R,1 13=112,10,L4:R,0 21=52,10,L3:R,0 23=51,10,L8:R,1 24=53,10,L1:R,1 26=54,10,L11:R,1
  3. Thanks Pete - I have no idea how I ever missed the checkbox selection for FSX controls for all these years. I guess I never really looked for it since everything was controlled by FSX at one time. I have two saitek quads - I will see what happens with the names / GUIDs. If they get bunched up for some reason, I will know why. Thanks for the response. Benjamin.
  4. Evening all- I finally broke down and bought the L-39 - slapped in my X-52 (removing my yoke + quads) and reassigned my axis so the controls would perform correctly. I knew when I brought my yoke and quads back into play it was going to be trouble. ...fast forward, I put the yoke + quads back on the setup and removed the X-52. Of course I had to re-assign and then promply hit the manual since it was a pain in the neck. I hadn't hooked up the two different controllers since I picked up FSUIPC long while back. (I am a sucker for GA...so the yoke never came of the desk). Got it - page 25 / 26 of the manual. Before I dive into trying to getting everything interchangable, am I correct that: 1) If I lable each device and GUID to a alpha numberic letter - they will stay in the .ini when removed? That's what I get from "If you have assignments to an alpha ID and that joystick is removed, so no longer being named, the assignments remain included in the INI file but are not loaded into FSUIPC..." 2) If using Alpha lettering - do I still have to be consistant with the USB ports I use or are there different GUID or Names when different ports are used? This is the biggest one since I don't have a system down yet with my powered USB hub to control device. If it matters, I will label my cords & ports. 3) If my controls are all different, I could just turn on autoassignletters=yes, reassign my axis and be done with it. Nothing would be lost in any case. I am going to do some testing (backing up the .ini) and check it out but I just want to make sure I know what I am doing. Benjamin
  5. Thanks for the time to respond, Pete. Sage advice there on the SxS - noted. In the end, we got it sorted it out. You were correct in thinking that it's not a simconnect issue. I did change back to maxclients=64 and it all works. For testing, we also changed back to 10....err... it still worked. I did a few other minor changes like removing conflicting SaiPanel drivers etc. Could have been one of those. We don't really now. After 3 days... enough persistence and it now works. Thanks again- Benjamin.
  6. Pete- This is sort of off topic but you might be able to shed some light on what might be going on. This is long winded but here is what is happening with our shared cockpit experience. For years we haven't had much trouble with shared cockpit and everything seemed to be working par given the compatibility of various planes. We could transfer back a fourth 100 times and it always worked great. Now, all of a sudden we are encountering a problem when I transfer controls to the pilot not flying. If I host a session (via gamespy), we can depart just fine.. if I transfer the controls o the pilot not flying the plane hits a "ceiling" sort to speak. There is no longer vertical movement of the plane. Lateral movement is just fine. Even vertical speed shows a 1000 FPM climb but the plane will not ascend / not decend. As soon as the controls are transferred to me, away we go. We have about 5 guys that are in the group and they all have the same problem when they fly with me. Between other pilots, no problems. We have checked the usual suspects: 1) Hard reset of the router 2) Open up the stack of route ports 3) Verified windows firewall 4) Check and verified all A/P is shut off etc. 5) Hard reset of modem 6) FSPortTest has been checked 7) Removed MS FSX from Firewall then re-added 8) FSX run as administrator - verified 9) Check hard set IP gateway 10) Turn of DMZ 11) Blue line direct to modem with A/V off and firewall off Same results. Now the reason I come to FSUIPC forum (outside of your obvious expertise). This week we have been working with FSUIPC (John Szatmary has been doing all the work - thanks for that). While messing around with the throttle calibration I managed to wreck something to where my throttle quad wouldn't recognize correctly through fsx. Other applications started heading south as well. Long story short, I ended up doing a checkpoint restore from about 2 hours prior and I was back up and running. The check point worked fine and all seems well. The LUA coding that John put together works fine. All controls are fine. Fast forward about 2 hours and we are kicking off some shared cockpit flight and we encounter this problem with some of the data not being pushed through between the two pilots (namely the vertical climb/descent). As noted, the pilot flying hits a "ceiling" and the plane will not elevate nor descend. If I get the controls back, there is no problem. A few things I have noticed about my simconnect.xml <?xml version="1.0" encoding="Windows-1252"?> <SimBase.Document Type="SimConnect" version="1,0"> <Descr>SimConnect</Descr> <Filename>SimConnect.xml</Filename> <Disabled>False</Disabled> <SimConnect.Comm> <Disabled>False</Disabled> <Protocol>IPv4</Protocol> <Scope>Global</Scope> <Address>192.168.1.50</Address> <Port>4507</Port> <MaxClients>10</MaxClients> <MaxRecvSize>8192</MaxRecvSize> <DisableNagle>True</DisableNagle> </SimConnect.Comm> MaxClients - Is it possible I am maxing out in some form? I don't know the part this plays relative to shared cockpit. DisableNagle - should this be false? I am going to temporarily rename exe.xml and dll.xml and see what happens when nothing is loaded initially. Any way, I am just seeing what your thoughts may be since you are an expert. Before I do a rebuild, repair or install of simconnect (still don't know about how to specifically repair the other two sxs simconnect folders - that's a different chore) and I am grasping for last minute suggestions. Your thoughts and suggestions are welcome. Thanks. Win7 64b FSX + Acceleration FSUIPC v4.725b 7 Saitek USB modules (yoke / quads / boxes etc) Benjamin.
  7. Roger, I will do some testing with direct comparison. I will go an autosave and ";" in the relative same location and see what happens. I know FSUIPC isn't doing anything wonky I just can't figure out why is would be so much different. I will keep you posted on what I find. Thanks Pete!
  8. Ok, I just checked a standard manual save and it loaded in 18s.... I have no idea why the autosave would take so much longer. Any thoughts?
  9. Morning all- I have a quick question. I have just started using some of the features in FSUIPC registered version. My primary use is for WideFS and some remote applications. Lots of really nice features in this package. Autosave - I have autosave setup to save every 2 minutes or so... and to save 10 flights max. When I go to reload one of these flights they take forever (as in 5+ minutes). I have a SSD drive and when I just load a flight using the menus, they will load in about 12 seconds. Any thoughts on what is causing these saved flights to take so long? I will test it compared to a flight that I manually save and see if that makes any difference. Thanks! Benjamin.
  10. I see - I am with it now. I think the key is that all of my newer apps have a "connect" button which obviously kicks in the specific simconnect function. Where as the older apps I use really just look for a running FS application somewhere. Thanks for help and looking forward to utilizing all the features of FSUIPC. Benjamin.
  11. Afternoon all- I finally bit the bullet and hooked up with FSUIPC & WideFS combo. Sweet! The real reason I broke down and got it was because on one free application that I wanted to run on my laptop (FSBlackBox) I need to invest the time to learn all the benefits of the full blown version of FSUIPC. I have been simming for decades and feel like I have been missing out what it has to offer. Any rate, my question. Some of the other apps I run on the laptop include FSMap, PlanG, REX Engine, FSInn and BlockBox. All of the other apps have some version of a simconnect.cfg file that I marry up with the information I have setup in the simconnect.xml. Everything works great. The only program that didn't have such an option was this Blackbox so that ultimately brought me to FSUIPC + WIdeFS. The setup went after spending about 5 minutes in the manual. I went just for the direct IP connect connection by adding the Protocol=TCP and ServerIPAddr= information in the [config] section. My questions - is there any benefit to running all of my other application through WideFS connection or just keep them direct with a simconnect.cfg/.xml link? One benefit it that I wouldn't have to manage each of those connection profiles separate. If you get WideFS to connect, they should theoretically all connect without having to mess with simmconnet any longer.. correct? Second question - If I do have the WideFS started which way are my apps connecting? Will the applications connect through WideFS or through the simconnect information I have set up in each independent program? Thanks! Bman.
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.