Pete Dowson

The file you pasted was most certainly NOT the FSX.CFG file -- it is some sort of list of font and window definitions. I've no idea what file it is. You most certainly would not put any "high mem fix" parameter into it. You are evidently only reading part of what I'm writing! I actually said FSX.CFG only needs to be located because the DLL.XML file, needed to get FSUIPC loaded, is in the same folder. The file is not used by FSUIPC or its installer, it is only the proof that this is the correct folder for the DLL.XML file! I do not need or want to see any FSX.CFG file -- as I also said in my previous message: I also pointed out, and you seem to have ignored that message, that the installation was okay, there was no failure to find the FSX.CFG file as you stated in your original post. The log you so laboriously typed out actually told you it was found okay! The only question remaining for you to answer is the one I posed before, i.e.what exactly do you mean by this: Quote ?? Pete

Sorry, I've no idea what you are talking about. why are you interested in CFG files? What are you trying to do? And I have no idea what that stuff was you just posted. What relevance does it have to anything? It isn't an FSX.CFG file, and there's no point in showing me an FSX.CFG file -- it is nothing to do with FSUIPC. Pete

All you had to do was view the file in Notepad, select all the text and copy and paste into your message. That's what everyone else does! There's no problem. Don't try uploading the file, I never suggested that! As you must have noticed, contrary to your original report, FSX.CFG was found, and the DLL.XML updated okay: So the installation was okay. Which begs the question, what exactly do you mean by this: ?? Pete

Okay, then you'd have seen the way assignments are done and where they are shown. Below the numbers, on the left, 4 boxes each with a drop-down capability with the many things they can be assigned to. FSUIPC most certainly does NOT make assignments by itself, and nor would FS make changes to FSUIPC files. The most likely thing you've had happen is that FS has made automatic assignments itself because either you have disconnected and reconnected the device, or FS thinks you have for some reason of its own. I already explained this as a possibility if you look back. If you have the same lever assigned in both FSUIPC and FS then obviously there will be confising conflicts of the type you've described. Well, as I said, there's absolutely no way FSUIPC makes assignments of its own volition. I suggest you edit the INI file and delete all [Axes...] , [JoystickCalibration ...], [buttons ...] and [Keys ...] sections, so removing all assignments. Do this before loading FS. Pete

Both WideServer and WideClient have always been free to download and install. You have to purchase a key to unlock the Server. All that happened in FSUIPC4 was that the WideServer code was built into FSUIPC instead of being a separate DLL. This made it more efficient, a step made necessary by the heavier load placed on PCs by FSX. Yes. Pete

It isn't the numbers that matter, it is what you have assigned below -- you can have up to four different assignments and they are displayed below, on the left. The User Guide dfoes contain pictures you know. They may help -- surely worth a look at the supplied documentation occasionally, don't you think? All that does is clears the FSUIPC assignment. If you don't want to use FSUIPC that's fine. But why on Earth did you bother to make the assignments in the first place? FS will automatically make axis assignments if you aren't careful. It does this if you unplug a device then plug it back in, and it seems to do it at other times for reasons unknown. As I said earlier, you need to check that controllers are disabled in FS if you want to assign in FSUIPC. If you don't want to use FSUIPC, just delete the INI file from the FS Modules folder. Then you won't have any settings at all. Pete

FSX.CFG only needs to be located because the DLL.XML file, needed to get FSUIPC loaded, is in the same folder. You haven't shown me the Install log file, which is needed for me to help properly, but I suspect you've not installed FSX properly, or you have moved it or restored the registry since. Please go to yout FSX Modules folder, open the Install log, and cut and paste the whole thing into a message here. Pete

All of your crashes are in WEATHER.DLL. It is only not happening when FSUIPC isn't running because then FSUIPC isn't asking SimConnect for the weather data regularly. I suspect your problem is arising because of corrupted weather files. Try removing all .WX files from your Flight Simulator X Files folder in your Documents folder. You may also have a corrupt wxstationlist.bin file. That's in the same folder as your FSX.CFG file. Try deleting it so that FSX makes a new one. I've no idea why it only happens in full screen mode. The mode is completely irrelevant to both FSUIPC and WEATHER.DLL, so that seems more likely to be a video driver problem. Oh, and please install FSUIPC 4.928. I can't support earlier versions. Pete

Sorry, there is really no way I can support old versions, and not Windows 2000 either. The earliest operating system supported is XP. If you've been using FSUIPC successfully in any case, why are you needing to re-enter your registration? Pete

The #SIMC logging isn't needed now. Please remove the "LogExtras" line from the FSUIPC4.INI file, or, better, chage it to LogExtras=x8001, This complete flight session lasted only 55 seconds including loading time, with a "ready to fly" time of only 2 seconds, and it terminated normally. What is it supposed to show, please? Where is "the log file of when everything goes wrong"? I'm afraid I don't really understand this: What do you change in the FLT file? Or do you mean changing things in the start-up menu, and if so what -- is it to a specific aircraft? Maybe there is a corrupt or buggy aircraft being loaded which does the damage? Have you checked the Windows event viewer for the log entries detailing FSX crashes? Pete

Sorry, no. If FSUIPC can't get the DirectInput device connected, it can't assign its axes or buttons. I don't know what could be wrong, but it sounds like a corrupted Registry or Windows component. Pete

It sounds exactly like dual assignments -- try disabling controllers in FS. If it then works okay, you have the same axes assigned in both FS and in FSUIPC, to different actions. If it doesn't help, then either you have some Saitek software making assifgnemtns as well as FSUIPC, or you have dual assignments in FSUIPC -- but you should be able to see that latter case immediately by simply going to the Axes tab in FSUIPC and moving the levers. Pete

I've added the request, for controls to turn mouse move and mouse look on and off by key/button assignment, to my list for FSUIPC4 (only). Look out for an update in due course. Pete

I've moved your support question to the Support Forum so it can be handled. Please do post here -- the User Contributions subforum is for helpful additions by users to be retained for folks to find easily. FSUIPC exposes all of the controls which FS provides. If FS does not saupport something there will not be a control for it. If you are using an add-on which simulates such things then I assume that add-on must provide some way of controlling it, so you'd need to look there. That said, there are 4 alternator controls, Toggle alternator1 to Toggle alternator4 as well as the Toggle master battery alternator control. There is only one battery provided by FS, however. Pete

Just had time to do a quick test. I get these results: f5.csv: CYFC,0,0,"Fredericton" CYFC,1,127.55,"CYFC" CYFC,5,121.70,"FREDERICTON" CYFC,6,119.00,"FREDERICTON" CYFC,10,124.30,"MONCTON" CYFC,11,126.70,"HALIFAX" f4.csv: CYFC,Fredericton,127.55,0,121.70,119.00,0,0,0,0 I can only think that something is wrong with your SCENERY.CFG file. Yet I still cannot understand how F4 and F5 can differ so much -- they are both built at the same time with the same data, which is scanned only once. I'm using MakeRunways version 4.673. You didn't mention which version you were using. Note that the SCENERY.CFG file is located in your windows "ProgramData" settings -- MakeRwys only uses a SCENERY.CFG file in the FS folder if it cannot find the one in the correct place. Just for a cross-check, the entry in Runways.txt is: Airport CYFC :N45:52:07.9966 W066:32:14.0004 68ft Country Name="Canada" State Name="New Brunswick" City Name="Fredericton" Airport Name="Fredericton" in file: TestScenery\scenery\Fredericton Airport CYFC.BGL Start 15 : N45:52:28.2430 W066:32:25.3250 68ft Hdg: 130.3T, Length 5994ft Computed start 15 : Lat 45.874691 Long -66.540682 Start 33 : N45:51:51.2163 W066:31:22.7336 68ft Hdg: 310.3T, Length 5994ft Computed start 33 : Lat 45.864056 Long -66.522673 Hdg: 130.300 true (MagVar -19.000), Asphalt, 5994 x 150 ft *** List of ILSs *** *** Runway *** CYFC0150 Lat 45.874691 Long -66.540680 Alt 68 Hdg 149 Len 5994 Wid 150 *** Runway *** CYFC0330 Lat 45.864056 Long -66.522675 Alt 68 Hdg 329 Len 5994 Wid 150 Start 9 : N45:51:47.2318 W066:33:06.5752 68ft Hdg: 69.9T, Length 8000ft Computed start 9 : Lat 45.862995 Long -66.552338 Start 27 : N45:52:13.5360 W066:31:23.7427 68ft Hdg: 249.9T, Length 8000ft Computed start 27 : Lat 45.870548 Long -66.522751 Hdg: 69.860 true (MagVar -19.000), Asphalt, 8000 x 200 ft Primary ILS ID = IDC *** List of ILSs *** *** Runway *** CYFC0090 Lat 45.862995 Long -66.552338 Alt 68 Hdg 89 Len 8000 Wid 200 ILS 111.30, Flags: GS DME BC *** Runway *** CYFC0270 Lat 45.870548 Long -66.522751 Alt 68 Hdg 269 Len 8000 Wid 200 COM: Type=11 (FSS), Freq=126.70, Name="HALIFAX" COM: Type=1 (ATIS), Freq=127.55, Name="CYFC" COM: Type=5 (GROUND), Freq=121.70, Name="FREDERICTON" COM: Type=6 (TOWER), Freq=119.00, Name="FREDERICTON" COM: Type=10 (CENTRE), Freq=124.30, Name="MONCTON" Taxipoint #0, type 1 (normal): N45:52:13.9895 W066:31:21.9983 -- Forward Taxipoint #1, type 1 (normal): N45:52:07.5755 W066:31:46.9990 -- Forward Taxipoint #2, type 1 (normal): N45:52:06.9924 W066:31:49.3744 -- Forward Taxipoint #3, type 1 (normal): N45:51:46.7783 W066:33:08.3200 -- Forward Taxipoint #4, type 1 (normal): N45:51:50.6008 W066:31:21.6715 -- Forward Taxipoint #5, type 1 (normal): N45:52:13.5684 W066:32:00.5092 -- Forward Taxipoint #6, type 1 (normal): N45:52:19.2374 W066:32:10.1733 -- Forward Taxipoint #7, type 1 (normal): N45:52:27.4008 W066:32:24.0151 -- Forward Taxipoint #8, type 1 (normal): N45:52:28.8585 W066:32:26.3872 -- Forward Taxipoint #9, type 1 (normal): N45:52:16.0304 W066:31:45.1080 -- Forward Taxipoint #10, type 1 (normal): N45:52:16.8402 W066:31:46.4873 -- Forward Taxipoint #11, type 1 (normal): N45:52:18.0064 W066:31:48.4652 -- Forward Taxipoint #12, type 1 (normal): N45:52:18.8163 W066:31:49.8780 -- Forward Taxipoint #13, type 1 (normal): N45:52:19.5938 W066:31:51.2075 -- Forward Taxipoint #14, type 1 (normal): N45:52:20.4684 W066:31:52.6526 -- Forward Taxipoint #15, type 2 (Hold Short): N45:52:09.6811 W066:31:46.5322 -- Reverse Taxipoint #16, type 2 (Hold Short): N45:52:15.0262 W066:31:58.8614 -- Forward Taxipoint #17, type 2 (Hold Short): N45:52:29.1177 W066:32:23.1814 -- Reverse Taxipoint #18, type 1 (normal): N45:52:39.2895 W066:32:18.0444 -- Forward Taxipoint #19, type 1 (normal): N45:52:24.9388 W066:32:00.2841 -- Forward Taxipoint #20, type 1 (normal): N45:52:27.6923 W066:31:56.9785 -- Forward Taxipoint #21, type 1 (normal): N45:52:24.4205 W066:31:51.0898 -- Forward Taxipoint #22, type 1 (normal): N45:52:22.1529 W066:31:50.7537 -- Forward Taxipoint #23, type 1 (normal): N45:52:28.5346 W066:31:59.4199 -- Forward Taxipoint #24, type 2 (Hold Short): N45:52:20.5656 W066:32:08.6815 -- Forward Parking Park1 [#G0]: N45:52:21.8290 W066:31:48.6584 Type 3 (GA Ramp Medium), Size 14.0m, Hdg 40.3T Parking Park2 [#G1]: N45:52:21.0515 W066:31:47.2341 Type 3 (GA Ramp Medium), Size 14.0m, Hdg 40.3T Parking Park3 [#G2]: N45:52:20.2740 W066:31:45.8418 Type 2 (GA Ramp Small), Size 10.0m, Hdg 40.3T Parking Park4 [#G3]: N45:52:19.0107 W066:31:44.0959 Type 12 (?), Size 16.0m, Hdg 39.8T Taxipath (Runway 9): Type 2 (Runway), Start#=0, End#=1, Wid=45.72m Taxipath (Runway 9): Type 2 (Runway), Start#=1, End#=2, Wid=60.96m Taxipath (Runway 9): Type 2 (Runway), Start#=2, End#=3, Wid=60.96m Taxipath (Runway 15): Type 2 (Runway), Start#=4, End#=2, Wid=45.72m Taxipath (Runway 15): Type 2 (Runway), Start#=2, End#=5, Wid=45.72m Taxipath (Runway 15): Type 2 (Runway), Start#=5, End#=6, Wid=45.72m Taxipath (Runway 15): Type 2 (Runway), Start#=6, End#=7, Wid=45.72m Taxipath (Runway 15): Type 2 (Runway), Start#=7, End#=8, Wid=45.72m Taxipath (Name #0): Type 4 (Path), Start#=9, End#=10, Wid=27.43m Taxipath (Name #0): Type 4 (Path), Start#=10, End#=11, Wid=27.43m Taxipath (Name #0): Type 4 (Path), Start#=11, End#=12, Wid=27.43m Taxipath (Name #0): Type 4 (Path), Start#=12, End#=13, Wid=27.43m Taxipath (Name #0): Type 4 (Path), Start#=13, End#=14, Wid=27.43m Taxipath (Name #0): Type 3 (Parking), Start#=13, End#=G0, Wid=30.48m Taxipath (Name #0): Type 3 (Parking), Start#=12, End#=G1, Wid=30.48m Taxipath (Name #0): Type 3 (Parking), Start#=11, End#=G2, Wid=30.48m Taxipath (Name #1): Type 1 (Taxi), Start#=1, End#=15, Wid=27.43m Taxipath (Name #1): Type 1 (Taxi), Start#=15, End#=9, Wid=27.43m Taxipath (Name #2): Type 1 (Taxi), Start#=14, End#=16, Wid=27.43m Taxipath (Name #2): Type 1 (Taxi), Start#=16, End#=5, Wid=27.43m Taxipath (Name #3): Type 1 (Taxi), Start#=7, End#=17, Wid=21.34m Taxipath (Name #3): Type 1 (Taxi), Start#=17, End#=18, Wid=21.34m Taxipath (Name #4): Type 1 (Taxi), Start#=14, End#=19, Wid=21.34m Taxipath (Name #4): Type 1 (Taxi), Start#=19, End#=20, Wid=21.34m Taxipath (Name #0): Type 1 (Taxi), Start#=21, End#=22, Wid=21.34m Taxipath (Name #0): Type 1 (Taxi), Start#=22, End#=14, Wid=21.34m Taxipath (Name #5): Type 1 (Taxi), Start#=23, End#=24, Wid=21.34m Taxipath (Name #5): Type 1 (Taxi), Start#=24, End#=6, Wid=21.34m Taxipath (Name #0): Type 3 (Parking), Start#=10, End#=G3, Wid=30.48m Taxiname: #0 = Taxiname: #1 = A Taxiname: #2 = B Taxiname: #3 = D Taxiname: #4 = E Taxiname: #5 = C TaxiWay : 9-10-11-12-13-14-22-21 TaxiWay : G0-13 TaxiWay : G1-12 TaxiWay : G2-11 TaxiWay : G3-10 TaxiWay A: 1-15-9 TaxiWay B: 14-16-5 TaxiWay C: 23-24-6 TaxiWay D: 7-17-18 TaxiWay E: 14-19-20 FSM A/P CYFC, lat=45.868889, long=-66.537224, alt=68 Pete

Hmm. Instead of over-using the mouse, why not just assign buttons or a POV hat directly to the same Eyepoint controls which are used by FSUIPC's Mouse Move facility? I'll make a note for a switch facility, but it probably won't be using the mouse. It hets very complicated with the switching between mouse move, mouse look and mouse trim, as it is. Pete

All layers should be listed. 13 doesn't even cover the default FS layers! Are you sure yor editor isn't simply truncating the file -- it will be VERY big, far too big for many editors! Tell me its size. No. Most of my scenery layers are not even on the same drive as FS. The paths are all obtained from the SCENERY.CFG file, and MakeRunways processes it just like FS does. And in any case it wouldn't explain the difference between the f4 and f5 files. I've receieved the BGL and will look at this tomorrow -- I'm out all day today. Pete

I've erased your private key in your first message. NEVER openly publish private keys!!! You were evidently making a mistake originally -- it isn't just the key you must get right, but your name and email too. Pete

It looks like the IP address Windows is providing for your Server is an Internet address -- it checks out as this: 66.152.109.110 Host 66-152-109-110.tvc-ip.com Location US, United States City Albany, NY 12207 Organization Tech Valley Communications ISP Tech Valley Communications AS Number AS13536 Tech Valley Communications Latitude 42°65'68" North Longitude 73°74'69" West This sort of problem can occur in some odd router settings -- see the section in the WidefS Technical guide -- section 10 on page 5 describes it. You could try putting the correct IP address in the INI file, and the Protocol tro be used, as described in the WideFS user guide. FS98MAIN is the classname for all versions of FS (and ESP and P3D) since and including FS98. Pete

You'll need to send me the relevant BGL file (as noted in Runways.txt) for mer to have any chance of understanding this. Email to petedowson@btconnect.com. Pete

Why select the mouse move option if you don't want to use it? Zoom is not changed by mouse move -- mouse move allows you to maove the eyepoint side to side or forward and back, nothing to do with zoom. Pete

More information needed. What program are you running which says "same program or class"? If you mean WideClient, then that means FS is running on that PC. Since WideClient is used INSTEAD of FS on the netwroked PC, you can't run it on a PC also running FS. The whole point of WideFS is to allow FSUIPC applications to be run on connected PCs not running FS. Not heard of this "frooglesim" I'm afraid. Pete

The problem will be that FSUIPC is also being fooled and doesn't know it is P3Dv2, so the hooks are wrong. In any case, that's what I think might be happening. But please paste the LOG file here. Are you renaming P3D as "FSX.EXE", or changing the Version number in its Version Info? The other files FSUIPC4 uses (LOG, INI, KEY) will also use differernt names for a renamed FS EXE, and it gets complicated. But if you are changing the version number then there's no way it is going to work as the hooks are different for P3Dv1. Pete

Version of FS? Version number of FSUIPC? You've not provided enough information I'm afraid. In the currently supported versions there are no known problems with FSUIPC retaining profile details, so I don't really know what you are seeing. The usual reason folks think they need to enter settings and do things is that their devices have gone to sleep -- this is caused by Windows power management being enabled on the USB channels in the PC. You need to go to Device manager and turn that off. What happens when you visit FSUIPC options is that the devices are rescanned and this wakes them up. In the Buttons & Switches and Keys tabs the "specific" tick can be off or on -- when off it shows the generic settings applicable to this Profile, when on it shows the Profile Specific settings. Both can be active at the same time. That isn't true for Axes, for obvious reasons (axes are active al the time, whilst buttons and keys are only active when you use them). Pete

I'm strongly suspecting a Win8.1 bug here. FSUIPC cannot actually manufacture such an error -- "class not registered". FSUIPC doesn't need to register classes itself, that part of the systems job, classifying devices and the like. It seems some incompatibility between Win8.1 and Saitek. Pete