Pete Dowson

Why would calibration affect views? What would you be calibrating which relates to views? Sounds like you either have an axis assigned to panning and its default position is programmed to do that, or you have a conflict between two assignments. However, since you don't say anything about what you have programmed in relation to views, I cannot comment further. Maybe you could offer some additional information about what you are doing? Pete

What is it sending? Keypresses or Button toggles? How are you programming it? Keypresses or controls? Some information might help me help you. Regards Pete

If it is okay without registration, then it sounds like an invalid registration, and the cross-checking is causing the restart of SimConnect links. First make sure you are using the currently supported version of FSUIPC (4.60 minimum). If you are, run FSX, see the problem, then close FSX down and show me the FSUIPC4.LOG file from the FSX Modules folder. It might also be a SimConnect problem, as these are often caused by re-installing FSX (because the uninstaller does not correctly remove SimConnect and it becomes a mess on the install). However, if this were the case it would be the same whether you registered FSUIPC or not. Regards Pete

Sorry, you will have to describe what you are doing in more detail. How have you programmed these things? What are you using FSUIPC for and why do you think it has anything to do with it? Pete

There are many Win7 users including myself, and IPX isn't relevant as it really hasn't been much used for many years because of lack of adequate support by Microsoft. I use a mixture of TCP and UDP. There is no possible reason for your WideFS not working except for networking problems which you may have to fix first. There's nothing much involved in "making it work" if you have a working network. If you cannot describe your problem I cannot help you. Regards Pete

Part of the FSUIPC documentation is a List of FSX controls. And the manual does say you can assign buttons or keypresses to any of them. If you look in the list of controls you will find lots of Throttle controls, so how come you missed them? These are the relevant ones for your needs: THROTTLE1_DECR 65966 THROTTLE1_DECR_SMALL 66635 THROTTLE1_INCR 65964 THROTTLE1_INCR_SMALL 65965 THROTTLE2_DECR 65971 THROTTLE2_DECR_SMALL 66636 THROTTLE2_INCR 65969 THROTTLE2_INCR_SMALL 65970 THROTTLE3_DECR 65976 THROTTLE3_DECR_SMALL 66637 THROTTLE3_INCR 65974 THROTTLE3_INCR_SMALL 65975 THROTTLE4_DECR 65981 THROTTLE4_DECR_SMALL 66638 THROTTLE4_INCR 65979 THROTTLE4_INCR_SMALL 65980 Regards Pete

Re-installing never helps, nor does deleting everything. What helps is checking the Log files -- that's why they are produced! Check the FSUIPC4 log file and the Installer's log file. Show them here if things aren't clear to you then. Pete

What, exactly "wouldn't work"? Can't you describe your problem in a little more detail? Do you mean FS didn't work, or you couldn't even enter your registration, or what? No you shouldn't. If you'd just re-installed Windows there would not be any "existing" registration to be checked. You wiped everything clean. Peter

News of what? Have you corrected this line: and re-tested yet? As two of us have already pointed out, that cannot be the correct path to your SerialFP2 program! Pete

Without information I cannot help. There are WideClient and WideServer logs created to help. Please refer to them. Pete

No, it was just that whilst many of the files inside the ZIP were updated from the 28th release, the ReadMe didn't change and so I forgot to change its title. Sorry. It definitely is the 29th. Pete

You need to explain a little more than simply "not possible". What does that mean? Pete

Sorry, that is pretty old now and not supported. You need to update to the currently supported version if you want support. You do not need to purchase FSUIPC registration to use it withe licensed products such as those you mention. Regards Pete

Where's the rest? Pete

Still you don't show the WideServer Log file? Why not? It shows the other half of the story. I've asked three times now! I am away now till next Monday. Regards Pete

But your message says you are using an old version, 4.57! You shouldn't really reprogram that as it works okay as it is. However, if you do then, as documented, nearly all of the switches and levers need to be programmed to operate both on "press" and "release". FSUIPC cannot detect when they are "pressed" it simply receives a message. The VRI devices don't send "button down" and "button up" messages like normal devices, so FSUIPC treats alternates as "down" and "up". If you only program the "press" it Pete

Virtually everything in most add=on asircraft can be controlled by normal assignments to buttons or keypresses using the simple drop-downs. Advanced stuff likev Macros, Lua plug-ins and offsets only tend to apply to obscure stuff you don't need for general flying unless you are building a cockpit. If there are some essential controls in the aircraft which are inaccessible to normal assignments then you should really complain to the makers of the aircraft. There's really no excuse. Even complex aircraft like the PMDG ones have keyboard assignments for most functions and you can assign any GoFlight buttons to keystrokes easily in FSUIPC (or probably also in GoFlight's own software). I can't give general advice because every add-on aircraft implementation is different. If they don't have documentation telling you these things, and don't use standard FS controls, then it's a matter of detective work to find out what you have to do to use hardware to control them. And I cannot do that because (a) I don't have every add-on aircraft there is -- in fact I have almost none, just the one I need for my cockpit, and (b) there's is no way I could afford the time to investigate how to do everything with every aircraft. I can, however, answer specific questions, when asked. And I do, if you examine the threads here you will see I try to answer every specific question. I'm off now till Monday. Maybe you can find someone else using the same aircraft as you and who has sussed it out? Is your "J4100" the same aircraft discussed in the "PMDG J41 commands" stickie thread in this Forum? If so, did you read that? Maybe you should add your questions there? Mr. Guenseli is doing very well and he started knowing nothing too. ;-) Regards Pete

But the broadcast isn't being seen. I don't know anything other than workgroup difference which can stop broadcasts. No, that's the FSUIPC4 log again! Did you try adding the ServerName and Protocol to the WideClient.INI file as I suggested, and as documented for this type of problem? Pete

How does it know this? How does it do that? These are very nice -- and of course should apply to Button presses too -- but who knows how to do such things? I'm really past my best hacking deep into code days. That nearly made me give up in FS9 times. FSX was only relatively "easy" because of SimConnect, but of course that meant a complete re-write. However, even SimConnect doesn't provide this information. Regards Pete

As it says, it isn't seeing the Broadcasts from the Server which tell it where to go. That's probably because you have the two PCs with different Workgroup names. Please check the WideFS User guide about this. If you don't want to match workgroup names you must specify both the Server name (or IP address) and the Protocol in the WideClient INI file, else it cannot know where to connect. The WideClient log is only half of the story in any case. There might be more clues in the WideServer log which is in the FSX Modules folder. The FSUIPC log isn't relevant. Regards Pete

Sorry, I don't understand that sentence. Does the GoFlight display show the same as the Add-On display IF you change the display using the gauge buttons on screen? i.e. NOT using GoFlight? If so, then they are reading the value from some place. And you should be able to do the same when programming the VRInsight displays. If not then they are timing or delaying their changes to make sure the run-away you see with VRInsight doesn't happen. If you want VRInsight to do that too, you would need to write to them. You could probably emulate the slowing down of updates by programming the VRInsight adjustments in FSUIPC -- there will be 4 (FOUR) buttons to program in FSUIPC -- slow clockwise, fast clockwise, slow counter-clockwise and fast counter-clockwise. For each, you may need to program both "press" and "release", or only one. I don't know. Try it and see. Yes, but then you need to choose those among them which care about folks using hardware with their aircraft. Regards Pete

But there again, for default aircraft and many add-on aircraft you don't need any macros or Lua programming at all. All of the FS controls are available for direct assignment, and those that aren't can be done much more easily with simple writing values to offsets using the offset controls. "Macros" were first added to FSUIPC just to allow multiple actions on a single button -- a list of separate commands could be programmed as a sequence in a macro. that's all. "Mouse macros" were a way of using the existing macro facilities to make direct calls into some Add-On aircraft's Gauge code. Really this is what is known as "hacking" -- the macros defined actually contain the address, in code, of a particular part of the Gauge code which has to be called to do something. I only managed to make that easy-ish to do by hooking all of the code entries for Gauges written in a very specific way -- according to certain FS SDK rules. Theoretically similar entry points could be found for all sorts of code, but it would need programming and debugging expertise and hacking tools to find those not written to these "rules". The only "Lua" needed is when some PROGRAMMING is actually needed. I am not aware of any common controls you need to apply which needs a Lua program. The examples you can find which feature Lua programs are that way because folks were doing fairly complex things to make things easier for you. Most are collections of controls which can be assigned in any case, or macros to write to local gauge variables ("L:vars"). I've a feeling that you are really confusing local variables (L:Vars) with Lua. Lua is most definitely a programming language. L:Vars are not, they are variables specific to gauges. I hate to keep repeating this, but you seem not to be reading what I am saying. The only reason the two disagree is because there is probably no way to READ the Add-On's numbers and show them on an external display. It is because of your choice of add-on aircraft. If you choose an aircraft which isn't suitable for such hardware then it isn't suitable for such hardware. That is NOT true for default aircraft nor for any aircraft using the default autopilot. As I keep telling you, the problem is that it may not be possible to read the altitude from your add-on. Therefore there is no way of keeping them aligned. If GoFlight is any better I'd be surprised, but if it is it is because either it has a special driver for that aircraft or it is slower doing the changes in any case. Or possibly you are using a setting for VRInsight which uses keypress encoding whereas Goflight uses controls. I really can't tell from so far away from your PC. Keypress queuing is always going to be a problem when trying to keep things aligned. If you can obtain the value to be displayed, of course. But can you? If GoFlight drivers do, how do they do it? Maybe they have a special license for software access to your particular aircraft? I really do not know. Sorry. You need someone to help who is using the same aircraft and knows more about it. Why don't you try all this stuff with a default aircraft and see how well it can work? Regards Pete

But what is it you can't get working? You've never shown anything you've done. how can I help if you don't say? Are you saying you can program the buttons, or that you cannot? If the add-ons don't use the FS values which FSUIPC can read, then how do you think VRInsight or Goflight or anyone else can read them? It is sometimes possible for some aircraft -- LevelD 767, for instance, where a toolkit is provided -- but not others, like PMDG -- except for those few hardware manufacturers who could afford their special driver. If you have chosen an add-on aircraft which uses its own autopilot and keeps its values internal, how do you expect any external hardware to display therm correctly? There simply is no way to do it, for some aircraft. The only aircraft you are guaranteed to be able to read the A/P values for are those using the default FS A/P, and for those both GoFlight and VRInsight devices work fine. This is why folks who build their own cockpits choose the FS aircraft they use with great care and avoid those which are not compatible with any hardware. Many, like myself, just use flight models and no add-on panels, so can get away with, for example, the PMDG 737NG for FS9. then the instrumentation is all provided by external software like Project Magenta which can be accessed via FSUIPC and hence made compatible with any hardware. If you want to program your VRInsight or GoFlight displays yourself, it will come to programming. So you'd need to learn more. BUT if the aircraft you are using cannot provide the values you need, then it will still not be possible. Regards Pete

For programmers, yes. not otherwise. FSUIPC is an interface for applications to get to the innards of FS. Why do you think that? I am 67. Don't use them, then. You evidently have not even looked at the documents supplied else you would have seen the Lua package included. But Lua is for programmers, which you evidently are not and don't want to be by the sound of it. So why get involved? I'm sorry, but really there's no excuse because you could have looked at everything BEFORE you spent the money. Why rush into buying things you don't need and cannot understand? Just browse the documentation. If you don't understand it don't spend the money. As with many thing in computers, as well as in flying. It is easy to do easy things and harder to do hard things. There's no way of making really hard things easy. You have to actually spend some time and energy at it. Folks can help, but you have to be specific with your questions, not simply rant that you understand nothing because your an ancient person of 50 years and know nothing. If you want FS aircraft which are easy to use out of the box, that's what you buy. If you want complexity because that's what real life is like, you have to be prepared to knuckle down a bit. Horses for courses. Regards Pete

I think it works very well for many aircraft. It is just that it doesn't support all of the facilities on all of the aircraft. There are NO MCP implementations which do, as it is really an impossible task. All of the sophisticated aircraft models do things differently. It is going to be a compromise unless you specialise in one or two aircraft and are willing to program the controls for them. Yes, but we are at a point where it is perfectly possibly for you to re-rpogram the VRInsight to suit exactly what you want, but you are not able to understand my instructions and I do not know your aircraft nor problems well enough. This is why I keep suggesting you talk to the folks on the VRInsight support forum. Regards Pete