Jump to content
The simFlight Network Forums

Ian P

Administrators
  • Posts

    5,629
  • Joined

  • Last visited

  • Days Won

    7

Everything posted by Ian P

  1. You can use the throttle, but it will only work as a throttle, not correctly as the engine management system of an A320. The reason for this is that the A320 does not use throttles in the same way as, say, a Boeing 737 does - it uses a system of "gates", which you click the throttles into to select modes. Once it is in that gate, you don't move it until you enter a different phase of flight. Basically, once it it is CLB, you leave it there until you close the throttles to land. This is what the keypresses simulate. So if you want to use the throttles to fly, you can, but you can't use the autothrottle if you do so. There is no workaround for this. However, if you absolutely have to fly controlling the aircraft using the throttle quadrant to select the gates then the fix is "buy the FeelThere/Wilco A320", where the gate position is selected using the throttle on your stick or quadrant rather than by keypresses. It does have some bugs, yes, but so does the PSS model! Ian P. (Ex PSS beta tester once upon a time)
  2. Just for further information, my download was on the corporate system too, through two firewalls, two AV scans (although both are McAfee Enterprise) and the Proxy. Ian P.
  3. Given the name of the "virus" (which appears to be a heuristic "well it looks like a virus so I'd better flag it up" report rather than an actual live malware report) I'd suggest that's probably a false positive, but only the AV company can confirm that. I've just downloaded the 29th release (March 1st 2009 (4 MB)) from http://www.schiratti.com/dowson.html and McAfee is reporting it as clean here. What AV package are you using? Ian P.
  4. I don't think this is in the right place, so will move it to Pete Dowson's forum... However, I'm also not sure that you have the right tools to do what you want to anyway. Are you trying to display FS views (i.e. cockpit, or external view) on a different computer? If so, that isn't what WideFS does. Can you provide more information on what you are trying to do, please? Ian P.
  5. The driver updates did change the identity of the devices, Pete. I had the same issue (but fortunately didn't have much assigned through FSUIPC at that moment, because I was testing, so I just reassigned the controls to the new device IDs). Ian P.
  6. Most of that was found using the forum search tool, Mats - the information is all here, as Pete says. I think the only thing I had to work out myself was the gear lever, which wasn't too difficult either, to be honest. Have fun! I was there during the morning Pete, it's a pity I didn't get to say hello. I hate it when I find out that people I've wanted to meet for ages were in the same place at the same time and I didn't meet them! :mrgreen: I'll drop you a PM regarding my thoughts on the show, as this thread probably isn't really the place to discuss it. I thought it was OK though, at least it wasn't grossly overhyped like a certain now deceased show was. Edit: One thing that FSUIPC still does provide, which FS doesn't, is individual throttle reversers though - that single function is exceptionally useful, rather than having to reverse all throttles at the same time. Cheers, Ian P.
  7. FSUIPC behaves the same with a Saitek as a CH throttle, but the Saitek isn't built the same as a CH throttle - the reverser operates differently. While I was able to configure the CH TQ using the manual instructions, I had to do it slightly differently with the Saitek units. (Which I also bought at the Brum show... Were you there Pete?) Prior to having to redo everything because the FSUIPC calibrations clashed with SP1 of the A2A B377 (I'll discuss that one on another thread at some point), I had two standalone throttle quads, a yoke and pedals all calibrated and working via FSUIPC. The way I set them up was to put the Reverse and both Idle settings as being the same - the "idle" detent on the throttles. You have to remember that the reversers are buttons, not part of the potentiometer travel, on the Saitek quads. The "full power" setting is the top of the arc, so that's 16634 or whatever it should be, with the other three settings all at -16634 or whatever the number should be. That results in the full travel of the lever being used for power. For the reversers, set up a button so that it is pressed when the lever is moved to the reverse position. Set it to "Throttle 1 Decr" and "Repeat While Pressed", then for the "On Release" drop-down, set it to "Throttle 1 Close". This means that when you move the lever off the button, back to idle, it effectively presses F1, returning the throttle to idle power without having to add power, then remove it, using the lever. Repeat for throttle 2... and 3 and 4 if you're flying things with that many engines. That worked for me, with everything but the Stratocruiser. I now have the throttles for that configured using FSX internally, but the reversers and gear lever are still controlled by FSUIPC. It's all working perfectly. Ian P.
  8. Make sure you have the latest version of FSUIPC and reinstall it. Also try re-running SP2. This will ensure that you are running versions of FSUIPC and Simconnect that will talk to each other. That's the first thing to try, before doing anything more drastic! Ian P.
  9. No. As Jim says, it's an internal application - it can only be run inside FS. Although I believe you can window it and drag it to a second screen on the same system (I've never tried this). Sorry! Ian P.
  10. That sounds like a solution to my problem, Pete - we discussed this a while back. I'm currently running three different FSUIPC ini files and renaming them as necessary when I change control setups - the reason being that FSUIPC wants to call both my joystick and the throttle quad "controller 2" (the yoke is controller 3, the pedals controller 1). I can't leave the yoke and stick and TQ all plugged in at the same time, it's either "stick" or "yoke and quad", so to avoid my stick movements controlling engines, I need multiple FSUIPC.ini files. I think the solution you just outlined would solve me occasionally forgetting to rename ini files - it's actually exactly how I used to run FS9 with one for the Dodosim B206, one for 4-engine setups and one for 2-engine setups. Ian P.
  11. Hi Gerald, I'm pretty sure that problem has been discussed and solved before, most likely on Pete Dowson's support forum, further down the list here at Simflight. You might like to have a quick check through the threads here: viewforum.php?f=54 , particularly this one: viewtopic.php?f=54&t=58095 Hope that helps! Cheers, Ian P.
  12. That's just one word I always get wrong! :roll: I do know better as well. My fingers just don't listen to my brain... :lol: Cheers, Ian P.
  13. Sorry - Anti-Torque Rotor (tail rotor). Losing it when flying in the cruise is not a major disaster. Losing it at low speed makes you spin rather rapidly in the opposite direction than the main rotor spins and results in a collection of broken helicopter parts. Landing without an ATR is one of rotary wing aviation's great challenges. Anyway, back to the original topic, I do wonder how much of the internal failure options are designed to be used in an "instructor control" way, in either shared cockpit multiplayer or through a directly connected instructor panel as has been done in the past? It would definately be of use to ESP-based applications, but not so much to your average offline FS user right now, I suspect. Cheers, Ian P.
  14. There seem to be a lot more options available to fail "inside the sim" using the menu drop down than you seem to be able to control using Simconnect, as you note, or you can assign to keystrokes (which seems to be a half way house between what simconnect can control and the huge array of options inside the sim). The "failures" pages inside the sim also seem specific to the aircraft you are flying - comparing the Beaver which I looked in last night (masses of failure options including each individual engine cylinder), and the Bell 206 which I have open now (only a few, very little on the engine), it looks like the options you can assign to keystrokes or can fail through simconnect are only those that are "generic" to all aircraft. I do note that you can't fail the ATR in the helicopters. That's a pity, albeit an off-topic one. Cheers. Ian P.
  15. In the "failures" options under the aircraft drop-down in the sim, Pete, you can pick individual cylinders in the engine to fail (as well as, obviously, entire engines, oil supplies, fuel pumps and wotnot...) Cheers, Ian P.
  16. Hi Pete, thanks very much for your quick response. That, unfortunately, is where the problem lies - FSUIPC is seeing both the CH TQ and the Joystick (when not plugged in at the same time, obviously) as "device 2" and as such is assigning the functions I have assigned the TQ to the stick. If I change them for the stick, then plug the TQ back in, I have to reset them back for the TQ. Basically, it is seeing both controllers as the same device which is why I was hoping to find a way of convincing FSUIPC that they are different. Windows detects them differently, but the settings assigned to the CH TQ in FSUIPC overrule those I assign to the stick using any other system. I was hoping to avoid doing that for every helicopter and fast jet I have installed! :lol: I guess the easiest way is just to do an aircraft specific setup for each one as I use it for the first time. A pain, certainly, but not a massive one. Have a good Christmas. :) Cheers, Ian P.
  17. Hi folks, Deities know how many threads I've just trudged through (plus the manual, obviously) trying to find an answer to this, and I'm quite happy to accept that my searches have been bad, but I can't find an answer, although I'd be amazed if I'm the only person needing to do this... I have two completely different sets of controllers for FS: a yoke and throttle quad for fixed wing GA/airliners, etc and a stick for fast jets, helicopters, etc. Both have one common component - the Saitek pedals which are constantly connected. The issue is quite simple. Having set everything up with the fixed wing GA kit (Saitek Yoke, CH Throttle Quad, Saitek pedals) and got it working the way I want in FSUIPC 4.207, I now can't disconnect all that, plug in the joystick and fly - the reason being that the joystick is detected as device 2 - calibrated and assigned in FSUIPC as the CH quad. So my joystick has become throttle 1 and throttle 2 instead of elevator/ailerons. Apart from having everything plugged in all the time, which I physically cannot do, so FSUIPC detects them as different devices, is there any way I can tell it to differentiate between the stick and the TQ? Cheers, Ian P.
  18. Definately well deserved, Pete! Ian P.
  19. Off topic, for which I apologise, but you could always join Virgin Media / ex-NTHell / ex-Telewest, Pete - our ruddy modem is being remotely rebooted every day at 16:20. :roll: :x Well, it's one way to refresh IP/DNS I suppose! :lol: Ian P.
  20. Hi gents, FSPassengers runs as a module inside FS9, not a gauge and not an external application (fspassengers.dll). Cheers, Ian P.
  21. Hi Joseph, There's a dedicated FSUIPC support forums further down the list, where Pete Dowson will probably be far more able to help you. Cheers, Ian P.
  22. What anti-virus software are you using? I know a lot of people using WideFS without that report, so suspect it's a false positive (although some viruses do overwrite applications or files with themselves, so it's probably worth reinstalling WideFS just to be sure). Cheers, Ian P.
  23. Hi George, I'm not entirely sure this is the best place to post this... It might be more suited to Pete Dowson's support forum, further down the list. :) Hopefully an admin will appear shortly and move it down there or something. ;) Cheers, Ian P.
×
×
  • 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.