-
Posts
38,265 -
Joined
-
Days Won
170
Content Type
Profiles
Forums
Events
Gallery
Downloads
Everything posted by Pete Dowson
-
UTTERLY LOST WITH CONTROL ASSIGNMENTS
Pete Dowson replied to SimSamurai's topic in FSUIPC Support Pete Dowson Modules
Okay. Thanks -- looking forward to reading them! They aren't gauges as such, but windows. And the graphics are done using OpenGL, not DirectX. They are not gauges in that sense at all, but separate programs, nothing to do with FS except via their interface through FSUIPC. There are separate sections for axis Assignments (Axes) and Calibration (JoystickCalibration). As I've tried to explain before, you do not have to assign axes in FSUIPC to have it calibrate your axes. In fact the assignment part was a much later addition. The buttons are assigned in a section called [buttons]. I would have thought you'd just enable it in FS and make whatever assignments you want. I've never trusted FS's automatic assignment in any case, it goes weird too often. Watch out for minimum sensitivity sliders and overlarge null zones. Regards Pete -
FS2004 issue with Thrust Reversers(keyboard)
Pete Dowson replied to VirtualPIA's topic in FSUIPC Support Pete Dowson Modules
Sorry, I've no idea what "Tinmouse" is. Sounds like something is connected to throttle number two and its input is controlling things. It doesn't sound like it, as you said #2 reverser opens for a time. And why is that? Ah, so "Tinmouse" is an aeroplane? What do you think that might have to do with it? Really, I don't recall that. So, have you any joysticks assigned? Have you gone into the FS menu and explicitly disabled any? I'm not sure why you are coming here. Do you suspect FSUIPC for some reason? Is it registered? Have you used any options in FSUIPC? It doesn't do anything unless it is told to. Regards Pete -
Wide Client won't shut down
Pete Dowson replied to camaflight's topic in FSUIPC Support Pete Dowson Modules
I did not find out how to do this although I looked throgh both the user guide and the technical manual. How did you terminate Wideclient, then? I thought you said it became unresponsive. Anyway, I don't know where you looked, but you evidently missed all this in the WideServer parameters section of the Tech guide: And all this in the client section: How did you miss such big chunks? That's okay. It may be tomorrow before I can look at this stuff now. Regards Pete -
Why not get it sorted, as you did once, then save that as your new startup flight? Pete
-
Visibility above certain alt
Pete Dowson replied to Sam@MAN's topic in FSUIPC Support Pete Dowson Modules
The visibility limits only apply to the surface visibility layer. It sounds like you have a weather file or program which is setting the surface layer rather deep! You don't mention what version of FS you are using, so I'm going to assume FS2004. I'll also assume you are using global or externally-supplied weather, as the options you need don't apply otherwise. Look at the other items on the FSUIPC Visibility options tab. Do you see the options just below the one you mentioned which says "override upper altitude by ..." etc? Try using that to, er, override the upper altitude. There's a check mark to make and the altitude to enter. It's easy enough and should be self-explanatory. You might also want to visit the right-hand side of the same page and implement graduated visibility changes. These would work with any source of weather. Incidentally, all this stuff is also described in the FSUIPC User Guide. Regards Pete -
Good. Strange though. Regards, Pete
-
There isn't one in FSUIPC4. It wasn't possible to do it with the new way FSX is handling things. That facility could not possibly help sort that problem out in any case. In fact it would exacerbate it, as it would lock them in the wrong places, as those wrong places would be the initial positions and thus those to be locked! There is a program which will save and restore them for you. Check this thread: viewtopic.php?f=230&t=77240 Regards Pete
-
Wide Client won't shut down
Pete Dowson replied to camaflight's topic in FSUIPC Support Pete Dowson Modules
The log shows normal exchanges, no problems detected there as far as I can see. However, unfortunately you Zipped it before closing WideClient, so i get no statistics showing how well or otherwise it was performing. They also show how well the application did. If you find you cannot terminate it with ASV6 running, try terminating the latter first. And of course you can always use the facility to terminate it from the FS end. The question which needs answering mainly iswas ASV6 running okay? There's no indication here that it wasn't, though you imply not by saying "trying to run". If you do another test, change the "log=debug" to "log=debugall". Then I get to see the actual data exchanges too. But please try to get a complete log with WideClient (and WideServer) terminated. Use the termination facilities in WideServer/Client INI if necessary. And please show me the WideServer log too -- the Client side is really only half the story. Regards Pete -
UTTERLY LOST WITH CONTROL ASSIGNMENTS
Pete Dowson replied to SimSamurai's topic in FSUIPC Support Pete Dowson Modules
I only know the Beoing suite -- the programs PFD, CDU, RCDU and MCP (alongside pmSystems and pmSounds). The PFD program provides the PFD graphic itself, the ND, the EICAS (and secondary EICAS for those Boeings which have it), and the copilot PFD and ND. The one program can be configured to show all of these or just one part (PFD/ND, copilot ND/PFD, or one or other EICAS). The EICAS has optional standby instruments and other indicators such as trim gauge and flaps gauge. The various components can be sized, and moved around pretty much independently to suit the screen. In the past I've had three copies of PFD on one PC driving three screens on a Matrox TripleHead2Go, and one copy doing the same. In ther PFC cockpit the PFD program is running on three separate mini-PCs -- Pilot, EICAS and CoPilot. The instruments can be framed or unframed. Of course in my cockpit they are unframed as the screen they are on is framed in the cockpit MIP. The CDU and RCDU programs (the latter is a slave to the former, but can have a different display showing) can show a complete CDU with its keys and so on, or just the CDU screen itself for hardware CDUs, as in my cockpit and in CDU's by folks such as Engravity. The MCP does have an MCP graphic, but that is the rarest ever used as most PM users do have a hardware MCP -- the MCP program can interface directly to most of the well known ones. So, it isn't really a do-it-yourself panel kit. But the "frames" you can put them into can be user-supplied I think. I'm afraid I know nothing about the GA and other PM offerings. If you want to know more I think you can download demo versions. You might also want to look at competitors' offerings -- there are airliner suites by Flight Deck Software and SimAvionics. And there is FSxpand which may offer more choice for other aircraft. I don't think that's PM's style. They do a lot for professional training setups and I think prefer to concentrate on that market where they do a lot of specialised installation and support. The home hobbyist seems to be a bit of a distraction! ;-) Take a look at some of the cheaper offerings as well, then. There's also a freeware set too I think. If you visit http://www.mycockpit.org/forums, select an appropriate forum, and ask around I'm sure you'll get some good suggestions. My experience is really limited to PM Boeings which I've concentrated on now for the whole 10 years they've been in operation. Regards Pete -
Wide Client won't shut down
Pete Dowson replied to camaflight's topic in FSUIPC Support Pete Dowson Modules
Ah, the link layer topology thingy. Yes. But that really only applies to Vista automatically seeing and listing the XP computers. It shouldn't have affected WideFS's abilities at all. If both PCs are in the same WorkGroup** then WideFS links automatically, but even if not you simply specify the ServerName and Protocol in the client's INI file. WideFS doesn't use the Explorer links discovered by the topology fix. You didn't say what programs you are running on the Client. It is quite possible for client applications to hold WideClient in a tight loop so that processing windows messages becomes difficult for it. There are ways to counter that by parameters in WideClient's INI file -- but before trying that I'd like to know what the programs are, if any. If this problem is occurring even before you run any client applications, then it must be something to do with the Network somewhere. Maybe that log you got shows clues? Regards Pete ** You set the WorkGroup name in the same place as you set the Computer name -- in My computer Properties. Vista has a different default WorkGroup name to XP, so you do need to change one of them to match the other. Or, better, change them both to something sensible. My workgroup is named "Petes". ;-) -
Something is holding the brakes on, then, and as it only happens with the one aircraft I'm afraid it is over to them (PMDG?). If it was more general, i.e. all aircraft, I would, indeed, suspect some old assignment to your now not connected rudders -- especially if they were Game Port connected. If you have a game port driver still attempting to read a device no longer connected, it will return values which can do things like hold brakes on. Check the list of controllers assigned anyway, just in case. Regards Pete
-
Wide Client won't shut down
Pete Dowson replied to camaflight's topic in FSUIPC Support Pete Dowson Modules
That's strange. It sounds like something is running on that PC and using it so intensely that it is not getting time to follow any less urgent Windows messages. What programs are you running on the Client? Alternatively, if the frame rate it shows is low or zero, then it would be some sort of hang up in the networking driver part of your client PC. You can get the frame rate displayed in the WideClient title bar - there's a parameter for it (check the documentation). See if that tells you which circumstance applies. Or perhaps easier, set Log=Debug in the INI file and see if the Log continues and continues or simply comes to an untidy end. What problem is that? Until i updated to Windows 7 RC a few months ago I was happily using a Vista server with XP clients. In fact I have 7 XP clients in my main cockpit setup. Regards Pete -
No, the '.' key momentarily presses the brakes. So pressing and releasing it presses and releases the brakes. It also releases the parking brake if that was set, mimicking what happens in a real aircraft. So if something has set the brakes on but not released them, pressing '.' would release them -- providing whatever was setting them wasn't doing it continuously. There's no sign of any toe brake or any brake activity at all in the log, so I shouldn't think so. Are you sure the brakes aren't on in the Flight you are loading, and you are just not releasing them? Try pressing ".". Regards Pete
-
Ah, that is not "autobrakes". Autobrakes can be set to any value, and they don't illuminate that sign because autobrakes do not come on until the aircraft lands. I think you are a bit mixed up. The "Brakes" sign means that the brakes command has been given -- either via both toe brakes being pressed at once (only one would give "differential brakes"), or via the single overall brakes command -- the same one operated by the "." keypress. Manual braking is the exact thing which was occurring if the BRAKES sign was shown on the screen. Autobrakes do not illuminate that sign at all. So which words don't you know? They are pretty much either numbers or English -- not your natural language? Okay. First thing to note is that you are using an out-of-date unsupported version of FSUIPC. Please update before you come back for more help. Please review the Announcements in this Forum which tell you what versions are supported. Second, just a simple search for the word "BRAKE" shows that there are no brake controls logged as being sent to FS during the portion of your session shown. There is also no sign of any obviously spurious buttons or keypresses in the portion shown. In fact the number of button presses (only 7!) for as complete a flight as you said is remarkably low -- evidently you either don't use them much or many are not assigned in FSUIPC. Nevertheless, FS does see all the controls which are sent to FS, whether from your buttons or from other sources such as PMDG aircraft. There are quite a few of the latter by the look of it -- like this repeated cycle early on: However, none of them operate the brakes. So, either the brake operation occurred before or after the portion of the session as logged (with the options needed selected), or it is somehow being applied directly, in a way not using any FS control. Sorry, I'm no help with this. As it only happens with the PMDG aircraft i suspect it is only they who can help here. Maybe if you talked to them again, but without talking about "autobrakes" (which is an irrelevancy and probably took them on the wrong track), but instead merely talked about brakes being operated, they may understand better. One question. when "BRAKES" was shown, did you try pressing the "." key to turn it off? Another question: do you have rudders with toe brakes? Have you calibrated the toe brakes so that they are always off when untouched, even with pressure on the rudder? Regards Pete
-
No, sorry, only with FSX and ESP. Regards Pete
-
Sorry, what does "can stock" mean? For FSX or ESP there are facilities in FSUIPC4, which extensions in Lua, for reading and writing L:vars, variables which are used in XML gauges. Is that what you mean? Please check the FSUIPC documentation. The L:var macro facilities are described in the Advanced User's guide and the Lua facilities in the Lua Library document. there's also an example Lua program which lists L:vars for you. Regards Pete
-
Autobrake set to what? How do you know if there's no indication -- in other words where IS the indication if it isn't on the autobrake switch? And how are you undoing it if the autobrake switch is still in the Off position? Translate into what lanbguage? Which bits don't you understand? there is nothing there about autobrakes -- why do you think there would be? No. You need first to go into FSUIPC's logging options and set the Event logging on -- it's one of the checkmarks on the left. In case it is a button or keypress, check the Buttons/Keys logging option too. Do not check or press anything else other than "Ok". It's unlikely to be a spurious button press then, though early versions of the Saitek throttle quadrant were known to create spurious button activity. So much so, in fact, that there's an FSUIPC option to try to remove them (it's the "EliminateTransients" parameter for the [buttons] section, as described in the FSUIPC Advanced user's guide). BTW, why did you remove the initial lines from the Log, which show me the FSUIPC version you are using? Please don't do that. You'll need to tell me the version. Regards Pete
-
FSUIPC4 and Fatal Error Message
Pete Dowson replied to karbil's topic in FSUIPC Support Pete Dowson Modules
It occurs to me that there's actually one last EASY thing for you to try first. Remove all of the .WX type files from your "My Documents\Flight Simulator X Files" folder. In case you might want them (and removing them does not help), put them someplace else for now. This is just in case of the possibility that the crash is due to a corrupted Weather file. That might not matter to most programs, but in order to supply weather information to client applications, FSUIPC asks SimConnect for the weather at regular intervals, soon after you press the Fly Now button. It is one of the few things it will be always doing even in an unregistered installation. Though FSUIPC does check all the data it gets from SimConnect (the latter supplies weather data in a METAR report style), it seems SimConnect expects the binary data in the WX files to be properly consistent, and would crash in its efforts to formulate the METAR string if there's even a minor corruption. The SimConnect log might show us this if you could actually get one, but if not, try removing the .WX type files. Regards Pete -
FSUIPC4 and Fatal Error Message
Pete Dowson replied to karbil's topic in FSUIPC Support Pete Dowson Modules
Surely it was very clear in the FSX Help Announcement text? It provides you with most of the file -- you only have to put the path in for the log file -- and it tells you exactly where to save it! I surely shouldn't need to repeat it here? Look here is what it said. Perhaps you can read it better here than there for some reason? Do you see where it clearly tells you where to save it? I have highlighted it for you. Let's see: SimConnect]missing [ before the S level=Verboseokay console=Nookay file=\Modules\SimConnect%01u.Log ... No!!!!! I don't think your FSX path starts with " file_max_index=9okay Wrong! How can you not read anything I write? Look, it says clearly: "save this file as Simconnect.ini" Oh dear! :-( You seem not to have bothered to read much at all. :-( It tells you that clearly too, look: Look, I am very sorry, but i really do not have the patience to answer any more of these sorts of questions, questions which have all the answers already in the place to which you were referred. It isn't as if it was a lot to read, but you've evidently read hardly any of it. What is the point of me trying to help? No idea. I don't have enough information to tell. Something is wrong with your system, something is wrong with his. Yours is evidently more wrong than his. Anyway, if you are going to have such difficulty just reading and following a few simple lines i think we should draw a line under tihs and call it a day. I recommend you either forget FSUIPC and hope you never need it and that nothing else is badly affected, or do a complete uninstall, delete all three WinSXS SimConnect folders, and start again from scratch. It's probably going to come to that in any case. Regards Pete -
No. There's no graphics support in any of my programs. you need the panels SDK. Regards Pete
-
Sorry, I've never heard of it. What do you want to do? FSUIPC supports Lua plug-ins, which are really powerful -- I added socket support recently, for networking and internet access from a plug-in. Regards Pete
-
I use FSX and FSUIPC4 on Windows 7. There is nothing different in FSUIPC whether on XP, Vista or Win7. Neither of those will be any different if you use the same FSUIPC4.INI file as you had before. It sounds like you let FSX install into its default place, in "Program Files". I think that's a big mistake with Vista or Win7, as every folder in Program Files is write-protected against normal user access. You need elevated Administrator privileges to access it. Installers have these privileges automatically, but other programs only get them by selecting "Run As Administrator" from their right-click menus. Just being the administrator isn't enough. The extra FSUIPC menu entries are enabled by checking the appropriate FSUIPC options. If the profile system isn't working too, it is sounding like some or all of your FSUIPC4.INI [General] section parameters have defaulted. The profile systems is enabled/disabled by one parameter in the [general] section. And of course it also needs the Profiles listed as well. Seems to me you have a corrupted INI file. Try copying the original back. Changes in joystick assignments would have been best dealt with by using the facilities provided in FSUIPC for this -- assigning letters to each device instead of using their system-assigned numbers. Then the changes you need to do are either eliminated completely, or reduced to minor adjustments in the [joynames] section. Not sure why you'd want to throw all your presumably good settings away. I repeat, there is absolutely no difference in how these things work in XP, vista or win7. The code is not affected in any way, not in the slightest. Your problems all seem to emanate from changes in the INI file. Regards Pete
-
windows 7 fs wideclient help
Pete Dowson replied to fredfox's topic in FSUIPC Support Pete Dowson Modules
Probably, before, you had both FS and the client PCs on the same WorkGroup. That way the Broadcasting from WideServer is seen by the Client and it then knows automatically what the Server name and Protocol is. The client would certainly never have used parameters in an INI outside the [Config] section -- Windows won't even allow it to read them. Vista and Windows 7 have a different default WorkGroup name to XP. You can go back to the same automatic system you had before simply by changing the name to match the one in the other PC. I always use the workgroup name "PETES" for instance, on all my PCs. You can find the place to change it in your Computer properties, in the same area that you set the PC name. Regards Pete