Jump to content
The simFlight Network Forums

Murray Crane

Members
  • Posts

    18
  • Joined

  • Last visited

About Murray Crane

  • Birthday 01/01/1970

Contact Methods

  • Website URL
    http://

Profile Information

  • Location
    Croydon, UK

Murray Crane's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. I'll open with the following: I haven't yet tried this. My setup is in a state of semi-permanent flux at present and this is just one of the future "concerns" I have. Does GFDisplay work in Vista X64/against FSX directly? I currently have my GF panels plugged straight into my FS PC, which is now Vista Home Prem X64, and running FSX Deluxe as well. I've got all working happily enough in GFConfig as I want, but it's about time I redid the FSUIPC button programming for IVAP/SB3, and the associated GFDisplay programming. Murray
  2. Right you are Pete. Thought you might know something about it (FSUIPC being your "baby" and all ;)) I'll reply to the email that the pricelist arrived on...
  3. Hi Peter, I recently (within the last week) got a copy of the PM private price list and I noted with interest the following paragraph: Am I reading this correctly; when I purchase one of the "main" PM products (PMSystems in this particular case) I can claim an FSUIPC licence for free?
  4. Haven't up to now, but I've just printed the documentation PDFs and I'll give it a go (along with using WideClient to start TS2 and directing the keysend to it via the RunX option). UPDATE: Turning on UseSendInput got it working (at least until the microphone "crashed"... Time to reboot ;))
  5. But of course Pete ; ----------------------------------------------- [User] AllowShutdown=AppOnly Log=Errors+ ; =============================================== KeySend1=123,16 KeySend2=123,24 I'm no developer, but a simple Google search yesterday suggests that SetWindowsHookEx still exists as a call Vista understands, so I would think/hope that there is a way to do this.
  6. Hi everyone, My FS9/WinXP-based setup has been running fine for a good few years now, and I've always had a laptop (via WideFS) running IVAP/TS2 (and/or the FSInn recently) with button 1 on my yoke as the TS2 PTT button (via KeySend) That was until I upgraded my newest laptop from WinXP to Vista. Now, whenever I push the PTT button, the log on the laptop starts recording the following error: 748562 Can't SetWindowsHookEx! (Action request 0) 814718 Can't SetWindowsHookEx! (Action request 0) 880843 Can't SetWindowsHookEx! (Action request 1) 946734 Can't SetWindowsHookEx! (Action request 0) 1012968 Can't SetWindowsHookEx! (Action request 0) 1079046 Can't SetWindowsHookEx! (Action request 0) And so on. Anything I can do to get it working again? I've tried the obvious of turning on compatibility (XPSP2) and run as administrator, all with no success as yet. EDIT: Forgot to say, I'm running latest FSUIPC v6/WideServer/WideClient throughout my setup.
  7. Pete, I was thinking out loud on the FDS forum about how to get a separate controller for tiller/nosewheel, and I came up the following: In thinking a little longer, it occurs to me that this sort of feature could be a part of FSUIPC itself - but I'm no programmer, I haven't the faintest idea whether it would even be possible to "kludge" a different controller, even using (the excellent) FSUIPC! Thoughts?
  8. Yes, I think so. I don't use it myself so I've not tested it, but there's some stuff in the WideFS documentation about how to do it from another user. Did you check? Put simply, yes this can be done (I've been doing it myself for best part of a year now...) Program a keysend in FSUIPC for the joystick button you want to use, then set up WideFS to produce the appropriate keypress when the keysend is received. Unfortunately, following a recent move of house, my FS setup is scattered, so I can't provide any specific examples at this time...
  9. Mattias, Using GFDisplay (thanks Pete), FSUIPC and the GoFlight software, with a button set up to toggle Transponder mode works as expected, with the on-screen switch moving as expected, and all I have FSUIPC doing is setting the offset. Which version of IVAP are you using? There were a few problems with previous versions that Kenny fixed in the RC4 release.
  10. To quote Mr. Winner, "Calm down dear..." :D Not to worry; I had (a) not made the initial request as clear as I should (more on which in a moment), and (b) misunderstood the documentation entirely. Precisely, but I have subsequently realised that the best place to "fix" this will likely be at source, inside IVAP and/or SB3 (don't fly on VATSIM myself, but others do...) Once the IVAO forums are running again (down at time of writing) I'll be requesting this as a feature (given cockpit builders are the only ones affected by this offset...)
  11. Not a sufferer of this myself (haven't gotten the hardware to run my PM yet, but it's on the way...) so I can't be specific, but as a Network Admin I do know a thing or two about these sorts of things. Obvious suggestions would be:- [*:ff362]Firewalling/A-V software (and the like) - Have wide-open permissions between all your FS machines. Check especially on the XP SP2 machines, since the Windows Firewall was tightened up (and turned on by default) in SP2. [*:ff362]Networking hardware - If you can afford the extra hardware, put all your FS machines onto their own switched subnetwork. Get a little 5 or 8 port 10/100 switch (depending on how many machines you have) and plug only your FS machines into it, and cascade it to the rest of your network. Never use a hub for this, hubs *will* cause problems with packet collision! [*:ff362]Windows networking - A much overlooked issue. If you don't have a Windows Domain of some description on your network (I use a Samba server myself), and/or correctly and fully specified hosts and lmhosts files (look in %windir%\system32\drivers\etc) on all the machines, much of the Windows network communication will be by TCP/IP|IPX/SPX broadcast! This is extremely wasteful of CPU cycles (all your machines have to process these broadcast packets, so that one machine can answer it) [*:ff362]Cable runs - keep all your ethernet cables as short as you can, but never less than 1 metre. Avoid coiling network cables, and try to keep the ether cables away from power cables whenever possible. One final suggestion, maybe think about getting a copy of [ XPLite ] and uninstalling as much of the unnecessary Windows XP clag as you can (leave IE installed!). It has made a vast improvement to my XP SP2 FS client machine.
  12. In which case, mea culpa and I'll RTFM properly next time, promise :) Didn't know that... shame I worked out how to do what I wanted well enough in FSInterrogate. It definitely appears like something screwy is going on in IVAP, but now I know thath GFDisplay is only doing what I told it to, it does explain what I am seeing the light doing. Thanks for all the help Pete, no doubt I'll be back later with more daft questions... :)
  13. David, I'm working on something similar myself: Transponder mode and IDENT via GF controls, for IVAP in my case. I suspect the GoFlight side of this will be of little interest to you (unless you have GF modules and haven't considered using them in this respect) but the FSUIPC button programming will still be valid: 2=P101,6,Cx01007B93,x01 3=P109,6,Cx01007B91,x00 4=U109,6,Cx01007B91,x01 I use a toggle switch for transponder mode [P/U109] and a push button for IDENT [P101]. Unfortunately, I am grabbing the button programming via Remote Desktop from my home machine and as such can't confirm the specifics of the programming out of the FSUIPC GUI (i.e. the exact Offset function I am using). Given the offsets in IVAP and SB3 are identical, you should be able to use this with minor modifications - I'd suggest using "Offset Byte togglebits" if your using a non-locking push button for transponder mode.
  14. Pete, Hate having to dig up an "old" topic, but... I'm having a problem with the new timed flash functionality. I have the following code snippet in my GFDisplay.ini [GFP8.0] Needs=E B B=8 L6=X7B93 U8 !=0 Fs5off;IVAP/SB3 IDENT active - Slow flash for 5 seconds With IVAP not running, this code works perfectly (press the L6 button, the LED above slow flashes for 5 seconds then goes off - having said that, I didn't try it a second/third time just to be sure. Expect a further edit/post when I get home tonight). Unfortunately, if IVAP is running (so that the X7B93 offset is also being read/written by IVAP) the LED just isn't working correctly: a single flash on the first button press, then nothing on subsequent presses. This leads me to suspect that the problem is inside IVAP but, to aid my debugging/aportioning blame, can I confirm that GFDisplay subsequently ignores the content of X7B93 and the 5 second flash will continue regardless once triggered? Also, I don't suppose you (or anyone else out there in FSUIPC/GF programming land) have a debugging tool that is capable of monitoring the content of specified offset(s) in real time? I tried using the offset monitoring tool from the SDK (FSInterr?), but that wasn't immediate enough for testing/debugging this issue (least ways, not how I assumed it was supposed to be used - if it's capable of this, guidance would be most appreciated). Ideally, what I want to achieve is monitoring X7B93 in real time.
  15. Basically, yes, but... That would be even better (and is pretty much exactly what I am after). The IVAP IDENT offset functionality makes the P8 button act as a non-locking push-to-make, the moment the button is released the offset is (re)set to x00, making reminder indications difficult. Your proposed solutions would be perfect for me; slow flash while the offset is x01 (button press), and leave it flashing for N seconds after the offset returns to x00, then turn the indicator off altogether. This is kind of what GFConfig does when the gear is assigned to a T8 switch: LED on steady when gear is down and locked, slow flash while gear is in motion, off when gear is retracted. Thanks in advance of the release that understand this.
×
×
  • 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.