ronzie

Since the 2K4 sdk isn't posted yet, I was wondering if the FS2K4 localized cells precip rates at specific offsets from the aircraft position can be read from FS. I am curious about this for purposes of someone creating a radar storm gauge. This was not realistic in FS2K2 because only global manipulation was possible. I wish to read this from FS's data so I would not be tied in to a specific weather program. Possible?

The reason was it was necessary to undock to allow windshield visibility for ground AI, then move back. I'll use the hotkey option for hiding. It is not a big issue. It sounds like a focus problem as you describe caused possibly by the later builds of RC or AS. I have RealityXP FLA and Jetline 2 (most recent) installed but these do not react with either module.

Along with FSUIPC 3.05 (full features), FS2K2, W98SE, ActiveSky WXRe 1.9b2, Radar Contact 3.1 build 2205. When add-ons are running, right clicking in the window momentarily shows dropdown list and disappears not allowing selection in dropdown list. My workaround is to bring up an aircraft without any Adv using apps, force it open via the modules menu (it is set to hide when empty), right-click to open the dropdown, reselect and redock, then open add-on apps. Active Sky is NOT set to show Flightwatch text. This is a fairly recent problem.

Thanks for your reply. Take the time to sniff the roses and keep your sanity.

I was referring to each aircraft.cfg have an area for FSUIPC parameters used for that specific aircraft. An example might be throttle mapping and control sensitivities where the user might want different characteristics for each model design.

In 2.975 I wonder if I missed any selection that would affect autopilot sensitivities. Anyway, there have been a few discussions elsewhere regarding poor over or under control of autopilot under approach situations. This might be something you wish to think about. Also, this might require a suggestion I made some time ago that perhaps those settings which are specific for each aircraft's performance be stored either in that aircraft's folder or in a section of aircraft.cfg.

Ok. At different times, I purchase two payware packages that include FSUIPC. Will these be download permits rather than included software so we do not get version clobbering from different vendor products as we install the apps? And yes, it is about time you got royalties for royal work!

Perhaps a clue in the panel.sdk? I would think of that more as a panel function with conversion of raw data into either displayed value, something not handled by FS itself. But then, I'm not a panel/FS hacker. I do not know if there is a button assignment in the tables for that MACH/KNOTS function but if there is such a table entry then perhaps the state can be read.

Perthaps a captured dump from the FS restart page (click details) might lend a small clue. It should state what module (dll) or task crashed if under FS's umbrella.

If there is an ini file for the driver, than there might be a cariable definition for the last state of the device. It could be set to 0, false, or off for one state and 1, -1, true, or on as the programmer defined the variable. For setting com port handshaking, assuming no other app sets that port (in other words it is dedicated to the Safeline), go into Device Manager, select the port, get to the properties, and I think it is under advanced settings. The program can overide these settings you should note, but these defaults should return when starting Win. The exact procedure to get to the handshaking depends on your Win version. You can also get an inexpensive serial port break-out box with indicators so you can watch the state of the status pins. For a 25 pin connector you open the through switches for 4,5,6,8,20. Then on each side of the box you tie (using the test pins and patches provided) pins 4 and 5 for one group, and a second group you tie of 6,8,20. I don't recall the 9 pin settings. This basicly provides constant handshaking values of true in both directions with only the comm stream signal getting through. You may not want to go this far but if you do search for a tutorial on RS232 communications. Some vendors that sell these boxes also offer a small book called RS-232 Made Easy. By the way, for a 25 pin connector, the comm bits fly in one direction on pin 2 and the other on pin 3 with 7 being the signal common. Unless you are at a slow baud rate, you may not see the indicator blink or change color.

If there is an ini file for the driver, than there might be a cariable definition for the last state of the device. It could be set to 0, false, or off for one state and 1, -1, true, or on as the programmer defined the variable. For setting com port handshaking, assuming no other app sets that port (in other words it is dedicated to the Safeline), go into Device Manager, select the port, get to the properties, and I think it is under advanced settings. The program can overide these settings you should note, but these defaults should return when starting Win. The exact procedure to get to the handshaking depends on your Win version. You can also get an inexpensive serial port break-out box with indicators so you can watch the state of the status pins. For a 25 pin connector you open the through switches for 4,5,6,8,20. Then on each side of the box you tie (using the test pins and patches provided) pins 4 and 5 for one group, and a second group you tie of 6,8,20. I don't recall the 9 pin settings. This basicly provides constant handshaking values of true in both directions with only the comm stream signal getting through. You may not want to go this far but if you do search for a tutorial on RS232 communications. Some vendors that sell these boxes also offer a small book called RS-232 Made Easy. By the way, for a 25 pin connector, the comm bits fly in one direction on pin 2 and the other on pin 3 with 7 being the signal common. Unless you are at a slow baud rate, you may not see the indicator blink or change color.

Hmmm. Wonder what the Euro conversion rate was when I donated via the sim site. Oh, well, the bill will get here in a day or two. (I'm a Yank, by the way.)

Hmmm. Wonder what the Euro conversion rate was when I donated via the sim site. Oh, well, the bill will get here in a day or two. (I'm a Yank, by the way.)

You state that sometimes you can see the gauge just as you kill the console. This makes me think of some possibilties: Perhaps there is a software on/off toggle out of phase with whatever message or state is detected from the console. Look for a registry or .ini file entry that might be reversed. Try on the com port in question different handshaking methods, or turn off hand-shaking entirely to force all the hardware handshaking statuses to a true state.

You state that sometimes you can see the gauge just as you kill the console. This makes me think of some possibilties: Perhaps there is a software on/off toggle out of phase with whatever message or state is detected from the console. Look for a registry or .ini file entry that might be reversed. Try on the com port in question different handshaking methods, or turn off hand-shaking entirely to force all the hardware handshaking statuses to a true state.

Many integrated modules are actually created as gauges written in XML to be embedded within FS. If FSUIPC can be your interface, consider that. While BASIC can be good for developing a functional overview type prototype, it does lack an easier if at all method of low level API calls provided by FSUIPC and FS itself. If you want a RAD interface, maybe Borland's C++ builder may fit your needs, but it might not offer you the linkage components you require. You can write direct C in it. How well their libraries are compatible under FS environment I do not know. These are just thoughts derived from perusing varios forums. I have no experience with FS or C++ builder myself, but I have other apps written in VC++.