
MarkN
Members-
Posts
14 -
Joined
-
Last visited
Profile Information
-
Gender
Male
-
Location
Canada
MarkN's Achievements
Newbie (1/14)
0
Reputation
-
Pete, I've got it sorted now. I thought I already had the '.' key assigned to Brakes in FSUIPC but that was not so. The key '.' now causes the Parking Brakes to come off and, if held down, the word 'Brakes' appears momentarily and then reappears and stays on until Key '.' is released. It didn't stay on before. The CH '0' button now releases the Parking Brakes and holds 'Brakes' on until released. I was initially concerned that Rob Barendregt's 'Ground handling Gauge' may have been interfering with the brakes. Kind regards, Mark
-
Hi again Peter, Problem with brakes in FSX. Parking Brakes: 'Ctrl+.' works OK, both to apply and release. But pressing '.' does not release Parking Brakes. Brakes: Pressing '.' does nothing - no braking and no on screen-message. Pressing Button 0 in CH Yoke releases Parking Brakes but brakes do not stay on , i.e. action of Button 0 is only momentary, not continuous. Pedal Brakes intermittently fail to act. What should I change in FSUIPC? Regards, Mark
-
Hello Peter, <Grovel Mode: ON> I must apologise for posting my query on the wrong forum - I was at my wits' end with the problem and rushed for time. Yes, of course, 'Autopilot On' will only turn it On & not Off - but those were the only 'Autopilot' commands I could find under 'Control sent when button pressed'. I didn't think to look under 'Ap', assuming that 'Autopilot On' & 'Autopilot Off' were the only autopilot controls available. ( I also now assume that controls beginning with 'AP' (as opposed to 'Ap') refer to AirPorts. Is this correct? <Grovel Mode: OFF> However, Peter, I must congratulate you on an amazing piece of programming in the shape of FSUIPC. But please remember that not all of your satisfied customers are as programming-savvy as your good self! I have just turned 80, and therefore my total cerebral agility is not what it used to be (if it ever was...). Thanks for your help! Kind regards, Mark
-
Hi, I've just been using FSUIPC4 to set up FSX for my CH FlightSim Yoke and Saitek Pro Flight Rudder Pedals. Everything worked as advertised with one exception: I cannot find a way of setting the autopilot to toggle on/off using Button 1 on the CH Yoke. I can toggle the A/P with the 'Z' key or the 'AP' button on the instrument panel but not with the CH Yoke. In FSUIPC, I select 'Buttons + Switches', press the 'Btn# 1' and click on 'Select for FS Control', then choose 'Autopilot On' from the 'Control sent when button pressed' dialogue. I've even tried various combinations of 'Control to repeat when held' and 'Control sent when button released' and tried inserting 'C1005' in 'Parameter' - but to no avail... Button 1 will only turn the A/P On, not Off. I've searched through the User Guide and the Advanced Users PDFs but cannot find the answer. I've even tried editing FSUIPC.INI with, again, no success. Any clues would be welcome! Thanks, Mark
-
Hi Pete, That did it! I deleted the line: UseSimConnect=SP1 //Temporary. And removed the comment: // Orig: Flight And then tried FSX.... WARNING MESSAGE about FSUIPC !! So I renamed FSUIPC4.INI, chose to continue running FSX with FSUIPC and this time it ran. As you expected, FSUIPC made another .INI file, which is 2248 bytes, as opposed to the old one of 1075 bytes. The difference is entirely in the [General] section, which is very much longer. Thanks for all your time spent on this problem! All due to my not knowing that FSUIPC4.INI doesn't allow comments. I'm afraid the finer points of programming are completely lost on me, e.g. "... the TCASid parameter check", so I can only happily take your word for what happens.:rolleyes: Oh, and BTW, thanks for FSUIPC itself. It's quite beyond me how anyone can think of such clever programming! Regards, Mark
-
Hi Pete, First of all, thanks for getting back to me so quickly - and after Midnight, UK time, too.:rolleyes: My time zone is - 8 hrs, so it's afternoon here on the West Coast of Canada. I've just tried to run FSX again - usual error messages - and here is the latest iteration of SimConnect0.log:- 0.00000 SimConnect version 10.0.61259.0 0.03463 Server: Scope=local, Protocol=Pipe, Name=\\.\pipe\Microsoft Flight Simulator\SimConnect, MaxClients=64 0.06514 Server: Scope=local, Protocol=IPv6, Address=::1, Port=55027, MaxClients=64 0.07702 Server: Scope=local, Protocol=IPv4, Address=127.0.0.1, Port=55028, MaxClients=64 8.44410 Panels data export found and set to 20B319D8 - as you can see, it's similar to the previous one, viz. no mention of FSUIPC. Here is a list of all the Lua files I can find. None is in FSX\MODULES; they are all in a folder under FSX\MODULES\, called FSUIPC Documents:- FSUIPC Lua Library.pdf FSUIPC Lua Plug-Ins.pdf Lua License.pdf Lua Plugins for VRInsight Devices.pdf Example LUA plugins.zip I have not UnZippd 'Example LUA plugins.zip' - should I have done? Here is my FSUIPC.INI file, dated 29 Aug 2011, 5:57:31 PM:- [General] Console=No UpdatedByVersion=4726 History=DT620LW6Q4S2UF827NG1D TCASid=Type+ // Orig: Flight TCASrange=40 AxisCalibration=No DirectAxesToCalibs=No ShowMultilineWindow=Yes SuppressSingleline=No SuppressMultilineFS=No AxisIntercepts=No DontResetAxes=No GetNearestAirports=No WeatherReadFactor=2 WeatherRewriteSeconds=1 CustomWeatherModify=No SimConnectStallTime=1 LuaRerunDelay=66 UseSimConnect=SP1 //Temporary [JoyNames] AutoAssignLetters=No 0=CH FLIGHT SIM YOKE USB 0.GUID={C0234100-2EAD-11DF-8005-444553540000} 1=Saitek Pro Flight Rudder Pedals 1.GUID={D5FEA040-4A78-11E0-8001-444553540000} [WideServer] WideFSenabled=Yes [sounds] Path=H:\Flying\FSX\Sound\ Device1=Primary Sound Driver Device2=Speakers (High Definition Audio Device) Device3=Digital Audio (S/PDIF) (High Definition Audio Device) Device4=Digital Audio (S/PDIF) (High Definition Audio Device) [buttons] ButtonRepeat=20,10 [MacroFiles] 1=747 OHD 2=APchart [AutoSave] AutoSaveEnabled=No Next=1 Interval=60 Files=10 SaveOnGround=No [GPSout] GPSoutEnabled=No [GPSout2] GPSoutEnabled=No I shall now get FSUIPC v. 4.727 and copy it over v. 4.726 and see what happens when I try to run FSX again. Same 'Fatal Error'. Here's the relevant Windows Error Log:- !. General:- Faulting application name: fsx.exe, version: 10.0.61637.0, time stamp: 0x46fadb14 Faulting module name: FSUIPC4.dll, version: 4.7.2.7, time stamp: 0x4e5ae1f9 Exception code: 0xc0000005 Fault offset: 0x0003d4d8 Faulting process id: 0x1e04 Faulting application start time: 0x01cc66b8f1e46bf5 Faulting application path: H:\Flying\FSX\fsx.exe Faulting module path: H:\Flying\FSX\Modules\FSUIPC4.dll Report Id: 7802c6dd-d2ac-11e0-a085-90e6ba2ec4a5 2. Details (XML View):- - <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> - <System> <Provider Name="Application Error" /> <EventID Qualifiers="0">1000</EventID> <Level>2</Level> <Task>100</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2011-08-30T02:05:02.000000000Z" /> <EventRecordID>49449</EventRecordID> <Channel>Application</Channel> <Computer>marksnemesis</Computer> <Security /> </System> - <EventData> <Data>fsx.exe</Data> <Data>10.0.61637.0</Data> <Data>46fadb14</Data> <Data>FSUIPC4.dll</Data> <Data>4.7.2.7</Data> <Data>4e5ae1f9</Data> <Data>c0000005</Data> <Data>0003d4d8</Data> <Data>1e04</Data> <Data>01cc66b8f1e46bf5</Data> <Data>H:\Flying\FSX\fsx.exe</Data> <Data>H:\Flying\FSX\Modules\FSUIPC4.dll</Data> <Data>7802c6dd-d2ac-11e0-a085-90e6ba2ec4a5</Data> </EventData> </Event> Regards, Mark
-
Hi Pete, I just went to "FSX fails to run after FSUIPC4 first installed". and tried renaming DLL.XML, re-running the FSUIPC installer (which told me it did not overwrite the newer version of FSUIPC.DLL) and then rerunning FSX. But I still get the error. I tried rerunning FSX a couple of more times, as you suggested, but the error kept repeating. Then I did a 'Repair' of FSX Acceleration from the original disk, in case SimConnect was corrupted - as you mentioned in "FSX Fails to Run after FSUIPC First Installed". This did not solve the problem. So I have now created a SIMCONNECT.INI and tried to run FSX again. It has produced SimConnect0.Log in FSX\MODULES, as expected.Here it is:- 0.00000 SimConnect version 10.0.61259.0 0.02661 Server: Scope=local, Protocol=Pipe, Name=\\.\pipe\Microsoft Flight Simulator\SimConnect, MaxClients=64 0.03813 Server: Scope=local, Protocol=IPv6, Address=::1, Port=50475, MaxClients=64 0.04613 Server: Scope=local, Protocol=IPv4, Address=127.0.0.1, Port=50476, MaxClients=64 -and here is DLL.XML (the original version before re-running the FSUIPC installer):- <?xml version="1.0" encoding="Windows-1252"?> <SimBase.Document Type="Launch" version="1,0"> <Descr>Launch</Descr> <Filename>dll.xml</Filename> <Disabled>False</Disabled> <Launch.ManualLoad>False</Launch.ManualLoad> <Launch.Addon> <Name>Object Placement Tool</Name> <Disabled>True</Disabled> <ManualLoad>False</ManualLoad> <Path>..\Microsoft Flight Simulator X SDK\SDK\Mission Creation Kit\object_placement.dll</Path> </Launch.Addon> <Launch.Addon> <Name>Traffic Toolbox</Name> <Disabled>True</Disabled> <ManualLoad>False</ManualLoad> <Path>..\Microsoft Flight Simulator X SDK\SDK\Environment Kit\Traffic Toolbox SDK\traffictoolbox.dll</Path> </Launch.Addon> <Launch.Addon> <Name>Visual Effects Tool</Name> <Disabled>True</Disabled> <ManualLoad>False</ManualLoad> <Path>..\Microsoft Flight Simulator X SDK\SDK\Environment Kit\Special Effects SDK\visualfxtool.dll</Path> </Launch.Addon> <Launch.Addon> <Name>FSUIPC 4</Name> <Disabled>False</Disabled> <Path>Modules\FSUIPC4.dll</Path> </Launch.Addon> </SimBase.Document> - and the Application Error in its entirety from Windows Logs:- Faulting application name: fsx.exe, version: 10.0.61637.0, time stamp: 0x46fadb14 Faulting module name: FSUIPC4.dll, version: 4.7.2.6, time stamp: 0x4e4b0613 Exception code: 0xc0000005 Fault offset: 0x0003d528 Faulting process id: 0x1d30 Faulting application start time: 0x01cc668d59ca6db8 Faulting application path: H:\Flying\FSX\fsx.exe Faulting module path: H:\Flying\FSX\Modules\FSUIPC4.dll Report Id: 27eb1e23-d282-11e0-a085-90e6ba2ec4a5 Finally (!), I inserted the line UseSimConnect=SP1 into FSUIPC.INI - but, again, no success. Hope the above gives you some clues... Regards, Mark
-
Hi Pete, Hope you had a good holiday! There is a FSUIPC4.LOG file in FSX\MODULES. It is dated: 28 Aug 2011, 11:49:26 PM, which is the last time I attempted to run FSX. Here is the file:- ********* FSUIPC4, Version 4.726 by Pete Dowson ********* Reading options from "H:\Flying\FSX\Modules\FSUIPC4.ini" Trying to connect to SimConnect Acc/SP2 Oct07 ... User Name="Mark Nixon" User Addr="maenixon@shaw.ca" FSUIPC4 Key is provided WIDEFS7 not user registered, or expired Running inside FSX on Windows 7 (using SimConnect Acc/SP2 Oct07) Module base=61000000 Wind smoothing fix is fully installed DebugStatus=15 1669 System time = 28/08/2011 23:48:49 1669 FLT path = "C:\Users\Dr Mark A. E. Nixon\Documents\Flight Simulator X Files\" 1669 FS path = "H:\Flying\FSX\" Hope this helps with the diagnosis. Regards, Mark
-
Hi Ian, OK. But thanks for all your suggestions! I'll wait for Pete's return from his hols - when is he expected back? Mark
-
Hi Ian, The two downloads I have are:- FSUIPC4.ZIP, containing 'FSUIPC4.DLL' dated 15 April 2011and 'Install FSUIPC4.EXE' dated 25 April 2011, etc. FSUIPC4726.ZIP, containing only 'FSUIPC4.DLL' dated 17 Aug 2011. I first deleted the copy of FSUIPC.DLL from FSX\Modules and then set 'Install FSUIPC4.EXE' to 'Run As Administrator'. This installed V.4.3, 397,392 bytes in FSX\Modules. Loading FSX produced the usual complaint and it developed a Fatal Error I then copied across v. 4.726 to FSX\Modules and had the same result. Unless there's an installer for v. 4.726 that I can configure to run as Administrator, I cannot see what else I can do. Mark
-
Hi Ian, I didn't see any option for 'Run as Administrator" when installing FSUIPC. Have just read through "Installing and Registering FSUIPC4.pdf" and cannot find that option mentioned anywhere in it. Nor is it available under Properties. My copy of FSX is installed in H:\Flying\FSX, i.e. outside the Program Files folder. It is version 10.0.61637.0 ('Gold Edition' with 'Acceleration') and the OS is Win 7 Professional. In fact I did a recent reinstall of FSX about 10 days ago due to recurrent problems causing CTDs. It is only since then that FSX has shown the message about FSUIPC: "Flight Simulator has detected a problem with a third-party program (add-on): Name: FSUIPC4.DLL: FS new universal IPC interface Version: 4.726. Company: Peter L. Dowson. File: Modules\FSUIPC4.dll. Etc., etc..." Allowing it to run FSUIPC, against its recommendation, causes an immediate CTD. Mark
-
Hi Ian, Yes, I found that download for v.4.726 and installed it but, as you say, it did not resolve my problem. Any other suggestions that I might try? Are there any parameters in FSX.CFG that need changing? Mark
-
Hi, I am getting CTDs (Crashes to Desktop) in FSX if I have FSUIPC v. 4.70b installed in FSX\Modules. If I remove it and then reinstall it, FSX complains saying that it has a problem with this file and do I want to run it. Choosing 'Yes' results in a CTD shortly. thereafter. I have tried downloading a fresh copy of FSUIPC but the problem remains. The problem has been going on for a few days but I am only now getting the message about FSUIPC. Any ideas what's wrong? Mark