svenks

Thanks for info, John. Much appreciated 😁 Brgds Sven

Thanks, John For info, I have also tried running P3D in full screen mode. Same result. Brgds Sven

Cancel that, I just tried with an undocked Overhead Panel (which I moved to another screen) and got the stupid headrest I cannot move away from until I click it first. Sorry about that, Sven

Hmmm, regarding 1127 and 1128. Even if I assign Mouse Look On and Mouse Look Off directly in FSUIPC, they don't do anything - UNLESS I also enable Mouse look in FSUIPC's Misc section. And If I do that, well, as I said it does behave weird and sluggish probably due to the conflict I have mentioned earlier. So that was the explanation for 1127 and 1128... On the focus related and original problem, I found out a small detail, which might provide an extra clue: All child window, docked or undocked, causes this behaviour, once they have had focus (provided you don't click in the main window afterwards). But the smaller the child widow is, the less movement you have in the main window. So the main window does move, but it can only move within the size of the child window. Therefore, it is really annoying to see this on an MCDU (where it's impossible to move away from a close-up of the headrest), but if it's the overhead panel causing it, you have almost free movement. BRGDS Sven

Hi John Yes, they should - but they don't do anything when used from LUA. I even created a small section in LINDA user modules for A320 and assigned FIRE1.Press to do ipc.control(1127) and FIRE1.Rlse to do ipc.control(1128). Nothing happens. I'm attaching a partial FSUIPC.LOG. In the first part, I am using ipc.control(1127) and (1128) from my MousTrap.lua script. Then I changed the script and loaded The Mooney Bravo, so now it's using ipc.control(1071, 32) and (1072, 32). As you can see, this DOES invoke Mouse Look. BRGDS Sven fsuipc.log

While we're at it, shouldn't ipc.control(1127) and (1128) do the same as Spacebar down, then up? Because they don't do anything... BRGDS Sven

Hi John Mouse Look, of course! But I accidentally enabled Mouse Move, and this caused the weird movements I saw. But it is true that enabling Mouse Look in FSUIPC and having controls enabled in P3D will cause erratic behaviour. You cannot know. If I have used Mouse Look, I could easily have a switch right under any coordinates, unless of course 0,0 is in the title bar. Tried it - it's the menu bar, and so Scenario is selected 🙂 Isn't there really no other way than a click to move the focus? I'm beginning to think this is not doable with the tools at hand. Again, thanks for your efforts, BRGDS Sven

Hi John Thanks for a quick reply. Advanced controls are set OFF, as it will cause another sort of movement than mouse look using the middle/wheel button - sideways panning etc. Manually pressing spacebar still give you mouse look, but does not solve the problem. ext.setfocus doesn't APPEAR to do anything in this case, but on the other hand FS still sems to have focus - it just resides with the MCDU window. FSUIPC documentation for Mouse.Move states "...be sure not to have it enabled if you do have controllers enabled in P3D as the two facilities will clash". And it does behave weird... ipc.control(1125) doesn't change anything.... Now, if only I could remember to click the main window each time I want to use mouse.look - but... BRGDS Sven

Hi all I'm trying to do something simple, yet it turns out to be quite a bit more complicated than I thought... I'm using P3Dv5 and most I fly FSlabs A320. I have a button on my joustick assigned to Captains view and another to FO view. And I can pan aound just fine using the hat switch. But I would like to be able to use the Mouse to look around also - easy peasy, right? WRONG! The problem is not to get Mouse Look working, I can do that by assigning Spacebar to a mousebutton, or I can trap the middle mouse button. But however I do it, I run into trouble because I usually undock the 2 MCDU's and this confuses Mouselook. I usually wind up looking straight back into the headrest - UNLESS I remember to click in the main window BEFORE a try to use Mouse Look. It seems to me that is is probably due the MCDU window getting the focus, and since that is a flat 2D instument, Mouselook gets confused. I have tried lots of things, but the only thing that seems to work is to have my LUA script move the cursor and issue a click. But that is too risky, since I cannot know if a crucial switch is at the center of the screen, when I do this. None of the ways I have tried to set the focus to the main FS window seems to work (ext.focus etc). And as for ext.gethandle using the window title: it MIGHT work, but it is a long title, and it changes according to number of attached wideclients. It might also be possible to use FSUIPC Mousewheel MOVE, but using my Thrustmaster A320 Throttle and sidestick with FSlabs A320 apparently demands that the joysticks be enabled in P3D. Any ideas? I'm attaching the script I'm using to trap the middle mouse wheel. BRGDS Sven Sorensen, EKCH MousTrap.lua

Hi Peter It is NOT a problem! Please don't take my suggestion as a complaint or anything. I merily suggested something that to me seemed logical, but is a "feature“ of FS, not FSUIPC. And you must admit, it is somewhat redundant for FS to have both an arm zone as well as an arm key! Hence my confusion - and my suggestion. Brgds Sven

Hi Peter and Thomas Thanks for your replies I had already calibrated my axis thus. But what you are saying is, that whenever you name an axis as spoiler, that behavior is what you get from FS/P3D? I must confess, that is news to me. Maybe it shouldn't be, but this is the first time I've dug so deep into FSUIPC. Well, live and learn... Cheers, Sven

Hi Peter 🙂 Well, I'm still at it with my X52 Pro LEDs, and actually it's going very well, and I almost have a working setup for PMDG 747 QOTSII - almost. I thought I would do the spoilers last, as they seemed very simple to do - just a copy of the flaps section. However, there is one thing, I'm unable to do: Setting a LED when spoilers are armed. The reason is primarily that PMDG has obscured that setting pretty well - but another issue is the fact that FSUIPC insists on having a part of the spoiler travel range set to be an ARM SPOILER zone. Of course, if you don't want to use a keystroke (default: shift+/) or a button to arm them, then it's a good thing - but I would rather use a button or rather, move a lever on my Saitek Quadrant out of scale (below the lower, hard detent), as that is defined as a button: Toggle Arm spoiler on entry, and toggle again on exit. PMDG understands this very well, and even the animation is correct! I have seen other people a long time ago wondering about this arm zone, and so I would like to humbly suggest a checkmark for "No Arm Zone" for the spoiler axis, the same way as you have done for the throttle axes? Possible? BRGDS Sven Sorensen, EKCH

Just by being there...😁 It 2 things: 1) The error msg was totally misleading. I did have a valid 64 bit DLL, but 2) the dependant LUA DLL had a slightly different name, lua5.1.dll instead of lua51.dll... Thus, the passerelle DLL wouldn't load, and so I got "Not a valid win32 application". I also began using package.load to load the DLL - though require should have worked. Brgds Sven

After the break... One word: SUCCESS! Got the 64-bit passerelle working in FSUIPC's LUA engine, and I'm ready to begin implementing my idea for connecting offset values, buttons and LED's. Sometimes you need to step away from the problem, to get a new view on it... Thank you for your help, Peter

Ok, I've had it! How hard can it be to create a valid 64-bit DLL??? And I haven't got a clue as to what (if anything) I'm doing wrong. In desperation I installed Lua for Windows (5.1.4) on my gaming PC. Copied passerelle/32bit to its clibs folder. Tried Require("passerelle") => unable to load module from file / module not found. OK, at least it didn't say "Not a valid Win32 app" Now, the SAME passerelle DLL on my VirtualBox testrig, also copied to LFW 5.1.4\clibs: Require("passerelle") - and it works! Same DLL - Same LUA environment - two different outcomes. I need a break... /Sven