-
Posts
38,265 -
Joined
-
Days Won
170
Content Type
Profiles
Forums
Events
Gallery
Downloads
Everything posted by Pete Dowson
-
What? Of course I helped. You need to assign the release to the view you want it to go back to, exactly as the example quoted from the documentation! Please don't bother coming back. I don't need your ignorant attitude. It helps no one, least of all yourself. Read the answer properly. Pete
-
You program the hat switch in any way you want. It isn't pre-programmed in FSUIPC, so you must have assigned it! If you want it to return to a specific view when you release it, you have to program the button release to set that view. FSUIPC is not going to "guess" what you want to be assigned and do it for you. If you think that you'd really be best of not using FSUIPC at all. FSUIPC is a tool. You use it as YOU want, not as it decides without your permission! Did you not refer to the FSUIPC User Guide at all? Perhaps you missed that very suggestion, viz: There are also examples of editing the INI file for hat assignments for panning instead of view selection in the FSUIPC User Guide. Regards Pete
-
FSUIPC Screen Display Clipped
Pete Dowson replied to pbayley's topic in FSUIPC Support Pete Dowson Modules
3.915 is far too old to support. You won't have the problem if you simply update to at least a 2010 version of FSUIPC. Version 3.98 has been current for nearly a year now and is the earliest version still supported. Please always check you are using a supported version before posting here. Pete -
FSUIPC 4.6x, Windows7_64 and Flap Detents
Pete Dowson replied to UTF's topic in FSUIPC Support Pete Dowson Modules
There's little difference in how FSUIPC4 finds FSX.CFG in the two installers. It is always via the AppData\Roaming\Microsoft\FSX folder in the "Users" section. The only addition in the later installer was to search the "all users" section as well. you are doing it incorrectly then. You must calibrate the lever normally first, with the correct minimum and maximum values. Then you use the detente's facility to define a zone around each of your flap positions. Do NOT try to limit the values too much around those positions. Show me the results of your attempts in the INI file and I'll tell you what is wrong with them. How are you assigning the axis itself? since FSUIPC is obviously running that isn't surprising! Since it is something you are doing wrong, changing FSUIPC versions isn't going to help. Please supply some actual information and I'll check. Regards Pete. -
FSUIPC and ELITE THROTTLE QUADRANT
Pete Dowson replied to karijno's topic in FSUIPC Support Pete Dowson Modules
The PFC axes feed through to FSUIPC as axes on joysticks 16-18. They are assignable in the Axis assignments exactly like any other, so you can assign them either direct to FSUIPC calibration, or to an FS control which can then be calibrated. Are you using FS9 or FSX, BTW. You don't say which. I've not looked at PFC on FS9 for some time. But it does work fine in both. If the Wilco implementation doesn't allow negative thrust values to engage reverse, then I wouldn't think there was any way via an axis except to assign to the "throttle decr" FS control (same as F2) as send it repeatedly over the number of zones you are allowed in one direction, and throttle incr (same as F2) in the other direction, with maybe a throttle cut at the idle point just to be sure. This can be done on the right-hand side of the axis assignments tab. It's not very appetising though. Regards Pete -
WideFS works for FSX but not FS9
Pete Dowson replied to Poppa Bear's topic in FSUIPC Support Pete Dowson Modules
Is the firewall shut down, or else are both FS9.EXE and FSX.EXE allowed through? There is no wideServer.INI nor WideServer.DLL for FSX. It is included in the FSUIPC4 code and INI. In that case WideServer is not running on the FS9 installation. Did you install the DLL? Please check whether there is a WideServer.LOG file. If not then WideServer is not running. If there is please show it to me. Please also ALWAYS state FSUIPC and WideFS version numbers. Regards Pete -
FSUIPC and ELITE THROTTLE QUADRANT
Pete Dowson replied to karijno's topic in FSUIPC Support Pete Dowson Modules
You know you can disable the quadrant axes in the PFC driver and assign them in FSUIPC instead, don't you? All that can be done by assigning in FSUIPC and disabling in the PFC driver. Regards Pete -
Should it? How do you know? What version of FS is this? What version of FSUIPC? You don't give much information. There's a very good User Contribution for the PMDG MD11X. Is that the one you mean? If you are talking about FSX, you know you need at least SP1 applied for mouse macros to be usable? Pete
-
No, Microsoft hardly ever used the standard gauge building kit they made for add-on aircraft folks to use. The mouse macros are virtualy ineffective on all the defalut aircraft. Actually mouse macros have been used pretty effectively with most parts of the PMDG 747X, and the FS9 PMDG aircraft. See the User Contributions subforum. Pete
-
Controls Stops Working
Pete Dowson replied to bradrcfii's topic in FSUIPC Support Pete Dowson Modules
Not sure what all those <div>s and things are, but I didn't say "download site" but the Download Links subforum, here, one of the useful subforums and the one in which all interim updates are provided. Pete -
That's a pretty sure indication that the way the gauge is written doesn't allow mouse macros to operate. Exactly the case - the mouse click calls an FS base module, not a Gauge, and that module hasn't been written using the FS C/C++ SDK rules for constructing gauges. The mouse macro relies on a specific data structure which only exists when that system is followed. Regards Pete
-
Controls Stops Working
Pete Dowson replied to bradrcfii's topic in FSUIPC Support Pete Dowson Modules
Well I'll have to experiment, see what's possible. It won't be for a couple of days, I'm a bit tied up. Look out for info in the Download Links subforum. The current FSX FSUIPC there is 4.656 -- you are a bit out of date. If it changes to 4.657, scroll through the list of changes, to the end, to see if I've managed it or not. Regards Pete -
Can lua code replace GFDisplay.exe
Pete Dowson replied to r2500's topic in FSUIPC Support Pete Dowson Modules
As I thought was made clear in the Lua library documentation, the GFD library is not supported in WideClient -- see where it says "not in WideClient" in the title for that library? Maybe you have out of date Lua documentation, from before WideClient supported Lua at all? Please check the Download Links subforum. It might be possible to add most if not all of that library to Wideclient. But it isn't a trivial job. much of the one in FSUIPC used existing FSUIPC code. I wioll consider it though. Regards Pete -
Controls Stops Working
Pete Dowson replied to bradrcfii's topic in FSUIPC Support Pete Dowson Modules
If you are sending key presses I suspect that the FMC is taking the keyboard focus away from the FS routines which are intercepting those key presses. You'd need to click back on the main FS screen to restore focus. Not really. It's the way Windows keyboard focus works. Can you not assign the buttons direct at all, or use controls? Doesn't the Level D aircraft get support from the Nico Kaan interface program? It may be possible for me to add an option for FSUIPC to check where the focus is and maybe restore it to the FS screen each time, but I wouldn't want to do that as a general rule because sometimes the user might intend the keyboard focus to stay in one place when he's moved it by mouse or touch screen (which is effectively a mouse operation too). Maybe I'd need to provide a "restore FS focus" control for assignment to a spare button, too. I'm also not totally sure it can be made to work consistently even so. BTW please also always state FSUIPC version numbers when asking for advice. I don't even know whether you are referring to FS9, FSX or even FS98, but I do need actual FSUIPC numbers please. Regards Pete -
Calibration and Saving profile
Pete Dowson replied to Shermann's topic in FSUIPC Support Pete Dowson Modules
Ah, in that case it will be the calibration, especially the centre zone -- and you do want to set a small central zone so that slight movements either side do nothing. This then absorbs any jitter or variation in your controls. The other thing to check is the setting of the aileron and rudder trims. You might not have visible controls for those, depending on what aircraft you are using, but you can check them in the FLT file(s) you are loading -- or just save a flight then look. They'll be in lines like: RudderTrimPct=0 AileronTrimPct=0 in the [Controls.0] section. Make sure both are 0. If not you can change the file and reload the flight. Regards Pete -
Good, great news! Pete
-
Well as far as I can tell, in the files you pasted into the previous message, the only entry wrong was the AICarriers one in the EXE.XML, where this should be several lines, not all one: should be something like <Launch.Addon> <Disabled>False</Disabled> <ManualLoad>False</ManualLoad> <Name>AICarriers</Name> <Path>C:\Program Files\AICarriers\aicarriers.exe</Path> <CommandLine>-nogui</CommandLine> </Launch.Addon> You could insert that back if AICArriers isn't loading. Do it just before the last line (</SimBase.Document>). The CumulusX pasrt of the EXE.XML is: so you could try inserting that back into your EXE.XML, at the end, just before the last line (</SimBase.Document>). I thought it was simply a matter of entering your product key. I've not had to do that for years so I don't recall where it is done -- in the Help menu, maybe? If not maybe a post in the FSX Forum will elicit an answer? Regards Pete
-
RADAR CONTACT FSUIPC ERROR
Pete Dowson replied to Shermann's topic in FSUIPC Support Pete Dowson Modules
It's not FSUIPC. It's a timeout in RC which occurs sometimes when your FS is overloaded. RC should simply retry. I've no idea why it stops with an error instead. It is not at all drastic and it could carry on with no problems (as it will do if you click okay or whatever). Hopefully they will fix it in RC version 5. Please check the RC Support Forum where this subject has been flogged to death. I think folks there know what things can make it worse and how to make it not happen. I've never had it happen here and I've used RC since the very first version.. Regards Pete -
Calibration and Saving profile
Pete Dowson replied to Shermann's topic in FSUIPC Support Pete Dowson Modules
That's quite normal for prop planes due to prop torque and tail wash. You almost always have to apply some rudder pressure to one side or the other, depending on the direction of spin of the propeller. This gets even worse on the take-off roll as you increase the revs. When flying, you mean? In that case it isn't calibrated to centre correctly. Have you followed the numbered steps for calibration in the User Guide? did you try looking in the FSUIPC User Guide at all? When you click the profile button, in the drop down, one of the entries is for a new profile, which you can then name. It is documented, with pictures even! Same as before, click the button. Please do check the user guide, it is supplied with FSUIPC for a reason, to show you how to use the facilities. Regards Pete -
Ah, sorry, but I'm still none the wiser really. I think there's an aircraft builder or panel beater forum someplace, maybe on AVSIM. Maybe asking there would elicit answers? Regards Pete
-
Sorry, I'm completely lost I think. AP = Autopilot? Part of the aircraft? If it's a gauge then is needs to be loaded via the PANEL.CFG, and that can load it from the panel folder or the gauges folder, or, I think, elsewhere if you put a pathname in. But I wouldn't swear to that last one. Check the FSX SDK. There are chapters in the guides there about these files. Pete
-
Variables in any program, whether written in C, C++, C#, XML, ASM or whatever can only be seen outside that program if the programmer allows them to be seen, by exporting them in some manner. Within FS, XML gauges can use local named variables which are registered centrally in FS and which can be then accessed by name. These are known as "L:Vars", and FSUIPC provides macro facilities to be able to set them, whilst Lua has both read and write access to them. Please do look up the details of these, in indeed, the gauges are written this way. The User Contributions subforum also has lots of examples for different aircraft. And I see there is one called AirbusX - Lua file - GF-MCP Displays Oh, hold on! That's by you! Now I'm confused. What is the point of your question when you appear to have the answers? As far as other languages are concerned, there are mechanisms implemented in FSX for any part of it to supply any other part of it with data. For instance, the main sim engine defines variables, also accessible in XML, which are readable and sometimes writable via SimConnect. Those are all defined in the SimConnect SDK. These did mostly exist before SimConnect too, and accessible by name or index to gauges. BUT, and it is a big BUT, add-on gauges do their own thing, and often simply do not use the FS values. Sorry, I don't know anything about that. Regards Pete
-
Oh, not so much a demo, the unregistered time limit. I see. No need to. Words are fine. And is there NO "AddOn" menu entry, or an empty one, or what? No need to, words are fine. Not sure what the size on disk has to do with it? You need to employ a process of elimination. To start with, since FSUIPC most certainly is running and has confirmation back from SimConnect that the FSUIPC entry has been added to the "AddOns" menu, it sounds as if something is then managing to remove it. When you run FSX are you also running other things, yourself, or is everything aslso automatically starting as well? If the former, try it without running anythnig else as well. If the latter, please find and showe me your EXE.XML and DLL.XML files and we'll try to work out what to eliminate. Those files are found in the same folder as your FSX.CFG file. You may not have an EXE.XML, but there will certainly be a DLL.XML file because that's needed to load FSUIPC. If you don't know how to find these things, show me the FSUIPC Install log and I'll tell you where to find them. The install log is in the same place as the FSUIPC log you showed earlier. I really don't need pictures in any case. Don't worry about those. Descriptions are fine. Regards Pete
-
Calibration is OUT OF WACK
Pete Dowson replied to Drover's topic in FSUIPC Support Pete Dowson Modules
What version number of FSUIPC? Are you assigning in FSX or FSUIPC? Are you calibrating in FSUIPC? You don't really tell me anything to help I'm afraid. If you are assigning in FSUIPC, why? If you are assigning in FSUIPC are you using the "joy letters" facility so that FSUIPC can track your devices? Otherwise if you plug them in differently, or even do minor changes to your USB connections, like sometimes have them connected and powered and other times not, Windows re-numbers them so their IDs change (the joystick numbers 0 to 15 used in FSUIPC assignment). This is why I implemented the lettering facilities, which allows FSUIPC to change the number assignments should the devices move. If you are assigning in FSUIPC be sure you have disabled all controllers in FSX. In general there is no need to assign in FSUIPC unless you need to make use of some of FSUIPC's extra facilities. You can calibrate FSX assigned axes in FSUIPC too. Regards Pete -
Yes, that shows FSUIPC4 is installed and running okay. It even proves that its menu entry is added too. FSX in demo mode? What does that look like? Where are you looking? What "addon area"? What's in the AddOns menu then? SimConnect most certainly confirms it has added the menu entry. Mind you, if FSX is running in "demo mode" maybe it doesn't give you a full menu bar? That is not a message from FSUIPC. I've never seen it before. Something else you are running is doing that. Regards Pete