Pete Dowson

For a prop magneto switch, the one marked off-left-right-both (not the 737 style jet starter you appeared to be wanting) I'd assign exactly as I would in FS itself. You seem to think FSUIPC is different. Yes, it does present the complete list of FS controls, not the subset FS provides in its menus, and, yes, it does add some special controls related to its own facilities. But for things done with default aircraft in FS the controls ARE the FS ones, and they are all listed for you in the document entitled something like "List of FSX controls" installed for you in the FSUIPC documents folder. For separate engines you have the MagnetoN_ xxx series of controls (N= Engine number), all entitled quite understandably. There is also a generic all-engine series without the 'N' part. Pete

I've moved this from the FAQ subforum to the Support Forum. Please post support questions here in future. What program "directs" you to SimMarket? I hope you realise that WideFS is nothing to do with using other PCs with FS running on them. WideFS is for supporting other programs on PCs NOT running FS. If you simply want multiple PCs running FS all synchronised you need something like OpusFSX or WideView. Have you not bothered to read even a little of the WideFS user documentation provided? All you need on the client PCs is WideClient, which is in the WideFS zip file. It provides the FSUIPC interface for whatever FSUIPC applications you want to run there. Pete

None of those are "offsets", they are controls. The first two are FScontrols -- FS Kohlsmans inc and dec. FS simulated the altimeter QNH setting, as I said, and PM doesn't interfere with that. The other two controls are simply FSUIPC controls which write to PM offsets. For the FO side you must find the offsets and the parameters in the PM offsets list, as I already told you. Did you not bother to go look? Because the FO side is not handled by FS, only by PM. Again, you don't appear to have read my previous reply!! The first one there is for the PM offset 04FA. You need the FO equivalent to that. Why not just look it up, as I would have to? The second (66040) is the FS control for the altimeter QNH and 16211 is the numeric value for 1013.2 hPA x 16. FS controls are listed in the FS controls list you have in your FSUIPC documents folder. For the FO altimeter you'd need to write it to whatever offset PM is using. Please please try and look things up for yourself. I am not PM support. They publish details of all their offsets for you to refer to. Pete

Where's the question in all of this? When you say "Rotary Switch is far left on Ground = FSCUIP settings screen is blank" you do realise, i hope, that this simply means that position is the "off" or "not pressed position of the next position, so just program it at the GRD position but as "released". The others have their own button "press" numbers so don't need programming for "release". Assign them to whatever works for whatever aircraft it is you are using. But you should also realise that FS does not simulate any Starter switch with GND-OFF-CONT-FLT positions. Pete

What "offset file" is that? Are you sure you aren't referring to the Project Magenta offsets file which is accessible on the Project Magenta site? How do you work out that 171 = 170 + 100? Why is "170" the "panel number"? Do you mean the joystick number? I don't know Goflight joystick numbers off by heart, you need to use FSUIPC -- press a button on the panel and see what number it comes up with. Well, without poring through lots of documents, I don't know about the first. How did you assign it that way, and why? Check the PM documents and see what offset 04FA being set to 20 (=x14) is supposed to do. I think it might be Captain's DH, in which case you need to look up the correct offset for the FO DH. The offsets list and instructions are on the PM site. The second appears to be an assignment to the FS altimeter "Kohlsman set" control, to set the altimeter to STD. FS doesn't simulate the FO side, so that changes completely for PM -- you'd need to use the PM offset for the FO QNH. Again, that will be listed in PMs documents, not mine. Regards Pete

I think much of that is completely unnecessary in any case. Certainly there is no need to install SimConnect on the FS PC as it is installed with FS. And I'm pretty sure nothing needs the SDK. Not sure why you installed that anywhere. Your SimConnect.xml file has errors in two of the lines. You are evidently not copying stuff so well? Both lines like this <Address>192.168.1.7 need to be like this: <Address>192.168.1.7</Address> Apart from that, sorry, I'm unable to help. Pete

It isn't an FSUIPC function. If you are using Ezdok then you need to refer to Ezdok documentation. I don't really know what a "free float camera zoom" is. FSUIPC offers facilities for eyepoint movement with the Mouse ("mouse move"), or you can assign to FS zoom or eyepoint functions directly from buttons. But when using Ezdok it takes over most of those eyepoint and panning actions I think. Maybe you just need to select the "repeat whilst held" option for your button? Pete

As clearly stated in the download place and in the release notes AND in the sticky post at the top of this forum, you MUST update to P3Dv2.2 build 10438 if you want to use FSUIPC. There are many possible crashes otherwise, and half the facilities won't be working in any case. Lockheed-Martin changed quite a bit and the hooks FSUIPC uses just don't match! And there's certainly no point at all trying FSUIPC 4.928 because that pre-dates 10437 by several versions! Pete

You need to assign fuel shutoff/idle to mixtureN lean (shutoff) and mixtureN rich (idle) controls! (N=Engine number)! If you know how to do all this using keyboard or mouse on the screen cockpit, you can easily find the right controls by using FSUIPC's logging. Just enable Event logging. You can even see it in real time on screen if you (temporarily) run FS in Windowed mode and enable FSUIPC's console log. Pete

Axis assignment? Rotary switches normally send button pulses. How are you doing an axis assignment, and how are you making two different assignments to the same axis? Pete

There's no "packets". FSUIPC is not a hardware driver. You need to write your own driver and include an interface to FSUIPC to read/write FS data. Please download the FSUIPC SDK for details. Pete

Why on Earth do you want to use an autostart action, which is designed for folks with no switches, just a spare button or keypress, when you have separate switches? You want to use the"StarterN set" control (N is the engine number), not autostart! The parameter for that is 0 for off, 1 for ground (=start), 2 for "gen" (not a proper 737 setting for the starter switch, but FS doesn't truly simulate a 737 in this area). Pete

You aren't in the wrong 'section', but yours is a new question and you are appending it to an existing thread about a different matter. I'll answer it here, but please, when you have a NEW question please start a new topic. You'll see the button to do this. Then entitle the topic with something relevant. I'm afraid I don't use VB so I can't tell you myself. Have you looked at example code in the FSUIPC SDK? It can't be too hard. It might be even easier if you use Paul Henty's .Net interface (see separate subforum above).. If you really want more help then you need a topic entitled with a question which will attract the folks who can help. Pete

You are using the additional FSUIPC separate engine autostart controls? I thought you were talking about operating things yourself. There are no sounds produced by FSUIPC. I really don't know what is going on with your system, but here's exactly what that autostart system does: 1. Switches the battery on (offset 281C) 2. Switches the avionics on (offset 2E80) 3. Selects appropriate fuel tank(s) (offsets 3880, 37C0, 3700, 3640 according to engine number) 4. Turns the appropriate fuel pump on (bit in offset 3125) 5. Turns the starter switch to start, according to engine type (jet/prop) and engine number (offsets 0892, 092A, 09C2, 0A5A) After a delay (20 seconds for jets, 2 for props) 6. Sets props to full (offsets 088E, 0926, 09BE, 0A56) 7. Sets fuel rich for all but turbos, which start with about 40% (offsets 0890, 0928, 09C0, 0A58) Waits to see engine combustion flag (offsets 0894, 092C, 09C4, 0A5C), then: 8. Returns starter switch to "Gen", "Both" or "off" depending on engine type (same offsets as before) 7. Switches engine generator on (offsets 3B78, 3AB8, 39F8, 3938) And that's it. As you can see it is a truly lazy way of preparing the cockpit for flight! I can only think that the sound you are hearing is from one of the subsystems and is an effect built into your aircraft, or maybe supplied by another app, such as pmSounds. I know, for instance, that pmSounds produces an electrical fan/motor type noise when you have the avionics turned on. If this is it and it goes off after 15 minutes it seems you are turning whatever subsystem it is back off. If you don't like the sound, try turning it off at source. Pete

ProATC-X works fine over a network -- I think it needs SimConnect and maybe WideFS as well, I'm not really sure off-hand as I've not used it for a long time, awaiting the long-promised update! ;-) I think FSGRW is an FSUIPC client application in any case so should work okay via WideFS. But I'm not a user and can't help with instructions I'm afraid. With all these products you would be much better off asking on the relevant support forum. Certainly there will be instructions in the documentation too -- I know that for a fact with EFB and I'm sure the others will have something documented. For ProATCX there are helpful threads on their Support Forum. Pete

Well, I think it can read the ATIS messages, though I vaguely recall that the main purpose of the facility in the first place was to grab text output from FS Adventures, in FS2000, It's a bit hazy, as this was done many years ago, after all -- with over 14 years of continuous FSUIPC development it is getting difficult to identify how or why things were done. And I am a lot older now which doesn't help. I really don't know about the ones you are interested in -- many are not posted to the function being intercepted. I know it doesn't get the paused, slew, view names and brakes messages, and perhaps the exit opening and closing messages are in that group. If they don't appear in the same place (actually the "message window") as the ATIS messages, then they aren't sent to that window, and there's no way you will do it with FSUIPC, You'd need to find the correct place in FS's Windows.DLL to hook into (assuming they even go through Windows.DLL). Pete

Assigning a hat as an axis to "Pan view" is the same as assigning in FS/P3D -- it IS the same function, exactly. FSUIPC isn't doing the panning. The only difference in performance will come from the fact that FSUIPC has to send the controls via SimConnect as it does with all of its other functions. Maybe your SimConnect is overwhelmed? The panning is certainly smooth here, in both FSX and P3D. There is no real button equivalent to "pan view" -- button repetition has an in-built initial delay before repeating in any case because of the need to be able to use a buttin once. Pete

Probably a difference in timing rather than specific coding. I'd need to see the log for that for comparison. Also, when you provide logs could you please close FS first, so the log is closed too. They should be short enough to paste into the message -- use the <> button above the edit area to enclose them. Pete

There is no way -- in FS9 it was done via a direct hack into a part of FS which is no longer there in FSX. I really don't understand how you are getting sudden visibility changes in ASN, which works wonderfully for me. It is realistic in every way and I commend HiFi for their achievements. Are you sure you are not mixing up entering and exiting clouds (which are precisely placed and known by ASN) with visibility which is most certainly very smooth here? And even with clouds, those with wispy edges give gradual transition -- the thicker ones with sharper edges are more dramatic, as in real life. Pete

The reason is that FSUIPC is not starting. So part of the FS setup and installation is not providing FSUIPC with the correct indications that FS is "ready to fly". Only after those indications are correct with FSUIPC be able to correctly populate the offsets which FSC s attempting to read. The last time I saw this was in the thread fsx-not-sending-position-to-adex/, and it turned out to be due to SimConnect getting overloaded with FSUIPC's requests for airport vehicles, in order to deal with GSX/AES duplications (an option which is enabled by default). I made a small change for that which is included in FSUIPC4934h, so please try that and let me know. Pete

Where did you read that? The offsets list for FS2004 (as installed in your FSUIPC Documents folder) actually describes the READING of the messages at 3380 before the additional function of writing messages -- though there are a number of FS messages which can't be seen this way, like "BRAKES", "PAUSE" or "SLEW". Not sure about the door messages, though of course for those you can simply read the door status offset and make your own message. The FSX list, on the other hand, is different. In FSX the messages from FS itself can't be so read, only those from third party software using FSUIPC Maybe the source for the information you have was about FSX? Pete

Yes, you are correct. Each Bodnar card will be seen in FS and FSUIPC as a separate joystick with axes and buttons which you can then assign as needed. No PFC software of mine or PFC will be needed. I use the cards for a variety of additional controls in my cockpit. If you will be assigning in FSUIPC i'd strongly advise you to use the joystick lettering options in FSUIPC to identify the joysticks. Also, I've a feeling that every Bodnar board looks identical to Windows, so it doesn't keep a unique GUID associated with the device, only with the USB port used -- so once connected and programmed take care to keep the ports unchanged (i.e. don't move them around). Of course if you are only using those two different ones this might not be a problem. Pete

What program is making a "grinding" noise? Merely enabling the fuel to flow at the correct N2% value is the way to start a jet engine, then you release the starter back to "off" when the EGT has peaked (or simply watch the combustion flag in FSUIPC offsets). There's no other 'correct' way. Pete

Sorry, I don't really have anything to do with sales. You'll need to raise a ticket with SimMarket, explaining the mistake, and see if they will replace it. Regards Pete

That was a different person. This second user, "Virtual-Pilot" Yves has tagged a different problem onto an existing thread about something else! And, yes, I just checked -- he purchased a key for WideFS7, not WideFS6! Thanks for telling him! Pete