Jump to content
The simFlight Network Forums

scott967

Members
  • Content Count

    40
  • Joined

  • Last visited

Everything posted by scott967

  1. I was wondering if there was any way to move the user aircraft to a given ICAO? I don't need the exact runway start, just the airport ref point would be good enough. Sort of like using the "go to airport" menu. scott s. .
  2. Thanks. I was looking for a shortcut that I could put in a Lua script. What I am doing is tryng to automate some testing. I'm working on a project to create accurate timezones for FSX which involves creating a relatively large number of timezone rectangles that set the base time offset and the DST dates. The probem is that with the large number of resulting timezones doing a reasonable test. The only way I can find to know the local time offset that's being used in FSX is to manually look at the world -- time and season settings menu. I went through about 50 or so airports this way, first "go to airport" then reading out the local time. So next I wrote a script that is writing to file the offset 0246 on an offset event and also by timer along with aircraft lat/lon, and then trying to write flightplans that take me over a reasonable test area and run at simrate 8x to capture data, then ploting it to see if it is "right". Still kind of slow. I was thinking it might be an improvement instead of flying a flightplan to just jump from airport to airport and log the offset at each one. I can look at my plot and get a good selection of possible trouble airports (such as near time boundaries) and also some random selection. So my idea was to use a list of ICAOs as input and then move the user aircraft, read the offest, and repeat all under the script. I guess I can extract airport lat/lon/alt data from my plot but that's just a bit more work. sorry for posting in wrong forum. I was looking for some info in the FAQ and didn't realize I wasn't back in support forum when I posted. scott s. .
  3. I was wondering if there was any control that can set the 2d panel transparency such as in the FSX options display aircraft slider? I'm thinking maybe not, as it seems if transparency is set to 0% the outside view will take the sizeX and sizeY parameters from panel.cfg, while any transparency above 0% causes the outside view to fill the window and I imagine that would be hard to change on the fly with a control. scott s. .
  4. scott967

    Saitek Joystick Modes

    My suggestion would be if you are going to use fsuipc to program your Saitek, dump the Saitek drivers and just use the default win 7 ones. AFAIK all you get with the Saitek drivers is the "auto-calibrate" feature of Saitek which never worked well for me anyway. scott s. .
  5. I've been looking at the multi-joystick assignment "method 2" shown in the advanced user guide. My question concerns the throttle axis: joystick 1 has a single throttle lever which normally would be assigned "axis throttle set". joystick 2 has multiple throttle levers, set "axis throttle 1 set""axis throttle n set" as appropriate on a per-aircraft basis. Joy1 is always connected. Joy2 is only connected at times. So when Joy2 is not connected I want to use Joy1, but when Joy2 is connected I want to prefer Joy2. Any way to make those work together? I haven't experimented, but I assume that the "throttle" and "throttle 1" would be seen by fsuipc as different controls and each would be sent to FS? My first thought was to assign the joy1 throttle to "throttle 1", and then in calibrations calibrate throttle 1 and in throttle 2 check the "map 1 to 234" checkbox, but that seems to prevent calibrating throttle 2, 3, or 4 on joy2. scott s. .
  6. Thanks, I'm a little slow getting back because I am reinstalling everything on Win 7 x64 and I am trying to redo stuff in a better setup, rather than just duplicate what I had been using before. I've always plugged the second joy into the same USB and seem to not have had any problems with windows xp reassigning , though I guess Win 7 may differ. I think just having both sticks assigned will probably work OK, at least for the throttle as I have a bit of idle zone assigned. Will have to see how it works with aileron and elevator. My saitek x45 stick seems to get noisy pots sometimes. In my old setup I had different fs9.cfg files I called by shortcut and each called a different fsuipc.ini but I was wanting to get away from the two different FS9 shortcuts. scott s. .
  7. Well, the SimMarket product page says: UPGRADING FROM FSUIPC 3 or/and WIDEFS 6? If you purchased FSUIPC 3 or/and WIDEFS 6 after or on JULY 1st 2007, you are entitled to the special upgrade price of EUR12.00 (+VAT where applicable) only. NOTE: The special upgrade price will be awarded automatically, therefore you must be logged into your same account used to purchase the previous version! If in doubt contact simMarket support first! NO REFUNDS GIVEN! So my guess would be contact simMarket support. scott s. .
  8. OK, I have my JoyNames: [JoyNames] AutoAssignLetters=No 0=Saitek X45 Flight Controller 1=CH Pro Pedals USB 2=Saitek Pro Flight Yoke 3=Saitek Pro Flight Quadrant so is the idea that I edit these such as [JoyNames] AutoAssignLetters=No S=Saitek X45 Flight Controller R=CH Pro Pedals USB Y=Saitek Pro Flight Yoke Q=Saitek Pro Flight Quadrant or do I append these these lines to this section? Then for my existing assignments, I edit them all accordingly 1=R2,20,C65966,0 to 1=RY,20,C65966,0 and 0=2Z,256,F,65765,0,0,0 to 0=YZ,256,F,65765,0,0,0 ? scott s. .
  9. got it -- thanks scott s. .
  10. Is there any problem moving sections around in the fsuipc.ini file? My aircraft calibrations / assignments are kind of randomly added and I would like to straighten them out a bit. scott s. .
  11. The multi-ini support in 4.306 is working very nice. Thanks for putting it in. scott s. .
  12. Is there a way to get multiple ini's in FSUIPC4? ControlName= in fsx.cfg doesn't seem to do anything. Or some other way to achieve this effect? I have different hardware configurations and use different fsx.cfg variants for them, and would like to match FSUIPC options to them, as I did in FSUIPC3. scott s. .
  13. scott967

    FSUIPC4 multiple ini?

    I do use the aircraft specific options, which works really well along with shortname. My yoke takes up a lot of deskspace, and sometimes I just want to use the stick for some quick work, esp when I am doing scenery development. I guess it's mainly the roll, pitch, and throttle axis settings, I don't think there is a problem with duplicate button settings. scott s. .
  14. scott967

    FSUIPC4 multiple ini?

    I found it really useful!!! I have both a stick and yoke, with different assignments and calibrations depending on which I have plugged in. Multi fs9.cfg with matching fsuipc.ini is a life saver. It would be great to have it back if possible. scott s. .
  15. Now that you mention it, I think when I was first playng around I might have selected the "throttlen_set by mistake which maybe part of my comprehension problem. Will keep playing. scott s. .
  16. I'm trying to figure out how FS will interpret the position of axis_throttle_n_set, prop_n_set, and mixture_n_set for any arbitrary aircraft. Is there a section of aircraft.cfg or the .air file that defines this? For example, some throttles give max, idle, reverse, some have max, flight idle, beta/ground fine, ground idle, reverse. Some no reverse. etc. Other than trial and error, I would to do a better job of setting up the operating range and null spots in fsuipc axis settings. scott s. .
  17. scott967

    Help with SAITEK

    I'm not Pete, but I also recently bought the Saitek yoke and throttle quads (6 lever axis total) and have started to investigate how best to use. So far I've been playing with only default AC (baron and 737). Here is what I'm doing on the 737 and probably will work on the DF727. Right now I am working just on FS9, though FSX probably is about the same. I have FSUIPC 3.82 registered installed. At this point I am not using the Saitek drivers or profiler at all, just the generic MS HID driver. 1. Using the control panel game controller applet, calibrate the axis levers. For me, I found the quad a bit of work, as the first 2 levers are interpreted as x y joystick, and the calibration assumes they have a "centered" position. I tried to approximately place both the levers in their midpoint position. This isn't a problem for the yoke axis levers, since the calibration will set the actual "yoke" to the x y joystick axis. 1. Start FS, load your 727, then go to the control assignments. remove all axis lever assignments, both yoke and quad. You can leave the aileron/elevator if you want. Also, go into the button assignments and remove all button assignments for the yoke and quad. Most important is buttons 8-10 on the yoke, but get rid of all the rest while you are at it. You can replace them later one at a time. Leave the yoke POV assigned as-is. 2. read the FSUIPC user guide. Make sure you are in normal (not slew) mode. open FSUIPC from the menu. In axis calibration move your throttle 1 axis lever so FSUIPC sees it. Set it to "aircraft specific". select the "send to Fs as a normal axis. In the boxes below, check the top one and select Axis Throttle 1 Set (NOT THROTTLE1 SET!!!) 3. Repeat for the other 2 axis levers, except select Axis Throttle 2 set and Axis Throttle 3 set of course. 4. Go into calibration. Go to the throttle 1-4 page. On throttle 1 click on "set" move the throttle all the way up and click the max "set". Move the throttle all the way down (but do not push it into the button position) and click the nin "set", then click the idle "set ONCE. MOve the lever up slightly (maybe about to -15700 or so) and click the idle set once again. This will set your throttle idle band at min lever position and give no reverse. 5. Repeat the calibration for throttles 2 and 3. 6. Go into buttons + switches. once again check aircraft specific. Pull throttle 1 lever down so that it activates the "reverser" button (all the way to the stop). Check the "select for FS control". In the box below, select Throttle 1 Decr. Also check the "control to repeat while held". 7. Repeat for the buttons on your throttle 2 and 3. Setting them to throttle 2 decr and throttle 3 decr of course. That should be it. Note that with engines in reverse, you have to move the throttles slightly out of idle to cancel the reverse. Note that when you set your idle band, it is impossible to get all three the same and it might be a good idea to open up fsuipc.ini in a text editor and find the right section and set the idle the same on all (like -15700 on all 3): Throttle1=-16384,-16384,-15700,16383 Throttle2=-16384,-16384,-15700,16383 Throttle3=-16384,-16384,-15700,16383 scott s. .
  18. scott967

    WideFS 6.65 no Connect

    FWIW, I also hit my head against the ServerIPAddr and Portotcol= issue. Actually, I had the problem on 6.6.1.7 beta, and went back to 6.5.1, then I just d/led 6.6.5 and find the problem is still there. You (Pete) were on holiday at the time IIRC so didn't post. I take it to set PreferredProtocol on the server I also have to set advertiseservice=yes? I'm getting so many variant copieis of the inis now on my systems I'm kind of getting lost. I ended up dumping my inis and using the ones in the zip file; that at least got me connected again. I guess I'm old school and just prefer calling servers by IP address. scott s. .
  19. scott967

    Axis Assignment Problem 3.60

    Thanks. I grabbed 3.617 and will give it a try. BTW, I had occasion to use GPSout and it works very well, thank you. scott s..
  20. Using FSUIPC 3.60. I have an axis (V) assigned to axis elev trim set. My main problem is that the iFly B747-400 panel does not like having an axis assigned to elev trim, either using FS9 joystick assignment, or via FSUIPC axis assignment. What I would like to do, is find a way to delete this axis assignment, just for this aircraft. In trying to do this, I tried checking the "this aircraft ony" box, then removing the check for axis elev trim set. This appeared to work (the box was cleared) but it didn't seem to take. So then I tried to delete the assignment for all aircraft, both by unchecking the axis setting box and clicking the "clear" box. either way it seems to take according to the UI, but when I restart FS9 it is back. I also tried reseting the axis in the axis calibration dialog, thinking that might have an effect (it didn't). Viewing the ini I see the line is still in there: [Axes] 1=0V,256,F,65766,0,0,0 0=0U,256,F,66382,0,0,0 It appears that the GUI isn't working to remove an axis assignment, or am I doing something wrong? Obviously I can edit the ini. Is there a way to remove the axis assignment, just for one aircraft while having it available for all others? Or maybe there is a better way to try to have an axis controlling elev trim that perhaps would not cause problems with the iFly panel? scott s. .
  21. Thaks for the support. I will fwd this info and in the meantime make the manual key entry. scott s. .
  22. Installed unregistered FSUIPC 3.22. FSUIPC now alerts that an unaccredited program is attempting to access FSUIPC. The log file also complains about Active Radar (part of Active Sky) but if I don't select the Dash 8 aircraft I don't get that error. FSUIPC 3.202 (previous version I was running) does not present this error. Note that the MakeItVersion2002 flag is set in ini. Log follows. scott s. ********* FSUIPC, Version 3.22 by Pete Dowson ********* User Name="" User Addr="" FSUIPC not user registered WIDEFS not user registered, or expired Module base=61000000 ClassOptions: UIPCMAIN=FF7F, FS98MAIN=FF7F, FS2KMAIN=FF5E WeatherOptions(Orig)=0000B027[0000B027] InitDelay: 0 seconds WeatherReadInterval=4 MakeItVersionFS2002 is set! LogOptions=00000001 DebugStatus=0 3254 System time = 10:51:07 3264 D:\Microsoft Games\Flight Simulator 9\ 3264 System time = 10:51:07, FS2004 time = 12:00:00 (00:00Z) 5878 C:\Documents and Settings\sws\My Documents\Flight Simulator Files\PHNL gate 23.flt 5928 AIRCRAFT\MS_b737_400\Boeing737-400.air 5928 Aircraft="MS Boeing 737-400 Orbit" 9173 Module identified = "ActiveRadar.dll" 9173 ModuleOK="ActiveRadar.dll" 18436 AIRCRAFT\Dash8-Q300_2\DHC8Q3.air 18436 Aircraft="Dash8-Q300 V1.004b Jazz Green" 18857 Module identified = "Dash8All.GAU" 19247 Illegal read attempt: offset 0C49, size 1 19247Program or module not accredited for use with this unregistered FSUIPC 20349 Module identified = "ActiveRadar.dll" 20349 ModuleOK="ActiveRadar.dll" 22502 Illegal read attempt: offset 0C4C, size 1 22502Program or module not accredited for use with this unregistered FSUIPC 22512 ### IPC Message processed in 3265mSecs ### 26007 System time = 10:51:30, FS2004 time = 10:51:12 (20:51Z) 26007 *** FSUIPC log file being closed Memory managed: 2 Allocs, 2 Freed ********* FSUIPC Log file closed ****
  23. Thanks. 1. I have not entered any keys manually. Both programs use installers, and I don't have any record if they attempted to install keys as part of the overall install. If there is a published key for the fanda dash 8, I haven't seen it. 2. Here is the key data: [Programs] ActiveRadar.dll=5G3EUHFOBQE4 There is no entry for the Dash8All.gau 3. Enabling IPC write logging gave a 60k file after just a couple secs. I don't know if there is a way to send attachments, or other way to forward info. Here is an excerpt, hopefully of use: 39908 System time = 20:33:54, FS2004 time = 20:33:23 (06:33Z) 39908 WeatherOptions set, now 0000B027 (timer=0) 39908 LogOptions changed, now 00000005 (LogExtras=0) 40068 Traffic File #14 = "scenery\world\scenery\trafficsu04ver3" 53227 AIRCRAFT\Dash8-Q300_2\DHC8Q3.air 53227 Aircraft="Dash8-Q300 V1.004b Jazz Green" 54178 Module identified = "Dash8All.GAU" 54178 WRITE0 (failed, read-only!) 330A, 2 bytes: 4C 04 55460 Illegal read attempt: offset 0C49, size 1 55460Program or module not accredited for use with this unregistered FSUIPC 56371 Module identified = "ActiveRadar.dll" 56371 ModuleOK="ActiveRadar.dll" 57052 Illegal read attempt: offset 0C4C, size 1 57052Program or module not accredited for use with this unregistered FSUIPC 57052 Illegal read attempt: offset 0872, size 2 57052 Illegal read attempt: offset 0C4A, size 1 57052 Illegal read attempt: offset 3000, size 25 57052 Illegal read attempt: offset 0C4B, size 1 57052 Illegal read attempt: offset 0C4C, size 1 57052 Illegal read attempt: offset 0870, size 2 57052 Illegal read attempt: offset 085C, size 4 57052 Illegal read attempt: offset 0864, size 4 57052 Illegal read attempt: offset 086C, size 4 57052 Illegal read attempt: offset 0872, size 2 57052 Illegal read attempt: offset 0C5A, size 1 57052 Illegal read attempt: offset 301F, size 25 57052 Illegal read attempt: offset 0C5B, size 1 57052 Illegal read attempt: offset 0264, size 2 57052 Illegal read attempt: offset 0BCA, size 2 57052 Illegal read attempt: offset 0BC0, size 2 57052 Illegal read attempt: offset 0BB6, size 2 57052 Illegal read attempt: offset 02B8, size 4 57052 Illegal read attempt: offset 02B4, size 4 57052 Illegal read attempt: offset 02C8, size 4 57052 Illegal read attempt: offset 3070, size 8 57052 Illegal read attempt: offset 0B7C, size 4 57052 Illegal read attempt: offset 0B98, size 4 57052 Illegal read attempt: offset 0310, size 8 57052 Illegal read attempt: offset 0568, size 8 57052 Illegal read attempt: offset 0560, size 8 57052 Illegal read attempt: offset 023A, size 1 57052 Illegal read attempt: offset 0239, size 1 57052 Illegal read attempt: offset 023B, size 1 57052 Illegal read attempt: offset 034E, size 2 57052 Illegal read attempt: offset 0BC4, size 2 57052 Illegal read attempt: offset 0BC6, size 2 57052 Illegal read attempt: offset 2ED0, size 8 57052 Illegal read attempt: offset 31A8, size 8 57052 Illegal read attempt: offset 3078, size 8 57052 Illegal read attempt: offset 31A0, size 8 57052 Illegal read attempt: offset 31C8, size 8 57052 Illegal read attempt: offset 31B0, size 8 57052 Illegal read attempt: offset 3080, size 8 57052 Illegal read attempt: offset 31B8, size 8 57052 Illegal read attempt: offset 3088, size 8 57052 Illegal read attempt: offset 2910, size 4 57052 ### IPC Message processed in 1592mSecs ### 58925 WRITE0 8001, 25 bytes: 5A 55 48 52 41 58 34 31 43 48 59 35 44 61 73 68 58925 38 41 6C 6C 2E 67 61 75 00 58925 WRITE0 2910, 4 bytes: 80 00 02 00 59065 WRITE0 2418, 8 bytes: D0 B8 95 CF 89 BC F7 3F 59065 WRITE0 2518, 8 bytes: D0 B8 95 CF 89 BC F7 3F 59065 WRITE0 0C4E, 2 bytes: 00 00 59065 WRITE0 0350, 2 bytes: 00 00 59065 WRITE0 0388, 1 bytes: 02 59065 WRITE0 0C5E, 2 bytes: 00 00 59065 WRITE0 0352, 2 bytes: 00 00 59065 WRITE0 0388, 1 bytes: 02 59065 WRITE0 034C, 2 bytes: 90 01 59065 WRITE0 0356, 2 bytes: 00 00 59065 WRITE0 0389, 1 bytes: 02 59065 WRITE0 034E, 2 bytes: 95 22 59065 WRITE0 038A, 1 bytes: 02 59065 WRITE0 0354, 2 bytes: 21 00 59065 WRITE0 038A, 1 bytes: 01 59065 WRITE0 (failed, read-only!) 2EF0, 8 bytes: 00 00 00 00 00 00 00 00 59065 WRITE0 (failed, read-only!) 2EE8, 8 bytes: 00 00 00 20 0D EA D0 BF 59065 WRITE0 07C0, 4 bytes: 00 00 00 00 59065 WRITE0 07C4, 4 bytes: 00 00 00 00 59065 WRITE0 07C8, 4 bytes: 00 00 00 00 59065 WRITE0 07D0, 4 bytes: 00 00 00 00 59065 WRITE0 07D8, 4 bytes: 00 00 00 00 59065 WRITE0 07EC, 4 bytes: 00 00 00 00 59065 WRITE0 0804, 4 bytes: 00 00 00 00 59065 WRITE0 0808, 4 bytes: 00 00 00 00 59065 WRITE0 07CC, 2 bytes: 00 00 59065 WRITE0 07D4, 4 bytes: 00 00 00 00 59065 WRITE0 07F2, 2 bytes: 00 00 59065 WRITE0 3122, 1 bytes: 00 59065 WRITE0 0D0C, 2 bytes: 00 00 59065 WRITE0 2910, 4 bytes: 80 00 02 00 59065 WRITE0 2418, 8 bytes: D0 B8 95 CF 89 BC F7 3F 59065 WRITE0 2518, 8 bytes: D0 B8 95 CF 89 BC F7 3F 59065 WRITE0 0C4E, 2 bytes: 00 00 59065 WRITE0 0350, 2 bytes: 00 00 59065 WRITE0 0388, 1 bytes: 02 59065 WRITE0 0C5E, 2 bytes: 00 00 59065 WRITE0 0352, 2 bytes: 00 00 59065 WRITE0 0388, 1 bytes: 02 59065 WRITE0 034C, 2 bytes: 90 01 59065 WRITE0 0356, 2 bytes: 00 00 59065 WRITE0 0389, 1 bytes: 02 59065 WRITE0 (failed, read-only!) 2EF0, 8 bytes: 00 00 00 00 00 00 00 00 59065 WRITE0 (failed, read-only!) 2EE8, 8 bytes: 00 00 00 20 0D EA D0 BF 59065 WRITE0 07C0, 4 bytes: 00 00 00 00 59065 WRITE0 07C4, 4 bytes: 00 00 00 00 59065 WRITE0 07C8, 4 bytes: 00 00 00 00 59065 WRITE0 07D0, 4 bytes: 00 00 00 00 59065 WRITE0 07D8, 4 bytes: 00 00 00 00 59065 WRITE0 07EC, 4 bytes: 00 00 00 00 59065 WRITE0 0804, 4 bytes: 00 00 00 00 59065 WRITE0 0808, 4 bytes: 00 00 00 00 59065 WRITE0 07CC, 2 bytes: 00 00 59065 WRITE0 07D4, 4 bytes: 00 00 00 00 59065 WRITE0 07F2, 2 bytes: 00 00 59065 WRITE0 2910, 4 bytes: 80 00 02 00 59065 WRITE0 2418, 8 bytes: D0 B8 95 CF 89 BC F7 3F 59065 WRITE0 2518, 8 bytes: D0 B8 95 CF 89 BC F7 3F 59065 WRITE0 0C4E, 2 bytes: 00 00 59065 WRITE0 0350, 2 bytes: 00 00 59065 WRITE0 0388, 1 bytes: 02 59065 WRITE0 0C5E, 2 bytes: 00 00 59065 WRITE0 0352, 2 bytes: 00 00 59065 WRITE0 0388, 1 bytes: 02 59065 WRITE0 034C, 2 bytes: 90 01 59065 WRITE0 0356, 2 bytes: 00 00 59065 WRITE0 0389, 1 bytes: 02 scott s. .
×

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.