Pete Dowson

Hi Fulvio, Since we last spoke I've been doing some experiments to see how to improve the way I can influence the visibility in FSX without the excellent control I had in previous versions, and I've managed to improve it quite a bit -- to the extent that I think the graduated visibility function, as well as the limits, are generally usable. There still might be the odd glitch -- I try to ensure I get and change the 3 WX stations which impinge on the ambient weather at the aircraft, and do so by changing the 9 nearest WX stations in a sort of 3 x 3 grid fashion. I do know, though, that some of the triangulation used in FS to work the 3 affecting WX stations is rather odd, so in some areas I suspect it won't work so well. Please try it though and see what you think -- FSUIPC 4.167, available now in the FSX Downloads above. Regards Pete

I don't know. I never use fixed virtual addresses -- are you sure they are truly Globals? Most stuff in FS2004, it being written in C++, is allocated on the heap or stack as objects are created, so a lot depends on the timing and order of initialisation. I'd need to find links to them. I'll certainly take a look. Additionally, if I do support them in FS2004 I'd like to be able to in FSX -- forward compatibility being the paramount raison d'etre of FSUIPC. Having done so well in FS2004, do you think you can do the same in FSX? Regards Pete

Sorry, I really do know absolutely nothing at all about Java. Pete

It's happened before, and has always been due to some third party program running and interfering with the way ordinary dialogues work. If you haven't tried doing in with FS9 in Windowed mode, not full screen, try that first. Otherwise I'm afraid it's a matter of trial and error disabling other programs or services you have running. One well known case was one version of the Kensington mouse driver, so that's one avenue to explore. Regards Pete

Sounds like you have the command formatting incorrect. But the AWI is not good for FS2004 and certainly not for FSX. Please change over to the NWI, which is used very successfully by prominent programs such as ActiveSky 6.5, FSMeteo and so on. It is also much easier, being an offset-mapped system just like the rest of FSUIPC's interface, whilst AWI was an attempt to build a command/response type of system onto it, making it far too complex. It was designed for FS2000 -- i.e. a long time ago! Regards Pete

Seems some folks have periodic problems like this. The server is okay and all the links work from here, so it is likely to be your ISP. Try again at another time -- by past reports it comes and goes and only affects a few folk. Pete

Old versions are not supported at all. Please re-check with the current supported version, 4.16 or later. Check the Announcements above, please, before asking for support. Regards Pete

It may well be possible, but as far as I'm aware the information isn't specifically useful as I didn't think AI traffic bothered to use the transponder. In fact nothing in FS itself really uses it -- external programs such as Radar Contact and of course the on-line flight programs do, but they are dealing with user-flown aircraft. It wouldn't be at all easy to add transponder details, assuming they are available, as the data structures are rather overfilled as it is, and expanding them is not an option because of current program compatibility. Maybe I could make the values available on a specific request basis, similar to the way the full string data is provided. but this is a lot of work. I'd really like to understand your reasons, please. It surely depends on which way you view it. For instance: "Autopilot heading value, as degrees*65536/360" for offset 07CC is correct -- the formula says how the value is created from degrees. Whilst 0578 is worded "Heading, *360/(65536*65536) for degrees" implying that the formul is how you convert back to degrees. In the D040 section the wording is "in degrees * 65536 / 360", which is perfectly correct. Take your degrees, multiply by 65536 and divide by 360 and you get the value in those locations. Please always read the words around the formula which provide the correct context! (I'm sorry it isn't consistent throughout, but the document has been derived over many years bit by bit, not composed from scratch as a single work). Regards Pete

FSUIPC provides an interface to FS, and as far as the throttle is concerned, inside FS, there are no "detentes", it is just one continuous range apart from idle and reverse . I've no idea how your Airbus detentes are implemented, so there is no way I can possibly provide any special calibration. Surely, this is all handled by the specific add-on aircraft you are using? Doesn't it have specific controls to set specific thrust modes? If you want to map these onto specific regions of your throttle lever it is easy enough in FSUIPC, via the Axis Assignments facilities -- look at the right-hand side of the Options, and read the user guide on how tyo use this. I am certainly not in a position to provide drivers for individual motorised throttles. I'm afraid you'll need to write your own driver for than unless one has been provided by the manufacturer. Regards Pete

There's no transfer of route or waypoint information. All that the protocols available do is provide positional and movement data (latitude, longitude, altitude, airspeed, ground speed). The whole system is actually designed to make FS look like a GPS device to the receiving program, which was intended to be a moving map, probably on a separate PC or notebook. Using FS+GPSout to feed a GPS has always appeared a strange twist to me. Really the comparison I would have in mind is a GPS, in your real-life cockpit, connected to a notebook PC presenting you with a map and pinpointing your position on that map. In that scenario, FS+GPSout is the GPS unit. That said, folks do link it to their aviation GPS units. I really don't understand the attraction in that. I have three real GPS units but none of them accept external position inputs in any case -- they all OUTPUT such information, if required, in exactly the same way as GPSout. In this sense GPSout is a GPS simulator. Regards Pete

Whether it is FSX or before won't make any difference, as the GPSout facility in FSUIPC4 is identical to that provided for earlier versions by the separate GPSout.DLL. Didn't you try searching in this Forum? I just did and came up with this one, showing someone at least has it working: viewtopic.php?f=54&t=63982&hilit=Garmin+96 Regards Pete

That one is applicable, but there is more information in the FSX downloads Announcement above. always scan the Announcements! They Announce things! ;-) Regards Pete

I read threads. Threads can make some sense, follow a sort of logical process. Each new thread is just that to me, a new thread. See how big this Forum is? Look at how many threads I've answered and dealt with? Random messages appearing in a new thread making no sense are really just a waste of time. Please keep in thread in future. I am not going to try and search down to relate a new thread to an old one, especially one with such an uninformative subject heading as this! And I'm not going to try to remember and match poster's names either. I really do have other things to do occasionally, you know. If you like, but I know nothing at all about this "GoFlight Remote". You'd be better off talking to GoFlight folks I think. Regards Pete

Odd post, odd thread to startshouldn't there be something before all this to explain what you are talking about? Pete

Why are you now talking about updating to FSX? There have been new versions of FSUIPC in the last year for FS9 and before too! You said: Do you hope to get FSX for free? Won't that be costing you some $$$ too? Of course! You are expected to keep up to date! As I have said, I cannot and will not support old versions. You do NOT pay for a specific single version 3.xxx: if you have paid it covers ALL version 3.xxx. Only if you move to FSX would you need a new completely re-written version of FSUIPC, called FSUIPC4. Both are maintained in parallel. Current supported versions (for FS9 and before AND for FSX and beyond) are listed in the appropriate announcement above. Regards Pete

Sorry, this sounds more like a problem with PM. Have you tried their support? If you want more assistance here please be more specific as to exactly what you are assigning in FSUIPC. it doesn't matter whether the source of control is the keyboard, joystick or a GoFlight module. The only part which matters is how you are trying to make things occur in the PM modules. Of course the connection to PM matters too. Are you using wideFS? Is that all working? I am this "Dowson" (though I much prefer to be called "Pete"), and GFdisplay has been available for many years, it is far from new. And it has nothing to do with buttons or switches, it is just a way of using the digital and LED displays on GF units. In that case kindly update to the latest versions before asking any more questions. I cannot support anything other than current versions, as listed in the Announcement above! Who on Earth said any money was involved? Just update -- you should be updating regularly in any case. I provide updates almost monthly. I cannot support old versions. Regards Pete

Well, I'm sorry you've had such problems, but SimMarket has been very good for FSUIPC and my other programs and I'm not considering any change. Do you really find PayPal too complex? I find it very easy and useful, and much more versatile on the Internet than credit cards -- especially once you've set up an account (which admittedly does take a few days whilst they do the security stuff). Regards Pete

Ah, FS2002not seen one for that. I have a TrackIR4 running on FSX only. Its software uses SimConnect and I'm pretty sure it's nothing to do with GoFlight. Seems like GoFlight and TrackIR had some commonality years ago (FS2002 now being, what, 6 years old?) Ah, I'm probably confusing it with the viewpoint setting. Without an on-line method of setting it, tracking it through the code in a debugger/disassembler is a bit of a nightmare! Regards Pete

Really? GoFlight make NaturalPoint's software for them? Is the DLL the 'module' you mean? Else I'm confused. Yes, I know. It's also settable in the FS menus, isn't it? Presumably NaturalPoint (or GoFlight?) have found a way to do it on-the-fly. It would be a matter of tracing the code from the menu changes to find out where to hook. Regards Pete

Yes, it is. But I believe the tower view has been used in programs to provide automatic fly-by facilities. I don't think GoFlight has anything to do with TrackIR -- TrackIR is made by a company called Natural Point, I think ... ... and of course they don't publish details of their methods. I'm not going to hack into such third party programs to find out, sorry. If you do find a way to do it please let me know. You might also want to look at FSX as it is completely different. There are ways of setting up cameras (via SimConnect, not FSUIPC), but oddly, as yet, no way of reading existing camera details. Regards Pete

Ah, sorry, FSUIPC won't work in a real airplane! It needs FS. ;-) Yes. Using FSUIPC to interface to an aircraft in FS cannot remodel that aircraft. Regards Pete

The error is that it can't find MFC42.DLL at all. In any case, I thought you said that the older (currently released) version of FStarRC got further, or at least didn't fail like this? Odd that there's been no change in any of that area -- the changes were mainly to do with providing additional parameters for Radar Contact APL plans. Pete

Well in FS that might possibly be done by the clever programming in the model you have, but otherwise, in the inbuilt FS controls, it's certainly within the continuous range of a prop pitch control which can go down through zero (feathered) into negative values (for reverse). If that is how it is implemented in your FS model, so be it. In that case you don't need any fancy reverse pitch calibration in FSUIPC or anything else, you simply need to assign a button. Why don't you try the model you have and see how it actually works in the Sim? Then you can look at how to emulate that on external controls. Regards Pete

Strange. I've seen such once. Not often, but I think there's a bug in the weather rendition code in FSX. Yes, it is utterly horrible, isn't it? I reported this soon after FSX came out last year. It makes any attempt at setting upper visibility pointless. You can get the same results manually, setting visibility layers. It makes that facility in FSUIPC useless at present. As soon as I can make things work the way they should, by actually directly changing the visibility as I could in FS2004 and before, I'll be onto it, don't worry. But it obviously won't be this year as Microsoft are fully committed. Regards Pete

That sounds exactly like normal jet reversers. There are facilities in FSUIPC for assignment of up to 4 reverser levers as axes (not switches), and the reversers then act as throttles, pulling back further increases the reverse thrust. It seems odd that with a prop you get reverse thrust with the prop pitch staying the same -- or are the engines actually rotating the props the other way, i.e. against the normal pitch? .Well, assuming the FS model has that enabled, yes. Have you not tried experiementing just using the mouse or keyboard controls on the default graphic quadrant? I think you need to experiment first to see what it is you really need to do. Once you are sure I can advise you further. If you are talking about true thrust reversal, using throttles, yes. I though prop reversal was by reversing pitch. But I must admit to knowing very little about all this. I fly a 737 or a Piper Arrow III. Regards Pete