-
Posts
38,265 -
Joined
-
Days Won
170
Content Type
Profiles
Forums
Events
Gallery
Downloads
Everything posted by Pete Dowson
-
There's a set of offsets you can use for exactly that. They are those in the range 3BA8-3BC6. They originated for use by my PFC driver, and so used to have a range only of 0-127 and had to be assigned as 'raw' for other uses, but all recent versions of FSUIPC will scale them automatically if they see a value greater. Or you can preset the scaling in the assignment lines in the INI file. The PFC assignments normally made are listed in the offsets list, but you don't need to stick to those. Any of those offsets can be assigned to any axis control. They appear in the assignments on joystic numbers 16-18. Well, it is one of the Lua examples still included in the "Example LUA Plugins.zip" file, which is inside the Lua_Plugins.zip package, which is installed for you in the FSUIPC Documents subfolder in your FS Modules folder. Or you can download the latest from the Download Links subforum. I don't know why you couldn't find it? But VRInsight devices are not HID devices, just normal serial COM devices, and FSUIPC does include special treament for those, so the document you refer to is not transferable. SerialFP2 is a VRI driver, no use for anything else. And it is actually superseded now by VRI's newer software. You can't apply a driver made explicitly to handle one serial protocol to handle another completely different one. See the first answer, above, Regards Pete
-
New build up. Same version numbers. Weird glitch in build process, don't understand why, but these are okay. Pete
-
The offset of the entry point in the Gauge or DLL code for the function required. That is the place the mouse click causes a jump to. The numbers after the * are just two check bytes whch FSUIPC uses to check that the code is still the same as it was when you made the macro. You'd need a dissassember to make any sense of it. It is code. Sorry, I've no idea about anything regarding that aircraft. I don't have it. you'd need to experiment. If you've tried the parameters for the macros and nothing works then it probably isn't possible. What do those two macros you have do, anyway? I thought the LevelD 767 was well served by Nico Kaan's interface program. Regards Pete
-
rotary switches and FSUIPC
Pete Dowson replied to gr8guitar's topic in FSUIPC Support Pete Dowson Modules
I assume the lines aren't really numbered X, X+1 etc? You are still inventing your own syntax for these control lines. There is no facility to send a keypress AND a control. I don't know where you got this idea from -- I already told you it was wrong, way back. You also have an extra ( in a couple of the lines. Honestly, I cannot make out what you are doing, or rather trying to do. It makes no sense just like the early examples you posted. I did try to explain at length why they were wrong. If you want multiple actions on the same buttons you must have multiple lines for each action. There's only one 'result' of each line, not as many as you like. I honestly cannot understand where you got this from, nor why you are persisting with it. I think you are going to make it far too compicated using multiple flags. What you are trying to do is far easier, for any number of different actions, using offsets and offset conditions. There's an example of a 4-way one in the Advanced User's guide, near the end of the secion on Button programming (the last example before the section listing "ERRORS IN BUTTON PARAMETERS". It begines at the paragraph starting "Finally, ...". Regards Pete -
FSUIPC 4.803 not found
Pete Dowson replied to Timonier's topic in FSUIPC Support Pete Dowson Modules
4.803, properly built, is now up. Regards Pete -
FSUIPC 4.803 not found
Pete Dowson replied to Timonier's topic in FSUIPC Support Pete Dowson Modules
Sorry, it's offline at present. There was a build error. I'm just re-building and re-testing. Should be okay in an hour or so. Pete -
Just tested and discovered this. working on it now. Sorry. Don't know what happened, yet. See revised previous message. Pete
-
There's no way it can do that. Did you delete the INI file? You never have to do that! It shouldn't delete anything at all unless it's invalid in any case. Perhaps your Axis section was corrupted? It deletes any bad sections, that's all, ones with bad headers (the bit inside the [ ] parentheses). [LATER] On my ***! So it does! What the ** happened there? Sorry. I'm on to it now. Meanwhile removed the updates! Pete
-
It was easy to do, and i had to make bug-fix releases, so the facility ("mousebutton swap") is now available -- get versions 4.803 and/or 3.999d from the Download Links subforum. I've tested it in FSX with the PMDG 737NGX and it works quite well. Just assign a button to that added control. It lasts from the next left button down to the subsequent left button up. Regards Pete
-
The updates are available now. Regards Pete
-
PFC Button Press Error
Pete Dowson replied to cavaricooper's topic in FSUIPC Support Pete Dowson Modules
It will see it as a joystick if Windows sees it as a joystick, as will FS. But it seems to be described as a keyboard -- I couldn't see anything suggesting otherwsie. You can of course assign FS controls and so on to keypresses as well. Regards Pete -
WideFS for a beginner in networking
Pete Dowson replied to pylon101's topic in FSUIPC Support Pete Dowson Modules
Why do you need to read it all and understand it all. There is only really a couple of pages you need to read. But 99% of users simply install it, register it, enable it, and use it. It is almost entirely self-configuring, especially if you use the same version of Windows on each PC. I'm afraid there is really nothing in any WideFS document to help you get a Network working. That's a pre-requisite. And I do not know enough to help with Network problems. You need to get your Network working beforehand. - with kind assistance of guys from Microsoft Russia I fixed issues with establishing workgroups and network. Now laptop's workgroup sees FSX (though it is llibrary FSX). Desktop's workgroup also "sees" folder on laptop. Er. WHAT "dll" exactly did you place into the FSX modules folder? The only one of mine you need should already be there -- FSUIPC4.DLL. That's installed there by the Installer. There's no other you need. Have you put Wideclient.exe onto your client and run it? Without a client to talk to, how do you think the server, in FSUIPC4, can talk to it? Pete -
rotary switches and FSUIPC
Pete Dowson replied to gr8guitar's topic in FSUIPC Support Pete Dowson Modules
Sorry, I'm a bit lost here, now. I think I've lost the context. One point, though. Control 1003 is the control to set a button flag, so i don't see how you can "count" with that. Folks who have multiple uses for single buttons or switches tend to use one of the Offset increment controls to change the value of a user offset 9eg x66C0), then use offset conditions in the button assignment definitions. It varies enormously. Since the methods of updating disaplys depends completely on the device -- no two are the same -- and the methods of getting information out of FS varies enrmously, often depending on the add-on aircraft in use, there's no single answer. FSUIPC's Lua plug-in facilities offer facilities to drive Go Flight displays directly, and you can drive VRInsight displays using the COM library. Examples of these are provided. There are no other standard methods. Obviously, for displays, you first need some sort of interface to those displays, and you start from there. The ony reason the input side of things is relatively standard is because it is specified in the Windows joystick interface. This is a subset of its HID (Human Interface Device) standard which is precisely defined. The rest, the general facilities for handling any device, more or less allow implementers to do it any way they wish. Regards Pete -
Just load each plane in turn, for which you want different buttons, go to the Buttons tab, select Profile specific, and name the profile (or select one which is applicable to this plane), then assign the specific buttons. This process won't change the other sections which you aren't changing (i.e. axes, calibrations, keypresses), and the buttons you don't re-assign will still operate as per the general default settings you set already. Yes. You might want to wait till later today, though, and grab the next update for FSUIPC -- 3.999d or 4.803 -- because i just found a bug which can produce spurious sections in the INI file and may lead to misleading results. I'll be uploading these updates within the next few hours, so please check the Download Links subforum later today. Regards Pete
-
Esound is not supported these days. In fact it hasn't been for a long long time, and I'm afraid i cannot even remember how to configure it. The sound facilities are now provided via the Lua plug-in libraries. There's a full sound library in FSUIPC3, FSUIPC4 and WideClient. Please see the Lua documentation installed in your FSUIPC Documents subfolder in the FS Modules folder. Regards Pete
-
In that case I don't understand how you got this result: "the range of one of the throttles (throttle 2 I think) was reduced so moving the lever all the way to idle resulted in the throttle in the NGX only moving back to about 50-40%". That makes no sense when all the sync pos does is match positions, equating different input values for the two axes to the same output values, then calibrating between. If that simple mechanism is going wrong I need to know, so you shouldn't really keep it a secret. Please show me the resulting calibration sections from the INI, and if possible do a bit of logging -- log Axis events whilst moving the levers, together, slowly from full back to full forward. Odd that no one else gets such a problem. And especially with the page 1 single throttle, which doesn't change the FS control used at all even if you don't change thje INI setting. That's just a straight-forward adjustment ofg the axis values as they pass through FSUIPC. I understood you said that all along. Not sure why you are repeating it here. I simply do not understand why your setyup uniquely has an autothrottle cutout problem with FSUIPC using standard FSX controls when no one else seems to. But all calibration is doing is massaging the axis values en route. It isn't changing anything else. Regards Pete
-
If this because the touchscreen support has no middle or right button methods? Not at present. I carefully avoided adding any facilities to detect mouse button clicks or moves, primarily because this presents very nasty problems involving recursion. I cannot see any way, for instance, of distinguishing between a mouse click made by the user from one sent by my code. If I trap the messages I trsp them all. You can imagine what that would end up like! If I implemented such a facility it would have to be built into the main code, not programmable via Lua. That wouldn't be difficult. FS itself never uses anything other than left clicks for panels -- right click produces pop-up menus. I know PMDG introduced the idea of left/right clciks for turning knobs different ways. Are others copying this now? Anyway, I'll put it on my list. i've a couple of other things to sort out first. Regards Pete
-
Yes, this is a good solution and many others use it Good. Regards Pete
-
The sync pos facilities in FSUIPC calibration could deal with such discrepancies easy enough. You can choose a number of positions to make the equate and FSUIPC will interpolate between. It effectively creates a specific curved calibration grapg instead of using the plain linear method. That doesn't sound anything like the sync pos facility. With the latter you simply create many positions which are to give equal input numbers and it fills in the parts between accordingly. You can certainly create enough positions to give very smooth reaults over the whole range. I don't know what you were using to make such a mess, but it wouldn't have been that. If using the same throttle controls as FSX assignment uses causes an autothrottle problem ,then there's certainly a bug or design deficiency in the aircraft modelling. You've confused me now. How does using a single throttle axis solve anything, apart perhaps from your sunc? Pete
-
SAITEK and FSUIPC incompatibility
Pete Dowson replied to rmcfp's topic in FSUIPC Support Pete Dowson Modules
That's a very old version now and not supported. The current version is 4.80. Sorry, I have no idea. Does FSUIPC see the button? You may want to try Saitek's support forum. I can't really support their products. Or maybe search this Forum. someone might have posted something. Regards Pete -
fsuipc/ windows 7 wont work with fsx
Pete Dowson replied to fullofattitude06's topic in FSUIPC Support Pete Dowson Modules
Not to the end of the whole file, I hope. Those lines must be in the section headed [General]. If you aren't sure where that ends, insert them as two new lines immediately after the [General] line. No, and certainly not before we understand what is wrong. Reinstalling often generates more problems than it solves. It is a last resort -- we've not looked at the first resort yet! Unfortunately I'm out this evening -- leaving soon -- but if you obtain a log and paste it here, I should have time to check it when I return, late. Regards Pete -
Good! Happy flying! Pete
-
FSUIPC doesn't change the mouse pointer, so this definitely shows that it is something to do with the FS facility. In the logging, enable Button/key logging too. That will show the derivation of the controls logged. Regards Pete
-
Sorry, i don't know. there is no code in FSUIPc which does anything but place the mouse cursor back where you last left it. There's no centre computation, no code to do it. In FSUIPC's logging page, turn on Event logging and Axis event looging, then try it and see what controls are being sent. Pete
-
Use the new FSUIPC mouselook controls, NOT the FS "Toggle mouse Look". There's no way i can stop the latter from returning to its previous position -- which is the way you liked it excet in this case it cannot remember its previous position because it isn't doing the moving. You don't need to use the space bar in any case, you can press and hold the middle button. Is there any difference for view panning? I've only implemented panning. Something you are doing is sending the FSX control "toggle mouse look" then. Certainly nothing in FSUIPC re-centres mouse look (as it didn't before -- that was FSX),. It does of course move the mouse cursor -- back to the place you last left it in mouse look mode. [LATER] I just used it on the outside view, trying both space bar method and the middle mouse button (which needs no assignments). Both work perfectly as far as I can see. It makes me even more certain that you are either assigning the wrong control or you still have the FSX toggle control assigned as well. Or maybe you aren't using FSUIPC 4.802? Regards Pete