Jump to content
The simFlight Network Forums

lawndartleo

Members
  • Posts

    13
  • Joined

  • Last visited

Everything posted by lawndartleo

  1. Will try next time I can't find it, thanks.
  2. From time to time the interface for FSUIPC will completely disappear, not minimized but gone. The icon is not in system tray or the task bar, I can't alt+tab to it, but the application is still running (background) as evidenced by me relaunching and getting the error message FSPIPC is already running which then makes the interface available, again. Maybe its in how I am interacting with the app.
  3. Apologies for the question if its been answered but my cursory search came up dry. FSUIPC 7 started, FS started, use FSUIPC at some point, go back to sim, FSUIPC disappears (no tray, no task bar), restart FSUIPC.... warning FSUIPC already running. Its not a show stopper because the interface comes back but is there a way to prevent the vanishing act?
  4. Is it fair to say that not making simconnect and FSUIPC work together well would be detrimental to the creation of a flourishing addon ecosystem?
  5. Does Windows7-FSX-FSUIPC enumerate axes the same way every time all the time? Here's the situation. I just started to use FSUIPC for all axis assignments. The radio box in FSX for controllers is unchecked. Everything is through FSUIPC. I have 6 controllers.... CH Yoke, Fighterstick, Combatstick, Pro throttle, Throttle quadrant and Pro pedals (showing as CH Control manager devices 1-6). I assign unique profiles per adddon in FSX. This had been working fine but today I go fly something and the axes are all screwey. Rudders affect stick, stick affects throttle and so on. I check FSUIPC and sure enough, the axes are doing exactly what they say they are doing. Everything got jumbled up. What did I do?
  6. On the bright side, I've learned a few things about ownership and permissions. I don't recall that I went registry hunting. I know that is usually the quickest route to digital damnation. I'll give the disks a spin and hope the installers are there. I have the folders I yanked but something tells me reinstall is the prudent choice of action.
  7. How many instances of simconnect should be in my Winsxs folder? One or three? I may have let somebody lead me down the primrose path of FSX destruction. FSX Deluxe with Acceleration installed if that matters. I'm thinking there are supposed to be three instances, each installed by.... rtm, sp1 and sp2/accel respectively.
  8. Is there a file/config within the structure of FSX or its supporting directories that contains all the button assignments for FSX that can be deleted or edited so that all default joystick axes and joystick buttons are unassigned? I do not want to delete keyboard press assignments, just those things that are setup automagically by FSX that are joystick related. 1.... it takes a good amount of time to go through the UI and delete them one by one 2.... for some reason, landing gear and next view seem to take multiple times to kill off, they just keep coming back (buttons 9 and 10).
  9. Hello, Not long after posting, I ran across the 907 version.... I always get my "up to date" files from http://www.schiratti.com/dowson.html but just learned that page is not necessarily up to date. My first inclination was to look for updates in the link at the top of this page (http://forum.simflight.com/files/) but 907 is not there so it was unknown to me. A little more forum cruising and I found http://forum.simflight.com/topic/66139-updated-modules/ which was what I needed all along. 907 did the trick. Odd that the Nostromo was causing problem as it works just fine. Thanks!
  10. I'm going to assume that this is a preferred thread to post in.... Clean install of FSX and Acceleration. Once FSUIPC 4.0 is installed, it all breaks down. I have used the loader that is mentioned in other threads. Here is all the information I can provide.... FSX, starts (spinner with the ultralight), hangs a few seconds later. This was a "clean" install precipitated by the dreaded trust issue (precipitated by the installation of 4.90) that just would not go away no matter how many times I tried per Peter's instruction. All previous FSX and addons were uninstalled with their uninstallers and the registry cleaned with CCleaner. My paid registration can be confirmed by association with my forum account email. The important line from the fsx.cfg... and this is the first and only change made, fresh cfg. [Trusted] E:\Microsoft Games\Microsoft Flight Simulator X\Modules\FSUIPC4_Loader.dll.klqaahzckecbzzcoubnihncklowttzqzqaizhkhb=1 ********* FSUIPC4, Version 4.90 by Pete Dowson ********* Running inside FSX on Windows 7 Module base=54200000 User Name="<private information>" User Addr="<private information>" FSUIPC4 Key is provided WIDEFS7 not user registered, or expired 827 System time = 06/07/2013 11:27:34 827 FLT path = "C:\Users\Paul\Documents\Flight Simulator X Files\" 858 Trying to connect to SimConnect Acc/SP2 Oct07 ... 873 FS path = "E:\Microsoft Games\Microsoft Flight Simulator X\" Installer for FSUIPC4.DLL version 4.90 Looking in registry for FSX install path: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\10.0 Parameter"SetupPath" ... >>> OK! FOUND FSX! <<< ... Looking in registry for ESP install path: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft ESP\1.0 Parameter"SetupPath" Not there, so looking in: HKEY_CURRENT_USER\ESP Parameter"AppPath" ... NOT found! ... Looking in registry for Prepar3D install path: HKEY_LOCAL_MACHINE\SOFTWARE\LockheedMartin\Prepar3D Parameter"SetupPath" Not there, so looking in: HKEY_CURRENT_USER\Prepar3D Parameter"AppPath" ... NOT found! ... =========================================================== INSTALLATION FOR FSX: SetupPath="E:\Microsoft Games\Microsoft Flight Simulator X\" Checking version of FSX.EXE: ... Version 10.0.61637.0 (Need at least 10.0.60905.0) Checking compatibility with installed SimConnect: Found SimConnect build 60905 (Original) Found SimConnect build 61242 (SP1 May07) Found SimConnect build 61259 (Acc/SP2 Oct07) Checking if there's already a version of FSUIPC4 installed in: E:\Microsoft Games\Microsoft Flight Simulator X\Modules\FSUIPC4.DLL ... No previous valid version found. FSX Modules folder already exists. Okay -- installed FSUIPC4 into "E:\Microsoft Games\Microsoft Flight Simulator X\Modules\FSUIPC4.DLL" Looking for the current user's Application Data path: ... found as "C:\Users\Paul\AppData\Roaming" Now finding \Microsoft\FSX\FSX.CFG for all users, including this one Looking in "C:\Users\All Users\AppData\Roaming" ... No FSX.CFG there Looking in "C:\Users\Default\AppData\Roaming" ... No FSX.CFG there Looking in "C:\Users\Default User\AppData\Roaming" ... No FSX.CFG there Looking in "C:\Users\Paul\AppData\Roaming" Found FSX.CFG in "C:\Users\Paul\AppData\Roaming\Microsoft\FSX\FSX.CFG" Now checking DLL.XML ... ... There is a previous DLL.XML, checking for FSUIPC4 section. No previous FSUIPC4 entry found, so adding it now ... ... FSUIPC4 section of DLL.XML written okay Now checking for a SimConnect.XML file ... ... No SimConnect.XML file found. This is okay. Looking in "C:\Users\Public\AppData\Roaming" ... No FSX.CFG there "Modules\FSUIPC Documents" folder created okay! Now installing additional files into the "Modules\FSUIPC Documents" folder: Installed "FSUIPC4 User Guide.pdf" okay Installed "FSUIPC4 for Advanced Users.pdf" okay Installed "FSUIPC4 History.pdf" okay Installed "List of FSX controls.pdf" okay Installed "FSUIPC Lua Library.pdf" okay Installed "FSUIPC Lua Plug-Ins.pdf" okay Installed "Lua License.pdf" okay Installed "Lua Plugins for VRInsight Devices.pdf" okay Installed "LuaFileSystem.pdf" okay Installed "Example LUA plugins.zip" okay Installed "Offset Mapping for PMDG 737NGX.pdf" okay Installed "FSUIPC4 Offsets Status.pdf" okay =========================================================== All installer tasks completed. Registration for FSUIPC4 was successful! (result code 00) *************** End of Install Log *************** <?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_Loader.dll</Path> </Launch.Addon> </SimBase.Document> Log Name: Application Source: Application Hang Date: 7/6/2013 11:28:42 AM Event ID: 1002 Task Category: (101) Level: Error Keywords: Classic User: N/A Computer: Paul-PC Description: The program fsx.exe version 10.0.61637.0 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Action Center control panel. Process ID: 179c Start Time: 01ce7a65a2588d36 Termination Time: 24 Application Path: E:\Microsoft Games\Microsoft Flight Simulator X\fsx.exe Report Id: 14d5d37a-e659-11e2-af61-50e5495458bd Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Application Hang" /> <EventID Qualifiers="0">1002</EventID> <Level>2</Level> <Task>101</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2013-07-06T16:28:42.000000000Z" /> <EventRecordID>28776</EventRecordID> <Channel>Application</Channel> <Computer>Paul-PC</Computer> <Security /> </System> <EventData> <Data>fsx.exe</Data> <Data>10.0.61637.0</Data> <Data>179c</Data> <Data>01ce7a65a2588d36</Data> <Data>24</Data> <Data>E:\Microsoft Games\Microsoft Flight Simulator X\fsx.exe</Data> <Data>14d5d37a-e659-11e2-af61-50e5495458bd</Data> <Binary>55006E006B006E006F0077006E0000000000</Binary> </EventData> </Event>
  11. Yes, I know how they are supposed to work. To be quite honest, my flight instructor didn't like it when I released the brakes in that manner. He insisted hold the lever, apply pressure to brakes and ease the lock off. When you say set zero, what exactly do you mean? I fiddled with the mins and maxes in the calibration tab and that still didn't have the desired effect. BTW, the solution posted was actually attributed to you on the A2A forum.
  12. BrakeReleaseThreshold=75 Set to 0... can't disengage parking brakes by pressing toe brakes any more but honestly that is not a big deal. Actually, it prevents unwanted PB release.
  13. Greetings, I've done some searching here but found nothing specific to my issue. Here are the details... FSX Acceleration A2A Mustang, only CH Pro Pedals All axis assignments through FSUIPC Toe brakes are assigned and operating properly..... almost. Press left toe brake, left brake Press right toe brake, right brake Press both and they negate each other. I can apply one exclusively but as I apply the other they seem to "sum up" in some weird mathematical equation to equal no toe brakes. I have checked the behavior in many other addons (even other A2A addons) and there is no problem. With the Mustang... frustration. I am even able to visibly see this because the toebrakes are animated on the rudder pedals on the model. When combining left and right toe brakes (straight ahead stop), they depress to full brakes at about half deflection of each pedal then then start to release as the brakes are fully depressed. Pressed individually, they go to the floorboards as they should. Help!
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.