Hi!Now that I started using the keyboard emulation feature of SIOC, and I have setup quite a bit of my cockpit into SIOC, I have started to realize that something in my setup is not right. This thing became more clear now that I have started setting up the GPS keyboard shortcuts using the keyboard emulator functionality in IOCards (EmulatorK plus SIOC3 built-in keyboard emulator)This also relates to my problem with encoders (skipped inputs) and also some switch inputs going missed.I tested SIOC without FS at all. Everything works super-fast and nicely, the encoders perform beautifully. Keyboard events flow pretty much real time from the turn of a knob into Notepad. So the hardware works great.The problem is, when I start my FS. FS has good FPS, no problems there (except that Sioc3 drops my FPS to 2, but that is another issue, SIOC 2.0 works okay)But the moment FS is running, the keyboard emulator starts to stutter: my knob outputs keyboard events a lot slower, and also some switches need to be flicked several times into "on" to make FS see them. It looks like *something* is hogging the system to make SIOC struggle to keep up with the hardware?Nico, you use a lot of keyboard shortcuts, right? How do you manage this? Or do you use the keyboard emulator card?Does anyone know what this could be? I have Win2kPro and FS2004 (no 9.1 patch yet though) and a registered FSUIPC. FSBUS performs just fine, so there is nothing fundamentally wrong in the FS setup or FSUIPC I think.Any clues?//Tuomas

>Nico, you use a lot of keyboard shortcuts, right? How do you>manage this? Or do you use the keyboard emulator card?I let FSCONV generate the keyboard shortcuts directly via C system calls... works fine.So, no, I do not use the keyboard emulator card of SIOC, nor do I use the keyboard emulator facility built into SIOC3. You should restrict the use of keyboard shortcuts to the bare minimum, fsuipc offsets are to be preferred ;-)I have no performance problems with SIOC3 (and FSCONV, and FSUIPC, and MCP747.exe, and .. FS9 ...)Nicowww.nicokaan.nl

>I let FSCONV generate the keyboard shortcuts directly via C>system calls... works fine.Ah right!>So, no, I do not use the keyboard emulator card of SIOC, nor>do I use the keyboard emulator facility built into SIOC3. You>should restrict the use of keyboard shortcuts to the bare>minimum, fsuipc offsets are to be preferred ;-)Sure. This is the reality xp gps gauge that needs keyboard shortcuts. They work ok from the keyboard. I need to check my sioc code for stupid infinite loops too. Hopefully I can figure this out, once the gns530 is done, this sim is ready for vatsim again :)>I have no performance problems with SIOC3 (and FSCONV, and>FSUIPC, and MCP747.exe, and .. FS9 ...)Yea, thanks. I need to keep looking for the problem. Something is wrong clearly since it should not be that slow..//T

Okay, after reinstalling Win2000 (it was about time, all kinds of cruft tends to accumulate over the years, making things slow) - it works now.The slowness seems to have something to do with either Dreamfleet Baron 58 or the RealityXP GNS530. Everything works GREAT with the default panel of the Dreamfleet Baron. But when I did a new panel from scratch using FS Panel Studio, I got the slowness - about .5 sec lag in GNS keyboard event sending from SIOC.Default panel of the Dreamfleet Baron is fine, everything works really smooth (like you can see on the crappy video I posted)Setting the GNs530 on the Cessna 172 panel also works fine.When I put a custom panel to the DF Baron, the problem appears.I need to try to sort out the issue - I'm just making a custom panel based on the default, just moving gauges around and making a full screen black background bitmap for the main panel. So far it works, I am removing gauges one by one to see what the problem is.Anyway, I noticed another issue.SIOC 2 and SIOC 3 seem to work DIFFERENT when it comes to encoders! With SIOC2, I have this code:-----------------------Var 92, Link IOCARD_ENCODER, Input 56, Aceleration 1, Type 2{ IF V92 > 0 // up { V1 = 15 } IF V92 < 0 // down { V1 = 16 }}-----------------------(V1 = key emulator variable, 15 gives letter "A" and 16 gives letter "B")With SIOC2, if I turn the knob back and forth, I get "AAAAAAAAABBBBBBBBBBBAAAAAAAAAAABBBBBBBB" like I expect.With SIOC3, I get just one event, when I start to twist the knob in a direction. So, the above becomes: "ABAB".Any ideas? Same code, different SIOC version..??//Tuomas

Hah, okay, that was easy.-----------------------Var 92, Link IOCARD_ENCODER, Input 56, Aceleration 1, Type 2{IF V92 > 0 // up{V1 = 15}IF V92 < 0 // down{V1 = 16}V1 = 0 // <== ADD THIS}-----------------------Looks like EmulatorK and the built-in keyboard emulator work slightly different: I need to manually set the keyboard emulator variable to 0 once the key event was sent. Now it works beautifully.Ferdie, if you are reading this - is this on purpose or accidental change?//Tuomas