Pete Dowson

There's no "toggle panel" control listed. The one which corresponds to the "W" key in FSUIPC's list (and in FS9's CFG files) is "Panel Hud Toggle". This cycles through panel-minipanel-no panel. There are specific panel part toggles, usually mapped to Shift+1 to Shift+9 -- the "main panel" is usually Shift+1, but this relationship is defined in the Panel.CFG files. There is a "Panel Toggle" which toggles the panel on and off without cycling through the minipanel. You are assigning the wrong control. Try using either the FS assignments with "Panel on/off" (which I have just tested and certainly works fine with the Num/ key), or, in FSUIPC, the "Panel Hud Toggle". These are the same controls and both work fine. I don't understand why you are making such complication out of this. Why not just go to FS Options-Controls-Assignments, find the assignment to "W" (against Panels On/Off) and reassign that control? In FS "W" is "Panel On/Off" and will work when assigned to Num/. Why haven't you used FS for this? In FSUIPC it is Panel hud toggle (as, indeed it is inside FS and in the FS9.CFG file), and it will work as well when assigned to Num/. Regards, Pete

Well, you completerly confuse me. Why map one KEY to another KEY? And how on Earth do you do this in FS assignments? What would you want either KEY to do? Surely if you want Num/ to do what W used to do you should simply change the Panel On/Off mapping from W to Num/. What would mapping "W" to anything accomplish? "W" is just a Key on the keyboard. Why do you want it to produce Num/, even assuming FS could do it? You seem to be mixing up keyboard keys and FS controls. The FS control is "Panel On/Off". Keys are those things on your Keyboard. You can assign almost any key to any of the FS controls listed in FS assignments, but you cannot assign a key to a Key! It makes no sense. :( Can you actually explain what you are trying to achieve? What do you want to use the W key for that you have to reassign the Panels On/Off control in any case? Pete

Try the thread entitled ""re: writing active weather to fsuipc from active sky". Sorry i can't post another at present, but there will be an update for wider tests up in an announcement later this week. Regards, Pete

I don't think it's my place to do this, sorry. I have quite a lot to do of my own, and am 100% rooted in MSFS. It is easy enough to find details of the NMEA sentences he would need to produce on the web these days. When I first did GPSout I had to purchase a copy of the NMEA specifcation, a 100 page document, for several hundred dollars. He certainly won't have that sort of problem now! :wink: Regards, Pete

For writing a station the TimeStamp is at C824. What are you doing with CC00? If you meant read the timestamp at C824, then yes. If you are setting a string of stations you would read it in the same Process call as the previous station. Something like this: 1 read timestamp 2 write station 3 Process 4 save timestamp read as "x" 5 read timestamp 6 Process 7 if timestamp changed frm "x"? If not loop to 5 (at next time interval) 8 save new timestamp as 'x' 9 continue at 2 till done all This "timestamp" business is a hand-shaking protocol -- there's only one set of weather data being processed in FSUIPC at a time, so you have to know it's done one before sending the next. For reading weather, not writing. Is that what you are trying to do? If you mean when SETTING stations, then I'm afraid that you will read back what you've just written. It will only get changed to "GLOB" (say) if it's not a WX station. If you are talking about only reading weather, then, yes. In fact once you've set the station and it is accepted it will update every second and the timestamp will change accordingly. But if someone else asks for weather, or the ICAO isn't a listed WX station, you might wait forever, so take precautions. Many programs simply ask for weather by Lat/Lon to get around the problems of WX station lists. Well, I'm confused -- are you asking about READING weather stations, or WRITING them? Your subject line implies writing, but the questions are then a bit, er, skewed. :wink: Regards Pete

Yes. Regards, Pete

No, but I've never noticed it as a problem -- your throttles should have been pulled back to idle of close for the descent in any case. The spooling delays are sufficient for you to "get the feel" for the correct throttle quickly enough. The only other way would be to get a motor drive for the throttle quadrant with some interface for a driver in the PC. Regards, Pete

Yes, it's been reported before in several threads. It's a bug in 3.45 fixed in interim versions attached to one or two replies here already. It only happens if Throttle1 is calibrated in the multiple throttles page of FSUIPC. Apologies for this. You can either check for those mesages with attachments below to get an interim patched version, or wait till about the middle of this week when I'll be posting "official" interim versions for wider testing in the Announcements section above. Regards, Pete

Why not do this in FS? It's the control called "Panel on/off" in FS's assignment list. The default action of the "W" key is the "Panel HUD toggle" FS control -- see the "missing view command" thread below. Regards, Pete

Show me the relevant INI file parameters. There's no reason for it not to work. Pete

Yes, sort of. You'd need to only program the single ones for "release", because it is not going to be actually possible to "press them together" exactly -- one will always be seen before the other. The more usual way is to have one button as a sort of "shift" to give an extra function of all the other buttons. This is what FSUIPC calls "conditional" button programming, and means editing the FSUIPC.INI file instead of entering things only in the dialogue. The Advanced User's guide describes the facilities that are available -- which include conditions based on other buttons, on "flags" which can be set and cleared, and even on the values of FS inner variables, via FSUIPC "offset" values. Be warned, though, it can get quite complicated. One day, maybe, if I ever get time, I should write a user-friendly front-end for it all. Regards, Pete

Well, I would either have to do it through TrafficInfo, or hack it to find out how it does it. Neither is very appetising I'm afraid. It's an area I know nothing about, so it makes it very difficult in any case -- I'd have to learn a bit about mulitplayer, which I've never used, and I just don't see how I'm going to be able to fit it in. Sorry. Regards, Pete

Good catch! The flag indicating whether the flight is already frozen or not (to avoid re-reading the position) isn't cleared in the correct place. it works fine using the added FSUIPC controls, but not the offset itself. Sorry. It will be fixed in the next release. I will be posting an interim test update here soon, hopefully by the middle of the week. Good. Please try the interim WideFS update I shall be releasing mid-week (here too). The main change is that I've stopped using Windows timers for all the timings and I'm using my own timing thread now. This seems to tighten everything up a little, giving better responses. I suspect the Windows timer messages were bunching up on occasion. They are treated at very low priority by Windows. Also I think Windows merges multiple timer messages in the queue, so timings go atray as well at busy times. Regards, Pete

What version of AdvDisplay are you running? Is it enabled? Regards, Pete

The FSHotSeat author has not contacted me, and I have absolutely no details about such a problem. I am afraid that it will never be "fixed" if no one seeks a solution. Going back to an old unsupported release really solves nothing. I'd really rather you check the KEY file first please. The suggestion I made to you was merely to ascertain whether it was due to a bad user key, but. I'm sorry, I omitted to ask whether you are FSUIPC user registered first. If you are not, then my earlier post is completely irrelevant so shouldn't be repeated in any case. If you do have a bad key (that is a stolen or counterfeit FSUIPC user key) then most things using FSUIPC won't work in any case. What happened after 3.40 is that the user key checking was tightened. So far there's been no case at all of any good non-time limited keys falling foul of the checks, but about forty cases of counterfeit keys discovered and one good but time-limited key. If you do go back to the FSHotKey support site then the best thing to do would be to have the FSHotSeat person responsible for this suggestion contact me directly, and discuss what is happening so a solution can possibly be found. Maybe FSHotSeat is writing to an undocumented part of the FSUIPC offsets, the function of which I am not aware of, and that area has been re-mapped elsewhere. If this is the case I'm sure it can be located and rectified quite quickly. It has been several months since version 3.40 was superseded (five months at least, in fact), with as many intermediate releases. To let a problem go for so long with no one botthering to try to get it fixed doesn't really bode well. Why not see if it can be dealt with, even if belatedly? Thanks & Regards, Pete

Ah, yes, I think you are right. In FS2004 at least it isn't what you need -- best to assign View Forward instead. It does what I wanted view Reset to do in any case. I'm afraid FS doesn't provide any conditionals for use with its assignments. Whatever clever things you do in FSUIPC won't stop FS interpreting buttons and POVs the way it has them assigned. Sorry. Regards, Pete

I was in the process of replying to a PM (Private Message) from an FSUIPC user who was complaining about the Brakes problem in version 3.45, when the system inexplicably came back with "user doesn't exist" and both his and my messages disappeared! The message was comparing 3.44 with 3.45 and mentioned two problems -- one about the brakes not working (known and reported here a while back) and one concerning thrust reverse, for which I needed more details. Can the person who posted it please re-post here (preferably with more details about the reverse problem) so I can deal with it properly? There was nothing private about the "Private Message" in any case. :wink: Please, all readers, never post technical queries or bug reports privately. There's limited capacity there, both for numbers of posts and for attachments, no threading and so no history. Worse, only the poster and postee sees the message, so answers help no one else and may be a long time coming when I'm on holiday. Thanks, Pete

Oh, right. Sorry, I would never have understood that from what he said. Thanks! But if you are Creating a Flight initially in any case the date and time are presented to you so it is easy enough to change there and then. Thanks. I've not heard of that one. I do use FSRealTime, which allows you to set an offset to your system time -- I'll look at Time Keeper. Regards, Pete

I'm not sure what you mean, but if you need to contact me privately you can do so initially via the Private Message (PM) function here. Regards, Pete

FSUIPC does not touch sound or have anything whatsoever to do with it. If you have a problem with >3.40 which isn't present in 3.40 then the most likely cause is an incorrect user Key. Try removing the FSUIPC.KEY file from the FS Modules folder. If that fixes it, then I need to see the KEY file -- do NOT show it here, ZIP it and send it to me at petedowson@btconnect.com.

Oh, but I would so love to find time to fly other than my standard test flights. I need to be able to notice every little difference, so on the few occasions I do manage to fly it is usually the same routes. I'm very sorry, but I still don't understand. I thought you were referring to the Zulu time on the weather being different from your local time, which of course it will be except in the Zulu time zone. Surely if you are creating your own flight you can set the time and date how you wish it to be? I don't think this is dependent upon time zones. When I go to the "Create a Flight" dialogue I see, in box 4 ("Selected time and season") the current date and time. This is obtained by FS from my PC system. For example, I am just looking now and it says "12/02/2005 02:06". Now, I did not enter that. This is FS's setting because I have the option set (Settings - General) to use System Time. Perhaps you haven't set this? There are some problems with crossing time zones, which is why I recommended FSRealTime to you. Have you looked for it? Maybe it will answer your needs (which I plainly still do not understand)? Regards Pete

There are 6 files in the WideFS ZIP with names beginning "Wide": WideFS.pdf WideFS.doc -- the documentation in two different formats WideClient.exe WideServer.dll -- the programs themselves WideClient.ini WideServer.ini -- the configuration settings for the two programs. Please look again. In the case of WideServer.ini it really doesn't matter a great deal in any case, because WideServer will generate one automatically when FS is run, and all the default settings it makes should be fine. It is a little more important to start off with one for WideClient because you have to edit it to tell the Client the name of the Server. Regards, Pete

Why are you assigning them as Keystrokes? Best to use the FS controls for view selection. Why do you have them repeating? There's no point in repeating fixed view selections. Best to program them for the controls, on "Press", with release assigned to view reset. That's because that scrolling is "panning", not view selection. By default FS uses the Hat for panning. The only advantage of using FSUIPC is to get view selection instead, which best suits 2D cockpits. I think they will pan if you set "pan_in_cockpit-mode=1" somewhere in the FS9.CFG, but I'm not sure about that and don't really see the point. If you like panning you are best using FS's Hat system. Regards, Pete

Living and mostly flying where I do, in the UK, local and Zulu time are the same, usually, so I don't notice any problem, if there is one at all. Weather METARs are timed in Zulu time in any case, not local time -- is that the "problem" you see? I'm really not sure I understand. You can fix the latter by reloading the AI traffic. In FSUIPC I've provided an additional control to toggle AI traffic off and on -- if you do that, when it is reloaded it will obey the current weather. As for the first part of this 'problem', sorry, I've not experienced that, but then I tend not to use the "create flight" dialog. A matter of long-term habit, I suppose, over many versions of FS. I prefer it to load straight into a flight. If I want to download weather I do so then via the Menus, but mostly I use ActiveSky or FSMeteo in any case. Sorry if I'm not being much help. Maybe this is a better discussion for the FS2004 Forum? Regards, Pete

The key programming is saved in the file called "FSUIPC.INI" in the FS modules folder. All FSUIPC options and selections are saved there. Are you using the latest version (3.45) of FSUIPC? If not, please upgrade first. Then, if it still happens, show me the [Keys] section of your FSUIPC.INI file. Maybe that is in a mess from some problem earlier? Regards, Pete