Pete Dowson

No, it means that FSUIPC doesn't offer any facilities for you to change the weather settings. It doesn't touch FS's weather at all unless asked, and you can't ask it. If your weather is being changed through FSUIPC it will be another program doing it, or else you have some problem with your graphics card or its driver settings. Why having FSUIPC there or not would make any difference I've no idea, but generally it will be because of whatever is using it. Anyway, delete your FSUIPC.INI file before running FS next time, in case it has been corrupted. Regards, Pete

FSUIPC isn't actually doing anything itself as your FSUIPC is not registered. Since it isn't registered there won't have been any settings you could have changed. Regards, Pete

The FSUIPC user guide, of course! Where else? You program the buttons in the button page in the FSUIPC options, so of course that is where it is documented!! :roll: I take it from the rest of your rather insulting and very presumptious message that you won't be here again, which is actually rather good news for me, as you've been almost monopolising my time and most of the forum for a whileand yet still don't take any of my advice. I really hope you understand aircraft and flying rather better than you seem to do English. Good flying and good bye. Regards, Pete

Ah. How quaint! If he's getting ASv6 CTDing he most certainly needs to deal with their support. There's no way I can get inside someone else's program even if it was something I should be doing. The ActiveSky folks should be able to get to the bottom of it with enough information. It obviously connects to FSUIPC okay as his log shows. Pete

But you said you were running the GF45 on the FS PC. Please go back and read your message! This is the crux of that confusion, which you still have not resolved. Please read this part of your message AGAIN! If, instead of doing what you say you were doing, but are trying to run it on a client PC, then why not say so? Ah but it does, clearly. YOU read it! Here, I will extract the relvant paragraph: I AM SAYING NO SUCH THING! You can put the thing wherever you like. It ws you that said you moved it. I don't care a fig where you have it, that is entirely up to you! Of course! The documentation is very clear on that. You aren't even looking at it for sure! See these parts, for example: It is becoming more and more obvious that you are simply not bothering to use the documentation at all. I shall henceforth reply to such questions with "see the manual", as this is simply getting too exasperating. I should not need to keep quoting parts of the documentation merely to refute your inaccurate and untrue accusations! Nonsense. Read what it says. It's a case of programming things as you want them to be. It is the flexibility which it is becoming evident that you do not like or understand. Since that is the case I respectfully suggest that you don't use FSUIPC at all and ask GoFlight to support whatever it is you want. Regards Pete

Sorry, but the documentation has stood the test of time, over five years or more. I can answer specific questions here, but you don't even ask specific questions, only general ones which would require reproducing parts of the documentation. As far as the GF devices are concerned there are practical examples and file extracts which can be used in the GFdisplay package, but I certainly wouldn't expect you to look that far. Apart from that. FSUIPC treats GF devices as mere bundles of switches or buttons just like any other, and the programming of those is not only intuitive but has been explained to death here innumerable times. You must try to help yourself to some extent and not expect everyone to be telepathic and understand your questions, most especially when they are self-contradictory, as in the recent example. If there are specific parts of the documentation which you don't understand, spell it out and ask, but don't just keep asking me to solve problems that it seems you cannot explain at all, and, worse, give no helpful information for. Can't you see that it just wastes both our time? Regards Pete

But this is the confusion -- you said you moved the GF device to the FS PC, didn't you? You actually said it in the same sentence, viz: I really strongly suggest that you actually READ what you are writing to make sure it is what you mean before you send it. Please! How would that display anything to do with pitot heat? If you want to program displays on your GF devices without using GF software then you have to use my GFdisplay freeware. FSUIPC doesn't know anything about them at all. The button facilities are for programming buttons. I'm sorry, but I don't use GF devices and I really cannot support them. All I provide is an opportunity to program their buttons and switches if FSUIPC recognises them. For everything else, including support of hardware and GF software you have to go back to GoFlight. Well, many users certainly manage to use the GF rotaries with FSUIPC assignments, and it is thoroughly tested with them. I think you are not reading things correctly, again. If you are seeing no response in FSUIPC's buttons page when you turn the knobs then I really don't know what you've done. I suggest that you reinstall the GF software and start again. I really cannot help with such skimpy information. If you cannot see the buttons, switches and rotaries from your GF devices in FSUIPC then the GFdev module isn't available in the correct place, the place to which it is installed by GF's installer. Please see my documentation. As for GFremote or other ways of using GF devices, this is all outside my area of competence. Sorry. You will have to rely on GF support. Pete

What WideClient folder? You cannot use WideClient on the FS PC! I'm not surprised. It seems you are not reading the FSUIPC documentation again. The GF rotaries produce 4 button inputs in FS -- two each way, one for fast one for slow. Furthermore they send pulses (on-off-on-off ...) as you turn. If you want every click to matter you have to assign your controls to both press and release for both slow and fast buttons! You cannot do that without uninstalling the Go Flight software -- FSUIPC will always detect the buttons. If you don't want them to do anytthing you have to delete the assignments. What display? I don't know of any red pitot heat display! Yes of course. PLEASE READ THE DOCUMENTATION. There are shut down parameters in both WideServer and WideClient INI files, all described in the documentation. You are sending lots of questions here on all sorts of subjects, almost all of which are easily answered yourself if you'd only use the documentation. Please try that BEFORE writing here. Regards, Pete

No, as I've mentioned here many times before, it is an error in FS. When you arm spoilers on the ground they deploy. Pete

FSUIPC doesn't do anything with any aircraft. Some aircraft use it, but even then only usually for stuff like TCAS displays. You have something else wrong with your system. This shows ASv6 has connected okay, and has cleared the weather and set the FSUIPC weather options. It also shows some Squawkbox stuff running okay. I really have no idea what your odd term "porks" means, but this shows ASv6 is working with FSUIPC okay. The log also shows that no aircraft (loaded in this part) are using FSUIPC, so it won't have any affect on them whatsoever. Next time you show me a log please make sure it is a complete log -- i.e. close FS first. Regards, Pete

Just try assigning a different keypress then -- it sounds like they use the one you chose as a hotkey for something. Regards, Pete

Four button returns? Aha! That certainly occurs with the rotaries, where FSUIPC/WideClient create a "fast" and a "slow" button for each direction -- the rotaries send pulses at varying speeds according to how fast you turn the knobs. Anyway, if that's what it is returning, then, yes -- though if you want a more delicate trim you should really only program one in each direction -- but check the repeat whichever way, so you can hold the lever up or down for a continuous trim change. [LATER] Ah .. wat a minute. Is the trim on the LGT a wheel, like the trim wheel in a Cessna? Sorry, I seem to have fogotten most of the little I knew about the GoFlight stuff. I only had them for a while, whilst I was programming them. (Not enough space to keep everything! ;-)) If it is the wheel, then, yes, it is actually a rotary, just like the ones with left-right turning knobs on other deives like the GF MCP and the GF 45, 46, 166 devices. In that case check the FSUIPC documentation where it does explain about the 4 buttons, fast left, slow left, slow right, fast right. You could take advantage of those for sure. Program the fast versions for Trim Up/Down on both press and release, but the slow ones on only press. That will give you two speeds of trim, one faster than the other. I think I covered this in my examples in the documentation and accompanying files for GFdisplay. You may want to look there and take advantage of work done already. Here's an extract from the documentation: Regards Pete

Depends whether you are calibrating the brakes in FSUIPC or not. FSUIPC is more precise -- FS's slider is more guesswork or trial and error. For FSUIPC you just press them a bit (however much you think you might press them accidentally, and a bit more) and click the MIN set button. Pete

The trim lever on the GoFlight LGT is not an axis at all, it is a double pole centre-off sprung switch, represented as two buttons, one for up and one for down. There is absolutely no way possible to use a button or switch as an axis with more than one value each -- axes must provide variable parameter values to be of any use as axes. Regards Pete

If I remember rightly, I didn't understand why. FS has mixture and pop pitch assignments for any axis it can detect. Did you go into FS's Options-Controls-Assignments and try? Why? The ability to assign axes in FSUIPC is only very recent, and the facility isn't even on general release yet. Surely you should be using FS's assignments in the first instance. That is plainly not true. There are facilities for assigning axes to almost anything in FSUIPC, rather more than there is in FS in fact. Please explain how you think I can add facilities for yet more assignments when everything that is possible to be assigned already is available? Pete

Download and install the latest Glass Cockpit software from the PM website. Pete

How are you telling? Do you have the red "brakes" message on screen? Are you using rudders with toe brakes? If so, keep you feet well away from the braking part, or calibrate with a much larger null zone. INI for what program? I've not heard of any such adjustment in any case. Regards, Pete

Good. Ah ... I think (but I am not 100%) that FS only looks for files with DLL types, so that shouldn't have made any difference. However, I could be wrong. That said, the new FSUIPC facilities are designed (and tested) to cooperate with AdvDisplay, so either way this wouldn't explain it. I don't believe it can be that one. That is actually the most likely. Some glitch at some crucial stage somehow caused the needed Font not to be correctly loaded, even though it must have been marked as such 9else it would have been loaded again on the next FS restart). Were there any crashes of any program, whether FS related or not, in the same session before FS exhibited the problem first? I know it isn't (shouldn't be) often necessary these days to re-boot after a crash (WinXP supposedly being so bullet-proof), but I remember you'd really dare not continue without re-booting after anything crashed in good old Win95/98/Me days. There was simply too much likelihood of something being screwed up. :wink: Regards, Pete

I've fixed it in FSUIPC by sending one of the messages to WideServer which it would normally get but which is being inhibited in "menu" modes. The fix will be in the next Interim Update for FSUIPC, which will be available in the Interim Versions announcement above either later today or over the weekend. Regards, Pete

That should only appear if there is a multiline message to be shown. What are you running? Hmmm. I don't know anyway to stop the text being shown. Sorry. The lower option is only offered if the FSUIPC window is not required 9i.e. the first option is not checked). that is all. Obviously, if you opt to have the multiline messages all going to the FSUIPC window, there is no need to suppress them in FS because they don't reach FS in any case. If you are registered that option is more easily accessibly in the Miscellaneous options tab, as documented. disabled or removed? Have you tried removing it? No, they are not in SIM1, they are in the LANGUAGE.DLL in the main FS folder -- different language versions of FS have different versions of that DLL. FSUIPC doesn't touch any messages at all, or any text for that matter. It sounds more likely that you have somehow lost the font which FS uses. I don't know how that can happen. It certainly cannot happen merely by inserting a new version of FSUIPC. This seems to also be indicated by the fact that AdvDisplay displays the text correctly -- Advdisplay uses normal Windows fonts (and has a font selection dialogue too). No, it isn't. One of my PCs uses a 9800. Try removing your FS9.CFG file (don't delete it, so you can replace it if it isn't responsible). FS will make a new one. i'm not sure where the fonts are defined, but that would be a god starting point. Regards, Pete

I assume you mean in the joystick sections of the FS CFG file? I didn't think the LOCKED parameter did anything in FS2004. In fact I seem to remember it only ever worked in versions of FS before FS2002, when Microsoft changed the whole joystick system to DirectInput. It was DirectInput that really drove me to do things in FSUIPC as I couldn't get any control otherwise for my EPIC devices. Changed in FS's CFG file? There's no calibration information there at all, only the Scale (sensitivity slider values) and the null zone, both set from the sliders. They shouldn't change on their own. The original use of "LOCKED" was to prevent assignments changing when some loads of FS had different joysticks connected, or some re-arrangement of USB connections had occurred in the interim. Locked=0 is probably default, so isn't needed and isn't output when FS re-writes the CFG file, as it does on each FS close. If it did output this then it would always be there. It sounds like you did it when FS was still running. No such changes stick when FS is running as it will rewrite it from its internal settings on closing. I really didn't think it actually does anything useful. I'm not sure what these "changes" you are detecting are, but FS doesn't do any calibration in any case. If you aren't happy using FS for joystick allocations, note that since FSUIPC 3.536 you can disable the joystick in FS and use FSUIPC for all assignments, as documented. Regards, Pete

If that is the only problem then it sounds like the spoiler axis is jittering (i.e. feeding different values all the time even when it isn't being moved). If that is the case, then the change I have now made here in FSUIPC should fix it -- I am now ignoring changes in the axis if they remain inside the ARM zone. That change will be in the next interim version of FSUIPC, probably for release in the Announcements above tomorrow, or certainly over the weekend otherwise. I have also now tested some changes in Project Magenta which fix the spoiler indication on the EICAS (Boeing GC package), and I know Enrico will be making some updates available on his website soon too. So between them the main indication and deployment of the spoilers should be okay. The only thing remaining for you to sort out is the adjustment for use of the spoilers as speed brakes with deployments from 7% upwards. That will be down to good calibration and will depend on your joystick axis only. Regards, Pete

That sounds very much like the INI file was marked as Read Only! Anyway, glad you sorted it out. Regards, Pete

Yes. it is always better to use the names. It takes Wideclient a fraction of a second longer to connect, as it has to ask Windows to translate the name, but I don't think you'll notice! ;-) Pete

Right. I've found the reason. Whilst Windows is processing the Menus (rather than the dialogues they may produce), it apparently isn't sending any messages to any other Windows, and doesn't call any of its Chains, so my WideServer variable scanning is suspended. It only sees the setting when you actually get into a dialogue and messages resume. Looks like I'll need either to make WideServer intercept other parts of FS (ugh), or make FSUIPC send WideServer some special message when 3365 changes. I'm looking at that possibility first. Regards, Pete